You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting security.syslog=true causes the MISP server to send copious details to the system log via syslog, and not just about security (successful/failed authentication) either, so the setting is a bit misnamed.
The MISP syslog plugin MISP/app/Plugin/SysLog/Lib/SysLog.php sends messages using syslog facility "LOCAL0". Error messages go at priority error, warning messages go at priority warning, but the plugin maps all other actions especially info to syslog priority DEBUG.
On a RHEL7 server the config file /etc/rsyslogd.conf has no rule for facility LOCAL0, at priority debug. As a result the regular MISP messages like "added event" are silently dropped.
I don't know how syslog is configured on Ubuntu.
The text was updated successfully, but these errors were encountered:
Setting
security.syslog=true
causes the MISP server to send copious details to the system log via syslog, and not just about security (successful/failed authentication) either, so the setting is a bit misnamed.The MISP syslog plugin MISP/app/Plugin/SysLog/Lib/SysLog.php sends messages using syslog facility "LOCAL0". Error messages go at priority error, warning messages go at priority warning, but the plugin maps all other actions especially info to syslog priority DEBUG.
On a RHEL7 server the config file /etc/rsyslogd.conf has no rule for facility LOCAL0, at priority debug. As a result the regular MISP messages like "added event" are silently dropped.
I don't know how syslog is configured on Ubuntu.
The text was updated successfully, but these errors were encountered: