|
From: | Martin Pala |
Subject: | Re: 2 copies started at once |
Date: | Mon, 30 Jul 2007 23:00:27 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.5) Gecko/20070715 Iceape/1.1.3 (Debian-1.1.3-1) |
please start monit deamon in debug mode (-v option) and send the log output Thanks, Martin Martin Pala wrote:
... and what about the configuration of services 'bs1' and 'checkntpd'? Some dependency between them? ('depends on ...' statement?) Thanks, Martin Nick Upson wrote:ok, I think I now have a predictable test case, if I'm correct it should happen to anyone. Just have a single command line that calls monit twice in quick succession. Mine says "monit start bs1; monit start checkntpd" when I run it like this I always get 2 copies of bs1 started, if I run them as seperate command lines or put "sleep 1" in between them, then it's ok On 30/07/07, Nick Upson <address@hidden> wrote:I'll try and do so, the problem is that it doesn't happen every time and I haven't found any rules to predict when it will fail. On 29/07/07, Martin Pala <address@hidden> wrote:Can you please?: - try to run monit in debug mode (monit -v) and send output - send the configuration of the problematic service from monitrc and the start/stop scripts Thanks, Martin On Jul 28, 2007, at 11:21 PM, Nick Upson wrote:I'm using 4.9 On 27/07/07, Martin Pala <address@hidden> wrote:Yes, there was bug which was fixed in monit 4.9: --8<-- * Fix the extra restart action which was called by monit in addition to user requested start action of stopped process. This didn't occured in the case that the 'every' statement was used on the service definition as well. Thanks to Aaron Scamehorn for help. --8<-- Which version do you use? Thanks, Martin Jan-Henrik Haukeland wrote:On 27. jul. 2007, at 16.39, Nick Upson wrote:could I be seeing a problem with monit starting to monitor bs1 again (so start 1) AND start bs1 (start 2) because I told it to, or something like that.I see that there was a bug fix in the change log for 4.9 that may be related. Martin has done most, if not all coding on monit for the latest releases and maybe he knows more. Anyway, make sure you run the latest version of monit, i.e. 4.9 or the CVS version I told you about before. Other than that I'm not sure how to help short of debugging the program on location. Maybe you know someone who can run gdb on monit or trace it? -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general-- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general-- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general-- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general-- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general-- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general
[Prev in Thread] | Current Thread | [Next in Thread] |