Bug 969152
| Summary: | [abrt] libvirt-daemon-0.10.2.4-1.fc18: vasprintf: Process /usr/sbin/libvirtd was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ivan Makfinsky <ivan.makfinsky> | ||||||||||||||||||||||
| Component: | libvirt | Assignee: | Ján Tomko <jtomko> | ||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||
| Version: | 18 | CC: | berrange, clalancette, crobinso, itamar, jforbes, jtomko, jyang, laine, libvirt-maint, veillard | ||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||
| Whiteboard: | abrt_hash:3a33c9db59e4cbfcca53fef9711a93766f0e9e9e | ||||||||||||||||||||||||
| Fixed In Version: | libvirt-0.10.2.7-1.fc18 | Doc Type: | Bug Fix | ||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||
| Clone Of: | |||||||||||||||||||||||||
| : | 971904 (view as bug list) | Environment: | |||||||||||||||||||||||
| Last Closed: | 2013-08-15 02:54:56 UTC | Type: | --- | ||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||||||
| Bug Blocks: | 971904 | ||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||
|
Description
Ivan Makfinsky
2013-05-30 19:20:53 UTC
Created attachment 755017 [details]
File: backtrace
Created attachment 755018 [details]
File: cgroup
Created attachment 755019 [details]
File: core_backtrace
Created attachment 755020 [details]
File: dso_list
Created attachment 755021 [details]
File: environ
Created attachment 755022 [details]
File: limits
Created attachment 755023 [details]
File: maps
Created attachment 755024 [details]
File: open_fds
Created attachment 755025 [details]
File: proc_pid_status
Created attachment 755026 [details]
File: var_log_messages
Apparently I had udev_log="debug" in /etc/udev/udev.conf. I set the log to info and libvirtd service starts up normally. I found the solution here: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/968930 It shouldn't crash just because udev is logging debug messages. Upstream patch proposed: https://www.redhat.com/archives/libvir-list/2013-June/msg00349.html Now fixed upstream:
commit f753dd62f951cc62e164421d0c6491f39e4c68ad
Author: Ján Tomko <jtomko>
AuthorDate: 2013-06-07 11:55:27 +0200
Commit: Ján Tomko <jtomko>
CommitDate: 2013-06-14 13:17:27 +0200
udev: fix crash in libudev logging
Call virLogVMessage instead of virLogMessage, since libudev
called us with a va_list object, not a list of arguments.
Honor message priority and strip the trailing newline.
https://bugzilla.redhat.com/show_bug.cgi?id=969152
git describe: v1.0.6-76-gf753dd6
libvirt-0.10.2.7-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/libvirt-0.10.2.7-1.fc18 Package libvirt-0.10.2.7-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libvirt-0.10.2.7-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-14066/libvirt-0.10.2.7-1.fc18 then log in and leave karma (feedback). libvirt-0.10.2.7-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |