Hi gang! I'm trying to determine the best way to periodically check the status of production Freeswitch deployments. While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway. Has anyone considered or done this yet? My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be. thinking of using show channels or show calls, in addition to status. Any thoughts? Is this a wrong-headed approach? Thanks for any feedback. Lon
To me monit works the best. http://mmonit.com/monit/ On Friday 02 April 2010, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
One way I've contemplated is to use munin/munin node on the FS box and nagios on a central server. That would provide notification if the service were to go offline. I have the components in place, but haven't gotten around to writing a FS nagios plugin (which could use fs_cli -x status, for example). -Troy On Apr 2, 2010, at 2:24 PM, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
We run monit on each local machine sending out an options ping every minute. If it doesn't get a response then monit restarts the freeswitch process. The nice thing about this is that you can actually verify that Freeswitch is responding to SIP requests. On Apr 2, 2010, at 2:24 PM, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Would you care to share an example of the config for monit? I will document the practice on the wiki. On Fri, Apr 2, 2010 at 2:54 PM, Spencer Thomason <spencer@5ninesolutions.com> wrote:
We run monit on each local machine sending out an options ping every minute. If it doesn't get a response then monit restarts the freeswitch process. The nice thing about this is that you can actually verify that Freeswitch is responding to SIP requests.
On Apr 2, 2010, at 2:24 PM, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
check process freeswitch with pidfile /opt/freeswitch/run/freeswitch.pid start program = "/etc/init.d/freeswitch restart" stop program = "/etc/init.d/freeswitch stop" if totalmem > 1000.0 MB for 5 cycles then alert if totalmem > 1500.0 MB for 5 cycles then alert if totalmem > 2000.0 MB for 5 cycles then restart if cpu > 60% for 5 cycles then alert if failed host HOST_IP_ADDRESS port 5060 type udp protocol sip within 2 cycles then restart if 5 restarts within 5 cycles then timeout On Friday 02 April 2010, Lon Baker wrote:
Would you care to share an example of the config for monit? I will document the practice on the wiki.
On Fri, Apr 2, 2010 at 2:54 PM, Spencer Thomason
<spencer@5ninesolutions.com> wrote:
We run monit on each local machine sending out an options ping every minute. �If it doesn't get a response then monit restarts the freeswitch process. �The nice thing about this is that you can actually verify that Freeswitch is responding to SIP requests.
On Apr 2, 2010, at 2:24 PM, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Thank you! On Apr 2, 2010, at 5:55 PM, Sergey Okhapkin wrote:
check process freeswitch with pidfile /opt/freeswitch/run/freeswitch.pid start program = "/etc/init.d/freeswitch restart" stop program = "/etc/init.d/freeswitch stop" if totalmem > 1000.0 MB for 5 cycles then alert if totalmem > 1500.0 MB for 5 cycles then alert if totalmem > 2000.0 MB for 5 cycles then restart if cpu > 60% for 5 cycles then alert if failed host HOST_IP_ADDRESS port 5060 type udp protocol sip within 2 cycles then restart if 5 restarts within 5 cycles then timeout
On Friday 02 April 2010, Lon Baker wrote:
Would you care to share an example of the config for monit? I will document the practice on the wiki.
On Fri, Apr 2, 2010 at 2:54 PM, Spencer Thomason
<spencer@5ninesolutions.com> wrote:
We run monit on each local machine sending out an options ping every minute. �If it doesn't get a response then monit restarts the freeswitch process. �The nice thing about this is that you can actually verify that Freeswitch is responding to SIP requests.
On Apr 2, 2010, at 2:24 PM, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I would recommend to, obviously, ping all profiles of FS. I recently had an issue where one profile only stopped working. It happened only once, in a previous svn, but who knows... Another way to monitor is to send a test call with sipp through a registered user to a gateway. David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. Le 03/04/2010 à 08:16, Lon Baker a écrit :
Thank you!
On Apr 2, 2010, at 5:55 PM, Sergey Okhapkin wrote:
check process freeswitch with pidfile /opt/freeswitch/run/freeswitch.pid start program = "/etc/init.d/freeswitch restart" stop program = "/etc/init.d/freeswitch stop" if totalmem > 1000.0 MB for 5 cycles then alert if totalmem > 1500.0 MB for 5 cycles then alert if totalmem > 2000.0 MB for 5 cycles then restart if cpu > 60% for 5 cycles then alert if failed host HOST_IP_ADDRESS port 5060 type udp protocol sip within 2 cycles then restart if 5 restarts within 5 cycles then timeout
On Friday 02 April 2010, Lon Baker wrote:
Would you care to share an example of the config for monit? I will document the practice on the wiki.
On Fri, Apr 2, 2010 at 2:54 PM, Spencer Thomason
<spencer@5ninesolutions.com> wrote:
We run monit on each local machine sending out an options ping every minute. �If it doesn't get a response then monit restarts the freeswitch process. �The nice thing about this is that you can actually verify that Freeswitch is responding to SIP requests.
On Apr 2, 2010, at 2:24 PM, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Sergey: Thank you for sharing , I am just recently looking to use monit to monitor our freeswitch and other production servers. Henry Chat Skype: unicsolution MSN: b_ball_henry@hotmail.com Contact Me [image: Linkedin]<http://www.linkedin.com/pub/henry-huang/1/654/578>[image: Facebook] <http://www.facebook.com/profile.php?id=595148342>[image: Twitter]<http://twitter.com/unicsolution> On Fri, Apr 2, 2010 at 5:55 PM, Sergey Okhapkin <sos@sokhapkin.dyndns.org>wrote:
check process freeswitch with pidfile /opt/freeswitch/run/freeswitch.pid start program = "/etc/init.d/freeswitch restart" stop program = "/etc/init.d/freeswitch stop" if totalmem > 1000.0 MB for 5 cycles then alert if totalmem > 1500.0 MB for 5 cycles then alert if totalmem > 2000.0 MB for 5 cycles then restart if cpu > 60% for 5 cycles then alert if failed host HOST_IP_ADDRESS port 5060 type udp protocol sip within 2 cycles then restart if 5 restarts within 5 cycles then timeout
On Friday 02 April 2010, Lon Baker wrote:
Would you care to share an example of the config for monit? I will document the practice on the wiki.
On Fri, Apr 2, 2010 at 2:54 PM, Spencer Thomason
<spencer@5ninesolutions.com> wrote:
We run monit on each local machine sending out an options ping every minute. �If it doesn't get a response then monit restarts the freeswitch process. �The nice thing about this is that you can actually verify that Freeswitch is responding to SIP requests.
On Apr 2, 2010, at 2:24 PM, Lon Baker wrote:
Hi gang!
I'm trying to determine the best way to periodically check the status of production Freeswitch deployments.
While Freeswitch has been incredibly stable in production, I would like to ping it periodically to check that its not hung in someway.
Has anyone considered or done this yet?
My thought it so issue a command via fs_cli periodically and compare the out. But am trying to determine what a good command would be.
thinking of using show channels or show calls, in addition to status.
Any thoughts? Is this a wrong-headed approach?
Thanks for any feedback.
Lon
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Henry Huang UniC Solution - Communication Unified VoIP & Open Source software Consultant
participants (6)
-
David Ponzone
-
Henry Huang
-
Lon Baker
-
Sergey Okhapkin
-
Spencer Thomason
-
Troy Anderson