In which log should I check for udev errors?
Solution 1
You can change logging priority to "info" level or even "debug" by:
udevadm control --log-priority=info
Then you should see all logs in your system log. If you don't, then rsyslogd
may not be configured to read kernel logs and you may still view the kernel logs using dmesg
.
When you are done, bring it to default "err". See in /etc/udev/udev.conf
what is your default logging level.
Solution 2
unbuffer udevadm monitor --environment
The use of unbuffer
is optional, but when piping output to grep
saves you a headache. By default output is buffered in 4k blocks, nothing will be printed until that buffer is full.
You didn't forget to reload the rules?
sudo udevadm control --reload
Related videos on Youtube
eoinoc
Updated on September 18, 2022Comments
-
eoinoc over 1 year
I've written a
udev
rule which is run each time my device is mounted/dismounted.However, in which Linux (Debian) error log should I check when debugging such rules?
-
enzotib about 12 yearsShould be noted that
unbuffer
is not installed by default on Debian. -
jippie about 12 yearsThat's correct, it is in the expect-dev package. It can be installed by
sudo apt-get install expect-dev
un Debian/Ubuntu. -
silvernightstar almost 9 yearsI am confused why there are two points of configuration for logging priority. Care to explain how
udevadm control --log-priority=info
is different from settingudev_log="err"
in/etc/udev/udev.conf
? Thanks -
boycy over 8 yearsThe
udevadm
method is to change the logging priority of the runningudevd
;udev.conf
is for permanently changing it.