glibc detected *** /usr/bin/mod_gearman2_worker: double free

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
abhishek
Posts: 20
Joined: Fri Oct 21, 2016 12:24 pm

glibc detected *** /usr/bin/mod_gearman2_worker: double free

Post by abhishek »

Hi,
I am facing one issue in my all Mod_gearman_Worker's which are below. kind help me over come from this issue.


mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x0000000002326180 ***
mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x00000000023260e0 ***
mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x0000000002325f60 ***
mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x00000000023e4950 ***
mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x00000000023260e0 ***
mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x0000000002325f60 ***
mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x00000000023e4950 ***
mod_gearman2_worker: *** glibc detected *** /usr/bin/mod_gearman2_worker: double free or corruption (!prev): 0x00000000023264c0 ***
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: glibc detected *** /usr/bin/mod_gearman2_worker: double

Post by rkennedy »

I believe this issue is actually with gearmand trying to bind to IPv6 - it was solved based on a customer post here - https://support.nagios.com/forum/viewto ... 91#p146439

Code: Select all

According to my good friend "Google" it appears that if gearmand can't bind to an IPV6 socket it won't start.
https://bugs.launchpad.net/gearmand/+bug/1134534

The workaround is to add the -L <X.X.X.X> option to force it to bind to IPV4
I've done this and gearmand service starts OK now and gearman_top displays OK - only if I pass the IP address - eg: gearman_top -H X.X.X.X

This was a problem with gearmand 1.0.3 - gearmand 1.1.8 is installed and it's still a problem?

Considering I am using a standard Nagios supplied VM , why is there no mention of this in the Integrating Mod-Gearman With Nagios XI document.

BTW - I also just found out the hard way that you alos need to replace 'localhost' with the server IP address in the mod_gearman_neb.conf & /mod_gearman_worker.conf files

regards... Fred
Former Nagios Employee
Locked