Red Hat Bugzilla – Bug 1263920
journal-remote: systemd-journal-remote.service failed to restart
Last modified: 2016-07-19 13:55:06 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):
Steps to Reproduce:
1. systemctl restart systemd-journal-remote.service
1. systemctl start systemd-journal-remote.service
2. dnf update systemd
systemd: Stopping Journal Remote Sink Service...
systemd: systemd-journal-remote.socket: Got POLLHUP on a listening socket. The service probably invoked shutdown() on it, and should better not do that.
systemd: Unit systemd-journal-remote.socket entered failed state.
systemd: Started Journal Remote Sink Service.
systemd: Starting Journal Remote Sink Service...
systemd: systemd-journal-remote.service: main process exited, code=exited, status=1/FAILURE
systemd: Unit systemd-journal-remote.service entered failed state.
systemd: systemd-journal-remote.service failed.
systemd-journal-remote.service can restart.
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.
Fixed in https://github.com/systemd/systemd/pull/1286
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.