[dm-devel] multipathd: error calling out mpath_prio_hds_modular

[malahal at us.ibm.com]

Craig Simpson [csimpson at visto.com] wrote:
> 
> The symlink didn't work, but coping the file to / worked. 

That is very odd! symlink or hardlink or a real copy of the program
should not make any difference as far as the execv() goes.

> 
> Thank You!
> Craig
> 
> -----Original Message-----
> From: dm-devel-bounces at redhat.com [mailto:dm-devel-bounces at redhat.com]
> On Behalf Of Craig Simpson
> Sent: Friday, May 16, 2008 4:19 PM
> To: device-mapper development
> Subject: RE: [dm-devel] multipathd: error calling out
> mpath_prio_hds_modular
> 
> 
> 
> I put a symlink in / 
> ln -s  /sbin/mpath_prio_hds_modular mpath_prio_hds_modular
> 
> But it still has the error. 
> 
> Where would I edit my /etc/multipath.conf to set this? 
> 
> Thanks!
> Craig
> 
> -----Original Message-----
> From: dm-devel-bounces at redhat.com [mailto:dm-devel-bounces at redhat.com]
> On Behalf Of malahal at us.ibm.com
> Sent: Friday, May 16, 2008 2:02 PM
> To: dm-devel at redhat.com
> Subject: Re: [dm-devel] multipathd: error calling out
> mpath_prio_hds_modular
> 
> The multipathd tried calling mpath_prio_hds_modular program but it could
> not find it! There is a bug in some version of RHEL where multipath has
> "mpath_prio_hds_modular" instead of "/sbin/mpath_prio_hds_modular".
> Update your multipath tools package or fix it in your
> /etc/multipath.conf (this requires some careful modifications!)
> 
> --Malahal.
> PS: since execv looks for your executable file in the 'cwd', you can
> probably make it work by just copying /sbin/mpath_prio_hds_modular to
> /mpath_prio_hds_modular (I am assuming that multipathd daemon makes "/"
> as it ***home*** before calling this.)
> 
> Craig Simpson [csimpson at visto.com] wrote:
> > 
> > My RedHat 5.1 ES server (actually it is that but rebranded as Oracles
> > latest Linux) is  logging this in /var/log/message all the time. 
> > 
> > It is attached to a Hitachi SAN device. 
> > 
> > All seems to be working OK, but these errors go on and on. 
> > 
> > Don't get what they mean?
> > 
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 65:0
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 65:16
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 65:32
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 65:48
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 65:64
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 65:80
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 8:0
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 8:16
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 8:32
> > May 16 19:48:01 wpe01 multipathd: error calling out
> > mpath_prio_hds_modular 8:48
> > 
> > 
> > Craig
> > 
> > --
> > dm-devel mailing list
> > dm-devel at redhat.com
> > https://www.redhat.com/mailman/listinfo/dm-devel
> 
> --
> dm-devel mailing list
> dm-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 
> --
> dm-devel mailing list
> dm-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 
> --
> dm-devel mailing list
> dm-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel