return code of 139 is out of bounds

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.
Locked
emp001
Posts: 2
Joined: Tue Oct 07, 2014 8:36 pm

return code of 139 is out of bounds

Post by emp001 »

Hi,

one nagios server:
use nagios-3.2.3.tar.gz, nagios-plugins-1.4.15, nrpe-2.12.tar.gz
os: Red Hat Enterprise Linux Server release 5.7 (Tikanga)
100 nagios client :
use: nagios-plugins-1.4.15.tar.gz, nrpe-2.12.tar.gz
os : Red Hat Enterprise Linux Server release 5.7 (Tikanga)

before 2014.9.30 , everything is ok .

2014.9.30, when I fixed the bash bug , there is a problem .
Sometimes, nagios responese info "return code of 139 is out of bounds"

I check nagios log and system log :

nagios log:
[1412737703] Warning: Return code of 139 for check of host '192.168.1.102' was out of bounds.
[1412737703] HOST ALERT: 192.168.1.102;DOWN;SOFT;1;(Return code of 139 is out of bounds)
[1412737773] HOST ALERT: 192.168.1.102;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 0.17 ms

system log :
Oct 1 11:19:04 localhost kernel: sh[19081]: segfault at 00000000000000c0 rip 000000349e453784 rsp 00007fffff69bba0 error 4
Oct 1 11:19:13 localhost nagios: Warning: Return code of 139 for check of host '192.168.1.102' was out of bounds.
Oct 1 11:19:13 localhost nagios: HOST ALERT: 192.168.1.102;DOWN;SOFT;1;(Return code of 139 is out of bounds)
Oct 1 11:19:33 localhost nagios: HOST ALERT: 192.168.1.102;UP;SOFT;2;PING OK - Packet loss = 0%, RTA = 0.21 ms

This problem happen randomly when I fixed the Bash bug.

could you help me .
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: return code of 139 is out of bounds

Post by abrist »

emp001 wrote: Oct 1 11:19:04 localhost kernel: sh[19081]: segfault at 00000000000000c0 rip 000000349e453784 rsp 00007fffff69bba0 error 4
Is there any other information in the log related to this segfault?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
emp001
Posts: 2
Joined: Tue Oct 07, 2014 8:36 pm

Re: return code of 139 is out of bounds

Post by emp001 »

I use " tail -f /var/log/message " to check system log .
There is no more information except the segfault line .

I find "segfault at 00000000000000c0 rip 000000349e453784 ..." is repeat

I copy other log :

Oct 9 11:29:09 localhost kernel: sh[24942]: segfault at 00000000000000c0 rip 000000349e453784 rsp 00007fff81482fc0 error 4
Oct 9 11:29:13 localhost nagios: SERVICE ALERT: 192.168.1.3;/opt;OK;SOFT;2;DISK OK - free space: / 61792 MB (70% inode=99%):
Oct 9 11:29:13 localhost nagios: Warning: Return code of 139 for check of service '/usr' on host '192.168.1.4' was out of bounds.
Oct 9 11:29:13 localhost nagios: SERVICE ALERT: 192.168.1.4;/usr;CRITICAL;SOFT;1;(Return code of 139 is out of bounds)
Oct 9 11:29:17 localhost kernel: sh[25007]: segfault at 00000000000000c0 rip 000000349e453784 rsp 00007fffa956a330 error 4
Oct 9 11:29:23 localhost nagios: Warning: Return code of 139 for check of service '/usr' on host '192.168.1.5' was out of bounds.
Oct 9 11:29:23 localhost nagios: SERVICE ALERT: 192.168.1.5;/usr;CRITICAL;SOFT;1;(Return code of 139 is out of bounds)
Oct 9 11:29:47 localhost kernel: sh[25254]: segfault at 00000000000000c0 rip 000000349e453784 rsp 00007fff64451030 error 4
Oct 9 11:29:53 localhost nagios: Warning: Return code of 139 for check of service '/opt' on host '192.168.1.6' was out of bounds.
Oct 9 11:29:53 localhost nagios: SERVICE ALERT: 192.168.1.6;/opt;CRITICAL;SOFT;1;(Return code of 139 is out of bounds)
Oct 9 11:30:13 localhost nagios: SERVICE ALERT: 192.168.1.4;/usr;OK;SOFT;2;DISK OK - free space: /usr 2448 MB (52% inode=92%):
Oct 9 11:30:15 localhost kernel: sh[25902]: segfault at 00000000000000c0 rip 000000349e453784 rsp 00007fff9f3dd530 error 4
Oct 9 11:30:15 localhost kernel: sh[25905]: segfault at 00000000000000c0 rip 000000349e453784 rsp 00007fffdd1ecdf0 error 4
Oct 9 11:30:23 localhost nagios: Warning: Return code of 139 for check of service 'current load' on host '192.168.1.7' was out of bounds.
Oct 9 11:30:23 localhost nagios: SERVICE ALERT: 192.168.1.7;current load;CRITICAL;SOFT;1;(Return code of 139 is out of bounds)
Oct 9 11:30:23 localhost nagios: Warning: Return code of 139 for check of service '/usr' on host '192.168.1.8' was out of bounds.
Oct 9 11:30:23 localhost nagios: SERVICE ALERT: 192.168.1.8;/usr;CRITICAL;SOFT;1;(Return code of 139 is out of bounds)
Oct 9 11:30:23 localhost nagios: SERVICE ALERT: 192.168.1.5;/usr;OK;SOFT;2;DISK OK - free space: /usr 1868 MB (39% inode=91%):
Oct 9 11:30:53 localhost nagios: SERVICE ALERT: 192.168.1.6;/opt;OK;SOFT;2;DISK OK - free space: /opt 160431 MB (66% inode=99%):
Oct 9 11:31:23 localhost nagios: SERVICE ALERT: 192.168.1.7;current load;OK;SOFT;2;OK - load average: 0.01, 0.02, 0.00
Oct 9 11:31:23 localhost nagios: SERVICE ALERT: 192.168.1.8;/usr;OK;SOFT;2;DISK OK - free space: /usr 1796 MB (38% inode=91%):
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: return code of 139 is out of bounds

Post by abrist »

There sure are a number of segfaults from sh (your shell).
How did you fix the bash bug? If you updated from a repo, can you check to see if there was an additional update released for bash since then? If you didn't update from repo - how did you update bash?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Locked