|
From: | Vaughan Magnusson |
Subject: | Re: [monit] Monit wont start/stop any processes |
Date: | Mon, 17 Aug 2009 16:51:45 +1200 |
Thanks Jan-Henrik, I've adjusted the stop directive to be as follows: stop = "/home/edforceps/bashdate.sh" Just to be clear, I'm actually trying to monitor backgroundrb, but when the start/stop directives weren't working, I tried to see if I could get *anything* to work. This is why I'm using bashdate.sh, which as the following contents #!/bin/bash date >> datetest.txt echo 'ok' Once I call 'monit stop all' I check datetest.txt to see if the current date has been appended. I cannot get this to work. When I execute 'monit stop all' I get the following in the log. [PDT Aug 16 21:30:57] debug : stop service 'backgroundrb_11006' on user request [PDT Aug 16 21:30:57] info : monit daemon at 29750 awakened [PDT Aug 16 21:30:57] info : Awakened by User defined signal 1 [PDT Aug 16 21:30:57] debug : stop service 'ps9844' on user request [PDT Aug 16 21:30:57] info : monit daemon at 29750 awakened [PDT Aug 16 21:30:57] info : 'backgroundrb_11006' stop: /home/user/bashdate.sh [PDT Aug 16 21:31:27] error : 'backgroundrb_11006' failed to stop [PDT Aug 16 21:31:31] info : 'backgroundrb_11006' stop action done [PDT Aug 16 21:31:36] info : 'ps9844' stop action done This is actually what i expect, (as the pid that is being monitored still points to an existing process), however there is no evidence of the bashdate.sh actually being run - ie, the current date has not been appended to datetest.txt. Does anyone know of a simple hello world like experiment I can use to see if monit itself is working? or am I missing something here? Cheers, Vaughan. ps. here are my server details: Linux version 2.6.22.19-xeon-vserver-grsec2.1.11-vs2.2.0.7 (address@hidden) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri Aug 14 23:58:13 PDT 2009 pps. monit lives in /home/user/bin/ On 17/08/2009, at 14:50 PM, Jan-Henrik Haukeland wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |