restart multipathd automatically

restart multipathd automatically

[Stephen Mike]

Hi,

To restart multipathd automatically after it dies, is it ok to put, in
/etc/inittab, a line like this? 

# run multipathd at level 4 (restart)
mphd:4:respawn:/etc/rc.d/init.d/multipathd start

I am not sure whether the daemon has any dependencies to make it not OK
to start/restart this way.

Thanks
Mike

Re: restart multipathd automatically

[Luca Berra]

On Mon, Jan 21, 2008 at 03:54:02PM +0100, Stephen Mike wrote:
>Hi,
>
>To restart multipathd automatically after it dies, is it ok to put, in
>/etc/inittab, a line like this? 
>
># run multipathd at level 4 (restart)
>mphd:4:respawn:/etc/rc.d/init.d/multipathd start
>
no, it is not.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

Re: restart multipathd automatically

[Mike Anderson]

Luca Berra <bluca@comedia.it> wrote:
> On Mon, Jan 21, 2008 at 03:54:02PM +0100, Stephen Mike wrote:
>> Hi,
>>
>> To restart multipathd automatically after it dies, is it ok to put, in
>> /etc/inittab, a line like this? 
>> # run multipathd at level 4 (restart)
>> mphd:4:respawn:/etc/rc.d/init.d/multipathd start
>>
> no, it is not.

To add a little (hopefully)...

If multipathd is dieing it is better to determine why it is dieing.

Running multipathd in foreground mode with verbosity may provide info.
"/sbin/multipathd -d -v4"

If the issue is multipathd causing a segfault you would need to build a
non-strip version and then use ulimit -c unlimited to allow creation of a
core file.

You could then use gdb post getting a segfault to run "bt full" on the
core file to hopefully determine the area of the problem.

-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com