> 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 tight loop trying to read the PID file, as I stated. All of
my monit configs have the number of restarts limited.
> And you should fix this service - pid file shouldn't be empty!
Obviously, but that does not change the fact that this bug exists in
monit. Monit should fail gracefully, handling an empty PID file the same
way it would handle a non-existent PID file.
** Changed in: monit (Ubuntu)
Status: Incomplete => New
--
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1277655/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
