[SOLVED] Crowdsec (and munin?) plugins fail with 23.7.4 upgrade ?

[meepmeep]

I upgrade to 23.7.4 this evening.
The reboot took a lot more time, like a service timeout.
After few long minutes it looks like crowdsec plugins isn't correctly start (nothing listening on port, timeout on the cli).

Anyone else getting this behavior?

[wbennett]

Same, except I have been sitting on "Waiting for PIDS: 5 digit number

[meepmeep]

rolled back to 23.7.3, everything is running fine again. I'll open a ticket with crowdsec.

[wirefall]

same here first, but just another restart solved it. Runs smoothly since then.

[meepmeep]

restart of crowdsec plugin only ?

[wbennett]

Just restarting the Crowdsec plugin worked for me.

[meepmeep]

still not working for me with a plugin or even a full reboot.

[mmetc]

still not working for me with a plugin or even a full reboot.

Hi, could you try "service crowdsec_firewall restart" ?
Otherwise I should have a look at the last few lines in /var/log/crowdsec/crowdsec-firewall-bouncer.log

[mmetc]

Hi, I'm the plugin maintainer.

What happens is simply that the bouncer does not wait for the lapi service to be responsive, and is not restarted automatically. Restarting only the bouncer is correct. Restarting both may work or not.

You can try a new version here - https://github.com/crowdsecurity/cs-firewall-bouncer/releases/download/v0.0.28-rc5/crowdsec-firewall-bouncer-0.0.28.r5.pkg

We are releasing it with crowdsec 1.5.3, but it will take a few day to land in the freebsd and opnsense repositories.

I'd be glad if you could confirm that the above version is working for you.

[meepmeep]

I took some time to investigate further, and the problem was way more simple that I thought .. I had no gateway for the DNS, so timeout was quite logical for every url / outbound access.

Changed it under System > Settings > General, and everything is now running smoothly.