I ran the chsh command to change the nologin shell for the nagios user to
/bin/bash, and also provided a password for the nagios account. After that,
I ran the check_nrpe command again from the command line, ie: manually, and was
able to get a response back from the nrpe client.
Listed below are posts that were requested from a previous e-mail:
1. The output of "check_nrpe -H <nrpe_client> -c <remote_command>" run
as the Nagios user:
DISK OK [50534480 kb (99%) free on cosmos2:/database
2. The Nagios command definition for your check_nrpe command:
# 'check_nrpe' command definition
define command{
command_name check_nrpe
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -t 60 -c $ARG1$
3. A Nagios service definition that uses the check_nrpe service on the
relevant host:
command[check_disk1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p
/cosmos2/database
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy Shellam
(Mailing Lists)
Sent: Friday, December 29, 2006 8:58 AM
To: Kaplan, Andrew H.
Cc: Nagios Users mailinglist
Subject: Re: [Nagios-users] Service Check Timed Out Error
Kaplan, Andrew H. wrote:
> I configured the ip tables on both the nagios server and the nrpe client to
> allow all inbound and outbound traffic. Additionally, I made sure the
> /etc/services file on both systems had port 5666 open to tcp and udp traffic.
>
> I was able to telnet to port 5666 on the nrpe client, but I was still getting
a
> connection refused for the same port on the server.
>
You won't be able to telnet back from the client to the server unless
you're also running nrpe on the server.
As long as you can telnet server to client on that port, you're fine.
Also nrpe uses TCP only (I believe.)
> I verified also, that the network speed, ie: half vs. full duplex, was the
same
> for both systems. The speed here is 100 half duplex no autonegotiation.
>
> I repeatedly ran the check_nrpe command manually and did get output back every
> time. Why am I able to run the command manually, but not automatically?
>
Like David says, try su'ing to the Nagios user and running the command
manually.
If all else fails, please post back the following:
2. The Nagios command definition for your check_nrpe command
3. A Nagios service definition that uses the check_nrpe service on the
relevant host
Andy.
-------------------------------------------------------------------------
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
_______________________________________________
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
THE INFORMATION TRANSMITTED IN THIS ELECTRONIC COMMUNICATION IS INTENDED ONLY
FOR THE PERSON OR ENTITY TO WHOM IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL
AND/OR PRIVILEGED MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR OTHER
USE OF OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS OR
ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU RECEIVED THIS
INFORMATION IN ERROR, PLEASE CONTACT THE SENDER AND THE PRIVACY OFFICER, AND
PROPERLY DISPOSE OF THIS INFORMATION.
-------------------------------------------------------------------------
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
_______________________________________________
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
