Nagios Support Forum

Moderator Edit: This thread has been split from another - https://support.nagios.com/forum/viewto ... =7&t=35982
In the future, please create a new thread and link to the old one instead of adding on.

Am also getting the same error, but am using the latest version of nagios core 4.3.2

*************************************************
Sep 15 01:12:55 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:12:55 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:12:56 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:12:57 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:12:58 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:12:59 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:13:00 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:13:01 monitor nagios: job 99 (pid=23992): read() returned error 11
Sep 15 01:13:02 monitor nagios: wproc: 'Core Worker 23496' seems to be choked. ret = -1; bufsize = 996752: written = 722880; errno = 32 (Broken pipe)
Sep 15 01:13:02 monitor nagios: Unable to run check for service 'mysql_longqueries' on host 'node2'
Sep 15 01:13:02 monitor nagios: wproc: iocache_read() from Core Worker 23496 returned -1: Connection reset by peer
Sep 15 01:13:02 monitor nagios: wproc: Socket to worker Core Worker 23496 broken, removing
Sep 15 01:13:02 monitor nagios: Caught SIGSEGV, shutting down...
***************************************************************

Please turn on debugging in nagios.cfg. Set debug_level to -1 and debug_verbosity to 2. Then, restart nagios(service nagios restart).

Now, when you see the read() returned error 11 appear please run ps uw -C nagios, and see which PID is taking up the most resources. Run gdb -p pid (install gdb if needed with yum install gdb, and replace pid with the #). Now, run bt and post the results of the backtrace here.

Are you using mk_livestatus, mod_gearman or some other "plugin"?
Reason for me asking is that with Nagios-4 these plugins does have some issues causing Nagios to SIGSEGV.

Thanks for the input danjoh! kabileshPR, can you confirm?