Multipath receiving SIGHUP and renaming paths

Solution Verified - Updated -

Issue

  • Multipath receiving SIGHUP. Then 30 mins later, renaming them back
Oct  17 14:33:42 server1 multipathd: reconfigure (SIGHUP)
Oct  17 14:33:42 server1 multipathd: LUN_001_ROOT: stop event checker thread (140693179512576)
Oct  17 14:33:49 server1 multipathd: 360000970000292604292533030383233: rename LUN_001_ROOT to mpathb
Oct  17 14:33:49 server1 multipathd: mpathb: load table [0 62914560 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:16 1 8:64 1 70:240 1 65:368 1]
Oct  17 15:05:07 server1 multipathd: reconfigure (SIGHUP)
Oct  17 15:05:07 server1 multipathd: mpathb: stop event checker thread (140693170337536)
Oct  17 15:05:14 server1 multipathd: 360000970000292604292533030383233: rename mpathb to LUN_001_ROOT 
Oct  17 15:05:14 server1 multipathd: LUN_001_ROOT: load table [0 62914560 multipath 1 queue_if_no_path 0 1 1 round-robin 0 4 1 8:16 1 8:64 1 70:240 1 65:368 1]

Environment

  • Red Hat Enterprise Linux 6
  • Multipath

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.