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 #11061] Icinga 2 sometimes suddenly stops running #3887
Comments
Updated by mfriedrich on 2016-02-01 14:13:08 +00:00
Please look into the crash log directory (provided that you've installed gdb). Which distribution and which packages are used. Please add the output of "icinga2 --version". |
Updated by mfriedrich on 2016-02-01 14:13:49 +00:00
|
Updated by GreenRover on 2016-02-01 14:19:46 +00:00
Ok i installed icinga2-dbg now and will provide the new crash log when generated. But actually attached the crash logs i found in folder without dbg
|
Updated by GreenRover on 2016-03-01 09:03:58 +00:00
Here a new crash report:
|
Updated by jflach on 2016-03-02 10:30:28 +00:00 Can you turn on the debuglog (icinga2 feature enable debuglog), wait for it to crash and then provide a fitting excerpt from this log please? It looks like some api requests are crashing icinga2 with no survivors, so we need to know which. |
Updated by mfriedrich on 2016-03-18 14:25:11 +00:00 We've fixed a couple of issues with such crashes in 2.4.2+. Please re-test with 2.4.4. |
Updated by mfriedrich on 2016-04-22 09:04:46 +00:00
We believe this has been fixed in the current stable release. |
Updated by prdatur on 2016-11-26 12:50:54 +00:00
Hello, This problem still exists in version r2.5.3-1 I have attached the crashlog Best regards, |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11061
Created by GreenRover on 2016-01-30 05:39:32 +00:00
Assignee: (none)
Status: Closed (closed on 2016-04-22 09:04:46 +00:00)
Target Version: (none)
Last Update: 2016-11-26 12:50:53 +00:00 (in Redmine)
I dont know why but my icinga2 installations stops from time to time by its self.
That is the error message:
And the matching syslog entry:
Can i provide any other helpfull informations?
Attachments
The text was updated successfully, but these errors were encountered: