28 Nov
2003
28 Nov
'03
10:49 a.m.
Hi!
Some time ago, I've tried to use "mon" (
http://www.kernel.org/software/mon/ ) and the TCP monitor to send a
INVITE message (to a non existing user) to the proxy and waiting for a
404 reply. mon was installed at the same server as ser, and if there was
no 404 coming back, I restarted ser.
Furthermore, I installed ser at two PCs which monitored themselfs using
heartbeat ( http://www.ultramonkey.org/2.0.1/ ). ser was only runnning
at one PC and if heartbeat detected a failure of the main PC it started
ser at the bakup PC and overtook the IP address of the failed server.
My results were:
1. ser never failed -> mon never had to restart ser
2. heartbeat failed very often -> both servers were running ser und
using the same IP address
regards,
Klaus
-----Original Message-----
From: Alexander Mayrhofer [mailto:axelm@nic.at]
Sent: Thursday, November 27, 2003 4:13 PM
To: serusers(a)lists.iptel.org
Subject: [Serusers] monitoring SER
Hi,
I'm thinking about how to monitor a running SER installation
end-to-end
(which may include an authentication source, a NAT traversal box etc.)
My preferred solution would be to use Nagios (http://www.nagios.com),
and let a Nagios plugin do e.g. a REGISTER/(de)REGISTER every few
minutes.
Has anybody made any efforts to write a SIP plugin for
Nagios? Any other
solutions you are using to monitor SER?
thanks & cheers
axelm
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers