Bug#769069: systemd: Failed to start Login Service

[Simon McVittie]

Unfortunately I don't see a "smoking gun" in your log.

It looks as though the system might have been having performance
issues in general:

On 13/11/14 23:36, Paul Menzel wrote:
> Nov 11 07:45:44 asrock-e350m1 systemd[1]: Looping too fast. 
> Throttling execution a little.

which might have contributed to timeouts, possibly?

> Nov 11 07:45:33 asrock-e350m1 systemd-remount-fs[385]: mount: /usr 
> not mounted or bad option Nov 11 07:45:33 asrock-e350m1
> systemd-remount-fs[385]: In some cases useful info is found in
> syslog - try Nov 11 07:45:33 asrock-e350m1 systemd-remount-fs[385]:
> dmesg | tail or so.

I don't know whether this is related but it doesn't look great. Is
this a known problem that you have subsequently fixed?

> Nov 11 07:46:16 asrock-e350m1 NetworkManager[942]: <info> caught 
> signal 15, shutting down normally. Nov 11 07:46:16 asrock-e350m1
> avahi-daemon[929]: Got SIGTERM, quitting.
...
> Nov 11 07:46:52 asrock-e350m1 NetworkManager[942]: <info> startup 
> complete Nov 11 07:46:52 asrock-e350m1 NetworkManager[942]: <info>
> exiting (success)

Any idea why these might have happened? They both use libdbus, so
getting disconnected from D-Bus with exit-on-disconnect enabled would
cause an _exit(1) rather than the raise(SIGTERM) you'd get from GDBus.

It looks vaguely as though *everything* on the system bus might have
been failing to connect to it?

Did you / do you have any unusual systemd or dbus configuration in use?

If you can't reproduce this, then I don't think we'll be able to work
out what is going on from that log, sorry.

    S