Bug 1259034

Summary: systemd-journald __open_nocancel crash
Product: Red Hat Enterprise Linux 7 Reporter: Scott Poore <spoore>
Component: systemdAssignee: systemd-maint
Status: CLOSED CURRENTRELEASE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: jsynacek, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-23 08:45:06 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:
Embargoed:
Attachments:
Description Flags
abrt email none

Description Scott Poore 2015-09-01 19:50:17 UTC 
Description of problem:

abrt crash seen for systemd when beaker LOCALWATCHDOG timed out:

time:           Tue 01 Sep 2015 03:07:18 PM EDT
cmdline:        /usr/lib/systemd/systemd-journald
uid:            0 (root)
abrt_version:   2.1.11
backtrace_rating: 4
crash_function: __open_nocancel
event_log:      
executable:     /usr/lib/systemd/systemd-journald
hostname:       hp-ml350gen8-01.testrelm.test
kernel:         3.10.0-313.el7.x86_64
last_occurrence: 1441134438
pid:            822
pkg_arch:       x86_64
pkg_epoch:      0
pkg_name:       systemd
pkg_release:    12.el7
pkg_version:    219
pwd:            /
runlevel:       N 3
ureports_counter: 1
username:       root

Version-Release number of selected component (if applicable):
systemd-219-12.el7.x86_64

How reproducible:
unknown

Steps to Reproduce:
unknown

Actual results:
crash

Expected results:
no crash

Additional info:
Happened in same job as bug #1259031

Will append full crash email
Comment 1 Scott Poore 2015-09-01 19:51:08 UTC 
Created attachment 1069124 [details]
abrt email
Comment 4 Jan Synacek 2016-11-23 08:45:06 UTC 
There have been numerous journal fixes in RHEL-7.3. I believe this was a one-off error that doesn't happen in RHEL-7.3 anymore. If it reappears, feel free to reopen with up-to-date information.