-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.6.0 container fails to start on crowdsec/whiltelist installation #2786
Comments
@bufanda: Thanks for opening an issue, it is currently awaiting triage. In the meantime, you can:
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
Hi there was a patch pushed to the repository today. You can move over to the |
Link to closed issue #2779 |
Interesting you have custom/tainted the |
Just checking the docker start script code, I see the issue and have reported it to the team. Thank you 🦙 we hope to get a fix merged and maybe a subsequent version release by next week depending on scope. |
No Idon't use compose I use ansible to deploy the configuration and yes I had to create my own whitelist to whitelist my own IP as I got constantly block because the Nextcloud Client on my PCs was HTTP probing and that triggered the decision to block me. So whitelisting was my solution for it. I can try to remove the parser from the env variable though, but as you said there is an issue in the startup script I might hold of for the time being on that. Meanwhile I reverted back to Version 1.5.5 on the host. |
Hi, Since the last update using docker i think i facing the same issue: Local agent already registered |
Hi, did you read the comments above how to resolve? |
Hello @LaurenceJJones Thanks for your reply, im using docker-compose with no env variable: version: "3.4" services: crowdsec-traefik-bouncer: networks: |
Hi, I rolled back to 1.5.5 and now everything is working properly |
I had the same problem, after I've updated container today to the Both rollback to the |
We have released a |
What happened?
When I updated from 1.5.5 to 1.6.0 crowdsec failed with follwoing log
What did you expect to happen?
Crowdsec should migrate configuration to new version and start up.
How can we reproduce it (as minimally and precisely as possible)?
Have crowdsec container version 1.5.5 running with parser crowdsec/whitelists running and upgrade to v1.6.0 container
Anything else we need to know?
No response
Crowdsec version
I would post the version but container isn't running so I can't attach to it to print version string.
But it is the latest container (v1.6.0) with hash
OS version
Enabled collections and parsers
Config show
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
The text was updated successfully, but these errors were encountered: