Console-connection gets stalled when container is restarted
I've noticed that if I restart the crowdsec-container, I get issues with the connection to the console. It doesn't update anymore and I need to re-enroll.
I've mounted
/var/lib/crowdsec/datato my host and I have no issues with crowdsec in generall surviging restarts of the container. It's just the console that resets and looses the connection to the conolse.
It doesn't tell me that it lost the connection when I run cscli console status but when I log into the console I see it's complaining and that I have no updates in the console where the LAPI has updates.
From what I've read, the path above is the only one of interest to survivie restarts, thus I'm unsure why this happens.4 Replies
Important Information
This post has been marked as resolved. If this is a mistake please press the red button below or type
/unresolve© Created By WhyAydan for CrowdSec ❤️
Could you paste the logs from the container ?
It's probably because
/etc/crowdsec is not persisted, this is where the CAPI credentials are storedThanks for the hint about
/etc/crowdsec , I did not mount the full directory leading to some files being recreated and as you say CAPI-files where affected. Now it survived multiple rules.Resolving Console-connection gets stalled when container is restarted
This has now been resolved. If you think this is a mistake please run
/unresolve