#CrowdSec on Opnsense Restart Problems

1 messages · Page 1 of 1 (latest)

hushed cedar
#

Hello Community,

I hope I’m in the right place. I already posted about this issue in the OPNsense forum and was redirected to the CrowdSec .

My issue:
After the latest OPNsense update and reboot, I had to manually access the console and terminate the CrowdSec process using kill -9 (PID). I know other users who are experiencing the same problem.

No special configurations have been made in CrowdSec—only the add-on was installed to make it visible in the dashboard. Interestingly, this issue does not occur on clients where the add-on is not installed.

Additional information:

A regular reboot works without any issues.
The problem only happens after an OPNsense update when the system restarts.
The service hangs while shutting down.
System details:

os-crowdsec: 1.0.8_1
OPNsense: 24.7.12_4-amd64
Does anyone have an idea what might be causing this?

Thanks in advance!

Best regards,

glossy walrusBOT
#
Important Information

Thank you for getting in touch with your support request. To expedite a swift resolution, could you kindly provide the following information? Rest assured, we will respond promptly, and we greatly appreciate your patience. While you wait, please check the links below to see if this issue has been previously addressed. If you have managed to resolve it, please use run the command /resolve or press the green resolve button below.

Log Files

If you possess any log files that you believe could be beneficial, please include them at this time. By default, CrowdSec logs to /var/log/, where you will discover a corresponding log file for each component.

Guide Followed (CrowdSec Official)

If you have diligently followed one of our guides and hit a roadblock, please share the guide with us. This will help us assess if any adjustments are necessary to assist you further.

Screenshots

Please forward any screenshots depicting errors you encounter. Your visuals will provide us with a clear view of the issues you are facing.

© Created By WhyAydan for CrowdSec ❤️ ·
versed tangle
#

Hello, this is the same problem when upgrading from Opnsense Business 24.10.1 to 24.10.2 (based on community 24.7.12)

On this thread https://discourse.crowdsec.net/t/bug-opnsense-24-7-5-crowdsec-1-6-3/2057
The bug seems to be fixed on version 24.7.6 but it still exists today

Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
[58/61] Upgrading pciids from 20241024 to 20241125...
[58/61] Extracting pciids-20241125: ..... done
[59/61] Upgrading crowdsec from 1.6.3_3 to 1.6.4...
[59/61] Extracting crowdsec-1.6.4: .......... done
crowdsec is running as pid 14449.
Stopping crowdsec.
Waiting for PIDS: 14449.
Waiting for PIDS: 92556

CrowdSec
[BUG] OPNSense - 24.7.5 & Crowdsec 1.6.3

Hello, CrowdSec 1.6.3, 1.6.3-1 distributed with OpnSense 24.7.5 (fixed in 24.7.6) introduced a bug in the service stop feature, leading to various issues: Service restart will get stuck (as CrowdSec doesn’t manage to stop) OpnSense and CrowdSec upgrade process will get stuck (when trying to shutdown CrowdSec) Notification plugins can end up ...

hushed cedar
#

Hey Shay, luckily I'm not the only one with this problem... I've had this issue with multiple OPNsense firewalls.
Is there already a workaround or a solution?

Thanks!