Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
18.1 Legacy Series
»
Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
« previous
next »
Print
Pages: [
1
]
Author
Topic: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118 (Read 4129 times)
TheLatestWire
Jr. Member
Posts: 70
Karma: 6
Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
«
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.
Logged
dcol
Hero Member
Posts: 635
Karma: 51
Re: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
«
Reply #1 on:
April 16, 2018, 02:04:23 am »
Enable syslog in Intrusion detection
Logged
franco
Administrator
Hero Member
Posts: 17570
Karma: 1596
Re: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
«
Reply #2 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
Logged
TheLatestWire
Jr. Member
Posts: 70
Karma: 6
SOLVED: Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118
«
Reply #3 on:
April 17, 2018, 03:32:14 am »
Thanks dcol and Franco. Enabling syslog and rebooting cleared the angry red alert.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
18.1 Legacy Series
»
Angry Error on Console at Startup - SC_ERR_MISSING_CONFIG_PARAM 118