4.4.2 upgrade and mod_gearman

[delboy1966]

Hi All

I have updated Nagios to 4.4.2 from 4.3.4 and now have an issue that i have encountered before, but with this forums help I was able to resolve it.

When I updated and restarted Nagios after about 15 seconds it exits without logging anything.
When I comment out the line

broker_module=/usr/lib64/mod_gearman_nagios4.o config=/usr/local/etc/mod_gearman/module.conf

And restart Nagios, all is fine.

Now I had this issue previously, https://support.nagios.com/forum/viewto ... =7&t=45491
But followed the advice given and all was fine.

In this instance I have recompiled mod_gearman with the Nagios 4.4.2 headers as I did previously but on this occasion it hasn't worked.
Has anyone updated to 4.4.2 with mod_gearman? Did you have any issues?

Thanks in advance
Tony

[delboy1966]

Some further info

I upped the debug level and run started Nagios using strace I got

lseek(6, 0, SEEK_CUR) = 700558
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3661, ...}) = 0
write(6, "[1535446508.677893] [001.0] [pid"..., 66) = 66
lseek(6, 0, SEEK_CUR) = 700624
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3661, ...}) = 0
write(6, "[1535446508.678003] [001.0] [pid"..., 66) = 66
lseek(6, 0, SEEK_CUR) = 700690
write(6, "[1535446508.678100] [064.1] [pid"..., 69) = 69
lseek(6, 0, SEEK_CUR) = 700759
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)



But still no further info in the log file as to why it stopped.

[delboy1966]

I have found there is a compatibility issue between mod_gearman and Nagios 4.4.x

https://github.com/sni/mod_gearman/issues/136

[scottwilkerson]

I have found there is a compatibility issue between mod_gearman and Nagios 4.4.x

https://github.com/sni/mod_gearman/issues/136

Yes, currently mod_gearman is not compatible with Core 4.4.x