Description of problem:
Version-Release number of selected component (if applicable):
I hit this with both the RHEL4 update 4 and update 5 (RC1) version of
Every time, following the instructions below
Steps to Reproduce:
1. Server is connected via a switch to an EMC CX300, zoned so that one HBA in
the server can talk to SP A in the CX300, the other HBA in the server can talk
to SP B in the CX300.
2. Pull the fibre channel cable from one SP in the CX300.
3. Run "multipath -l" repeatedly until it hangs. Kill it via ctrl-c, then run
"multipath -l" again (it will hang again). Don't know if running it a second
time is important or not, but killing one invocation is important--no error if
you don't do this.
4. After a little while, the multipath -l command will un-hang itself; at this
point, multipathd dies.
I hit this under update 4 originally. I also hit the same problem in update 4
with Stratus ftScalable Storage, by shutting down and restarting both RAID
Things are a bit different under update 5, in that if I did "multipath -ll" I
wasn't able to control-c the command, and in that case multipathd survived. But
with "multipath -l" I was able to reproduce the problem. I did my update 5
testing with Stratus ftScalable Storage, because I didn't have an update 5
system connected to a Clariion.
multipathd does not die
The following patch fixes the problem. This is from
[multipathd] ignore SIGPIPE
Christophe Varoqui [Thu, 16 Mar 2006 08:07:02 +0000 (09:07 +0100)]
Maxim Kozover reported daemon segfault when breaking the recieving side
of the unix socket. Credits.
diff --git a/multipathd/main.c b/multipathd/main.c
@@ -1215,6 +1215,7 @@ signal_init(void)
+ signal(SIGPIPE, SIG_IGN);
Patch applied. Thanks!
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.