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 #13371] icinga2 libbase segfault #4816
Comments
Updated by arno on 2016-11-30 14:15:49 +00:00
Update Since we are having some sensitive data (passwords in plaintext) in our icinga2 core dump, Please find icinga2-satellite04-backtrace.txt (the backtrace only) is attached. Edit:
Please let me know if there any piece of information we can give you in order to help troubleshoot/find the cause of the problem. Kind regards, |
Updated by mfriedrich on 2016-12-05 09:56:01 +00:00
|
Updated by mfriedrich on 2016-12-05 09:56:14 +00:00
|
Updated by gbeutner on 2016-12-06 07:29:07 +00:00
After careful examination I believe that this is a duplicate of #12718, i.e. it should already be fixed in the master branch. Can you re-test this with the current snapshots? |
Updated by arno on 2016-12-12 14:33:18 +00:00 Hello, we are waiting for the release of 2.6.0. Is there any approximate date when 2.6.0 is going to be released? Thanks, Andrey Arapov |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13371
Created by arno on 2016-11-30 13:37:13 +00:00
Assignee: (none)
Status: Rejected (closed on 2016-12-06 07:29:07 +00:00)
Target Version: (none)
Last Update: 2016-12-12 14:33:18 +00:00 (in Redmine)
Dear Icinga2 devs,
we are getting icinga2 segfault almost every week.
you could possibly link this report with https://dev.icinga.com/issues/12650
we have followed the doc https://docs.icinga.com/icinga2/latest/doc/module/icinga2/toc\#!/icinga2/latest/doc/module/icinga2/chapter/development#development-debug-core-dump in order to enable core dumps.
We have the core dump files from two icinga2 satellite servers in size 90MiB and 72MiB (gzipped)
Please let me know where could I securely upload the core dump files for the analysis. (or send it in private)
Kind regards,
Andrey Arapov
Attachments
Relations:
The text was updated successfully, but these errors were encountered: