Page 1 of 2

FTP error

Posted: Thu Feb 01, 2007 10:57 am
by narasimha
Hi all,

I am using FTP stage to transfer data from one server to another.

It is simple job design

Code: Select all

FTP Stage ------> Sequential File
The jobs has been running it production for well over a month now, but lately the job is aborting.(sporadically)
The log messages show as below

Code: Select all

IbiHeadGrpFileFtp..File_To_Be_Read.IDENT1: DSD.StageRun Active stage starting, tracemode = 0.
IbiHeadGrpFileFtp..HeadGrpFile_FTP: 230 User xxx logged in.
IbiHeadGrpFileFtp..HeadGrpFile_FTP: Error while trying to open connection for receiving data from the FTP server, FTP command PORT failed
Attempting to Cleanup after ABORT raised in stage IbiHeadGrpFileFtp..HeadGrpFile_FTP
Job IbiHeadGrpFileFtp aborted.
Changing the tracemode could give me more information, but I was wondering if somebody has had similar issues and got it resolved without doing that.
Any clues...

Posted: Thu Feb 01, 2007 11:02 am
by chulett
Any 'From previous run...' information if you reset the job? :wink:

Regardless, suggest you bump up the tracing level.

Posted: Thu Feb 01, 2007 11:02 am
by jhmckeever
narasimha ,

Have you tried telnetting to your server and performing the relevant FTP manually from the shell prompt?

J.

Posted: Thu Feb 01, 2007 11:04 am
by narasimha
Craig,

I get no addition information after doing a reset :(

Posted: Thu Feb 01, 2007 11:10 am
by narasimha
jhmckeever wrote:narasimha ,

Have you tried telnetting to your server and performing the relevant FTP manually from the shell prompt?

J.
Tried that too, runs without warnings
I get this error sporadically :?

Don't know why, I get the below warning message, only which the abort happens. Don't see this message in the previous runs though!

Code: Select all

IbiHeadGrpFileFtp..HeadGrpFile_FTP: 230 User xxx logged in.

Posted: Thu Feb 01, 2007 11:52 am
by jhmckeever
Hmmm ... sporadic errors are always the trickiest!

What's your FTP stage's settings for "FTP Data Connection Mode"? If it's the default 'active' then maybe try 'passive' (which will behave differently if you've got some weird firewall issue.)

J.

Posted: Thu Feb 01, 2007 12:16 pm
by narasimha
Yes, currently it is set to the default "Active". Will change it to "Passive" and bump up the trace level and see if it helps.
Sadly, I am not able to reproduce the errors consistently.

Posted: Thu Feb 01, 2007 12:21 pm
by I_Server_Whale
narasimha wrote:I get this error sporadically :?
Is there anything else (something different) happening with the Servers or the environment at those sporadic moments?

Posted: Thu Feb 01, 2007 12:36 pm
by narasimha
I_Server_Whale wrote:Is there anything else (something different) happening with the Servers or the environment at those sporadic moments?
Yes there other unrelated jobs which running at the same times on the same system.

Posted: Thu Feb 01, 2007 12:41 pm
by jhmckeever
I don't suppose those other jobs are also utilising the FTP stage?

J.

Posted: Thu Feb 01, 2007 12:43 pm
by narasimha
jhmckeever wrote:I don't suppose those other jobs are also utilising the FTP stage?

J.
Nope, This is the only job which is using the FTP Stage at that moment.

Posted: Thu Feb 01, 2007 1:33 pm
by DSguru2B
It seems like the open connection was denied for some odd reason or it was unable to open the connection. Its hard to trim the problem down if its not reproducable. Ditch the stage, do it from command line, get the file and read it with a sequential file stage.

Posted: Thu Feb 01, 2007 1:43 pm
by narasimha
"Ditch the stage" :wink:
I have saved it as my last option if nothing works.

Posted: Thu Feb 01, 2007 1:44 pm
by DSguru2B
I have never used that stage so I dont know how reliable it is. But if it keeps popping up with error, Id kill it :wink:

Posted: Fri Feb 02, 2007 4:15 am
by jhmckeever
narasimha ,

Which version of 7 are you using. I'm currently on a site using 7.1r2 and I've also had sporadic errors with the FTP Stage. In my case it's for a non-production job so I've not taken the time to uncover what's going wrong. Perhaps worth asking IBM about?

J.