Nagios Monitoring ERROR/BUG

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Nagios Monitoring ERROR/BUG

Post by tgriep »

There were some bug fixes that may fix the issue of the Status showing OK when a service check timeouts.

Here is the link to the Nagios Core 4.x Version History

http://www.nagios.org/projects/nagiosco ... on-history
Be sure to check out our Knowledgebase for helpful articles and solutions!
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

Thanks for everyone support.

My problem resolved after upgrading my nagios from 4.0.4 to 4.0.8, The status goes to CRITICAL from OK. But status information (Return code of 255 is out of bounds) still persist. (as my previous post show the information)
nagios ProblemSolved 16012015.jpg
User avatar
lgroschen
Posts: 384
Joined: Wed Nov 27, 2013 1:17 pm

Re: Nagios Monitoring ERROR/BUG

Post by lgroschen »

Now that you made the updates I think you should look through this topic from the beginning and make sure all the configs are correct: http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf



Also can you attach or PM me the nrpe.cfg file on the remote server??
/Luke
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

Dear,
lgroschen wrote:Now that you made the updates I think you should look through this topic from the beginning and make sure all the configs are correct: http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf

Also can you attach or PM me the nrpe.cfg file on the remote server??
My client /usr/local/nagios/etc/nrpe.cfg file attached. please review.
nrpe.cfg
(7.84 KiB) Downloaded 289 times
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: Nagios Monitoring ERROR/BUG

Post by Box293 »

Are all service checks for this host failing?

Can you also post any files in this directory:

Code: Select all

/usr/local/nagios/etc/nrpe
Your nrpe.cfg is including this directory.


On the remote host can you type these commands and post the output:

Code: Select all

ls -al /usr/local/nagios/libexec/

cat /etc/xinetd.d/nrpe

service xinetd status
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

Box293 wrote:Are all service checks for this host failing?

Can you also post any files in this directory:

Code: Select all

/usr/local/nagios/etc/nrpe
Your nrpe.cfg is including this directory.

On the remote host can you type these commands and post the output:

Code: Select all

ls -al /usr/local/nagios/libexec/

cat /etc/xinetd.d/nrpe

service xinetd status

Code: Select all

 ls -al /usr/local/nagios/etc/nrpe/
total 20
drwxr-xr-x. 3 nagios nagios 4096 Dec 20 12:10 .
drwxrwxr-x. 3 nagios nagios 4096 Jan 14 22:57 ..
-rw-r--r--. 1 nagios nagios  687 Dec 20 11:58 asterisk.cfg
-rw-r--r--. 1 nagios nagios 1309 Dec 20 11:58 common.cfg
drwxr-xr-x. 6 nagios nagios 4096 Dec 20 11:58 .svn

Code: Select all

ls -al /usr/local/nagios/libexec/
total 6892
drwxrwxr-x. 2 nagios nagios   4096 Dec 25 16:23 .
drwxr-xr-x. 8 nagios nagios   4096 Dec 20 11:57 ..
-rwxr-xr-x. 1 root   root   179354 Dec 20 11:57 check_apt
-rwxr-xr-x. 1 root   root     6897 Dec 20 11:58 check_asterisk.pl
-rwxr-xr-x. 1 root   root     1978 Dec 20 11:58 check_asterisk_sip_peers.sh
-rwxr-xr-x. 1 root   root     2251 Dec 20 11:57 check_breeze
-rwxr-xr-x. 1 root   root   179779 Dec 20 11:57 check_by_ssh
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_clamd -> check_tcp
-rwxr-xr-x. 1 root   root   137101 Dec 20 11:57 check_cluster
-rwxr-xr-x. 1 root   root     5355 Dec 20 11:58 check_cpu_stats.sh
-r-sr-xr-x. 1 root   root   175410 Dec 20 11:57 check_dhcp
-rwxr-xr-x. 1 root   root   174509 Dec 20 11:57 check_dig
-rwxr-xr-x. 1 root   root   193484 Dec 20 11:57 check_disk
-rwxr-xr-x. 1 root   root     9289 Dec 20 11:57 check_disk_smb
-rwxr-xr-x. 1 root   root   189163 Dec 20 11:57 check_dns
-rwxr-xr-x. 1 root   root    85147 Dec 20 11:57 check_dummy
-rwxr-xr-x. 1 root   root     3349 Dec 20 11:57 check_file_age
-rwxr-xr-x. 1 root   root     6315 Dec 20 11:57 check_flexlm
-rwxr-xr-x. 1 root   root   180877 Dec 20 11:57 check_fping
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_ftp -> check_tcp
-rwxr-xr-x. 1 root   root   157777 Dec 20 11:57 check_game
-rwxr-xr-x. 1 root   root   175480 Dec 20 11:57 check_hpjd
-rwxr-xr-x. 1 root   root   335964 Dec 20 11:57 check_http
-r-sr-xr-x. 1 root   root   182075 Dec 20 11:57 check_icmp
-rwxr-xr-x. 1 root   root   146227 Dec 20 11:57 check_ide_smart
-rwxr-xr-x. 1 root   root    15123 Dec 20 11:57 check_ifoperstatus
-rwxr-xr-x. 1 root   root    12600 Dec 20 11:57 check_ifstatus
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_imap -> check_tcp
-rwsr-xr-x. 1 root   nagios    748 Dec 20 11:58 check_init_service
-rwxr-xr-x. 1 root   root     6887 Dec 20 11:57 check_ircd
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_jabber -> check_tcp
-rwxr-xr-x. 1 root   root   158164 Dec 20 11:57 check_load
-rwxr-xr-x. 1 root   root     5989 Dec 20 11:57 check_log
-rwxr-xr-x. 1 root   root    21480 Dec 20 11:57 check_mailq
-rwxr-xr-x. 1 root   root   144333 Dec 20 11:57 check_mrtg
-rwxr-xr-x. 1 root   root   145386 Dec 20 11:57 check_mrtgtraf
-rwxr-xr-x. 1 root   root   157470 Dec 20 11:57 check_nagios
-rwxr-xr-x. 1 root   root    25602 Dec 20 11:58 check_netstat.pl
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_nntp -> check_tcp
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_nntps -> check_tcp
-rwxrwxr-x. 1 nagios nagios  76809 Dec 20 11:57 check_nrpe
-rwxr-xr-x. 1 root   root   179874 Dec 20 11:57 check_nt
-rwxr-xr-x. 1 root   root   184209 Dec 20 11:57 check_ntp
-rwxr-xr-x. 1 root   root   173214 Dec 20 11:57 check_ntp_peer
-rwxr-xr-x. 1 root   root   171459 Dec 20 11:57 check_ntp_time
-rwxr-xr-x. 1 root   root   212431 Dec 20 11:57 check_nwstat
-rwxr-xr-x. 1 root   root     3259 Dec 20 11:58 check_open_files.pl
-rwxr-xr-x. 1 root   root     8779 Dec 20 11:57 check_oracle
-rwxr-xr-x. 1 root   root   160205 Dec 20 11:57 check_overcr
-rwxr-xr-x. 1 root   root   183754 Dec 20 11:57 check_ping
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_pop -> check_tcp
-rwxr-xr-x. 1 root   root     4581 Dec 25 16:23 check_process_resources.sh
-rwxr-xr-x. 1 root   root   187033 Dec 20 11:57 check_procs
-rwxr-xr-x. 1 root   root   157663 Dec 20 11:57 check_real
-rwxr-xr-x. 1 root   root     9581 Dec 20 11:57 check_rpc
-rwxr-xr-x. 1 root   root     1453 Dec 20 11:57 check_sensors
-rwxr-xr-x. 1 root   root     2174 Dec 20 11:58 check_services
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_simap -> check_tcp
-rwxr-xr-x. 1 root   root     7599 Dec 20 11:58 check_sip
-rwxr-xr-x. 1 root   root   247930 Dec 20 11:57 check_smtp
-rwxr-xr-x. 1 root   root   251329 Dec 20 11:57 check_snmp
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_spop -> check_tcp
-rwxr-xr-x. 1 root   root   155491 Dec 20 11:57 check_ssh
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_ssmtp -> check_tcp
-rwxr-xr-x. 1 root   root   141169 Dec 20 11:57 check_swap
-rwxr-xr-x. 1 root   root   230853 Dec 20 11:57 check_tcp
-rwxr-xr-x. 1 root   root   156641 Dec 20 11:57 check_time
lrwxrwxrwx. 1 root   root        9 Dec 20 11:57 check_udp -> check_tcp
-rwxr-xr-x. 1 root   root   168653 Dec 20 11:57 check_ups
-rwxr-xr-x. 1 root   root   138043 Dec 20 11:57 check_uptime
-rwxr-xr-x. 1 root   root   136193 Dec 20 11:57 check_users
-rwxr-xr-x. 1 root   root     2936 Dec 20 11:57 check_wave
-rwxr-xr-x. 1 root   root      710 Dec 20 11:58 check_yum
-rwxr-xr-x. 1 root   root     3060 Dec 20 11:58 custom_check_mem
-rwxr-xr-x. 1 root   root      915 Dec 20 11:58 custom_check_procs
-rwxr-xr-x. 1 root   root     4176 Dec 20 11:58 nagisk.pl
-rwxr-xr-x. 1 root   root   131622 Dec 20 11:57 negate
-rwxr-xr-x. 1 root   root    64634 Dec 20 11:58 send_nsca
-rwxr-xr-x. 1 root   root   125868 Dec 20 11:57 urlize
-rwxr-xr-x. 1 root   root     1913 Dec 20 11:57 utils.pm
-rwxr-xr-x. 1 root   root     2791 Dec 20 11:57 utils.sh

Code: Select all

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       = 192.168.2.4 192.168.2.11
}

Code: Select all

service xinetd status
xinetd (pid  960) is running...
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Nagios Monitoring ERROR/BUG

Post by tmcdonald »

Could you post the asterisk.cfg and common.cfg files as @Box293 suggested?
Former Nagios employee
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

tmcdonald wrote:Could you post the asterisk.cfg and common.cfg files as Box293 suggested?

Code: Select all

 more asterisk.cfg
### ASTERISK ###

command[check_asterisk]=/usr/local/nagios/libexec/check_asterisk.pl $ARG1$
command[check_sip]=/usr/local/nagios/libexec/check_sip $ARG1$
command[check_asterisk_sip_peers]=sudo /usr/local/nagios/libexec/check_asterisk_
sip_peers.sh $ARG1$

# Nagisk (Asterisk) checks
command[check_asterisk_version]=/usr/local/nagios/libexec/nagisk.pl -c version
command[check_asterisk_peers]=/usr/local/nagios/libexec/nagisk.pl -c peers
command[check_asterisk_channels]=/usr/local/nagios/libexec/nagisk.pl -c channels

command[check_asterisk_zaptel]=/usr/local/nagios/libexec/nagisk.pl -c zaptel
command[check_asterisk_span]=/usr/local/nagios/libexec/nagisk.pl -c span -s 1

Code: Select all

 more common.cfg

### GENERIC SERVICES ###
command[check_init_service]=sudo /usr/local/nagios/libexec/check_init_service $A
RG1$
command[check_services]=/usr/local/nagios/libexec/check_services -p $ARG1$

### MISC SYSTEM METRICS ###
#command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
command[check_users]=/usr/local/nagios/libexec/check_users $ARG1$
command[check_load]=/usr/local/nagios/libexec/check_load $ARG1$
command[check_swap]=/usr/local/nagios/libexec/check_swap $ARG1$
command[check_cpu_stats]=/usr/local/nagios/libexec/check_cpu_stats.sh $ARG1$
command[check_mem]=/usr/local/nagios/libexec/custom_check_mem -n $ARG1$

### SYSTEM UPDATES ###
command[check_yum]=/usr/local/nagios/libexec/check_yum
command[check_apt]=/usr/local/nagios/libexec/check_apt

### DISK ###
command[check_disk]=/usr/local/nagios/libexec/check_disk $ARG1$
command[check_ide_smart]=/usr/local/nagios/libexec/check_ide_smart $ARG1$

### PROCESSES ###
command[check_all_procs]=/usr/local/nagios/libexec/custom_check_procs
command[check_procs]=/usr/local/nagios/libexec/check_procs $ARG1$

### OPEN FILES ###
command[check_open_files]=/usr/local/nagios/libexec/check_open_files.pl $ARG1$

### NETWORK CONNECTIONS ###
command[check_netstat]=/usr/local/nagios/libexec/check_netstat.pl -p $ARG1$ $ARG2$
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: Nagios Monitoring ERROR/BUG

Post by Box293 »

Thanks for the information.
rmuhammadali wrote:My problem resolved after upgrading my nagios from 4.0.4 to 4.0.8, The status goes to CRITICAL from OK. But status information (Return code of 255 is out of bounds) still persist. (as my previous post show the information)
So is the problem you are trying to fix (Return code of 255 is out of bounds) ... is that only happening when your host is down, or does it occur when the host is up?

Are all service checks for this host failing?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
rmuhammadali
Posts: 27
Joined: Sat Dec 13, 2014 4:02 am

Re: Nagios Monitoring ERROR/BUG

Post by rmuhammadali »

Box293 wrote:Thanks for the information.
rmuhammadali wrote:My problem resolved after upgrading my nagios from 4.0.4 to 4.0.8, The status goes to CRITICAL from OK. But status information (Return code of 255 is out of bounds) still persist. (as my previous post show the information)
So is the problem you are trying to fix (Return code of 255 is out of bounds) ... is that only happening when your host is down, or does it occur when the host is up?

Are all service checks for this host failing?
Yes, the is problem (Return code of 255 is out of bounds) still persist when the host is down, otherwise on host up everything is fine. Snapshot for the services information when host down
nagios ProblemSolved 16012015.jpg
Locked