Bug 1263920 - journal-remote: systemd-journal-remote.service failed to restart
journal-remote: systemd-journal-remote.service failed to restart
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
All Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-09-17 01:48 EDT by Yu Watanabe
Modified: 2016-07-19 13:55 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 13:55:06 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Yu Watanabe 2015-09-17 01:48:23 EDT
Description of problem:

When systemd-journal-remote.service stops, the socket entered failed state (see below). So, it is necessary to restart the socket if we want to restart.
This problem also hits when we update systemd. When updating systemd, 'systemctl daemon-reexec' command is called in the post-script. This restarts only services, not sockets. So after the updating process, systemd-journal-remote.service is in the failed state.

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


How reproducible:


Steps to Reproduce:
1. systemctl restart systemd-journal-remote.service


1. systemctl start systemd-journal-remote.service
2. dnf update systemd

Actual results:

systemd[1]: Stopping Journal Remote Sink Service...
systemd[1]: systemd-journal-remote.socket: Got POLLHUP on a listening socket. The service probably invoked shutdown() on it, and should better not do that.
systemd[1]: Unit systemd-journal-remote.socket entered failed state.
systemd[1]: Started Journal Remote Sink Service.
systemd[1]: Starting Journal Remote Sink Service...
systemd[1]: systemd-journal-remote.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Unit systemd-journal-remote.service entered failed state.
systemd[1]: systemd-journal-remote.service failed.

Expected results:

systemd-journal-remote.service can restart.

Additional info:

A workaround of this bug is putting the following line in /usr/lib/systemd/system/systemd-journal-remote.socket
This restarts the socket when restarting the service.

See also
Comment 2 Fedora End Of Life 2016-07-19 13:55:06 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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