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 #11352] Segmentation fault during 'icinga2 daemon -C' #4019

Closed
icinga-migration opened this issue Mar 10, 2016 · 5 comments
Closed
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Mar 10, 2016

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

Created by pfennigk on 2016-03-10 12:10:15 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2016-03-14 07:40:03 +00:00)
Target Version: 2.4.4
Last Update: 2016-03-15 12:19:38 +00:00 (in Redmine)

Icinga Version: 2.4.3+snapshot2016.03.08+2~wheezy amd64
Backport?: Already backported
Include in Changelog: 1

We receive a 'segmentation fault' message during a configuration check. Here are the last lines of output:

information/ConfigItem: Committing config items
Speicherzugriffsfehler

Some operating figures of our environment, before we receive the segmenation fault:

  • defined hosts: ~1900
  • defined services: ~10500
  • defined notifications: ~18000
  • (OS & Hardware: Debian Wheezy 7.9, amd64, 32 GB RAM, 8xCPU)

The time needed for a configuration check with these figures was about 50 seconds.

After adding 120 hosts, 2000 services and 2000 notifications, we got the segmenation fault.

No logs are written, features mainlog and debuglog are enabled.

Attachments

Changesets

2016-03-14 07:37:13 +00:00 by (unknown) a8ee6b2

Fix crash in ScheduledDowntime::TimerProc

fixes #11352

2016-03-15 12:15:57 +00:00 by (unknown) 4c7b5f7

Fix crash in ScheduledDowntime::TimerProc

fixes #11352
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 10, 2016

Updated by mfriedrich on 2016-03-10 12:17:16 +00:00

  • Status changed from New to Feedback
  • Assigned to set to pfennigk

Run it with gdb and generate a full backtrace for this issue, please.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 10, 2016

Updated by pfennigk on 2016-03-10 14:09:11 +00:00

  • File added icinga2_gdb_full_backtrace.txt

here ist the backtrace.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 14, 2016

Updated by gbeutner on 2016-03-14 07:37:48 +00:00

  • Status changed from Feedback to Assigned
  • Assigned to changed from pfennigk to gbeutner
  • Target Version set to 2.4.4
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 14, 2016

Updated by Anonymous on 2016-03-14 07:40:03 +00:00

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

Applied in changeset a8ee6b2.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 15, 2016

Updated by mfriedrich on 2016-03-15 12:19:38 +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.