Hi,
I’ve been using the CentOS VM image for LibreNMS monitoring.
I started to want to test syslog, so as documented here:
https://docs.librenms.org/Extensions/Syslog/
I first made the changes to /etc/rsyslog.conf:
# Listen for syslog messages on UDP:514
$ModLoad imudp
$UDPServerRun 514
then I created the file:
/etc/rsyslog.d/30-librenms.conf
with contents:
# Feed syslog messages to librenms
$ModLoad omprog
$template librenms,"%fromhost%||%syslogfacility%||%syslogpriority%||%syslogseverity%||%syslogtag%||%$year%-%$month%-%$day% %timereported:8:25%||%msg%||%programname%\n"
*.* action(type="omprog" binary="/opt/librenms/syslog.php" template="librenms")
& stop
When I restarted rsyslog via:
systemctl restart rsyslog
I received:
Job for rsyslog.service failed because the control process exited with error code. See "systemctl status rsyslog.service" and "journalctl -xe" for details.
I tried to find out why but couldn’t, so I removed:
/etc/rsyslog.d/30-librenms.conf
and recommented:
# Listen for syslog messages on UDP:514
#$ModLoad imudp
#$UDPServerRun 514
Restarted rsyslog and still won’t start up.
I rebooted, rsyslog still won’t start up.
I’m baffled, as it’s back to the way it was yet rsyslog refuses to start up.
Any ideas? this is just the CentOS VM image downloaded from the site, yet patched to the latest CentOS 7 packages.
Thanks.
Michael.