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 #11085] Crash in ConfigItem::RunWithActivationContext #3897

Closed
icinga-migration opened this issue Feb 4, 2016 · 2 comments
Closed
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Feb 4, 2016

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11085

Created by gbeutner on 2016-02-04 12:17:32 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2016-02-04 12:19:54 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:47 +00:00 (in Redmine)

Icinga Version: 2.4.1
Backport?: Already backported
Include in Changelog: 1

$ icinga2 console
Icinga 2 (version: v2.4.1-168-g949b129)
<1> => f = function() { }
null
<2> => __run_with_activation_context(f)
information/ConfigItem: Committing config items
../lib/config/configitem.cpp:524: assertion failed: newItems.size() > 0
Caught SIGABRT.
Current time: 2016-02-04 13:15:09 +0100

critical/Application: Icinga 2 has terminated unexpectedly. Additional information can be found in '/Users/gunnar/i2/var/log/icinga2/crash/report.1454588109.206907'

Abort trap: 6

Changesets

2016-02-04 12:17:37 +00:00 by (unknown) c06f6d7

Fix crash in ConfigItem::RunWithActivationContext

fixes #11085

2016-02-23 08:36:17 +00:00 by (unknown) 6cd9317

Fix crash in ConfigItem::RunWithActivationContext

fixes #11085
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 4, 2016

Updated by Anonymous on 2016-02-04 12:19:54 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset c06f6d7.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2016

Updated by gbeutner on 2016-02-23 09:58:47 +00:00

  • Backport? changed from Not yet backported to Already backported
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.