After update to 24.1.7Crowdsec will not start with LAPI disabled

[A.R.]

I run crowdsec in a distributed config and have an issue with crowdsec with LAPI disabled not starting after the update to 24.1.7.

Following can be produced by running

Code Select Expand

sh -x rc.d/crowdsec start

With LAPI enabled:

Code Select Expand

limits -C daemon /usr/sbin/daemon -f -P /var/run/crowdsec_daemon.pid -p /var/run/crowdsec.pid -r -R 10 -t crowdsec -- /usr/local/bin/crowdsec -c /usr/local/etc/crowdsec/config.yaml
With LAPI disabled

Code Select Expand

limits -C daemon /usr/sbin/daemon -no-api -f -P /var/run/crowdsec_daemon.pid -p /var/run/crowdsec.pid -r -R 10 -t crowdsec -- /usr/local/bin/crowdsec -c /usr/local/etc/crowdsec/config.yaml -no-api
daemon: illegal option -- n
usage: daemon [-cfHrS] [-p child_pidfile] [-P supervisor_pidfile]
              [-u user] [-o output_file] [-t title]
              [-l syslog_facility] [-s syslog_priority]
              [-T syslog_tag] [-m output_mask] [-R restart_delay_secs]

Somehow the -no-api parameter also is used for deamon. Looks to be in the construction of _doit in /etc/rc.subr

EDIT: Issue is caused by upstream changes. Tracked here: https://github.com/opnsense/plugins/issues/3985

[REB00T]

Can confirm. It happens to me as well.

[mmetc]

Thanks! Quick fix and PR in

https://github.com/opnsense/plugins/issues/3985#issuecomment-2118451676

[Taunt9930]

Thanks! Quick fix and PR in

https://github.com/opnsense/plugins/issues/3985#issuecomment-2118451676

If I were to pull the trigger on the upgrade now, would I need to fiddle about with the quick-fix or has the plugin already been updated and all should be good?

Thanks.

[Mr_Cus]

Can confirm it's currently still broken in -release (I'm here cleaning up after an update gone wild)

If I were to pull the trigger on the upgrade now, would I need to fiddle about with the quick-fix or has the plugin already been updated and all should be good?

Thanks.