We're running Nagios 2.9.  We have a command configured:

define command {
        command_name    host-notify-by-xmessage
        command_line    /etc/nagios/scripts/host-notify-by-xmessage 
"$HOSTSTATE$" "$HOSTNAME$" "$HOSTALIAS$" "$DATETIME$"
        }

The "host-notify-by-xmessage" is a shell script that pulls in a text file and 
displays that text file along with the host and the problem via an xmessage to 
an xdisplay.  This all works fine when run from the command line.  It even 
works when invoked by nagios, but when nagios invokes it, it also kills the 
process in about 30 seconds.  This wasn't a problem on Nagios 1.x.  We recently 
upgraded to 2.9 and ran into this issue.  I've tried nohup'ing the xmessage, 
but no luck - it seems like the nagios process kills it no matter what!?   I've 
tried converting the script to perl and using 'system' or 'exec' calls, but 
that didn't fix the problem either.

Does anyone have a workaround for this or a suggestion on things to try, please?

Thank you,
Greg Redder
Network Analyst
Colorado State University

===============================================================================
Greg Redder                         Academic Computing & Networking Services
Colorado State University, ACNS     Phone:(970)491-7222  FAX:  (970)491-1958
601 S. Howes, Room 625              E-mail: [EMAIL PROTECTED]
Fort Collins, CO 80523       PGP Fprint:CD62EAE6227D96FC7C232B16DFE3B5D9B2F64352
===============================================================================

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to