Am 04.03.2015 um 01:07 schrieb Daurnimator: > On 3 March 2015 at 18:42, Michael Biebl <bi...@debian.org> wrote: >> What's the output of >> systemctl cat systemd-logind.service >> systemctl status systemd-logind.service > > $ sudo systemctl cat systemd-logind.service > # /lib/systemd/system/systemd-logind.service > # This file is part of systemd. > # > # systemd is free software; you can redistribute it and/or modify it > # under the terms of the GNU Lesser General Public License as published by > # the Free Software Foundation; either version 2.1 of the License, or > # (at your option) any later version. > > [Unit] > Description=Login Service > Documentation=man:systemd-logind.service(8) man:logind.conf(5) > Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind > Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat > Wants=user.slice > After=nss-user-lookup.target user.slice > ConditionPathExists=/lib/systemd/system/dbus.service
That looks ok. > # Ask for the dbus socket. If running over kdbus, the socket will > # not be actually used. > Wants=dbus.socket > After=dbus.socket > > [Service] > ExecStart=/lib/systemd/systemd-logind > Restart=always > RestartSec=0 > BusName=org.freedesktop.login1 > CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN > CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER > CAP_SYS_TTY_CONFIG > WatchdogSec=1min > > # Increase the default a bit in order to allow many simultaneous > # logins since we keep one fd open per session. > LimitNOFILE=16384 > > > $ sudo systemctl status systemd-logind.service > ● systemd-logind.service - Login Service > Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) > Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56 > UTC; 4h 3min ago > start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago > Docs: man:systemd-logind.service(8) > man:logind.conf(5) > http://www.freedesktop.org/wiki/Software/systemd/logind > http://www.freedesktop.org/wiki/Software/systemd/multiseat > Main PID: 341 (code=exited, status=1/FAILURE) > Status: "Shutting down..." > > Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service > has no holdoff time, scheduling restart. > Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service... > Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... > Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service > start request repeated too quickly, refusing to start. > Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service. > Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit > systemd-logind.service entered failed state. > Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service. > Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service. Did you dist-upgrade the VM and those failures are from before the upgrade? Can you attach your /var/log/dpkg.log Is the problem reproducible after a reboot? Fwiw, I can't reproduce the problem in a VM without dbus installed, so we need to find what's special in your case. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
