On 2007-11-13, droid <jshowalter@gmail.com> wrote:
>> On Nov 12, 9:12 am, Bill Marcum <marcumb...@bellsouth.net> wrote:
>>
>>
>>
>> > val=$?
>> > echo "return code=$val"
>>
>> > You might try adding the -d option to ncftpget. It could be that one or
>> > more files were transferred successfully but some were not, or the ftp
>> > server is not a Unix server.
>
> Good suggestions, Bill. I added "echo "return code=$val"" and used "-
> d ncftpget.log". The server is Linux, so that is not the problem.
> The latest cron message has:
>
> bak_website: Now archiving http://mywebsite.com
> ncftpget: server said: File successfully transferred
> return code=3
> bak_website failed
>
> The ncftpget.log file is 805954 bytes - ncftpget does a lot of
> business! But grepping it for "error", "fail" and "warn" returns
> nothing.
>
Could you post a sample of that file, maybe the first or last 20
lines?

> Could return code 3 be set by the server message, "File successfully
> transferred" instead of by ncftpget?
>
That should not happen. Maybe you could try changing http:// to ftp://.

Have you tried getting files manually one at a time to see if you get an
error? Or you might try a loop like this:

until ncftpget -R http://mywebsite.com; do sleep 60; done

By default, ncftpget should try to resume a failed transfer, but this
might be a waste of time if the transfer failed for reasons other than
a broken connection (e.g. permission problems, i/o errors or disk full).