Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
I confirm the issue with monit 5.8.1, 5.9, 5.11: the same error output is. If I
use 5.8 and 5.7 - no problem then. I've checked the linux versions of monit
only.
Original comment by anton.wo...@gmail.com
on 29 Jan 2015 at 12:34
First of all I apologise for the delay.
I have just pushed #r10 that is tested against monit 5.8.1, 5.6 and 5.1.1 -
everything works seemingly fine, but please test the change on your systems.
Original comment by stas.vit...@gmail.com
on 31 Jan 2015 at 4:12
Hi, thank you a lot, it seems it's quite good for now, but not perfect.
I've tested on monit 5.10, so if all services are OK , then no differences:
OK: Total 4 services are monitored
But if any service monitored is "broken", then I see no the reason why:
New version on monit 5.10:
CRITICAL: PROCESS test
Old version on monit 5.5:
CRITICAL: PROCESS test: failed to start
Original comment by anton.wo...@gmail.com
on 30 Mar 2015 at 5:16
If I understood you correctly, you expect to see status message for failed
services?
It looks like monit removed <status_message/> XML tag from their status output
at around 5.6, so there's no way to report it since then.
This is how failed sshd status looks like on Monit 5.8.1:
<service type="3">
<name>sshd</name>
<collected_sec>1428022523</collected_sec>
<collected_usec>891721</collected_usec>
<status>4608</status>
<status_hint>0</status_hint>
<monitor>1</monitor>
<monitormode>0</monitormode>
<pendingaction>0</pendingaction>
</service>
Original comment by stas.vit...@gmail.com
on 3 Apr 2015 at 1:30
Original issue reported on code.google.com by
Screamin...@gmail.com
on 2 Jan 2015 at 2:38