Bug#781602: systemd: Invalid DBus call causes systemd to stop responding to DBus alltogether

[Michael Biebl]

Am 31.03.2015 um 15:52 schrieb Christian Seiler:
> Package: systemd
> Version: 215-12
> Severity: normal
> 
> Dear Maintainers,
> 
> while I was trying to set a different log level for systemd via DBus, I
> accidentally forgot that the 'Set' method for DBus properties expects a
> variant as a data type. So when using the following (wrong) command:
> 
> dbus-send --print-reply --system --dest=org.freedesktop.systemd1 \
>     /org/freedesktop/systemd1 org.freedesktop.DBus.Properties.Set \
>     string:org.freedesktop.systemd1.Manager string:LogLevel \
>     string:info
> 
> It won't complete (no answer is given) and systemd stops responding to
> DBus alltogether (at least on the systemd bus, the private socket is
> apparently still working, and systemd itself still does things, so it
> isn't completely crashed).
> 
> The only thing (besides a reboot) that could make systemd respond to
> DBus again was
> 

Hm, that's indeed nasty. Have you tried if v219 is affected by this as
well? If so, it would be worth raising this upstream.

Michael

-- 
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/20150331/e6c5fe7d/attachment-0002.sig>