Bug 481075
| Summary: | udev gets errors on update and ends up not runnig | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
| Component: | udev | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | harald |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 141-4.fc11 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-22 21:44:24 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
the groupadd is bug #480795 hmm, strange.. the other problem is new > hmm, strange.. the other problem is new
I was scratching my head too because if I am running relevant parts of scripts from a command line then everything works like expected. Maybe indeed some timing? 'udevd' was killed, eventually but long before I had a chance to check, only not to be restarted. Would be beneficial to have a short 'sleep' after 'kill' or something else may hold it?
I presume that it is not possible to have multiple instances of 'udevd' running in some circumstances. Or this indeed may happen?
An update to udev-137-2.fc11 got the same "error binding control socket, seems udevd is already running" and 'pgrep -f -l udev' after an update comes back empty but it shows a running one after '/sbin/udevd -d'. It appears that the previous instance of udevd prevents the new one from starting and gets later killed in a "preuninstall" script when yum is in a cleanup phase. Just guessing .... At least 'dialout' group moved to 18 and it does not clash with some other GID. :-) I'll try to make the %post section more hardened against that... This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping udev-141-4.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/udev-141-4.fc11 udev-141-4.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update udev'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7208 udev-141-4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: The following showed up on update: Updating : udev 79/164 error binding control socket, seems udevd is already running groupadd: GID 87 is not unique I am not sure about the first error. Timing? I see in package scripts if [ -n "$pid" ]; then kill $pid /sbin/udevd -d fi but the net result was that udevd was not running and had to be restarted. "groupadd: GID 87 is not unique" is correct because PolicyKit package already did "/usr/sbin/useradd -c 'PolicyKit' -u 87 ..." and there is "polkituser:x:87:" in /etc/group. Version-Release number of selected component (if applicable): udev-136-2.fc11