Bug 1263920

Summary:	journal-remote: systemd-journal-remote.service failed to restart
Product:	[Fedora] Fedora	Reporter:	Yu Watanabe <watanabe.yu>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	johannbg, jsynacek, lnykryn, msekleta, ssahani, s, systemd-maint, tcarter, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 17:55:06 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:
Embargoed:

Description Yu Watanabe 2015-09-17 05:48:23 UTC

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):

systemd-219-24.fc22.x86_64

How reproducible:

Always.

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
%%%%%%%%%
PartOf=systemd-journal-remote.service
%%%%%%%%%
This restarts the socket when restarting the service.

See also
https://github.com/systemd/systemd/pull/1286

Comment 1 Susant Sahani 2016-05-17 07:33:40 UTC

Fixed in https://github.com/systemd/systemd/pull/1286
https://github.com/systemd/systemd/commit/ef08ced6b44d4f56477a6798e56ba5c5c9e0023f

Comment 2 Fedora End Of Life 2016-07-19 17:55:06 UTC

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
bug.

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