Bug 176041
Summary: | udev_db_lookup_name: unable to open udev_db '/dev/.udev/db' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stephen Warren <swarren-tag-rhbugzilla> |
Component: | udev | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | clydekunkel7734, hdegoede, kay.sievers, kevinverma, reuben-redhatbugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-15 13:29:14 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: |
Description
Stephen Warren
2005-12-18 06:41:26 UTC
FYI, just updated udev and kernel, and it still happens with: udev-077-2 kernel-2.6.14-1.1770_FC5 This is caused by executing udevinfo while there is no database to read. udev 078 exports the symlinks to the event environment and calling udevinfo is not needed. I've also removed the error log for the next udev version. hmm, there is no script in the udev package, that calls udevinfo during system startup... Don't you call pam_console.dev anymore? It was calling udevinfo in the past. I am seeing this also as: Starting udev:udevd-event[944]: udev_db_lookup_name: unable to open udev_db '/dev/.udev/db': No such file or directory /dev/.udev/db is there, but I don't know when it is created. Also, I don't see any errors after booting and starting work. Nothing in any of the logs. Saw this today (1/5/2006) on a clean install of rawhide. *** Bug 176547 has been marked as a duplicate of this bug. *** pam_console.dev now uses $DEVLINKS, no udevinfo involved. Still present on clean install of FC5T2. Not every reboot, tho. Can't predict when the problem will occur. I've seen this happen after my laptop lost power. The next boot had this problem, and haldaemon wouldn't run. Rebooting fixed it. I suspect this is fixed in later versions of udev: From udev-081/ChangeLog ---- Summary of changes from v078 to v079 ============================================ Kay Sievers: don't log error if database does not exist <snip> ---- Of course current rawhide has 078, so a jump to 081 would probably solve this one. |