Red Hat Bugzilla – Bug 1525348
multipath: "spurious uevent, path already in pathvec" errors
Last modified: 2018-07-03 01:32:54 EDT
Description of problem: The following messages appear in /var/log/messages, when server is booting up. --- [rhel7u4]$ cat var/log/messages|grep "spurious uevent" Dec 7 18:27:33 <daemon.err> rhel7u4 multipathd:sde: spurious uevent, path already in pathvec Dec 7 18:27:33 <daemon.err> rhel7u4 multipathd:sdb: spurious uevent, path already in pathvec Dec 7 18:27:33 <daemon.err> rhel7u4 multipathd:sdc: spurious uevent, path already in pathvec Dec 7 18:27:33 <daemon.err> rhel7u4 multipathd:sdd: spurious uevent, path already in pathvec --- Per the confirmation with other senior engineer, it mentioned that these are informational only, it is harmless and could be ignored safely. Could you please advise why such messages are classified as "daemon.err" in /var/log/messages? Is it possible to make it shown as "daemon.info" or "daemon.notice" in /var/log/messages? Please advise. thank you Version-Release number of selected component (if applicable): rhel7u4 with kernel-3.10.0-693.2.2.el7.x86_64 device-mapper-multipath-0.4.9-111.el7.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Could you please advise why such messages are classified as "daemon.err" in /var/log/messages, if they are harmless? Is it possible to make it shown as "daemon.info" or "daemon.notice" in /var/log/messages? Additional info:
Since Customer have a batch of server which would be online(production) soon, their monitoring system are sensitive to such "daemon.err" messages. So, I will put this BZ severity as high, please kindly let me know, if you have any concerns. Thank you Vansen Ng
There is no good reason for them to have that severity. I'm fine with moving them down to a Notice. I'm not sure that there is time for this to make RHEL-7.5, not that I have any objection to it going in. If the bug gets all its ACKs, I'd have no worries about making this change.
Thanks for the clarification. Please kindly check if we have any plan to fix it in coming version or we have any other reason to keep the current severity of such messages. Thank you Customer Experience and Engagement, Red Hat
I've moved the level of these messages down to a notice.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0884