Hi all,
We run hundreds of // EXEC FTPBATCH steps every day, using CSI’s 1.5F stack and FTP client.
99.999% runs fine but every now and then we see the following happening for an FTP PUT to our FTP-server on the local network :
FTP309W COMMAND PUT FAILED AND WILL BE RETRIED.
FTP321W CONNECTION STALLED AT 22:02:54
FTP347W QUERY CONNECT,EXTENDED ISSUED FOR 0.0.0.0,0 (6667)
FTP321W CONNECTION STALLED AT 22:03:54
FTP347W QUERY CONNECT,EXTENDED ISSUED FOR 0.0.0.0,0 (6667)
FTP938W PAWA DATA CONNECTION OPEN TO F:0.0.0.0,0 L:127.0.0.1,6667 FAILED
FTP309W COMMAND PUT FAILED AND WILL BE RETRIED.
FTP321W CONNECTION STALLED AT 22:04:54
FTP347W QUERY CONNECT,EXTENDED ISSUED FOR 0.0.0.0,0 (6668)
FTP321W CONNECTION STALLED AT 22:05:54
FTP347W QUERY CONNECT,EXTENDED ISSUED FOR 0.0.0.0,0 (6668)
FTP938W PAWA DATA CONNECTION OPEN TO F:0.0.0.0,0 L:127.0.0.1,6668 FAILED
FTP320W QUIT COMMAND SENT AFTER ERROR
FTP350E NO SUCCESSFUL LOCAL 226 MESSAGE RECEIVED
FTP328E FTPBATCH FAILED RC=00000008 ,CHECK SYSLST FOR ERRORS
“SET RETRY 2 1500” was active for the PUT command, which is why the PUT command was executed 3 times.
But I have no clue whatsoever why the PUT command failed. There’s no FW involved, no errors were found on the network, no errors on the FTP-server, no network backups were locking any files etc…
Why is the FTP-client using(or at least showing) foreign IP address “0.0.0.0,0”?
An immediate rerun of the FTP-step worked just fine.
Sometimes this happens several times on the same day, sometimes it doesn’t happen for weeks in a row. Anyone seen this before?
Thanks,
Geert.
Did you try setting the DIAGNOSE on to see if any additional messages are being issued. I have run into this years ago, but not for a LONG time. Are you current with TCP/IP maintenance?
David Wakser
David,
I refreshed TCP/IP for VSE last year in June, and added a bunch of PTF’s.
I tried running with SET DIAGNOSE FTP but that doesn’t seem to give me any (understandable) extra info.
Still wondering why it’s using IP address 0.0.0.0,0…
Thanks,
Geert.
I agree – but last year June was a year ago! I think you’ll have to open a ticket with support, and might need to start a trace for them, but they will probably insist on you being current with their software.
David, I had a look at the descriptions of the 16 PTFs that were published after our refresh in June, but I didn’t see any that would directly apply to this problem.
Maybe I’ll open that ticket…
Regards,
1.5.F is current. I don’t think G is GA yet. We’ve been told by CSI several times to stay away from it for now….
__________________________________
Andy Engels
IS Team Leader - Technical Services
Illinois Municipal Retirement Fund
Oak Brook, IL
630-368-5346