make_tape_recovery make_tape_recovery completed unsuccessfully

[Goran Kubelka]

Dear Sirs,
When I start make_tape _recovery on HP-UX host (11i)
the last 3 lines of recovery.log are as follow:

* Creation of system archive complete

Program Terminated. SIGHUP received. Exiting.


======= 11/05/02 09:47:57 MET make_tape_recovery completed unsuccessfully

Plaese help

[steven Burgess_2]

Hi

Can you post your command, was this run from cron or the command line ?

Kill -1 = SIGHUP

1 SIGHUP Hangup Terminate; can be trapped

Regards

Steve

[Elif Gius]

Hi,

did you start your command in the forground???

Can you do a make_recovery -v ... ?

[Goran Kubelka]

The command from command line was:
make_tape_recovery -v -x inc_entire = vg00.

There is no any error message in the recovery log except the one previously mentioned.

[melvyn burnard]

did you log out before the command had completed?
Somoen/something has sent a SIGHUP to this process, telling it to terminate cleanly.
Normally, if you start a command, and then do Ctl-d or logout, this sends a SIGHUP to the process.
You can trap this by preceding the command with the nohup command:
nohup make_tape_recovery .....

If you did NOT log out or terminate that login session, then someone has sent a kill -1 to the process.
Finding that is going to be dificcult

[Goran Kubelka]

It look like Mr. Melvyn have an answer that is near my solution. I forget to mention that I start make_ tape_recovery via terminal session. Because timeout in session , I `m disconected from host during make_tape_recovery operation ,but if I check with "ps" from new terminal session the process of making recovery is still active. After 10-15 min it finish. Any Idea?

[melvyn burnard · Accepted solution]

well there is your answer.
The forced logout would have sent the SIGHUP to the make_recovery_process. As this tells the command to "finish what you are currently doing, and then die cleanly" , and the command may be writing to a tape, this can take time to actually finish and die, so it would have been adopted by PPID1 (init process) and carried on until exiting.
I would suggest you either turn off the auto timeout, or run eth command using nohup and put it in the background.

[Goran Kubelka]

Mr. Melvyn,
I thing the idea with turning off auto timeout will be more suitable for my situation since I start make_tape_recovery in verbose mode. Any suggestion about easyest and fastest way how to disable autotimeout for terminal sessions?

[T G Manikandan]

check for the parameter

Check for the variable
TMOUT=

check the global file /etc/profile or the local .profile file of the user and comment it out.

For csh, the variable is autologout and is in minutes.

If csh then look at the global file /etc/csh.login and the local files .cshrc and .login files.

Just comment it out to disable it.

Thanks