16 Oct
2005
16 Oct
'05
1:05 p.m.
Hi,
I'd like to use monit to monitor ser. Sometime ser has the pid file,
but stops responding to any request. I want to periodically send an
OPTIONS message to the udp port 5060 and expects the answer back.
However can't make it work with monit.
The config is something like this,
check process program with pidfile /var/run/ser.pid
start program = "/etc/init.d/rc.serstart"
stop program = "/etc/init.d/rc.serstop"
if failed port 5060 type udp
send "OPTIONS sip:test@........"
expect "SIP/2.0 200 OK"
with timeout 2 seconds
then alert
I can see the reply with ngrep. But monit still reports "connection
failed". Any suggestion?
Thanks,
Richard
17 Oct
17 Oct
5:48 a.m.
Hello,
maybe you can use sipsak (http://sipsak.org/) inside monit to detect if
the server responds or not.
Cheers,
Daniel
On 10/16/05 20:05, Richard Z wrote:
Hi,
I'd like to use monit to monitor ser. Sometime ser has the pid file,
but stops responding to any request. I want to periodically send an
OPTIONS message to the udp port 5060 and expects the answer back.
However can't make it work with monit.
The config is something like this,
check process program with pidfile /var/run/ser.pid
start program = "/etc/init.d/rc.serstart"
stop program = "/etc/init.d/rc.serstop"
if failed port 5060 type udp
send "OPTIONS sip:test@........"
expect "SIP/2.0 200 OK"
with timeout 2 seconds
then alert
I can see the reply with ngrep. But monit still reports "connection
failed". Any suggestion?
Thanks,
Richard
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
5:57 a.m.
Daniel-Constantin Mierla writes:
maybe you can use sipsak (http://sipsak.org/) inside
monit to detect if
the server responds or not.
monit does not allow executing external programs.
-- juha
6:04 a.m.
On 10/17/05 12:57, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Then the option is to have a shell script running in cron.d to do it or
use some other monitoring tool.
Daniel
maybe you can use sipsak (http://sipsak.org/)
inside monit to detect if
the server responds or not.
monit does not allow executing external programs.
-- juha
12:50 p.m.
My workaround so far is don't check the reply, instead check the
timestamp update of the log file.
On 10/17/05, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote:
On 10/17/05 12:57, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Then the option is to have a shell script running in cron.d to do it or
use some other monitoring tool.
Daniel
maybe you can use sipsak (http://sipsak.org/)
inside monit to detect if
the server responds or not.
monit does not allow executing external programs.
-- juha
7009
days inactive
7010
days old
4 comments
3 participants
participants (3)
-
Daniel-Constantin Mierla -
Juha Heinanen -
Richard Z