Bug 1399612 - Job for systemd-journald.service failed because a fatal signal was delivered to the control process
Summary: Job for systemd-journald.service failed because a fatal signal was delivered ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
: 1388049 1549149 (view as bug list)
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2016-11-29 12:24 UTC by SHAURYA
Modified: 2020-08-13 08:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-17 19:51:26 UTC
Target Upstream Version:


Attachments (Terms of Use)
Systemctl strace (111.36 KB, text/plain)
2016-11-29 12:26 UTC, SHAURYA
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.