Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 614188 - sys-fs/udev-init-scripts: please add longer timeout for stoping udevadm
Summary: sys-fs/udev-init-scripts: please add longer timeout for stoping udevadm
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo systemd Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-29 08:08 UTC by Marcin Mirosław
Modified: 2021-08-09 15:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Mirosław 2017-03-29 08:08:11 UTC
I'm observing since long time that restarting udev have to be done twice. First time:
# /etc/init.d/udev -D restart
 * Stopping udev ...                         [ ok ]
 * Starting udev ...
 * start-stop-daemon: /lib/systemd/systemd-udevd is already running
 * Failed to start udev                      [ !! ]

Second pass:
# /etc/init.d/udev -D restart
 * Stopping udev ...
 * Failed to stop udev using udevadm                [ !! ]
 * Trying with start-stop-daemon ...
 * start-stop-daemon: no matching processes found   [ ok ]
 * Starting udev ...
starting version 225  [ ok ]

This usually happens on not-idling hosts.

Reproducible: Always

Actual Results:  
As above.
Comment 1 Marcin Mirosław 2017-06-13 10:26:11 UTC
Any comments about it?
Comment 2 Marcin Mirosław 2017-11-27 08:24:17 UTC
Ping.
Comment 3 Mike Gilbert gentoo-dev 2017-11-27 16:41:41 UTC
The init script calls "udevadm control --exit", which has a default timeout of 60 seconds. Is that insufficient, or is it not working properly?
Comment 4 Marcin Mirosław 2017-11-27 20:33:00 UTC
It doesn't work correctly. Init script throws mentioned error after maybe 5 seconds.
Comment 5 Mike Gilbert gentoo-dev 2017-11-27 20:45:15 UTC
In that case, this is probably a bug that belongs upstream. udevadm should not exit until udevd has terminated or the 60 second timeout has expired.
Comment 6 Mike Gilbert gentoo-dev 2017-11-27 20:52:01 UTC
I suppose it is also possible that OpenRC has some timeout function for the stop() function as a whole... probably worth looking into.
Comment 7 Marcin Mirosław 2017-12-05 12:16:07 UTC
 time /etc/init.d/udev --nodeps restart
 * Stopping udev ...                                               [ ok ]
 * Starting udev ...
 * start-stop-daemon: /lib/systemd/systemd-udevd is already running
 * Failed to start udev                                            [ !! ]

real    0m1.185s
user    0m0.035s
sys     0m0.048s

Next try after a minute:

 time /etc/init.d/udev --nodeps restart
 * Stopping udev ...
 * Failed to stop udev using udevadm                               [ !! ]
 * Trying with start-stop-daemon ...
 * start-stop-daemon: no matching processes found                  [ ok ]
 * Starting udev ...
starting version 233                                               [ ok ]

real    0m0.156s
user    0m0.068s
sys     0m0.003s