New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #10783] segfault in libremote.so #3751
Comments
Updated by mfriedrich on 2015-12-07 13:52:55 +00:00
|
Updated by mfriedrich on 2015-12-07 13:57:40 +00:00
Can you run icinga 2 with gdb (gdb --args /usr/lib64/icinga2/sbin/icinga2 daemon and then 'run')? |
Updated by mfriedrich on 2015-12-07 14:00:49 +00:00
|
Updated by mnardin on 2015-12-08 08:15:22 +00:00 Here are the additional information:
gdb
bt
from /usr/lib64/icinga2/libremote.so
from /usr/lib64/icinga2/libbase.so
No symbol table info available.
from /usr/lib64/icinga2/libremote.so
No symbol table info available.
No symbol table info available.
No symbol table info available.
from /usr/lib64/icinga2/libbase.so
No symbol table info available.
No symbol table info available.
No symbol table info available.
No symbol table info available.
No symbol table info available.
No symbol table info available. |
Updated by gbeutner on 2015-12-10 08:45:18 +00:00 Can you please install the debug symbols (i.e. by installing the "icinga2-debuginfo" package) and re-run icinga2 with gdb? |
Updated by elimat on 2015-12-16 06:57:02 +00:00 Hi, I just wanted to inform I have similar issue with icinga2 crashing with below segfault error: Dec 15 17:13:05 prod-icinga01 kernel: icinga2[3260]: segfault at 0 ip 00002adb1291b892 sp 00002adb4c801720 error 4 in libremote.so[2adb12828000+191000] I started to get this after trying the icinga-dashing through API to icinga2. I suspect it have something to do with the API. |
Updated by tgelf on 2015-12-22 11:44:33 +00:00
Hi Gunnar, did the bt help, should a current snapshot fix this? Thanks, |
Updated by viniciusfs on 2016-01-06 11:02:23 +00:00 elimat wrote:
Same behaviour here after trying icinga-dashing. |
Updated by viniciusfs on 2016-01-06 17:22:34 +00:00
|
Updated by gbeutner on 2016-02-09 08:13:25 +00:00
This is most likely the same bug like #11006. |
Updated by gbeutner on 2016-02-09 08:13:34 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10783
Created by mnardin on 2015-12-07 13:31:15 +00:00
Assignee: gbeutner
Status: Rejected (closed on 2016-02-09 08:13:25 +00:00)
Target Version: (none)
Last Update: 2016-02-09 08:13:25 +00:00 (in Redmine)
Hi,
we just started installing a new icinga2 environment. The setup has 2 master and 2 zones (2 satellites + 1 satellite).
At the moment we just have configured the zones.conf file on all nodes and the ido-feature on the 2 masters.
That means that we have still the example config in conf.d included on all nodes. The setup will feature a config master when the setup is completed.
We use puppet to ensure the running state of the icinga2 service on all servers.
We have noticed that in some way the problem could be related to the service status query during the puppet agent run.
See the following log extract as example:
This are the all the relevant log lines on the impacted servers:
Since the installation only the 2 hosts (icingam01-p, icinga01-d) didn't crash.
What other information should I provide?
Thanks
Mirko
Relations:
The text was updated successfully, but these errors were encountered: