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 <[EMAIL PROTECTED]> 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
