"unable to create db file" warning if the device is normally placed in a subdir (input, devmapper, etc.)

Bug #73425 reported by Fabio Massimo Di Nitto
44
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
High
Scott James Remnant (Canonical)

Bug Description

Hi Scott,

i just noticed a new warning (at boot) with the latest ubuntu4 udev in feisty:

udevd-event[2365]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@mice': No such file or directory

The machine has a ps2 mouse, but doesn't have X or anything.. just a small server.

Fabio

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

There is also another one that happens more randomically that udevd-event fails to rename interfaces around. It seems that there is a race from the interface to appear and udev trying to give it the proper name. At the end of the boot everything still looks fine.

Fabio

Revision history for this message
Allcolor-g (allcolor) wrote :

I have the same warning about "/dev/.udev/db/class@input@mice" plus one about "/dev/.udev/db/class@input@input1@mouse0".

I also have this:

add_to_rules: DRIVER== This will change in future release, please use DRIVERS== in /etc/udev/rules.d/65-persistent-disk.rules:11

and

add_to_rules: do not reference parent sysfs directory directly, that may break with future kernel, please fix it in /etc/udev/rules.d/65-persistent-disk.rules:12.

Revision history for this message
DerekSlovin (derek-slovin) wrote :

In addition to getting the warning, the mouse is not useable. Xorg places the pointer in the middle of the screen and it won't move/can't be used.

I also noticed that hald is eating my system resources. Not sure if that is related to this.

I am using kernel 2.6.20-2 when I get this.

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

Derek that is a different bug. Please file another one and assign it to either X or kernel.

Fabio

Revision history for this message
Sokraates (sokraates) wrote :

I can confirm this:

udevd[4403]: lookup_group: specified group 'nvram' unknown
udevd-event[4448]_ udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@mice': No such file or directory

The mouse works, in the end.

As for my other problems see bug 74059. ;)

Revision history for this message
Allcolor-g (allcolor) wrote :

As confirmed by others

Changed in udev:
status: Unconfirmed → Confirmed
Revision history for this message
Victor Noël (victornoel) wrote :

i can confirm it too.

i get :
udevd[4403]: lookup_group: specified group 'nvram' unknown
udevd-event[4448]_ udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@mice': No such file or directory

and for the mouse, i just have a touchpad on my laptop. (and it works well of course :)

Revision history for this message
grazie (grazie-deactivatedaccount) wrote :

Confirmed on xubuntu feisty herd 3 candidate daily release 01/02/07.

udevd[2315]:lookup-group: specified group 'nvram' unknown
edevd-event [2394]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@mice': No such file or directory
edevd-event [2651]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@input0@mouse0': No such file or directory
edevd-event [2663]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@input3@mouse3': No such file or directory

Upgraded udev from 103-0ubuntu5 to 103-0ubuntu6 which required an dependancy upgrade to volumeid (same versions) which resulted in updated /boot/initrd.img-2.6.20-5-powerpc. On reboot the following additional messages where output prior to ones above

kinit: name_to_dev(/dev/disk/by-uuid/56f34625-d45b-4738-a776-2fad65e7c6b7) = hda4(3,4)
kinit: trying to resume from /dev/disk/by-uuid/56f34625-d45b-4738-a776-2fad65e7c6b7
kinti: No resume image, doing normal boot...

Revision history for this message
R Morrison (rmorrisonva) wrote :

nearly the same symptoms as everyone else. running feisty 7.04 all repos enabled on amd64 (ubuntu arch: amd64) .

Revision history for this message
Jaakko Heinonen (jheinonen) wrote :

Confirmed. Getting these errors after minimal install from alternative CD.

Changed in udev:
importance: Undecided → High
Tollef Fog Heen (tfheen)
Changed in udev:
assignee: nobody → keybuk
Revision history for this message
rasz (citizenr) wrote :

same here

where do you find this? I mean where is uved logging this shit? I searched an hour, even tried enabling logging in udev (from err to debug) an still couldnt find the log :(

Revision history for this message
Brian Fallik (bfallik) wrote : Re: [Bug 73425] Re: "unable to create db file" warning if the device is normally placed in a subdir (input, devmapper, etc.)

For me, I see this msg logged to the console during startup.

(transcribing during an fsck on boot)
  udevd-event[2623]: udev_db_add_device: unable to create db file
'/dev/.udev/db/class@input@mice': no such file or directory

Hope that helps.

On 3/30/07, rasz <email address hidden> wrote:
> same here
>
> where do you find this? I mean where is uved logging this shit? I
> searched an hour, even tried enabling logging in udev (from err to
> debug) an still couldnt find the log :(
>
> --
> "unable to create db file" warning if the device is normally placed in a subdir (input, devmapper, etc.)
> https://launchpad.net/bugs/73425
>

Revision history for this message
rasz (citizenr) wrote :

I know its in the console - I saw it there :P, Im asking where udev saves its logs

Revision history for this message
Brian Fallik (bfallik) wrote :

Running "sudo /etc/init.d/udev restart" produces the same error
messages in /var/log/syslog.

On 3/30/07, rasz <email address hidden> wrote:
> I know its in the console - I saw it there :P, Im asking where udev
> saves its logs
>
> --
> "unable to create db file" warning if the device is normally placed in a subdir (input, devmapper, etc.)
> https://launchpad.net/bugs/73425
>

Revision history for this message
rasz (citizenr) wrote :

rasz@capek:~$ cat /var/log/syslog |grep udev
rasz@capek:~$ sudo /etc/init.d/udev restart
Password:
 * Loading additional hardware drivers... [ OK ]
rasz@capek:~$ cat /var/log/syslog |grep udev
Apr 1 23:19:44 capek udevd-event[7961]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@mice': No such file or directory
Apr 1 23:19:45 capek udevd-event[8118]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@input0@mouse0': No such file or directory
Apr 1 23:19:47 capek udevd-event[8122]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@input2@mouse1': No such file or directory
rasz@capek:~$

thank you,
so shouldnt udev save the log to syslog at boot too?

Revision history for this message
Brian Fallik (bfallik) wrote :

Perhaps udev starts before syslog? It appears that, in either case,
udev is logging the same information. I'd guess that perhaps syslogd
isn't ready/listening so the msgs are echoed to the console during the
initial boot.</wild guess>

Revision history for this message
rasz (citizenr) wrote :

latest update fixes it for me

rasz@capek:~$ sudo /etc/init.d/udev restart
Password:
 * Loading additional hardware drivers... [ OK ]
rasz@capek:~$

Changed in udev:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.