{"action":"opened","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/266","labels_url":"https://api.github.com/repos/systemd/systemd/issues/266/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/266/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/266/events","html_url":"https://github.com/systemd/systemd/issues/266","id":89068821,"number":266,"title":"syslog.socket in failed state after entering emergency mode","user":{"login":"mbiebl","id":3609611,"avatar_url":"https://avatars.githubusercontent.com/u/3609611?v=3","gravatar_id":"","url":"https://api.github.com/users/mbiebl","html_url":"https://github.com/mbiebl","followers_url":"https://api.github.com/users/mbiebl/followers","following_url":"https://api.github.com/users/mbiebl/following{/other_user}","gists_url":"https://api.github.com/users/mbiebl/gists{/gist_id}","starred_url":"https://api.github.com/users/mbiebl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbiebl/subscriptions","organizations_url":"https://api.github.com/users/mbiebl/orgs","repos_url":"https://api.github.com/users/mbiebl/repos","events_url":"https://api.github.com/users/mbiebl/events{/privacy}","received_events_url":"https://api.github.com/users/mbiebl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-06-17T16:49:29Z","updated_at":"2015-06-17T16:49:29Z","closed_at":null,"body":"When entering emergency mode e.g. due to a wrong fstab entry, I get the following log failure for syslog.socket:\r\n```\r\nJun 17 18:29:00 debian systemd[1]: syslog.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction is destructive.\r\nJun 17 18:29:00 debian systemd[1]: syslog.socket: Unit entered failed state.\r\n```\r\nI'm using ForwardToSyslog=yes and rsyslog is installed and configured for socket forward mode.\r\n\r\nAfaics, syslog.socket is active when emergency.service is activated. This triggers a log message and a start attempt for rsyslog.service. Since this would conflict with the ongoing transition, the start request fails and syslog.socket is marked as failed.\r\n\r\nA simple solution (which we have shipped in Debian for a while), is to add \r\n```\r\nConflicts=syslog.socket\r\n```\r\nto emergency.service. This ensures that syslog.socket is stopped when emergency mode is entered.\r\nFor systems, which use rsyslog-journal (i.e.  ForwardToSyslog=no and a syslogger which pulls from the journal directly), this is a nop.\r\n\r\n\r\nI can prepare a PR for this issue, but wanted to gather some feedback first, if this is the right approach.\r\n\r\n"}}