Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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.
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: