I have saved the file in /usr/bin but have also tried having it in /usr/local/bin and it does not make a difference.
The name of the script on my machine is "notify-jabber" and the notification command that I have tried in the nagios configuration is the following: # This command is used to notify recipients of service problems: # 'notify-by-jabber' command definition define command{ command_name notify-by-jabber command_line /usr/bin/notify-jabber $CONTACTADDRESS1$ "$HOSTNAME$/$SERVICEDESC$ is $SERVICESTATE$\r\nAdditional Info: $SERVICEOUTPUT$" } # This command is used to notify recipients of host problems: # 'host-notify-by-jabber' command definition define command{ command_name host-notify-by-jabber command_line /usr/bin/notify-jabber $CONTACTADDRESS1$ "$NOTIFICATIONTYPE$: $HOSTNAME$ is $HOSTSTATE$\n$HOSTOUTPUT$" } I have configured the Jabber recipients as follows in my contact configuration: # This defines the generic template define contact { name system-administrator host_notification_period 24x7 host_notification_options d,u,r host_notification_commands host-notify-by-epager,host-notify-by-jabber service_notification_period 24x7 service_notification_options w,u,c,r service_notification_commands notify-by-epager,notify-by-jabber register 0 } # This defines a specific contact instance define contact { use system-administrator contact_name [joe] alias [joe blow] pager [pager email address] address1 [EMAIL PROTECTED] } I appreciate any insight you can offer! Sincerely, Norman Harebottle III Software Engineer Vikus Corporation -----Original Message----- From: Frederik Vanhee [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 12:52 AM To: Norman Harebottle Cc: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Jabber Custom Notification Script Not Working Norman Harebottle wrote: > Hello Everyone, > > I am wondering if anyone has had success getting the Jabber > Notification script written by David Cox to work. > > I have a user called nagios under which nagios runs and using "su > nagios" (on Debian) I can run the script and it notifies just fine. So > I am concluding that it is not a security related issue nor a script > execution error since it works correctly. However, when running the > Perl script in the Embedded Perl environment, something happens (which > is not logged) which causes the script to not execute as desired. > > Can anyone point me in the direction of a logging directive to enable > so that I can see any Perl errors that may be generated in the process? > > *Current nagios.cfg logging settings:* > log_archive_path=/var/log/nagios/archives > log_event_handlers=1 > log_external_commands=1 > log_file=/var/log/nagios2/nagios.log > log_host_retries=1 > log_initial_states=0 > log_notifications=1 > log_passive_checks=1 > log_rotation_method=d > log_service_retries=1 > use_syslog=1 > *Abbbreviated contents of /var/log/nagios2/nagios.log:* [1148388211] > SERVICE NOTIFICATION: norman;weathervane;Service: Jabber Notification > Test;CRITICAL;notify-by-jabber;No process matching ping found : > CRITICAL I appreciate any insight into this problem would be > appreciated. > > Sincerely, > > Norman H. Harebottle III > Software Engineer > Vikus Corporation Hello Norman, can you send me your Nagios notification command ? I have it working, so it should work. I had it working with embedded perl on Nagios 2.0b3 and on Nagios 2.0rc2 and without embedded perl on Nagios 2.3.1 Frederik ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _______________________________________________ Nagios-users mailing list Nagios-users@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