Re: ftp mget failing, update on progress

Just in case anyone cares (and I am not suggesting that you should) ...

On Fri, 2009-10-09 at 13:38 -0400, Terrence Enger wrote:

On Fri, 2009-10-09 at 11:11 -0500, Scott Klement wrote:

Are you going through a firewall? Possibly some of the ephemeral ports
are blocked?

Thank you, Scott, for telling me to get my nose out of my script.
<grin />

I think that that *may* have been the problem: on my local router, I
opened all inbound ports from the iSeries, and I have just run three
successful downloads in succession. I say only "may" because
(*) Until earlier this week, the download was working routinely anyway.
(*) My router is home-grade, and while the (html) display suggests it is
running IPTABLES, it protects from the details of the rules. Sigh!
(*) I do not understand just why the download would fail between one
member and the next. Still, nowhere is it written that I shall
understand everything. It is easy enough to imagine that the router
failed to clean up its table of related connections when connections
were closed, and then it is easy to throw around words like "table
overflow" and so forth.

Anyway, the problem is in abeyance for now, and for that I thank you.

Cheers,
Terry.

The problem returned, and it persisted even when I tried the transfer
from the DMZ offered by my router. I have changed the program to use
ftp passive mode, and it has run successfully several times in a row.

I do not understand, but once again the problem is in abeyance. Thank
you, Scott, for your help.

Cheers,
Terry.

Terrence Enger wrote:

Greetings,

I regularly do an ftp mget from an example of our favourite platform
(V5R2M0) to my PC (ubuntu hardy). I am making a local copy of a source
file.

About half the time, after transferring lots of members, the job pauses
indefinitely with the last few messages being something like ...

250 File transfer completed successfully.
11826 bytes received in 0.26 secs (43.8 kB/s)
local: QALLSRC.FILE/AA4614.MBR remote: QALLSRC.FILE/AA4614.MBR
200 PORT subcommand request successful.

When running from an expect script, the script eventually times out.
Interactively, I press ctl-C, and ftp tells me

421 Service not available, remote server has closed connection
receive aborted

Can anybody suggest something I can do to track down the cause of my
problem? I have authority to WRKJOB on the ftp server job only while
things are still working, not thereafter. <sigh />

Cheers,
Terry.