Bug 1322617

Summary: systemd-journald killed by SIGABRT
Product: Red Hat Enterprise Linux 7 Reporter: Robbie Harwood <rharwood>
Component: systemdAssignee: systemd-maint
Status: CLOSED INSUFFICIENT_DATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: bblaskov, jsynacek, msekleta, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-25 13:27:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
abrt directory tarball none

Description Robbie Harwood 2016-03-30 22:00:08 UTC
Created attachment 1141945 [details]
abrt directory tarball

I don't have a huge amount of context for this one: I booted my RHEL-7.2 VM and abrt complained about this.

Please find ccpp data attached.

Comment 2 Lukáš Nykrýn 2016-03-31 07:35:06 UTC
looks like this https://bugzilla.redhat.com/show_bug.cgi?id=1300212

Comment 3 Robbie Harwood 2016-03-31 15:47:32 UTC
(In reply to Lukáš Nykrýn from comment #2)
> looks like this https://bugzilla.redhat.com/show_bug.cgi?id=1300212

Makes sense.  Not sure if this caused it, but this was on a VM while the host was `pm-suspend`ed and resumed probably several times.

Comment 4 Robbie Harwood 2016-04-07 19:56:42 UTC
The problem has recurred.  I can attach another abrt directory if that's helpful.

Comment 5 Michal Sekletar 2016-04-08 08:27:07 UTC
(In reply to Lukáš Nykrýn from comment #2)
> looks like this https://bugzilla.redhat.com/show_bug.cgi?id=1300212

I don't think it is the same problem. From abrt data I can see that journal daemon, at the time of the crash, didn't have any actual on-disk file mmap-ed, Only run time journal was in use.

Comment 6 Jan Synacek 2017-01-25 13:27:21 UTC
There's not much we can do with no context.