Print Page - Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG

Title: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
Post by: TheLatestWire on April 15, 2018, 06:11:36 PM

Hi - There's an angry red error on the console at startup on my OPNSense server. I can't seem to find it in any of the log files or dmesg but I might not be looking in the right places.

The message is:
SC_ERR_MISSING_CONFIG_PARAM 118 No logging compatible with daemon mode selected

I'm not sure it's affecting anything but it's got my attention since it's in red at the console.

Anyone have any insight please?

Thanks.

Title: Re: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
Post by: dcol on April 16, 2018, 02:04:23 AM

Enable syslog in Intrusion detection

Title: Re: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
Post by: franco on April 16, 2018, 03:55:36 PM

Suricata has been know for a couple of overbearing warnings which have no operational impact whatsoever.

FWIW, we'll enable Syslog by default soon because since our early rework in 18.1.x it makes no sense to disable it anymore.

Cheers,
Franco

Title: SOLVED: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
Post by: TheLatestWire on April 17, 2018, 03:32:14 AM

Thanks dcol and Franco. Enabling syslog and rebooting cleared the angry red alert.

OPNsense Forum

Archive => 18.1 Legacy Series => Topic started by: TheLatestWire on April 15, 2018, 06:11:36 PM