Socket timeout issue

[Hari Sekhon]

if that is the nrpe on the remote machine then check_disk won't work cos 
you've defined check_disk1 and check_disk2 in your nrpe config.

also, isn't the allowed_hosts option unsupported now?

isn't the proper way to do that to tcpwrap it in xinetd? (which is what 
I do)


what problem are you having specifically. tell us what you are typing 
and what result you are getting...

-h

Hari Sekhon



Paul Roberts wrote:
> Hi,
>
> Thanks for looking.
> Hope this helps.
>
> Here is my inetd.conf file entry:
> nrpe 	stream 	tcp 	nowait 	nagios /usr/sbin/tcpd
> /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg --inetd
>
> server_port=5666
> allowed_hosts=x.x.x.x
> nrpe_user=nagios
> nrpe_group=nagios
> dont_blame_nrpe=0
> debug=0
> command_timeout=60
> command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
> command[check_load]=/usr/local/nagios/libexec/check_load -w 15,10,5 -c
> 30,25,20
> command[check_disk1]=/usr/local/nagios/libexec/check_disk -w 20 -c 10 -p /
> command[check_disk2]=/usr/local/nagios/libexec/check_disk -w 20 -c 10 -p
> /data
> command[check_zombie_procs]=/usr/local/nagios/libexec/check_procs -w 5 -c 10
> -s Z
> command[check_total_procs]=/usr/local/nagios/libexec/check_procs -w 150 -c
> 200 
> command[check_ping]=/usr/local/nagios/libexec/check_ping -H localhost -w
> 100.0,20% -c 500.0,60%
> command[check_samba]=/usr/local/nagios/libexec/check_procs -C nmbd 
>
> -----Original Message-----
> From: Hari Sekhon [mailto:hpsekhon at googlemail.com] 
> Sent: 05 April 2007 14:41
> To: Paul Roberts
> Cc: Nagios Users mailinglist
> Subject: Re: [Nagios-users] Socket timeout issue
>
> post your nrpe config
>
> is your nrpe tcpwrapped? run as daemon or from inetd/xinetd?
>
> -h
>
> Hari Sekhon
>
>
>
> Paul Roberts wrote:
>   
>> Hi All,
>>
>> Can someone help out with my CHECK_NRPE: Socket timeout after 10 
>> seconds issue.
>>
>> I have Nagios running on a Debian server, runs tests to Windows Boxes OK.
>>
>> I am attempting to do remote checks of an Debian server.
>>
>> I can telnet on port 5666 to the remote server, netstat -l reports: 
>> tcp        0      0 *:nrpe                  *:*                     LISTEN
>>
>> I can run this check on the remote server:
>>
>> # /usr/local/nagios/libexec/check_nrpe -H 10.0.10.200 -p 5666 -t 30 
>> check_disk # NRPE v2.0
>>
>> What information/configurations files do you need from me?
>>
>> Regards
>> Paul Roberts.
>>
>>
>>
>> ----------------------------------------------------------------------
>> --- Take Surveys. Earn Cash. Influence the Future of IT Join 
>> SourceForge.net's Techsay panel and you'll get the chance to share 
>> your opinions on IT & business topics through brief surveys-and earn 
>> cash 
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV
>> DEV _______________________________________________
>> 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
>>
>>   
>>     
>
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070405/1b0a7847/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
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