<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=240191013-14042006><FONT face=Arial color=#0000ff size=2>I
tried your suggestion, but it didn't work out. Any other sugestions are very
welcome.</FONT></SPAN></DIV>
<DIV><SPAN class=240191013-14042006></SPAN><FONT face=Tahoma><FONT size=2><SPAN
class=240191013-14042006><FONT face=Arial
color=#0000ff></FONT></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN class=240191013-14042006><FONT
face=Arial color=#0000ff>Regards,</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=240191013-14042006></SPAN></FONT></FONT> </DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN class=240191013-14042006><FONT
face=Arial color=#0000ff>Rick</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=240191013-14042006> </SPAN></FONT></FONT></DIV>
<DIV><FONT face=Tahoma><FONT size=2><SPAN
class=240191013-14042006> </SPAN>-----Original Message-----<BR><B>From:</B>
Lynne.G.Lawrence@uscg.mil [mailto:Lynne.G.Lawrence@uscg.mil] <BR><B>Sent:</B>
Friday, April 14, 2006 14:58<BR><B>To:</B> Mieden, Rick van der;
nagios-users@lists.sourceforge.net<BR><B>Subject:</B> RE: [Nagios-users] Epn
problems with perl plugin<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"><!-- Converted from text/plain format --><BR>
<P><FONT size=2>lgl> my notes inline<BR><BR>-----Original
Message-----<BR>From: nagios-users-admin@lists.sourceforge.net on behalf of
Mieden, Rick van der<BR>Sent: Fri 4/14/2006 6:46 AM<BR>To:
nagios-users@lists.sourceforge.net<BR>Subject: [Nagios-users] Epn problems
with perl plugin<BR><BR>Hi All,<BR><BR>I'm installing a new nagios server with
2.1 (upgrade 2.2 will follow<BR>soon) We've have a running nagios 2.0b3 server
and I just copied over my<BR>homebrewed perl plugins to the new server.<BR>I
noticed the embedded perl is a bit stricter in this 2.1 version, I<BR>compiled
nagios with embedded-perl and some of my plugins were not using<BR>the use
strict option, I adjusted all of them and they are working fine<BR>except
one.<BR><BR>To check some processes I've created a perl script which uses
ssh to<BR>login gather the info I need and do some
checkings:<BR><BR>....<BR>open (PS, "ssh -p 22 -o Protocol=2 $o_host -C \"ps
-ef| /bin/grep<BR>$o_name | /bin/grep -v grep\" |") || die("ps
-ef????");<BR>......<BR><BR>lgl> maybe try:<BR>lgl> open (PS, qq;ssh -p
22 -o Protocol=2 $o_host -C 'ps -ef| /bin/grep "$o_name" | /bin/grep -v grep'
|;) || die("ps -ef????");<BR><BR><BR>This works for all my processes in the
datacenter, except one. there I<BR>need to check for the following proces:
HLRTMD3 -t<BR>The -t has to be included and I covered this in the 2.0b3
version with<BR>"HLRTMD3\ -t" the backslash did the trick to deal with the -t
part.<BR>In 2.1 I have the correct output on commandline, but in the
Nagios<BR>Interface I get: (0 of HLRTMD3 -t processes running <= 0 :
CRITICAL)<BR><BR>Anybody an idea how to tackle this? Is there a way I can
re-produce this<BR>on commandline and have some troubleshooting output.
Anybody experience<BR>with this and a
solution?<BR><BR><BR>Regards,<BR><BR>Rick<BR><BR><BR>===========================================================<BR><BR>De
informatie opgenomen in dit bericht kan vertrouwelijk zijn en is alleen
bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt
u verzocht de inhoud niet te gebruiken en de afzender direct te informeren
door het bericht te retourneren. Hoewel Orange maatregelen heeft genomen om
virussen in deze email of attachments te voorkomen, dient u ook zelf na te
gaan of virussen aanwezig zijn aangezien Orange niet aansprakelijk is voor
computervirussen die veroorzaakt zijn door deze email.<BR><BR>The information
contained in this message may be confidential and is intended to be only for
the addressee. Should you receive this message unintentionally, please do not
use the contents herein and notify the sender immediately by return e-mail.
Although Orange has taken steps to ensure that this email and attachments are
free from any virus, you do need to verify the possibility of their existence
as Orange can take no responsibility for any computer virus which might be
transferred by way of this
email.<BR><BR>===========================================================<BR><BR></FONT></P></BLOCKQUOTE><p></p><p>===========================================================<br><br>De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is alleen bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. Hoewel Orange maatregelen heeft genomen om virussen in deze email of attachments te voorkomen, dient u ook zelf na te gaan of virussen aanwezig zijn aangezien Orange niet aansprakelijk is voor computervirussen die veroorzaakt zijn door deze email.<br><br>The information contained in this message may be confidential and is intended to be only for the addressee. Should you receive this message unintentionally, please do not use the contents herein and notify the sender immediately by return e-mail. Although Orange has taken steps to ensure that this email and attachments are free from any virus, you do need to verify the possibility of their existence as Orange can take no responsibility for any computer virus which might be transferred by way of this email.<br><br>===========================================================</BODY></HTML>