Operating System - OpenVMS
1828584 Members
2540 Online
109982 Solutions
New Discussion

Problem with telnet on Itanium

 
The Brit
Honored Contributor

Problem with telnet on Itanium

Just brought upt Itanium Cluster on OpenVMS 8.3-1H1 and TCPIP services V5.6 ECO2.

I am experiencing a problem on one node (the busiest, where TELNET/FTP crashes. I have not found any logfiles, (not sure where to look).

System doesn't crash. login at the console shows TCPIP$FTP process missing. Shutting down TCPIP Services and restarting fixes the problem and recreates the TCPIP$FTP process.

This has happened twice inside an hour, seems like some kind of TCPIP quota issue.

Any suggestions.

thanks.

Dave
6 REPLIES 6
marsh_1
Honored Contributor

Re: Problem with telnet on Itanium

dave,

log files should be in sys$sysdevice:[tcpip$ftp] , might also be privileges.

Robert Gezelter
Honored Contributor

Re: Problem with telnet on Itanium

Dave,

While troubleshooting, a small suggestion. Try only shutting-down/restarting the FTP service. There is a good chance that it is not necessary to re-start all of TCPIP.

The command files to do this should be in SYS$MANAGER.

- Bob Gezelter, http://www.rlgsc.com
marsh_1
Honored Contributor

Re: Problem with telnet on Itanium

dave ,

the server log file is in sys$manager, do they go straight away or while in use ? have any changes been made to those services ?

Wim Van den Wyngaert
Honored Contributor

Re: Problem with telnet on Itanium

Did you check accouting ?

Wim
Wim
Volker Halle
Honored Contributor

Re: Problem with telnet on Itanium

Dave,

the TCPIP$FTP_1 server process itself does not have a .LOG file. The individual FTP operations may be logged in SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_RUN.LOG

The TELNET service does not have a server process.

Are other TCPIP services enabled and still working ?

Volker.
The Brit
Honored Contributor

Re: Problem with telnet on Itanium

Problem finally tracked down after a system crash.

As part of the migration, chenged stacks from TCPWare to TCPIP Services. Some users were still executing the TCPWARE:Define_Commands command file and redefining the Telnet symbol as "run TCPWARE:TELNET" (which unfortunately still existed) and this is incompatable with the TCPIP Services stack, causing either process crash TCPIP$INET, or System Crash.

Thanks for all of your suggestions.

Dave