Configuration Issue?

[trafalgargirl]

Hi all

As you know I am pretty new ..but after some advice from Eric Loyd - have installed XI. I have set up different clients to monitor. One is working fine - the other is returning critical on all but ping - with a Return code of 255 is out of bounds. I followed the exact same steps for both.

I belive I need to edit the nrpe.cfg file but am not 100% sure so thought I would ask. I could not easily locate it to double check that the IP is entered in there - but given that ping is fine... I suspect it is?

Just one more piece of info - each client is on a different hosting environment. OVH is fine - AWS is not. I am about to try a few more clients on each to see if this is an AWS specific issue.

[trafalgargirl]

Update: was able to get another client up and running without any issue - so I can't pin the issue with the first client on AWS specifically.

Any thoughts?

[jolson]

I'd like you to log into the problem host and run the following commands:

Code: Select all

ps -ef | egrep "xinetd|nrpe"
cat /etc/xinetd.d/nrpe

Also, if you could share with us the installation steps that you took to get this server online in the first place, that would be very helpful.

[trafalgargirl]

root@:~# ps -ef | egrep "xinetd|nrpe"
root 772 1 0 17:15 ? 00:00:00 /usr/sbin/xinetd -dontfork -pidfile /var/run/xinetd.pid -stayalive -inetd_compat -inetd_ipv6
root 5036 4978 0 19:22 pts/1 00:00:00 egrep --color=auto xinetd|nrpe

root@:~# cat /etc/xinetd.d/nrpe
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port = 5666
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = xx.xxx.xxx.xx - replaced IP

sorry - are you asking about the Nagios XI server? If so I used an AMI on AWS that I was directed to.

[hsmith]

On the server you're having issues with, what kind of checks are you trying to get running?

Can I see the output of the following commands?

Code: Select all

grep nag /etc/passwd
netstat -nap | grep 5666
service xinetd status

[trafalgargirl]

On the server you're having issues with, what kind of checks are you trying to get running? n

Just the basics using the configuration wizard.

Can I see the output of the following commands?

Code: Select all

grep nag /etc/passwd

list:x:38:38:Mailing List Manager:/var/list:/bin/sh
nagios:x:1001:1001::/home/nagios:/bin/sh
root@ip-172-31-5-51:~# netstat -nap | grep 5666
tcp        0      0 0.0.0.0:5666            0.0.0.0:*               LISTEN      772/xinetd      
root@ip-172-31-5-51:~# grep nag /etc/passwd
list:x:38:38:Mailing List Manager:/var/list:/bin/sh
nagios:x:1001:1001::/home/nagios:/bin/sh

netstat -nap | grep 5666
tcp        0      0 0.0.0.0:5666            0.0.0.0:*               LISTEN      772/xinetd   

service xinetd status
xinetd start/running, process 772

[hsmith]

On the server you're having issues with, what kind of checks are you trying to get running?

Can you let me know what the answer to this is, please?

[trafalgargirl]

Oh sorry about that.

I have the following services set up via the configuration wizard:
/ Disk Usage
APT Updates
CPU Stats
Cron Scheduling Daemon
Load
Memory Usage
Open Files
SSH Server
Swap Usage
Total Processes
Users

All of these currently return the same Status Information:(Return code of 255 is out of bounds)

[hsmith]

Can you try the following(on the server with issues)?

Code: Select all

su nagios
cd /usr/local/nagios/libexec
./check_disk -w 1 -c 1

[trafalgargirl]

root@ip:~# su nagios
$ cd /usr/local/nagios/libexec
$ ./check_disk -w 1 -c 1
DISK OK - free space: / 42286 MB (88% inode=97%); /dev 1867 MB (99% inode=99%); /run 374 MB (99% inode=99%); /run/lock 5 MB (100% inode=99%); /run/shm 1875 MB (100% inode=99%);| /=5551MB;50395;50395;0;50396 /dev=0MB;1866;1866;0;1867 /run=0MB;374;374;0;375 /run/lock=0MB;4;4;0;5 /run/shm=0MB;1874;1874;0;1875
$