FTP not finish up its job

[mohdamir]

Hi there,
We found that, files transfer from server A to server B is sometimes not truly successful even though the log shows otherwise

2010/03/20 00:19:38 Connected to remote230 User cdisime logged in. Access restrictions apply.^M
2010/03/20 00:19:38 Transfering file c022M04a01006.1269015213550226.Z
2010/03/20 00:19:38 Done transfering
2010/03/20 00:19:38 /cdis/cdcc/fsdir/ForFTP/c022M04a01006.1269015213550226.Z File removed successfully
2010/03/20 00:19:38 Transfering file c0BEM18676023.1269015258210149.Z
2010/03/20 00:19:38 Done transfering
2010/03/20 00:19:38 /cdis/cdcc/fsdir/ForFTP/c0BEM18676023.1269015258210149.Z File removed successfully
2010/03/20 00:19:38 Transfering file c06CM454cc018.1269015346500170.Z
2010/03/20 00:19:38 Done transfering
2010/03/20 00:19:38 /cdis/cdcc/fsdir/ForFTP/c06CM454cc018.1269015346500170.Z File removed successfully
2010/03/20 00:19:38 Transfering file c09CM951c403a.1269015382790325.Z
2010/03/20 00:19:38 Done transferring

In reality, the above file from server A does not actually ftp over to server B completely. Some files are still not FTP but the log shows otherwise.
Is it due to ftpaccess implementation? I've checked the option and found that the target directory is allow largefiles.

[Dennis Handly]

>Some files are still not FTP but the log shows otherwise.

Are the files there at all or are they truncated?

What are the HP-UX versions of the two servers?

[Michael Steele_2]

Hi

I don't think is the syslog.log and all the error codes associated to the ftpd that are written into syslog.log. Nor does it look like you have the -d debugging option on.

Add -f top ftpd in /etc/inetd.conf, restart with inetd -c, and check syslog. I want the error codes.

I'd also like to see your scirpt, and for you to place this command right after you 'ftp' command,

ftp...
echo $?

-or-,

ftp
STAT=$?
...
echo $STAT

[Steven Schweda]

> In reality, [...]

Could you show us some of that reality?

> [...] the above file from server A does not
> actually ftp over to server B completely.

Which "the above file"? Evidence? (Actual
"ls -l" output, for example?)

You're sure that the source file is closed
and stable when the FTP transfer begins?

> Is it due to ftpaccess implementation?

I'm not aware of any ftpaccess options which
are intended to enable data corruption.

> I've checked the option and found that the
> target directory is allow largefiles.

Again, can we see the evidence?

> What are the HP-UX versions of the two servers?

A fair question (which should never need to
be asked).

[mohdamir]

b