Easy to reproduce. Here's syslog-ng on Ubuntu 12.04:
monit/conf.d/syslog-ng:
check process syslog-ng with pidfile /var/run/syslog-ng.pid
start program = "/etc/init.d/syslog-ng start"
stop program = "/etc/init.d/syslog-ng stop"
make sure monit status is running
echo > /var/run/syslog-ng.pid
Wait for monit to notice, then logs fill with:
monit: Error reading pid from file '/var/run/syslog-ng.pid'
Not the best example because syslog-ng will notice the empty pid file and start a new instance so this will not fill the logs entirely but any application that does not actively check the state of its PID file will.
Easy to reproduce. Here's syslog-ng on Ubuntu 12.04:
monit/conf. d/syslog- ng: syslog- ng.pid d/syslog- ng start" d/syslog- ng stop"
check process syslog-ng with pidfile /var/run/
start program = "/etc/init.
stop program = "/etc/init.
make sure monit status is running
echo > /var/run/ syslog- ng.pid
Wait for monit to notice, then logs fill with: syslog- ng.pid'
monit: Error reading pid from file '/var/run/
Not the best example because syslog-ng will notice the empty pid file and start a new instance so this will not fill the logs entirely but any application that does not actively check the state of its PID file will.