Description of problem: udevadm reporting unknown type --type=failed from /etc/init.d/udev-post Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. grep -i fail /var/log/messages 2. 3.
I can confirm this error on my box (as well as a couple others) Feb 25 10:55:22 Cedar1 udev-post[492]: Retrigger failed udev eventsunknown type --type=failed Feb 25 10:55:22 Cedar1 udevadm[559]: unknown type --type=failed Feb 25 10:55:23 Cedar1 upowerd[480]: UPower-Linux-WARNING **: failed to open /etc/crypttab: Failed to open file '/etc/crypttab': No such file or directory Feb 25 10:55:30 Cedar1 sm-notify[1462]: Failed to open directory sm.bak: No such file or directory Feb 25 10:55:31 Cedar1 netfs[1523]: Mounting other filesystems: [FAILED] Feb 25 10:55:39 Cedar1 ct_sync[1988]: Starting ct_sync: [FAILED] Feb 25 10:55:39 Cedar1 systemd[1]: Unit ct_sync.service entered failed state.
CC: (none) => jalaramie
I have this bug, with an additional couple of lines and also the multiple NIC problem (https://bugs.mageia.org/show_bug.cgi?id=4352). BTW, I have AMD CPUs. Feb 25 11:50:59 ourserver udev-post[688]: Retrigger failed udev eventsunknown type --type=failed Feb 25 11:50:59 ourserver udevadm[711]: unknown type --type=failed Feb 25 11:50:59 ourserver microcode_ctl[569]: CPU microcode data file not present (/lib/firmware/intel-microcode/intel-microcode.dat) [FAILED] Feb 25 11:50:59 ourserver systemd[1]: Unit microcode_ctl.service entered failed state. Feb 25 11:51:01 ourserver upowerd[604]: UPower-Linux-WARNING **: failed to open /etc/crypttab: Failed to open file '/etc/crypttab': No such file or directory Feb 25 11:51:07 ourserver netfs[1427]: Mounting other filesystems: [FAILED]
CC: (none) => jeffrobinsSAE
I did a little more digging and when I grep udev in my system logs I get a couple other errors: Feb 25 10:26:31 Cedar1 draknetcenter[19728]: running: /lib/udev/write_net_rules 00:11:09:01:8f:2b Feb 25 10:26:31 Cedar1 draknetcenter[19728]: program not found: /lib/udev/write_net_rules Feb 25 10:39:44 Cedar1 udev-post[482]: Retrigger failed udev eventsunknown type --type=failed Feb 25 10:39:44 Cedar1 udevadm[550]: unknown type --type=failed Feb 25 10:39:44 Cedar1 udev-post[482]: [ OK ] Feb 25 10:47:18 Cedar1 udevadm[543]: unknown type --type=failed Feb 25 10:47:18 Cedar1 udev-post[483]: Retrigger failed udev eventsunknown type --type=failed Feb 25 10:47:18 Cedar1 udev-post[483]: [ OK ] Feb 25 10:55:22 Cedar1 udev-post[492]: Retrigger failed udev eventsunknown type --type=failed Feb 25 10:55:22 Cedar1 udevadm[559]: unknown type --type=failed Feb 25 10:55:22 Cedar1 udev-post[492]: [ OK ]
CC: (none) => anssi.hannula, dmorganec, mageia, mageia, pterjan, thierry.vignaud, tmb
I'm confused. This is clearly the same error you reported a few minutes earlier in bug #4692 :s @Jeffrey: The draknetcenter bug is different and should be reported separately against the appropriate package. Thanks in advance :) *** This bug has been marked as a duplicate of bug 4692 ***
Resolution: (none) => DUPLICATEStatus: NEW => RESOLVED
No it is not. This bug is about the wrong arguments in the script when udevadm is called. The other bug is about the script not saying Starting/Reloading.
Status: RESOLVED => REOPENEDResolution: DUPLICATE => (none)
Well either way, the script is gone now.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
The draknetcenter bug may be related to bug 4352. Do you think I should wait until that is resolved or create another report and let the bug squad sort it out?
Yup, in actual fact I was just about to come back here to comment again as I've just updated udev to re-include that script again, so all is probably fine now. I suspect bug 4352 can now be closed but I'll let someone doing the real testing do that :)