Dear Folks,

I am writing to thank you for your letter and say,

>-----Original Message-----
>Message: 1
>Date: Wed, 24 May 2006 06:52:22 +0200
>From: Frederik Vanhee <[EMAIL PROTECTED]>
>To: Norman Harebottle <[EMAIL PROTECTED]>
>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.
>>  
>>  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.
>>  

embedded Perl Nagios like mod_perl is more sensitive to coding issues
than the 'fork a new Perl interpreter for each run' model.

There is every chance that a plugin that works fine from the command
line won't work under ePN.

You can turn ePN logging on by changing the DEBUG_LEVEL in p1.pl. Set it
to LEAVE_MSG (or whatever is mentioned in perldoc p1.pl). You need to
make
sure the log path and name suits you also.

In a former job, I found jabber/XMPP was very sensitive to the Perl
modules
and configuration of the Jabber server. I think we had an event handler
that
would publish stuff to jabber consoles with not much more than one of
the
example usages from the Perl jabber client. Unfortch my records are
elsewhere.

No experience unfortch with the jabber plugins.

Yours sincerely.


-------------------------------------------------------
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

Reply via email to