Hi Martin,
Thanks for the link and the quick response. I compiled and installed
monit-4.5-cvs20050106, and it runs like a charm, no problems. Running
verbose I get the output shown below. Just to check my sanity I went
back and ran monit-4.4, and the same error returns. Looks like the
version you sent me avoids the problem, but it would be good to know
what the problem was, wouldn't it. Please let me know if I can do some
more testing for you on this machine.
Thanks,
Allen
PS - Here's the output from `monit -v -I` with version 4.5-cvs20050106:
-------------------------------------------------------------------------------
Runtime constants:
Control file = /root/.monitrc
Log file = /var/log/monit
Pid file = /var/run/monit.pid
Debug = True
Log = True
Use syslog = False
Is Daemon = True
Use process engine = True
Poll time = 120 seconds
Collector(s) = Mail server(s) = localhost
Mail from = (not defined)
Mail subject = (not defined)
Mail message = (not defined)
Start monit httpd = True
httpd bind address = Any/All
httpd portnumber = 2812
httpd signature = True
Use ssl encryption = False
httpd auth. style = Basic Authentication
Alert mail to = address@hidden
Alert on = All events
The service list contains the following entries:
Process Name = apache
Group = (not defined)
Pid file = /var/run/httpd.pid
Monitoring mode = active
Start program = /etc/rc.d/init.d/httpd start
Stop program = /etc/rc.d/init.d/httpd stop
Pid = if changed then alert
Ppid = if changed then alert
Port = if failed iifwpdata.com:80/index.html [protocol HTTP]
with timeout 5 seconds then restart else if recovered then alert
Process Name = cron
Group = system
Pid file = /var/run/crond.pid
Monitoring mode = active
Start program = /etc/init.d/crond start
Stop program = /etc/init.d/crond stop
Pid = if changed then alert
Ppid = if changed then alert
Timeout = If 5 restart within 5 cycles then unmonitor else if
recovered then alert
Alert mail to = address@hidden
Alert on = Timeout
Process Name = mysql
Group = (not defined)
Pid file = /var/lib/mysql/iifwpdata.com.pid
Monitoring mode = active
Start program = /usr/bin/safe_mysqld --user=mysql
Stop program = /usr/bin/mysqladmin -pyogiism -u root shutdown
Pid = if changed then alert
Ppid = if changed then alert
Port = if failed iifwpdata.com:3306 [protocol DEFAULT] with
timeout 5 seconds then restart else if recovered then alert
Timeout = If 5 restart within 5 cycles then unmonitor else if
recovered then alert
Alert mail to = address@hidden
Alert on = Timeout
Process Name = sshd
Group = (not defined)
Pid file = /var/run/sshd.pid
Monitoring mode = active
Start program = /etc/init.d/sshd start
Stop program = /etc/init.d/sshd stop
Pid = if changed then alert
Ppid = if changed then alert
Port = if failed localhost:22 [protocol SSH] with timeout 5
seconds then restart else if recovered then alert
Timeout = If 5 restart within 5 cycles then unmonitor else if
recovered then alert
File Name = clam-update.log
Group = (not defined)
Path = /var/log/clam-update.log
Monitoring mode = active
Timestamp = if greater than 18000 second(s) then exec else if
recovered then alert
Process Name = MailScanner
Group = (not defined)
Pid file = /var/run/MailScanner.pid
Monitoring mode = active
Start program = /etc/init.d/MailScanner start
Stop program = /etc/init.d/MailScanner stop
Pid = if changed then alert
Ppid = if changed then alert
Timeout = If 5 restart within 5 cycles then unmonitor else if
recovered then alert
Alert mail to = address@hidden
Alert on = Timeout
Process Name = webmin
Group = webmin
Pid file = /var/webmin/miniserv.pid
Monitoring mode = active
Start program = /etc/init.d/webmin start
Stop program = /etc/init.d/webmin stop
Pid = if changed then alert
Ppid = if changed then alert
Starting monit daemon with http interface at [*:2812]
Starting monit HTTP server at [*:2812]
monit HTTP server started
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- orphaned process id 0
system statistic error -- cannot find process id 1
'system' load average [0.03][0.00][0.00]
'system' memory usage 819123.5% [-400696 kB]
'system' cpu usage 0.0%us 0.0%sy 0.0%wa
'apache' zombie check passed [status_flag=0000]
'apache' succeeded connecting to INET[iifwpdata.com:80]
'apache' succeeded testing protocol [HTTP] at INET[iifwpdata.com:80]
'cron' zombie check passed [status_flag=0000]
'mysql' zombie check passed [status_flag=0000]
'mysql' succeeded connecting to INET[iifwpdata.com:3306]
'mysql' succeeded testing protocol [DEFAULT] at INET[iifwpdata.com:3306]
'sshd' zombie check passed [status_flag=0000]
'sshd' succeeded connecting to INET[localhost:22]
'sshd' succeeded testing protocol [SSH] at INET[localhost:22]
'clam-update.log' timestamp test passed for /var/log/clam-update.log
'MailScanner' zombie check passed [status_flag=0000]
'webmin' zombie check passed [status_flag=0000]
'webmin' succeeded connecting to INET[iifwpdata.com:10000]
'webmin' succeeded testing protocol [DEFAULT] at INET[iifwpdata.com:10000]
[ here I manually killed the daemon ]
Shutting down monit HTTP server
monit HTTP server stopped
monit daemon with pid [7142] killed
Port = if failed iifwpdata.com:10000 [protocol DEFAULT] with
timeout 5 seconds then restart else if recovered then alert
Timeout = If 5 restart within 5 cycles then unmonitor else if
recovered then alert
Alert mail to = address@hidden
Alert on = Timeout
-------------------------------------------------------------------------------
Martin Pala wrote:
Hi,
i have tested it but it works on my station (debian 3.1) without
problems.
I have tried following configuration:
--8<--
set daemon 5
set logfile /var/log/monit
check file slapd_rc path /etc/init.d/slapd
if timestamp > 5 hours then exec "/bin/echo"
--8<--
within following tests:
1.) compile monit-4.4 on system running kernel 2.4.27, then test it on
system running kernel 2.4.27
status: OK
2.) compile monit-4.4 on system running kernel 2.4.27, then test it on
system running kernel 2.6.10
status: OK
3.) compile monit-4.4 on system running kernel 2.6.10, then test it on
system running kernel 2.6.10
status: OK
Then i tried the same tests with actual cvs version of monit - again
without problems. It seems that the problem depends on some special
condition which i'm not able to recreate.
I have created cvs snapshot of current monit version for you - you can
find it here:
http://www.tildeslash.com/monit/dist/snapshot/monit-4.5-cvs20050106.tar.gz
Please compile it and try to run with verbose option (-v). You can
also use -I option to run monit in the foreground (you will see
messages directly on console).
Thanks,
Martin
--
===========================================================
Allen Shaw
IIFWP Data and 914.631.1331 x.106
IT Services http://www.iifwp.org
------------------------------------------------------------------------
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general