Am 26.11.2014 um 19:54 schrieb Michael Biebl: > Nov 26 19:36:57 debian systemd[1]: Reloading. > Nov 26 19:36:57 debian systemd[1]: bind(@run/systemd/notify) failed: Address > already in use > Nov 26 19:36:57 debian systemd[1]: Failed to reload: Address already in use > Nov 26 19:36:59 debian groupadd[19888]: group added to /etc/group: > name=input, GID=122 > Nov 26 19:36:59 debian groupadd[19888]: group added to /etc/gshadow: > name=input > Nov 26 19:36:59 debian groupadd[19888]: new group: name=input, GID=122 > Nov 26 19:36:59 debian systemd[1]: Stopping udev.service... > Nov 26 19:36:59 debian systemd[1]: Stopped udev.service. > Nov 26 19:36:59 debian systemd[1]: Stopping udev Control Socket. > Nov 26 19:36:59 debian systemd[1]: Closed udev Control Socket. > Nov 26 19:36:59 debian systemd[1]: Stopping udev Kernel Socket. > Nov 26 19:36:59 debian systemd[1]: Closed udev Kernel Socket. > Nov 26 19:36:59 debian systemd[1]: Reloading. > Nov 26 19:36:59 debian systemd[1]: bind(@run/systemd/notify) failed: Address > already in use > Nov 26 19:36:59 debian systemd[1]: Failed to reload: Address already in use > Nov 26 19:36:59 debian systemd[1]: Reloading. > Nov 26 19:36:59 debian systemd[1]: bind(@run/systemd/notify) failed: Address > already in use > Nov 26 19:36:59 debian systemd[1]: Failed to reload: Address already in use > Nov 26 19:36:59 debian systemd[1]: Starting udev Kernel Socket. > Nov 26 19:36:59 debian systemd[1]: Listening on udev Kernel Socket. > Nov 26 19:36:59 debian systemd[1]: Starting udev Control Socket. > Nov 26 19:36:59 debian systemd[1]: Listening on udev Control Socket. > Nov 26 19:36:59 debian systemd[1]: Starting udev Kernel Device Manager... > Nov 26 19:36:59 debian systemd-udevd[19952]: Network interface NamePolicy= > disabled on kernel commandline, ignoring. > Nov 26 19:37:56 debian systemd[1]: systemd-journald.service watchdog timeout > (limit 1min)! > Nov 26 19:37:56 debian systemd-journal[19434]: Journal stopped > Nov 26 19:37:56 debian systemd[1]: Starting Trigger Flushing of Journal to > Persistent Storage... > Nov 26 19:37:56 debian systemd[1]: Started Trigger Flushing of Journal to > Persistent Storage. > Nov 26 19:38:29 debian systemd[1]: systemd-udevd.service start operation > timed out. Terminating. > Nov 26 19:38:29 debian systemd[1]: Failed to start udev Kernel Device Manager.
I think, that's the relevant part from the journal, specifically: > Nov 26 19:36:57 debian systemd[1]: bind(@run/systemd/notify) failed: Address > already in use > Nov 26 19:36:57 debian systemd[1]: Failed to reload: Address already in use Running lsof /run/systemd/notify, doesn't show any process listening on the socket. systemd-udevd in v215 uses Type=notify and I suspect it get's stuck in State activating since the sd_notify call doesn't succeed. I remember Sjoerd running into this issue as well, but I don't remember anymore if he found the root cause and how to fix it. -- 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
