Bug#764298: "Failed to start Login Service." after upgrade to 215-5+b1

[I. Schrey]

Package: systemd
Version: 215-5+b1

Greetings,

see below, errors after the latest apt-get (dist-)upgrade on a
minimal install Jessie VM which was running fine before.

Before the upgrade, I had the impression that the system wasn't
using logind at all. At least a search in my remote syslog db
doesn't find anything with the string 'logind' in it, up to the point
when I restarted the VM after the upgrade.


Maybe related:
after the upgrade, it suggested to autoremove

libdbus-1-3                          1.8.6-2
libgcrypt11                          1.5.4-3
libsystemd-daemon0                   208-8
libsystemd-journal0                  208-8
libsystemd-login0                    208-8

so I did.


I see in b.d.o that the "exit status 32" is being worked on - not sure
if that's related? The mounts look okay to me, after bootup,
nothing seems missing or read only.


Please tell me if you need more info, and what you need.
If it helps, I could do a rollback and redo the upgrade.


Regards
Ingmar


---snip journalctl---

Oct 06 23:13:53 bpo-jessie-s systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct 06 23:13:53 bpo-jessie-s systemd-logind[433]: Failed to connect to 
system bus: No such file or directory
Oct 06 23:13:53 bpo-jessie-s systemd-logind[433]: Failed to fully start 
up daemon: No such file or directory
Oct 06 23:13:53 bpo-jessie-s systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct 06 23:13:53 bpo-jessie-s systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-logind.service has failed.
--
-- The result is failed.
Oct 06 23:13:53 bpo-jessie-s systemd[1]: Unit systemd-logind.service 
entered failed state.


---snip syslog---

Oct  6 23:13:53 jessie-test kernel: alg: No test for crc32 (crc32-pclmul)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda3): re-mounted. Opts: 
errors=remount-ro
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda6): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda5): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda1): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda4): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test systemd-fsck[108]: /dev/vda3: clean, 
2773/117856 files, 119073/471040 blocks
Oct  6 23:13:53 jessie-test systemd-udevd[132]: Network interface 
NamePolicy= disabled on kernel commandline, ignoring.
Oct  6 23:13:53 jessie-test systemd-fsck[161]: /dev/vda1: clean, 
297/12288 files, 34551/49152 blocks
Oct  6 23:13:53 jessie-test systemd-fsck[174]: /dev/vda5: clean, 
3857/65536 files, 24471/261888 blocks
Oct  6 23:13:53 jessie-test systemd-fsck[187]: /dev/vda6: clean, 
29/98304 files, 22686/393216 blocks
Oct  6 23:13:53 jessie-test keyboard-setup[135]: Setting preliminary 
keymap...done.
Oct  6 23:13:53 jessie-test systemd-remount-fs[229]: mount: /usr not 
mounted or bad option
Oct  6 23:13:53 jessie-test systemd-remount-fs[229]: /bin/mount for /usr 
exited with exit status 32.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-remount-fs.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Remount Root and 
Kernel File Systems.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-remount-fs.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service start 
request repeated too quickly, refusing to start.
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test munin-node[463]: Process Backgrounded
Oct  6 23:13:53 jessie-test munin-node[463]: 2014/10/06-23:13:53 
Munin::Node::Server (type Net::Server::Fork) starting! pid(463)
Oct  6 23:13:53 jessie-test munin-node[463]: Resolved [*]:4949 to 
[::]:4949, IPv6
Oct  6 23:13:53 jessie-test munin-node[463]: Not including resolved host 
[0.0.0.0] IPv4 because it will be handled by [::] IPv6
Oct  6 23:13:53 jessie-test munin-node[463]: Binding to TCP port 4949 on 
host :: with IPv6
Oct  6 23:13:53 jessie-test munin-node[463]: Setting gid to "0 0"
Oct  6 23:13:54 jessie-test postfix[414]: Starting Postfix Mail 
Transport Agent: postfix.
Oct  6 23:13:57 jessie-beta rsyslogd: -- MARK --

---snip---