make_net_recovery lock file

[MikeL_4]

Receiving message:

ERROR: Another instance of make_net_recovery/make_tape_recovery is already running.

I had to cancel a make_net_recovery to resolve an NFS issue and when trying to restart I receive above message.

Is there a lock file somewhere that I need to remove ??

[Sameer_Nirmal · Accepted solution]

Hi Mike,

First of all, check for "make_net_recovery" process or related processes if running already.
# ps -ef | grep -i make

If there is any, kill those processes.

The make_sys_image_flag file
in /var/tmp/ign_config/make_sys_image/make_sys_image_flag is lock file that will prevent another process from running concurrently.
You can remove this directory
# rm -r /var/tmp/ign_config

Then try run make_net_recovery again.

[Robert-Jan Goossens_1]

Mike,

Check this doc.

Title: make_net_recovery fails to run
Document ID: UIUXKBRC00013210

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000080022104

Robert-Jan

[Darrel Louis]

Mike,

Make sure you've killed all the old ignite processes.

rm -r /var/tmp/ign_config

This temporary directory contains the file
/var/tmp/ign_config/make_sys_image/make_sys_image_flag that will prevent
another make_sys_image process from running concurrently.

Goodluck

Darrel

[Florian Heigl (new acc)]

The path to the ignite lock file is contained in this very error message, about 20 lines above.

but as You write about a NFS issue You might also have an ignite process stuck on IO.

the following commands could help looking for that:

ps -ef | egrep '(ignit|make)'

mount | grep ignite

(everything below /var/opt/ignite might be orphans from the last ignite run. umount them, if possible.)

[MikeL_4]

Thanks, found process that had NFS mounts to the Ignite server still active.