serial notification of contacts by call

[Mooney, Ryan]

What I did (for different reasons - I wanted to bundle all notifications within
a time period, that way I could get dozens, not hundred of e-mails :) was to 
write a couple simple perl scripts, one takes nagios notification messages
(very like notify-by-email), and writes them to a spool.  The other takes
the spool and processes it.  That would allow the outside program to handle
the syncronization of the message delivery without having to worry about the
asyncrounous fork and forget nature of nagios.  The usual caveats about file 
locking and so forth apply.

> -----Original Message-----
> From: Schimpke, Dr. Thomas / bhn [mailto:Schimpke at Lenze.de]
> Sent: Friday, July 18, 2003 9:15 AM
> To: Nagios User List (nagios-users at lists.sourceforge.net)
> Subject: [Nagios-users] serial notification of contacts by call
> 
> 
> Hi all,
> 
> I'd like to set up nagios, so that each member of a 
> contactgroup gets a call
> on his mobile phone. I use vboxputty to do the work, which 
> works OK. The
> problem seems to be, that nagios tries to call all members of 
> that contact
> group at the same time. From the nagios log file:
> 
> 
> [1058538003] SERVICE NOTIFICATION: 
> thomas_call_work;eulep01;P01/saparch
> FS;CRITICAL;notify-by-call;DO IT
> [1058538003] Warning: Attempting to execute the command 
> "/usr/sbin/sudo
> /usr/sbin/vboxputty -r 40 -t 40 -d /dev/ttyI0 -c 215xxx
> [1058538003] SERVICE NOTIFICATION: rz_call_work;eulep01;P01/saparch
> FS;CRITICAL;notify-by-call;DO IT
> [1058538003] Warning: Attempting to execute the command 
> "/usr/sbin/sudo
> /usr/sbin/vboxputty -r 40 -t 40 -d /dev/ttyI0 -c 130xxx
> [1058538003] SERVICE NOTIFICATION: 
> matthias_call_work;eulep01;P01/saparch
> FS;CRITICAL;notify-by-call;DO IT
> [1058538003] Warning: Attempting to execute the command 
> "/usr/sbin/sudo
> /usr/sbin/vboxputty -r 40 -t 40 -d /dev/ttyI0 -c 126xxx
> [1058538003] SERVICE NOTIFICATION: 
> thomas_call_home;eulep01;P01/saparch
> FS;CRITICAL;direct-call-service;DO IT
> [1058538033] SERVICE NOTIFICATION: 
> holger_call_home;eulep01;P01/saparch
> FS;CRITICAL;notify-by-call;DO IT
> [1058538034] Warning: Attempting to execute the command 
> "/usr/sbin/sudo
> /usr/sbin/vboxputty -r 40 -t 40 -d /dev/ttyI0 -c 001xxxxxxx
> 
> etc.
> 
> I took a look at the source code and found, that for a notification
> my_system() is called, which essentially forks() and executes 
> the command
> (vboxgetty in this case). vboxgetty does not wait (to my 
> knowledge), if the
> originator line is busy, but returns emmidiately with an 
> error. So only one
> contact of the contactgroup gets notified.
> 
> Is there a way to tweak nagios so, that each contact is 
> notified in turn ?
> Things look bad..I know...
> 
> Thanks in advance,
> 
> Thomas
> 
> 
>  
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a 
> single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual 
> machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS 
> when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null