telnet aborts

[James Ellis_1]

Hi,

I have a perculiar problem. My telnet session to a HP_UX 11.0 server aborts after inactivity of about 20 or 30 minutes. Are there anywhere I can look? The log files don't show anything, and when I try to run a make_recovery tape, in the ignite logs there is this line

"Program Terminated SIGHUP received."

Something terminated the creation of a make_recovery tape, but I cannot find what cause this termination. I hope you can pinpoint where to look?

Thanks.

[Sundar_7]

Hi James,

You might have TMOUT variable set. check /etc/profile for any reference to this variable.

Uncomment it or manually reset this parameter to 0 after logging in.

Sundar.

[Jeff_Traigle]

TMOUT set in the global profile or you're .profile?

[Sundar_7]

Hi,

It can be set in /etc/profile or in $HOME/.profile. Doesnt hurt to check in both the files.

Sundar.

[Bill Hassell]

Is the remote computer on another subnet or behind a router? Then you may have an automatic disconnect for idle telnet. This is a fairly common setting to avoid idle connections of a plain-text protocol. Change the options for Ignite/UX to add -v so there will be more text displayed. Even then, the actual backup of files may take longer than the idle telnet time in your router. Talk to your network administrator. Your only workaround is to run make_recovery in the background with a nohup and & to keep the process running.

NOTE: make_recovery has been obsolete for a long time. Download the latest Ignite package from http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IGNITEUXB

[James Ellis_1]

Thanks for your inputs!

I had another system administrator run make_recovery on another server and his completed. I tried to run make_recovery (same command) on the same server, and my telnet aborted.

Should the log files tell you it aborted? When I ran make_recovery, and the process terminated, the window hangs up.

I don't think its the command problem, it may be a network problem, but the net admin will look into this. Something is stopping me from running the complete make_recovery.

PS: I know I am in need of an Ignite upgrade, but will not do it until I get this fixed. This is because I have Ignite 4.2 on one server, and I have the same problem with executing Ignite on that server. At least in the server with Ignite 4.2, the /var/opt/ignite/recovery/latest/recovery.log shows a

"Program Terminated SIGHUO received".

I cannot seem to see where this is coming from, what process is terminating make_recovery.

Thanks.

[Bill Hassell]

SIGHUP is a hangup or disconnect. Something has terminated the session. Most likely it is a router with idle time rules that someone has forgotten about.