Skip to content
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

Closed
icinga-migration opened this issue Nov 30, 2016 · 5 comments
Closed

[dev.icinga.com #13371] icinga2 libbase segfault #4816

icinga-migration opened this issue Nov 30, 2016 · 5 comments
Labels
bug Something isn't working

Comments

@icinga-migration
Copy link

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)

Icinga Version: 2.5.4
Backport?: Not yet backported
Include in Changelog: 1

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:

@icinga-migration
Copy link
Author

Updated by arno on 2016-11-30 14:15:49 +00:00

  • File added icinga2-satellite04-backtrace.txt

Update

Since we are having some sensitive data (passwords in plaintext) in our icinga2 core dump,
I will post here the backtrace at the moment.

Please find icinga2-satellite04-backtrace.txt (the backtrace only) is attached.

Edit:

[Wed Nov 30 10:06:16 2016] icinga2[414]: segfault at 28 ip 00002af76cc55ec2 sp 00002af78dd0ec50 error 4 in libbase.so[2af76cb04000+1e5000]
-rw-------.  1 icinga icinga 450M Nov 30 10:06 core.icinga2.27689

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,
Andrey Arapov

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-12-05 09:56:01 +00:00

  • Relates set to 12718

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-12-05 09:56:14 +00:00

  • Relates set to 13151

@icinga-migration
Copy link
Author

Updated by gbeutner on 2016-12-06 07:29:07 +00:00

  • Status changed from New to Rejected

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?

@icinga-migration
Copy link
Author

Updated by arno on 2016-12-12 14:33:18 +00:00

Hello,

we are waiting for the release of 2.6.0.
So we can confirm only after 2.6.0 is released.

Is there any approximate date when 2.6.0 is going to be released?

Thanks,

Andrey Arapov

@icinga-migration icinga-migration added bug Something isn't working libbase labels Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant