monit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [monit] Re: started twice


From: Martin Pala
Subject: Re: [monit] Re: started twice
Date: Fri, 16 Nov 2007 23:45:10 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071008 Iceape/1.1.5 (Debian-1.1.5-1)

Hmm, this is strange. Can you please post the full monit configuration, startup script for bs4 (/opt/unb/bin/bs.sh) and full monit verbose log from the start till the problem occurrence?

Maybe there's some problem with how the the /opt/unb/bin/bs.sh creates the pidfile vs. how the bs4 service is started and monitored.

Martin


Nick Upson wrote:
set daemon 120 in the file

On 15/11/2007, Martin Pala <address@hidden> wrote:
How long is the testing cycle?

(this is set using either "set daemon ..." option in monitrc or -d
option on command line).

It seems that it is most probably very short ... 1 second?


Thanks,
Martin




Nick Upson wrote:
I've attempted to remove entries that relate to other processes to
keep the size down, please let me know if you need the full version.
The process in question is called bs4, the config is

  check process bs4 with pidfile "/var/run/bs4.pid"
    start program = "/opt/unb/bin/bs.sh 4 restart"
    stop program = "/opt/unb/bin/bs.sh 4 stop"
    if totalmem > 1000 Mb then
       exec "/bin/bash -c '/bin/echo bs4: memory alert >>
/tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'"
    if cpu usage > 95% for 3 cycles then
       exec "/bin/bash -c '/bin/echo bs4: cpu usage alert >>
/tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'"
    group ntpd_dependant

the original problem occurred before the last line was added

[GMT Nov 13 13:42:57] debug    : monit: pidfile '/var/run/monit.pid'
does not exist
[GMT Nov 13 13:42:57] info     : Starting monit daemon with http
interface at [*:2812]
[GMT Nov 13 13:42:57] info     : Starting monit HTTP server at [*:2812]
[GMT Nov 13 13:42:57] info     : monit HTTP server started
[GMT Nov 13 13:42:57] info     : Monit started
[GMT Nov 13 13:43:55] info     : monit daemon at 2040 awakened
[GMT Nov 13 13:43:55] info     : Awakened by User defined signal 1
[GMT Nov 13 13:43:55] info     : Monit has not changed
[GMT Nov 13 13:43:55] info     : monit daemon at 2040 awakened

[GMT Nov 13 13:43:55] info     : start service 'bs4' on user request
[GMT Nov 13 13:43:55] info     : monit daemon at 2040 awakened

[GMT Nov 13 13:43:55] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist
[GMT Nov 13 13:43:55] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist
[GMT Nov 13 13:43:55] info     : 'bs4' start: /opt/unb/bin/bs.sh
[GMT Nov 13 13:43:55] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist
[GMT Nov 13 13:43:55] debug    : Monitoring enabled -- service bs4

[GMT Nov 13 13:43:55] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist

[GMT Nov 13 13:43:55] debug    : 'bs4' check skipped -- service
already handled in a dependency chain

[GMT Nov 13 13:43:56] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist
[GMT Nov 13 13:43:56] error    : 'bs4' process is not running
[GMT Nov 13 13:43:56] info     : 'bs4' trying to restart
[GMT Nov 13 13:43:56] debug    : Monitoring disabled -- service bs4
[GMT Nov 13 13:43:56] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist
[GMT Nov 13 13:43:56] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist
[GMT Nov 13 13:43:56] info     : 'bs4' start: /opt/unb/bin/bs.sh
[GMT Nov 13 13:43:56] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist
[GMT Nov 13 13:43:56] debug    : Monitoring enabled -- service bs4

[GMT Nov 13 13:43:56] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist

[GMT Nov 13 13:43:56] debug    : monit: pidfile '/var/run/bs4.pid'
does not exist

[GMT Nov 13 13:43:57] debug    : 'bs4' Error testing process id [2531]
-- No such process

[GMT Nov 13 13:43:58] info     : 'bs4' process is running with pid 2641
[GMT Nov 13 13:43:58] debug    : 'bs4' zombie check passed [status_flag=0000]
[GMT Nov 13 13:43:58] debug    : 'bs4' cpu usage check passed [current
cpu usage=0.0%]
[GMT Nov 13 13:43:58] debug    : 'bs4' total mem amount check passed
[current total mem amount=792kB]


On 14/11/2007, Martin Pala <address@hidden> wrote:
You can use either the bug-tracing system:
https://savannah.nongnu.org/bugs/?group=monit

Or the mailing list.

Thanks,
Martin


Nick Upson wrote:
I now have a verbose log showing the problem, this is now using 4.10,
where should I send it

On 11/10/2007, Martin Pala <address@hidden> wrote:
Can you run monit in verbose mode (-v option) and provide logs?

Which monit version is it?

Thanks,
Martin

Nick Upson wrote:
I have monitoring a process called bs1, yesterday I had a problem
which I traced back to having 2 copies running at the same time (as it
talks down a serial line that caused problems).

The monit log shows it starting one copy at 16:58 and starting it
again at 17:00.
Normally monit looks after everything fine on this system which has
been used for several weeks, the config entry is below

    check process bs1 with pidfile "/var/run/bs1.pid"
    start program = "/opt/unb/bin/bs.sh 1 restart"
    stop program = "/opt/unb/bin/bs.sh 1 stop"
    if totalmem > 1000 Mb then
       exec "/bin/bash -c '/bin/echo bs1: memory alert >>
/tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'"
    if cpu usage > 95% for 3 cycles then
       exec "/bin/bash -c '/bin/echo bs1: cpu usage alert >>
/tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'"


--
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



--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general




reply via email to

[Prev in Thread] Current Thread [Next in Thread]