Red Hat Bugzilla – Bug 826122
uuidd fails to start
Last modified: 2012-06-27 23:30:18 EDT
uuidd fails to start because it is unable to create it's pid file
The reason is that /var/run (which is a symlink to /run)
is owned by root, and uuidd runs as itself, with uid of uuidd,
which has no permissons to create the dir uuidd in /run, ergo
cannot create the uuidd.pid file.
So, I moded /etc/init.d/uuidd to create the dir and chown it to uuidd:uuidd
That works. HOWEVER....
starting uuidd after the mod, it hangs for about 5 minutes looking
for /var/lib/libuuid/uuidd.pid file, which is never created,
and systemctl reports failure; albeit, uuidd remains running.
I have been notified by another fedora user that it is broken
in F17 as well.
Version-Release number of selected component (if applicable):
systemctl start uuidd.service
Steps to Reproduce:
1. start uuidd
Actual results: failure
Expected results: no failure
# rpm -qif /etc/init.d/uuidd
Name : uuidd
Source RPM : util-linux-2.21.1-1.fc17.src.rpm
util-linux-2.21.2-2.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing util-linux-2.21.2-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
util-linux-2.21.2-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.