Page 1 of 1

nrpe 3.1.0 libc issue

Posted: Mon Jun 26, 2017 5:30 am
by emjga
Folks

Was upgrading from NRPE 2.12 to 3.1.0
Most of the plugins seem to work fine however one kept on dying on the following

kernel: nrpe[19674] general protection ip:382a847946 sp:7ffc6da7d960 error:0 in libc-2.12.so[382a800000+18a000]

check_linux_stats.pl

If I run check_linux_stats on the machine it self , it worked fine but using nrpe the plugin would die with the above error.
Reverting back to NRPE 2.12 the above plugin works fine.

OS redHat 6.8

Any idea's

Re: nrpe 3.1.0 libc issue

Posted: Mon Jun 26, 2017 12:48 pm
by ssax
Please attach your check_linux_stats.pl plugin so that we can make sure that we have the same plugin to test with, I see a few different versions of that.


Thank you

Re: nrpe 3.1.0 libc issue

Posted: Tue Jun 27, 2017 2:11 am
by emjga
ssax wrote:Please attach your check_linux_stats.pl plugin so that we can make sure that we have the same plugin to test with, I see a few different versions of that.


Thank you
Attached is version 1.5

It only seemed to fail on the CPU check.
However if I ran the plugin directly on the remote machine , it worked fine.

Matt

Re: nrpe 3.1.0 libc issue

Posted: Tue Jun 27, 2017 1:45 pm
by tgriep
I did a test with the NRPE Agent but a newer version 3.1.1 and running the command worked without any errors.
What version of the check_nrpe plugin were you using in the Nagios server to test the command?
Can you post how the command was setup in the nrpe.cfg file?
How was the NRPE Agent installed on the remote system, was it compiled or an RPM was used?

Re: nrpe 3.1.0 libc issue

Posted: Wed Jun 28, 2017 8:33 am
by emjga
Indeed I see a newer version 3.2.0
Changelog does not say anything about LibC issues but after installing it the issue goes away.

Thanks

Matt

Re: nrpe 3.1.0 libc issue

Posted: Wed Jun 28, 2017 10:30 am
by tmcdonald
Good to hear! Are we okay to close this up?

Re: nrpe 3.1.0 libc issue

Posted: Wed Jun 28, 2017 10:33 am
by emjga
tmcdonald wrote:Good to hear! Are we okay to close this up?
Indeed we are , thanks for the help and point in the right direction.