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:

If /etc/multipath.conf contains a line 

        pg_timeout none

then messages like these

   Aug  8 06:21:30 infl0242 multipathd: DM message failed [set_pg_timeout 0]

show up during boot or multipathd restarts

Version-Release number of selected component (if applicable):

device-mapper-multipath-0.4.9-72.el6_5.3.x86_64             
device-mapper-multipath-libs-0.4.9-72.el6_5.3.x86_64

How reproducible:

always

Steps to Reproduce:
1. update device-mapper-multipath to the versions mentioned above
2. add pg_timeout none to the defaults section of the multipath.conf
3. reboot / restart multipathd

Actual results:

multipathd: DM message failed [set_pg_timeout 0]

is shown

Expected results:

no (error) message

Additional info:

Yeah.  The kernel doesn't support pg_timeout (it never has. The patch wasn't accepted).  So, setting it to any valid value (including "none"), will cause it to send a message that the kernel doesn't accept.

I assume that the issue is

# multipathd show config

displays

pg_timeout none

I can fix this so that multipathd will accept any value for pg_timeout, and not do anything with it, and not display that value when you run the "show config" command

Fixed as per Comment 2

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://rhn.redhat.com/errata/RHBA-2015-1391.html