Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

2016-11-06 Thread Elimar Riesebieter 
* 積丹尼 Dan Jacobson  [2016-11-06 06:11 +0800]:

> severity 843251 grave
> thanks
> Yes i386.
> And you know what?
> the user cannot ever boot his computer ever again, even from grub
> menus' "(recovery mode)".
> 
> ER> I can confirm this behaviour. Be care to reboot:
> ER> If booting with systemd you will be pulled in maintenance mode.
> 
> No you (I) will never get a prompt again, all one sees

Yes, I got it.

[...]
> Please tell me how to fix my computer to boot now. I am using a
> different one to write this message.

Read #843160
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843160

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

2016-11-05 Thread Michael Biebl 
Am 05.11.2016 um 23:11 schrieb 積丹尼 Dan Jacobson:
> severity 843251 grave
> thanks
> Yes i386.
> And you know what?
> the user cannot ever boot his computer ever again, even from grub
> menus' "(recovery mode)".
> 
> ER> I can confirm this behaviour. Be care to reboot:
> ER> If booting with systemd you will be pulled in maintenance mode.
> 
> No you (I) will never get a prompt again, all one sees
> 
>>> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Failed with 
>>> result 'timeout'.
>>> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
>>> hold-off time, scheduling restart.
> 
> is repeating every 90 seconds.
> 
> You see if **any** of these systemd processes have "no hold-off time" or
> something like that, they will loop over and over every 90 seconds.
> ***There should be a limit of one loop***. Else the user will never be
> able to boot his computer again, no matter how many choices there are in
> the grub menu.
> 
> Please tell me how to fix my computer to boot now. I am using a
> different one to write this message

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843160#100

Sorry for the inconvenience.

-- 
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

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

2016-11-05 Thread 積丹尼 Dan Jacobson 
severity 843251 grave
thanks
Yes i386.
And you know what?
the user cannot ever boot his computer ever again, even from grub
menus' "(recovery mode)".

ER> I can confirm this behaviour. Be care to reboot:
ER> If booting with systemd you will be pulled in maintenance mode.

No you (I) will never get a prompt again, all one sees

>> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Failed with 
>> result 'timeout'.
>> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
>> hold-off time, scheduling restart.

is repeating every 90 seconds.

You see if **any** of these systemd processes have "no hold-off time" or
something like that, they will loop over and over every 90 seconds.
***There should be a limit of one loop***. Else the user will never be
able to boot his computer again, no matter how many choices there are in
the grub menu.

Please tell me how to fix my computer to boot now. I am using a
different one to write this message.

Apparently I have to go to the grub command line, somehow mount the root file
system, and remove one of your /etc/ files.

Maybe it is /lib/systemd/system/systemd-journald.service . Will that fix
it? Thanks!!

Indeed my computer has separate /, /home, and /var .
However I can only tell you that because I kept a record of their
configuration on a different computer. Other users won't be able to
answer because they won't be able to boot to tell you.

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

2016-11-05 Thread Michael Biebl 
Am 05.11.2016 um 16:22 schrieb Elimar Riesebieter:

> I found this only on i386 arch with a separated /var and /usr

Your issue is a duplicate of  #843160

Removing RestrictAddressFamilies= [1] from the service files should
workaround the issue until a proper solution is found

Michael

[1] sed -i /RestrictAddressFamilies.*/d
/lib/systemd/systemd/system/systemd-*.service


-- 
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

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

2016-11-05 Thread Michael Biebl 
Am 05.11.2016 um 15:05 schrieb 積丹尼 Dan Jacobson:
> Package: udev
> Version: 232-1
> 
> Setting up udev (232-1) ...
> addgroup: The group `input' already exists as a system group. Exiting.
> Job for systemd-udevd.service failed because a timeout was exceeded.

Is that on i386?

P.S.: Please use reportbug next time. It would contain such information!


-- 
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

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

2016-11-05 Thread Elimar Riesebieter 
control: severity -1 important

* 積丹尼 Dan Jacobson  [2016-11-05 22:05 +0800]:

> Package: udev
> Version: 232-1
> 
> Setting up udev (232-1) ...
> addgroup: The group `input' already exists as a system group. Exiting.
> Job for systemd-udevd.service failed because a timeout was exceeded.
> See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript udev, action "restart" failed.
> ● systemd-udevd.service - udev Kernel Device Manager
>Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor 
> preset: enabled)
>Active: activating (start) since Sat 2016-11-05 22:00:35 CST; 76ms ago
>  Docs: man:systemd-udevd.service(8)
>man:udev(7)
>  Main PID: 8638 (systemd-udevd)
> Tasks: 1
>CGroup: /system.slice/systemd-udevd.service
>└─8638 /lib/systemd/systemd-udevd
> 
> 11月 05 22:00:35 jidanni2 systemd[1]: Starting udev Kernel Device Manager...
> dpkg: error processing package udev (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  udev
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Setting up udev (232-1) ...
> addgroup: The group `input' already exists as a system group. Exiting.
> 
> # journalctl -xe
> 
> 11月 05 22:02:09 jidanni2 systemd[1]: systemd-udevd.service: Failed with 
> result 'timeout'.
> 11月 05 22:02:09 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
> hold-off time, scheduling restart.
> 11月 05 22:02:09 jidanni2 systemd[1]: Stopped udev Kernel Device Manager.
> -- Subject: Unit systemd-udevd.service has finished shutting down
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- Unit systemd-udevd.service has finished shutting down.
> 11月 05 22:02:09 jidanni2 systemd[1]: Starting udev Kernel Device Manager...
> -- Subject: Unit systemd-udevd.service has begun start-up
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- Unit systemd-udevd.service has begun starting up.
> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Start operation 
> timed out. Terminating.
> 11月 05 22:03:39 jidanni2 systemd[1]: Failed to start udev Kernel Device 
> Manager.
> -- Subject: Unit systemd-udevd.service has failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- Unit systemd-udevd.service has failed.
> -- 
> -- The result is failed.
> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Unit entered 
> failed state.
> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Failed with 
> result 'timeout'.
> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
> hold-off time, scheduling restart.
> 11月 05 22:03:39 jidanni2 systemd[1]: Stopped udev Kernel Device Manager.
> -- Subject: Unit systemd-udevd.service has finished shutting down
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- Unit systemd-udevd.service has finished shutting down.
> 11月 05 22:03:39 jidanni2 systemd[1]: Starting udev Kernel Device Manager...
> -- Subject: Unit systemd-udevd.service has begun start-up
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> -- 
> -- Unit systemd-udevd.service has begun starting up.
> # systemctl status systemd-udevd.service
> ● systemd-udevd.service - udev Kernel Device Manager
>Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor 
> preset: enabled)
>Active: activating (start) since Sat 2016-11-05 22:03:39 CST; 1min 26s ago
>  Docs: man:systemd-udevd.service(8)
>man:udev(7)
>  Main PID: 8728 (systemd-udevd)
> Tasks: 1
>CGroup: /system.slice/systemd-udevd.service
>└─8728 /lib/systemd/systemd-udevd
> 
> 11月 05 22:03:39 jidanni2 systemd[1]: Failed to start udev Kernel Device 
> Manager.
> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Unit entered 
> failed state.
> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Failed with 
> result 'timeout'.
> 11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
> hold-off time, scheduling restart.
> 11月 05 22:03:39 jidanni2 systemd[1]: Stopped udev Kernel Device Manager.
> 11月 05 22:03:39 jidanni2 systemd[1]: Starting udev Kernel Device Manager...

I can confirm this behaviour. Be care to reboot:
If booting with systemd you will be pulled in maintenance mode.

I found this only on i386 arch with a separated /var and /usr
partition. Downgrading to testing's version (231-9) helped to reboot
systemd again. So hereby I set severity to at least important.
Should be grave IMHO.

amd64 machines with separated /var and /usr run fine, though.

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)

Bug#843251: Job for systemd-udevd.service failed because a timeout was exceeded.

2016-11-05 Thread 積丹尼 Dan Jacobson 
Package: udev
Version: 232-1

Setting up udev (232-1) ...
addgroup: The group `input' already exists as a system group. Exiting.
Job for systemd-udevd.service failed because a timeout was exceeded.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor 
preset: enabled)
   Active: activating (start) since Sat 2016-11-05 22:00:35 CST; 76ms ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
 Main PID: 8638 (systemd-udevd)
Tasks: 1
   CGroup: /system.slice/systemd-udevd.service
   └─8638 /lib/systemd/systemd-udevd

11月 05 22:00:35 jidanni2 systemd[1]: Starting udev Kernel Device Manager...
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up udev (232-1) ...
addgroup: The group `input' already exists as a system group. Exiting.

# journalctl -xe

11月 05 22:02:09 jidanni2 systemd[1]: systemd-udevd.service: Failed with result 
'timeout'.
11月 05 22:02:09 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
11月 05 22:02:09 jidanni2 systemd[1]: Stopped udev Kernel Device Manager.
-- Subject: Unit systemd-udevd.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-udevd.service has finished shutting down.
11月 05 22:02:09 jidanni2 systemd[1]: Starting udev Kernel Device Manager...
-- Subject: Unit systemd-udevd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-udevd.service has begun starting up.
11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Start operation 
timed out. Terminating.
11月 05 22:03:39 jidanni2 systemd[1]: Failed to start udev Kernel Device Manager.
-- Subject: Unit systemd-udevd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-udevd.service has failed.
-- 
-- The result is failed.
11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Unit entered failed 
state.
11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Failed with result 
'timeout'.
11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
11月 05 22:03:39 jidanni2 systemd[1]: Stopped udev Kernel Device Manager.
-- Subject: Unit systemd-udevd.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-udevd.service has finished shutting down.
11月 05 22:03:39 jidanni2 systemd[1]: Starting udev Kernel Device Manager...
-- Subject: Unit systemd-udevd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-udevd.service has begun starting up.
# systemctl status systemd-udevd.service
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor 
preset: enabled)
   Active: activating (start) since Sat 2016-11-05 22:03:39 CST; 1min 26s ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
 Main PID: 8728 (systemd-udevd)
Tasks: 1
   CGroup: /system.slice/systemd-udevd.service
   └─8728 /lib/systemd/systemd-udevd

11月 05 22:03:39 jidanni2 systemd[1]: Failed to start udev Kernel Device Manager.
11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Unit entered failed 
state.
11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Failed with result 
'timeout'.
11月 05 22:03:39 jidanni2 systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
11月 05 22:03:39 jidanni2 systemd[1]: Stopped udev Kernel Device Manager.
11月 05 22:03:39 jidanni2 systemd[1]: Starting udev Kernel Device Manager...