RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
debug in udev do not work with "udevadm control --log-priority=debug" command


Version-Release number of selected component (if applicable):
python-pyudev-0.15-9.el7.noarch
systemd-219-42.el7_4.10.x86_64

How reproducible:
everytime when udev is set in debug mode

Steps to Reproduce:
execute below
1. udevadm control --log-priority=debug
2. udevadm control --reload
3. cat /var/log/messages

Actual results:
udev do not log in debug mode

Expected results:
udev should log in /var/log/messages with log priority = debug


Additional info:

udevadm control --log-priority=debug actually enables debug mode. Try running udevadm trigger afterward and check the system log. You will see a ton of debug output from udev. Also, you will see a message "udevd message (RELOAD) received" in journal which is logged at debug level.

It is just that --reload doesn't really do what you'd expect. Udev reloads configuration lazily. It kills all worker processes and drops the config loaded from rules in the past, however, it doesn't reload all the rules immediately. It does that when next uevent is received in the future.

Btw, I was checking in journal to rule out the possibility of misconfigured rsyslog.