I have upgraded Nagios from 4.2.4 to 4.3.1 (luckily only on my development box) and now it crashes with a SIGSEGV / SIGTERM repeatedly (about once a minute).
For me it looks like a problem when a broker_module sends data "back" to nagios.
I base this on the following facts.
1) If I disable both (mod_gearman & mk-livestatus) in nagios.cfg, everything works OK.
2) If I enable mk-livestatus, but I do not feed data back to nagios (thruk - business processes) through mk-livestatus, it still works OK
3) If I enable mod_gearman or I let thruk feed data back to nagios through mk-livestatus it starts crashing.
Sadly, the only thing I can see in the nagios-log are:
Caught SIGSEGV, shutting down...
Caught SIGTERM, shutting down...
In the debug-log I do not see anything strange.
Here are my SW releases:
OS: RHEL 7.3
Nagios 4.3.1 (build from source)
mod_gearman 3.0.1-1 (labs.consol.de)
gearmand 0.33-5 (labs.consol.de)
mk-livestatus 1.2.8p18 (build from source)
Anybody out there using Nagios 4.3.1 with either mod_gearman and/or mk-livestatus?