[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
problem with start/stop arguments
From: |
Martin Pala |
Subject: |
problem with start/stop arguments |
Date: |
Wed, 23 Apr 2003 10:36:54 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314 |
Hi,current monit CVS version has problem with start/stop program
arguments (i found it durring new device monitoring task tests but it is
not related to it).
Example configuration:
check slapd with pidfile /var/run/sshd.pid
start program = "/etc/init.d/ldap start"
stop program = "/etc/init.d/ldap stop"
port 389 protocol ldap3
alert address@hidden
Result:
Process Name = slapd
Group = (not defined)
Pid file = /var/run/sshd.pid
Monitoring mode = active
Start program = /etc/init.d/ldap
Stop program = /etc/init.d/ldap
Host:Port = localhost:389 [protocol LDAP3]
Resource Limits = (not defined)
Every = (not defined)
Timeout = (not defined)
Alert mail to = address@hidden
alert from = (default)
alert subject = (default)
alert message = (default)
alert on timeout = yes
alert on restart = yes
alert on checksum = yes
alert on resource = yes
alert on stop = yes
alert on timestamp = yes
...
Trying to restart 'slapd'
Monitoring disabled -- process slapd
stop: (slapd) /etc/init.d/ldap
monit: Warning process 'slapd' was not stopped
...
As you can see, monit takes only one argument in start/stop program and
the rest is ignored. Next example which i tried was related to device
stuff (the same result):
stop program = "/bin/umount /data"
I'm busy until friday and i will try to finalize device/file/directory
monitoring as soon as possible. If nobody will have time to look on it,
i will fix it then.
Cheers,
Martin
- problem with start/stop arguments,
Martin Pala <=