** Changed in: monit (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277655
Title:
Monit fills logs when reading 0 byte pid file
To manage notificatio
This bug is still here (monit 5.20.0).
http://stackoverflow.com/questions/4177/monit-is-continuously-
throwing-error-reading-pid-from-file
In my case, the whole startup is slowed down because monit is
"initializing" the failing service which has an empty .pid file. It
catches itself into a lo
the config:
===
check process nginx with pidfile /var/run/nginx.pid
group web
start program = "/etc/init.d/nginx start"
stop program = "/etc/init.d/nginx stop"
if failed host 127.0.0.1 port 80 protocol http request '/robots.txt' then
restart
if 3 restarts within 5 cycles then alert
===
a
** Changed in: monit (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277655
Title:
Monit fills logs when reading 0 byte pid file
To manage notifications abo
On Sat, Mar 01, 2014 at 07:10:15AM -, agent 8131 wrote:
> 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 s
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
Same for 1:5.4-2.
Can you reproduce this:
-->8--
This is not the case, monit is not trying to restart the service, it is
entering a tight loop trying to read the PID file
-->8--
for this monit's version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
> This is the only message
Sorry. Then I'm unable to reproduce this on the current Debian package.
Can you check this version?
> This is not the case, monit is not trying to restart the service, it
is entering a tight loop trying to read the PID file, as I stated.
Here is my steps to check this
** Changed in: monit (Ubuntu)
Status: New => Confirmed
** Changed in: monit (Ubuntu)
Assignee: (unassigned) => Sergey B Kirpichev (skirpichev)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
> Is this is the only error you have seen in the log file? Or there are
others?
This is the only message
> I think, there is - e.g. monit tries to restart this service. If this
is the case - this is expected.
This is not the case, monit is not trying to restart the service, it is
entering a tigh
** Changed in: monit (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277655
Title:
Monit fills logs when reading 0 byte pid file
To manage notifications abo
> spews this error to the syslog:
> monit: Error reading pid from file
Is this is the only error you have seen in the log file? Or there are
others?
I think, there is - e.g. monit tries to restart this service. If this is the
case - this is expected. You should limit the number of restarts f
12 matches
Mail list logo
