check_oracle breaks when run under nrpe

Frederik Vanhee frederik.vanhee at perso.be
Tue Jul 19 12:03:13 CEST 2005


Ralph.Grothe at itdz-berlin.de wrote:

>Hi Frederik
>
>  
>
>>-----Original Message-----
>>From: Frederik Vanhee [mailto:frederik.vanhee at perso.be]
>>Sent: Tuesday, July 19, 2005 11:08 AM
>>To: Ralph.Grothe at itdz-berlin.de; Nagios Users
>>Subject: Re: [Nagios-users] check_oracle breaks when run under
>>    
>>
>nrpe
>  
>
>>Ralph.Grothe at itdz-berlin.de wrote:
>>
>>    
>>
>>>Hello,
>>>
>>>I know that I should post this to nagiosplug-help solely and
>>>      
>>>
>not
>  
>
>>>x-post to nagios-users.
>>>But I see there's much more activity in the latter and thus I
>>>reckon a bigger chance for me to draw attention.
>>>
>>>I set up nrpe on remote hpux host that runs an Oracle dbms.
>>>
>>>When I execute the check_oracle shell script from the nagios
>>>plug-ins on that host like such
>>>everything works fine
>>>
>>>[nagios at terra:/usr/local/nagios/etc]
>>>$ ORACLE_HOME=/app/oracle/product/9.2.0
>>>PATH=/usr/bin:$ORACLE_HOME/bin
>>>/usr/local/nagios/libexec/check_oracle --tns FREMD
>>>
>>>OK - reply time 30 msec from FREMD
>>>
>>>
>>>Wheras when I run it through check_nrpe by this command
>>>definition in nrpe.cfg
>>>
>>>[nagios at terra:/usr/local/nagios/etc]
>>>$ grep ^command\\[check_tns nrpe.cfg
>>>      
>>>
>>command[check_tns_FREMD]='ORACLE_HOME=/app/oracle/product/9.2.0
>>    
>>
>>>PATH=/usr/bin:$ORACLE_HOME/bin
>>>/usr/local/nagios/libexec/check_oracle --tns FREMD'
>>>
>>>
>>>this is happening
>>>
>>>[nagios at terra:/usr/local/nagios/etc]
>>>$ ../libexec/check_nrpe -H 127.0.0.1 -c check_tns_FREMD
>>>CHECK_NRPE: Response packet had invalid CRC32.
>>>
>>>[nagios at terra:/usr/local/nagios/etc]
>>>$ echo $?
>>>3
>>>
>>>
>>>Unfortunately nrpe or check_nrpe are of the silent sort,
>>>and thus nothing useful gets logged via syslogd
>>>
>>>[nagios at terra:/usr/local/nagios/etc]
>>>$ tail -1 /var/adm/syslog/syslog.log
>>>Jul 19 09:31:02 terra inetd[22034]: nrpe/tcp: Connection from
>>>localhost (127.0.0.1) at Tue Jul 19 09:31:02 2005
>>>
>>>
>>>First how can I raise verbosity of nrpe to detect more?
>>>
>>>Then what could have gone wrong?
>>>
>>>
>>>Regards
>>>Ralph
>>>
>>>
>>>-------------------------------------------------------
>>>SF.Net email is sponsored by: Discover Easy Linux Migration 
>>>      
>>>
>>Strategies
>>>from IBM. Find simple to follow Roadmaps, straightforward
>>    
>>
>articles,
>  
>
>>>informative Webcasts and more! Get everything you need to get
>>>      
>>>
>up to
>  
>
>>>speed, fast.
>>>      
>>>
>http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>  
>
>>>_______________________________________________
>>>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
>>    
>>
>>> 
>>>
>>>      
>>>
>>check your nrpe.cfg file :
>>
>>debug=1 -> more logging
>>did you fill the allowed-hosts variable ?
>>do you use ssl, otherwise, you should use check_nrpe with the 
>>-n option
>>
>>Frederik
>>
>>    
>>
>
>
>I have to admit that I've missed the debug=1 option in nrpe.cfg.
>Only joke is that setting it doesn't change a thing.
>
>[nagios at terra:/usr/local/nagios/etc]
>$ grep ^debug= nrpe.cfg
>debug=1
>
>As response from check_nrpe I get the same lousy, non-instructive
>CRC32 failure message,
>and in syslog there doesn't appear anything more than before,
>i.e.
>
>[nagios at terra:/usr/local/nagios/etc]
>$ ../libexec/check_nrpe -H 127.0.0.1 -c check_tns_FREMD 
>CHECK_NRPE: Response packet had invalid CRC32.
>
>[nagios at terra:/usr/local/nagios/etc]
>$ tail -3 /var/adm/syslog/syslog.log
>Jul 19 11:10:23 terra inetd[24777]: nrpe/tcp: Connection from
>localhost (127.0.0.1) at Tue Jul 19 11:10:23 2005
>Jul 19 11:16:39 terra inetd[24856]: nrpe/tcp: Connection from
>localhost (127.0.0.1) at Tue Jul 19 11:16:39 2005
>Jul 19 11:16:57 terra inetd[24861]: nrpe/tcp: Connection from
>localhost (127.0.0.1) at Tue Jul 19 11:16:57 2005
>
>
>just to show you that it doesn't have anything to do with allowed
>hosts settings
>here's a simple disk check I defined in nrpe.cfg
>
>[nagios at terra:/usr/local/nagios/etc]
>$ ../libexec/check_nrpe -H 127.0.0.1 -c check_disk_LOCPCT_W5C2
>DISK OK - free space: / 74 MB (53%); /stand 45 MB (55%); /var 39
>MB (6%); /var/www 440 MB (87%); /usr 8
>0 MB (7%); /usr/local/tmp 599 MB (40%); /tmp 20 MB (17%); /opt 43
>MB (7%); /home 44 MB (55%); /bs14 119
>2 MB (59%); /bs12 3358 MB (94%); /bs11 959 MB (94%); /b062 526 MB
>(99%); /b051 5692 MB (66%); /apptemp 
>1100 MB (55%); /u03 19493 MB (23%);| /=66MB;133;137;0;140
>/stand=37MB;76;79;0;81 /var=662MB;665;686;0;7
>00 /var/www=68MB;482;497;0;508 /usr=1029MB;1052;1085;0;1108
>/usr/local/tmp=901MB;1425;1470;0;1500 /tmp=
>100MB;114;117;0;120 /opt=597MB;608;627;0;640
>/home=36MB;76;78;0;80 /bs14=840MB;1930;1991;0;2032 /bs12=2
>26MB;3404;3512;0;3584 /bs11=66MB;972;1003;0;1024
>/b062=7MB;505;521;0;532 /b051=2981MB;8238;8498;0;8672 
>/apptemp=900MB;1900;1960;0;2000 /u03=65276MB;80529;83072;0;84768
>
>
>Besides, the comment rightly states that inetd doesn't pay
>attention to such a setting
>(at least as long as no tcp wrapper comes into play, as is the
>case on this box)
>
># NOTE: This option is ignored if NRPE is running under either
>inetd or xinetd
>
>#allowed_hosts=127.0.0.1
>
>
>I deliberately built nrpe on hpux from the sources with
>--ssl-disable set,
>because I knew that with these low hurdles that already prove
>unsurmountable I would be light years away from a working TLS/SSL
>tunnelling.
>
>
>If the whole of nagios remote plugin execution is so obfuscated
>and intricate as it appears to me
>(I've been wasting the last two days trying in vain to just get
>such a simple check to work!)
>then Nagios to me is just a toy for developers but not usable by
>the average sysadmin like me.
>Ok it's fine to have the sources if you are a seasoned C hacker,
>but I just want a basic functionality working quickly.
>You're left alone because the documentation is sparse and
>incoherent.
>In that respect Mon proved a much better tool to meet the basic
>demands of mine
>(I had that up and running with custom plug-ins in abt. a day)
>
>Sorry, but my frustration with Nagios grows...
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>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
>
>  
>

Please don't be frustrated about Nagios. Sometimes it takes some time, 
but it's worth the effort !!

I also use NRPE on HP-UX (10.20 and 11.11), but I never got it working 
under inetd.
So I suggest you try to run nrpe as a daemon, I admit running under 
inetd is a more beautiful solution...
It works for me. I use nrpe from 
http://www.bennyvision.com/projects/nagios/index.php

Good luck,

Frederik




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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





More information about the Users mailing list