Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #12022] Icinga crashes when using include_recursive in an object definition #4313
This issue has been migrated from Redmine: https://dev.icinga.com/issues/12022
Created by bebehei on 2016-06-22 13:57:56 +00:00
I tested a configuration change at our system with an include_recursive. It turns out to make icinga2 crash with SIGABRT.
Steps to reproduce are simple:
It will not crash, if there is no file inside the include_recursive from the host. In my case: If there is no file inside
If this is not supported, it would be great, icinga would show me this without a SIGABRT.
Answering the question Why are you supposed to use icinga2 this way? I want to generate the icinga2 host information automated via saltstack. I thought putting the single bits in serperate files might prevent some special cases, where if e.g. a harddrive dies and is not recognized by the system anymore and I regenerate the configuration without seperate files, icinga would not miss the harddrive anymore.
2016-06-22 15:01:36 +00:00 by gbeutner 906ab61
Updated by bebehei on 2016-06-22 14:18:50 +00:00
Of course I could. Could you please provide some information, how to do it? I'm not that experienced with gdb. I only find examples, which want to use gcore with the specific PID. But icinga2 crashes on startup.
BTW: Have you seen the stacktrace in failure-log.txt?
Updated by mfriedrich on 2016-06-22 14:22:24 +00:00
Once the crash again happens, icinga2 will invoke gdb in order to generate such automatically. If you prefer to run icinga2 yourself inside gdb, there's also information on the docs for that.
Updated by gbeutner on 2016-06-22 14:31:41 +00:00
Updated by bebehei on 2016-06-22 14:33:11 +00:00
Generated a complete core. This file is about ~650MB big!?
Updated by gbeutner on 2016-06-22 14:53:57 +00:00
We don't need the core dump - in fact you should probably remove it because it contains a copy of icinga2's memory (including parts of your config). We just need a new report.* file after you've installed GDB.
However, I have already been able to reproduce this here locally as you can see from the stacktrace I posted earlier.