Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #13715] Memory leak icinga-1.13.3 with mod_gearman 1.5.5 (libgearman 1.1.8) #1587

Closed
icinga-migration opened this issue Dec 21, 2016 · 9 comments
Labels

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/13715

Created by AndreWM on 2016-12-21 12:41:22 +00:00

Assignee: (none)
Status: Rejected (closed on 2016-12-22 16:46:58 +00:00)
Target Version: (none)
Last Update: 2017-01-17 13:37:59 +00:00 (in Redmine)

Icinga Version: 1.13.3
OS Version: Red Hat Enterprise Linux Server release 6.8 (Santiago)

Hello there!
We have the memory leak with icinga-core 1.13.3 via mod_gearman 1.5.5 (libgearman 1.1.8)
[root@icinga icinga-1.13.3]# pmap - x 55072 | head
55072: /usr/local/icinga/bin/icinga - d /usr/local/icinga/etc/icinga.cfg
Address Kbytes RSS Dirty Mode Mapping
0000000000400000 664 360 0 r-x-- icinga
00000000006a6000 4 4 4 rw--- icinga
00000000006a7000 44 44 44 rw--- [ anon ]
0000000001e5b000 68344 68296 68296 rw--- [ anon ]
0000000006119000 1756 1724 1724 rw--- [ anon ]
00007faa8c000000 132 4 4 rw--- [ anon ]
00007faa8c021000 65404 0 0 ----- [ anon ]
00007faa94000000 512 248 248 rw--- [ anon ]

In the String: 0000000001e5b000 68344 68296 68296 rw--- [ anon ]
column Dirty is growing up and isn't falling down i.e. we are watching memory leak of icinga working with mod_gearman module. This module starts up via broker (not via own config but via string broker_module=/usr/local/icinga/lib/mod_gearman/mod_gearman.o config=/etc/mod_gearman/mod_gearman_neb.conf in icinga.cfg )

Just to clarify we already have the variant with the latest version of headers.

@icinga-migration
Copy link
Author

Updated by mfrosch on 2016-12-21 13:30:58 +00:00

Have you had a try with valgrind? http://valgrind.org/docs/manual/quick-start.html

I'm not having any gearman environment myself.

Have you talked to the mod_gearman guys? https://mod-gearman.org/support.html

@icinga-migration
Copy link
Author

Updated by AndreWM on 2016-12-21 14:23:49 +00:00

mfrosch wrote:

Have you had a try with valgrind? http://valgrind.org/docs/manual/quick-start.html

I'm not sure

mfrosch wrote:

Have you talked to the mod_gearman guys? https://mod-gearman.org/support.html
I think yes. One of them suggested to try the old version here https://monitoring-portal.org/index.php?thread/37410-mod-gearman-and-icinga/ to my colleague

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-12-22 16:46:58 +00:00

  • Status changed from New to Rejected

mod_gearman is an external addon which we do not maintain. Memory leaks introduced by NEB modules cannot be avoided by the core itself, so I suggest to contact the addon developer about this possible leak.

@icinga-migration
Copy link
Author

Updated by AndreWM on 2017-01-09 07:33:50 +00:00

mfriedrich wrote:

mod_gearman is an external addon which we do not maintain.
Which addon do you maintain and can suggest then?

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2017-01-09 10:20:44 +00:00

I'm not sure what you mean.

@icinga-migration
Copy link
Author

Updated by AndreWM on 2017-01-09 11:28:31 +00:00

mfriedrich wrote:

I'm not sure what you mean.

I meant - which mod_gearman-like-application do you suggest to use? is there addon which supports icinga like mod_gearman supports nagios?

@icinga-migration
Copy link
Author

Updated by AndreWM on 2017-01-09 11:30:14 +00:00

P.S icinga 1.14.0 has the same problems with last stable mod_gearman

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2017-01-09 13:00:02 +00:00

mod_gearman is an external addon for Nagios/Icinga. Generally speaking, if you add any NEB module onto the core and it does not take care about proper memory handling, it may introduce memory leaks. Icinga Core itself as tested and released by us, does not introduce any.

Icinga 1.x itself doesn't provide any NEB modules, except for the IDOUtils module for the database backend. As said, I'd suggest to contact the mod_gearman developer and ask about possible leaks with specific functions. I don't have any test setup with mod_gearman around, and won't be of assistance here.

Kind regards,
Michael

@icinga-migration
Copy link
Author

Updated by AndreWM on 2017-01-17 13:37:59 +00:00

It seemed to work with libgearman 0.33. the memory leak has gone!!!
Thank you!
Close the ticket

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant