HP3000-L Archives

September 2002, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"HOFMEISTER,JAMES (HP-USA,ex1)" <[log in to unmask]>
Reply To:
HOFMEISTER,JAMES (HP-USA,ex1)
Date:
Tue, 17 Sep 2002 10:43:27 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (58 lines)
Hello All,

RE: FTP stall question

----------------------------------------------------------------------
470 ftp> PUT PMAUTHOT t123456.789
471 200 PORT command successful.
472 150 Opening ASCII mode data connection for t123456.789.
473 Connection timed out
474 ftp> :SETVAR PTFTP_PUTERR,FTPLASTERR
475 ftp> DIR
477 JOB aborted by system management. (CIERR 6027)
478 CPU sec. = 5.  elapsed min. = 303.  SUN, SEP  8, 2002, 12:15 AM.
----------------------------------------------------------------------

I would suspect the "473 Connection timed out" is likely due to a
network or link outage... if you are familiar with network logging on
MPE you could find more information by enabling informative logging
for ns-transport, duplicating the problem and then reviewing the NM
logfiles for retransmissions and connection terminations.

By specifying "exitonerror" prior to the PUT command you can avoid the
"DIR" command from being executed which is the hang condition you are
seeing.

The "DIR" command is waiting for a "200 PORT command ok" message from
the remote host and is not receiving the 2xx success message or a 4xx
or 5xx message indicating an error.  It is the correct operation for
the FTP client on the 3k to hang forever until:

- It receives a 2xx, 4xx or 5xx message.
- The TCP Connection for the FTP command port is closed.
- Or as in the case of this job: "JOB aborted by system management".

A workaround to the "extended" hang on the 3k FTP Client is to specify
the FTP Client "TIMEOUT" command in the job prior to the PUT with a
parameter specifying the maximum number of seconds to wait on a
receive on the data or command ports.  Rather than waiting 5 hours for
the job to be terminated, you could specify a "TIMEOUT 1800" for a 30
minute timeout.  Again it is important to use "exitonerror" or else
after this "TIMEOUT" on the dir, you will then execute the "next" FTP
command in this job which again may not make sense since the "put"
failed.

Note: SR 8606267935 includes a re-work of the "TIMEOUT" command and
some fixes for how long the FTP Client waits for open & close of
connections.  Beta patches FTPGDR4 7.0 & FTPGDR3 6.5 include this fix.

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2