Bug#757696: [systemd] systemd: writes messages to kmsg

[Michael Biebl]

forcemerge 748648 757696
thanks

Am 10.08.2014 18:30, schrieb Török Edwin:
> Package: systemd
> Version: 208-7
> Severity: normal
> 
> --- Please enter the report below this line. ---
> 
> systemd is writing messages to kmsg:
> 
> $ dmesg -x
> auth  :err   : [   27.565727] systemd-logind[3382]: Failed to enable subscription: No such method 'Subscribe'
> auth  :info  : [   27.566597] systemd-logind[3382]: New seat seat0.
> auth  :info  : [   27.567357] systemd-logind[3382]: Watching system buttons on /dev/input/event1 (Power Button)
> auth  :info  : [   27.567475] systemd-logind[3382]: Watching system buttons on /dev/input/event0 (Power Button)
> auth  :err   : [   27.570542] systemd-logind[3382]: Failed to start unit user at 1000.service: Unknown unit: user at 1000.service
> auth  :err   : [   27.570555] systemd-logind[3382]: Failed to start user service: Unknown unit: user at 1000.service
> auth  :info  : [   27.572213] systemd-logind[3382]: New session 2 of user edwin.
> auth  :info  : [   27.572249] systemd-logind[3382]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
> auth  :err   : [  841.498260] systemd-logind[3382]: Failed to start unit user at 65534.service: Unknown unit: user at 65534.service
> auth  :err   : [  841.498272] systemd-logind[3382]: Failed to start user service: Unknown unit: user at 65534.service
> auth  :info  : [  841.499580] systemd-logind[3382]: New session c1 of user nobody.
> auth  :err   : [  841.517534] systemd-logind[3382]: Failed to abandon scope session-c1.scope
> auth  :err   : [  841.517542] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope
> auth  :info  : [  841.524278] systemd-logind[3382]: New session c2 of user nobody.
> auth  :err   : [  841.537574] systemd-logind[3382]: Failed to abandon scope session-c2.scope
> auth  :err   : [  841.537583] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope
> auth  :info  : [  841.545551] systemd-logind[3382]: New session c3 of user nobody.
> auth  :err   : [  900.432607] systemd-logind[3382]: Failed to abandon scope session-c3.scope
> auth  :err   : [  900.432618] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope
> 
> There are several things wrong here:
> - it is the only userspace application that does that on a regular basis
> - the :info messages have nothing to do in kmsg. They are not something that you should act on, so why spam kmsg with useless messages like that? Write them to syslog where they belong
> - I might understand the :err messages if they would really indicate a serious error. But IMHO these messages should be :warn, or something less severe. Is there something that I should do
> based on those messages? Is something broken now? (well Networkmanager is, but thats a separate bug)
> - more importantly the :err messages are NOT logged to syslog at all. grep /var/log/* for 'Failed to abandon scope session-c2.scope' comes up empty. So I'm really confused on the purpose of these messages:
> on one hand they are logged to a place usually reserved for things like networking messages, coredumps, yet it is not logged in any persistent place, so they would go unnoticed by logwatch probably, etc.
> - if systemd would at some point log an important message it'd probably go unnoticed since I'd be used to ignoring messages from systemd in dmesg, and they are not in /var/log/*
> 
> The code that logs to kmsg seems to be write_to_kmsg in src/shared/log.c.
> 
> FWIW I have sysvinit-core and systemd-shim installed (I don't see that info appended by the bug script).
> 

That's a problem of running logind standalone.

The systemd log infrastructure uses the kernel ring buffer only during
early boot. As soon as the journal is available, the log messages are
logged to the journal.
The problem here is, that systemd-shim doesn't provide the journal
functionality, so the systemd components (like logind) continue to use
the kernel ring buffer (kmsg).

I'm inclined to re-assign this bug to systemd-shim, as this bug is
caused by running logind under systemd-shim and the shim failing to
provide that logging infrastructure.


In any case, merging with the existing bug report.



-- 
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: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140810/93327a40/attachment-0002.sig>