[Pkg-systemd-maintainers] Bug#731742: Bug#731742: systemd will not start syslog.socket. This causes rsyslogd to not start

[Michael Biebl]

Am 03.03.2014 23:02, schrieb Eric Cooper:
> -> Unit rsyslog.service:
> 	Description: System Logging Service
> 	Instance: n/a
> 	Unit Load State: loaded
> 	Unit Active State: active
> 	Inactive Exit Timestamp: Mon 2014-03-03 16:41:25 EST
> 	Active Enter Timestamp: Mon 2014-03-03 16:41:25 EST
> 	Active Exit Timestamp: n/a
> 	Inactive Enter Timestamp: n/a
> 	GC Check Good: yes
> 	Need Daemon Reload: no
> 	Name: syslog.service
> 	Name: rsyslog.service
> 	Fragment Path: /lib/systemd/system/rsyslog.service
> 	Condition Timestamp: Mon 2014-03-03 16:41:25 EST
> 	Condition Result: yes
> 	Requires: syslog.socket
> 	Requires: basic.target
> 	Conflicts: shutdown.target
> 	Before: shutdown.target
> 	After: syslog.socket
> 	After: basic.target
> 	TriggeredBy: syslog.socket
> 	References: syslog.socket
> 	References: basic.target
> 	References: shutdown.target
> 	ReferencedBy: syslog.socket
> 	StopWhenUnneeded: no
> 	RefuseManualStart: no
> 	RefuseManualStop: no
> 	DefaultDependencies: yes
> 	OnFailureIsolate: no
> 	IgnoreOnIsolate: no
> 	IgnoreOnSnapshot: no
> 	ControlGroup: cpu:/system/rsyslog.service
> 	ControlGroup: name=systemd:/system/rsyslog.service
> 	Service State: running
> 	Result: success
> 	Reload Result: success
> 	PermissionsStartOnly: no
> 	RootDirectoryStartOnly: no
> 	RemainAfterExit: no
> 	GuessMainPID: yes
> 	Type: notify
> 	Restart: no
> 	NotifyAccess: main
> 	Main PID: 1375
> 	Main PID Known: yes
> 	Main PID Alien: no
> 	KillMode: control-group
> 	KillSignal: SIGTERM
> 	SendSIGKILL: yes
> 	UMask: 0022
> 	WorkingDirectory: /
> 	RootDirectory: /
> 	NonBlocking: no
> 	PrivateTmp: no
> 	ControlGroupModify: no
> 	ControlGroupPersistent: yes
> 	PrivateNetwork: no
> 	IgnoreSIGPIPE: yes
> 	LimitNOFILE: 4096
> 	StandardInput: null
> 	StandardOutput: null
> 	StandardError: inherit
> 	-> ExecStart:
> 		Command Line: /usr/sbin/rsyslogd -n
> 			PID: 1375
> 			Start Timestamp: Mon 2014-03-03 16:41:25 EST


I don't see a "WantedBy: multi-user.target", which you should have if
the service is properly enabled.

Could you paste the output again of

ls -la /etc/systemd/system/syslog.service
and
/etc/systemd/system/multi-user.target.wants/

While your i-s-h log shows:
> ==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
> /etc/systemd/system/multi-user.target.wants/rsyslog.service
> /etc/systemd/system/syslog.service

i.e. the service should have been properly enabled by i-s-h
Your debug log doesn't show a dependency cycle (which could have caused
a service to be removed) and since it doesn't show any sign of
rsyslog.service being pulled in, my guess is, the
etc/systemd/system/multi-user.target.wants/rsyslog.service symlink is
missing.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140305/dc9e77eb/attachment-0002.sig>