It could be probably also caused by unresolvable hostname or invalid IP address in "set httpd" statement (which was snipped in your post).
It is not very likely, but has the "set httpd" part changed? Can you try to use IP address instead of hostname (and verify the IP address is correct and up on host where Monit is running).
If it won't help, please get strace of Monit like this and send output?:
strace -f -o monit.strace <path_to_monit>/monit -vIc <path_to_monitrc>
Thanks,
Martin
On Oct 8, 2009, at 10:53 PM, Mark Beattie wrote:
It's using /etc/monit/monitrc, but it's been working fine that way for a long time. All I did was add a another service to monitor and restart it, but since then it's http server has been dead. So of course the first thing I did was remove the service, but no change...
cheers
On Thu, Oct 8, 2009 at 11:54 PM, Eric Pailleau
<address@hidden> wrote:
Mark Beattie a écrit :
Yeah, definitely no zombie processes, and starting/stopping it using an init.d script as root.
There's always some stake holder who asks "but what happens if the monitor dies?", to which the usual response is <face-palm> :)
I faced another issue in past while changing from src compiled to debian package :
monitrc was not in same directory.
Debian package look for
/etc/monitrc
While my config was in
/etc/monit/monitrc
So I needed to create a /etc/monitrc with a simple include of /etc/monit/monitrc .
Have a look that you are loading the right monitrc.
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general