Bug 1399612

Summary: Job for systemd-journald.service failed because a fatal signal was delivered to the control process
Product: Red Hat Enterprise Linux 7 Reporter: SHAURYA <sshaurya>
Component: systemdAssignee: systemd-maint
Status: CLOSED INSUFFICIENT_DATA QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: fsumsal, kwalker, msekleta, muahao, nduffy, 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: 2019-06-17 19:51:26 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:
Bug Depends On:    
Bug Blocks: 1420851    
Attachments:
Description Flags
Systemctl strace none

Description SHAURYA 2016-11-29 12:24:28 UTC
Description of problem:

The Following command fails : 
 systemctl restart systemd-journald
Job for systemd-journald.service failed because a fatal signal was delivered to the control process. See "systemctl status systemd-journald.service" and "journalctl -xe" for details.
echo $? 
1

Where are you experiencing the behavior?  What environment?

RHEL 7.3

Version-Release number of selected component (if applicable):

systemd-219-30.el7_3.3.x86_64 

How reproducible:

Every time

Steps to Reproduce:


Steps to reproduce:

> install fresh System
> login to System
> execute the following command 

# systemctl restart systemd-journald
Job for systemd-journald.service failed because a fatal signal was delivered to the control process. See "systemctl status systemd-journald.service" and "journalctl -xe" for details.

# echo $? 
1

expected is a working command - this makes every puppet run fail.

Actual results:

Error should not come out

Expected results:

Should be able to restart systemd-journald

Additional info:

Comment 1 SHAURYA 2016-11-29 12:26:08 UTC
Created attachment 1225802 [details]
Systemctl strace

Comment 3 Michal Sekletar 2016-11-29 14:57:33 UTC
Please provide output of systemctl status systemd-journald.service after failed restart attempt.

Comment 12 David Tardon 2019-02-01 14:38:09 UTC
*** Bug 1388049 has been marked as a duplicate of this bug. ***

Comment 13 David Tardon 2019-02-06 07:29:34 UTC
*** Bug 1549149 has been marked as a duplicate of this bug. ***

Comment 14 Kyle Walker 2019-06-17 19:51:26 UTC
I am closing this bug as INSUFFICIENT_DATA as the initiating issue has been closed for nearly two years without further update. Please reopen this bug report in the event that this issue is observed with a recent release of systemd and further data can be provided.