timeout within copying script

I try to copy a remote file with a script and I always get the message, that the hostz did not answer for 15 seconds.

here is the end of log-file:

. 2005-08-30 12:02:52.406 Startup conversation with host finished.
. 2005-08-30 12:02:52.406 Cached directory change via "/usr/local/apache/sites/mysite.net" to "/usr/local/apache/sites/mysite.net".
. 2005-08-30 12:02:52.406 Getting current directory name.
. 2005-08-30 12:02:52.406 Listing file "index.htm".
. 2005-08-30 12:02:52.406 Locating to cached directory "/usr/local/apache/sites/mysite.net".
> 2005-08-30 12:02:52.406 cd "/usr/local/apache/sites/mysite.net" ; echo "WinSCP: this is end-of-file:$status"
< 2005-08-30 12:02:52.625 WinSCP: this is end-of-file:0
> 2005-08-30 12:02:52.625 ls -lad "index.htm" ; echo "WinSCP: this is end-of-file:$status"
< 2005-08-30 12:02:52.812 -rw-r--r-- 1 root root 446 Aug 28 2002 index.htm
< 2005-08-30 12:02:53.062 WinSCP: this is end-of-file:0
. 2005-08-30 12:02:53.062 Copying 1 files/directories to local directory "c:"
. 2005-08-30 12:02:53.062 PrTime: Yes; PrRO: Yes; Rght: rw-r--r--; PrR: No; FnCs: N; RIC: 01; Resume: S (10240); CalcS: No; Mask: /dev
. 2005-08-30 12:02:53.062 TM: M; ClAr: No; ExclM(No):
. 2005-08-30 12:02:53.062 AscM: *.*htm*; *.txt; *.php*; *.cgi; *.c; *.cpp; *.h; *.pas; *.bas; *.tex; *.pl; .htaccess; *.xtml; *.css; *.cfg; *.ini; *.sh; *.xml
> 2005-08-30 12:02:53.062 echo "WinSCP: this is begin-of-file" ; scp -r -p -d -f "index.htm" ; echo "WinSCP: this is end-of-file:$status"
< 2005-08-30 12:02:53.250 WinSCP: this is begin-of-file
. 2005-08-30 12:03:08.250 Waiting for data timed out, asking user what to do.
. 2005-08-30 12:03:08.250 Asking user:
. 2005-08-30 12:03:08.250 Host has not answered for 15 seconds.
. 2005-08-30 12:03:08.250
. 2005-08-30 12:03:08.250 Wait for another 15 seconds? Pressing 'Abort' button will close session. ()
. 2005-08-30 12:03:08.250 Attempt to close connection due to fatal exception:
* 2005-08-30 12:03:08.250 Terminated by user.
. 2005-08-30 12:03:08.250 Closing connection.

Copying the file with the gui is no problem. Authentication is via the same stored session.
What's wrong?

You meant that the timeout does not occur in GUI or that it is automatically resumed once the server finally replies?

In the gui there is no problem - everything works fine and quick.

martin wrote:

You meant that the timeout does not occur in GUI or that it is automatically resumed once the server finally replies?

Can you post log file from GUI showing file transfer? Have you tried setting longer timeout?

I doubt, that it has something todo with the timeout, because all other operations are really fast (DSL).

By the way: with pscp.exe from putty everything works fine.

Here is the end of log-file of the copying per GUI:

Directory listing with --full-time succeed, next time all errors during directory listing will be displayed immediatelly.
Startup conversation with host finished.
Changing directory to "mysite.com".
cd "mysite.com" ; echo "WinSCP: this is end-of-file:$status"
WinSCP: this is end-of-file:0
Getting current directory name.
pwd ; echo "WinSCP: this is end-of-file:$status"
/usr/local/apache/sites/mysite.com
WinSCP: this is end-of-file:0
Listing current directory.
ls -la --full-time ; echo "WinSCP: this is end-of-file:$status"
total 168
drwxr-xr-x 5 root root 4096 Sun Jun 12 21:57:32 2005 .
drwxr-xr-x 12 root root 4096 Wed Dec 10 12:37:59 2003 ..
-rw-r--r-- 1 root root 5729 Tue May 31 21:17:53 2005 index.html
WinSCP: this is end-of-file:0
Copying 1 files/directories to local directory "C:\Temp\"
PrTime: Yes; PrRO: Yes; Rght: rw-r--r--; PrR: No; FnCs: N; RIC: 01; Resume: S (10240); CalcS: Yes; Mask: *.*
TM: M; ClAr: No; ExclM(No):
AscM: *.*htm*; *.txt; *.php*; *.cgi; *.c; *.cpp; *.h; *.pas; *.bas; *.tex; *.pl; .htaccess; *.xtml; *.css; *.cfg; *.ini; *.sh; *.xml
echo "WinSCP: this is begin-of-file" ; scp -r -p -d -f "index.html" ; echo "WinSCP: this is end-of-file:$status"
WinSCP: this is begin-of-file
Sending NULL.
T1117567073 0 1125485207 0
Sending NULL.
C0644 5729 index.html
Sending NULL.
Ascii transfer mode selected.
SCP remote side confirmation (0)
Sending NULL.
WinSCP: this is end-of-file:0

Anonymous wrote:

I doubt, that it has something todo with the timeout, because all other operations are really fast (DSL).

OK, I admit that it may not have. But please give it a try at least, if you have not done already.

I posted in a couple of other forums too, but to reiterate -
(I am running from the command line, FYI )

1.) I am seeing the timeout all the time, despite pretty reliable networks.
2.) When the timeout occurs, no error is returned, so the batch file I use to launch this has no idea anything went wrong and can't retry.
3.) While this seems to be a winscp bug, there should also be some sort of auto-retry and auto-reconnect option.

I tried to do this with
:Retry
winscp3 blah blah blah || goto Retry

but since no error is returned on timeout, it never retries.

I'd poke around myself, but don't have Borland's tools...

Anonymous wrote:

I posted in a couple of other forums too, but to reiterate -
(I am running from the command line, FYI )

See answer in your other post.

martin wrote:

Anonymous wrote:

I posted in a couple of other forums too, but to reiterate -
(I am running from the command line, FYI )

See answer in your other post.

OK, but to boldly summarize feature requests,
1. There should be a configurable retry parameter with # of retries and timeout between them.
2. Timeout and log settings should be configurable from the command line.
3. Any error in transfer should return an error. Since several people have encountered it, it does seem likely that it is a bug.
4. There should be an option to suppress the second console window when running in console. I like to run silently in the background and capture output to a log file, and spawning a new terminal complicates this greatly.

Thanks for your quick response and keep up the good work.

1. There should be a configurable retry parameter with # of retries and timeout between them.

Sure, but it is quite difficult to implement.

2. Timeout and log settings should be configurable from the command line.

You cannot have everything configurable from command-line.

3. Any error in transfer should return an error. Since several people have encountered it, it does seem likely that it is a bug.

OK, once I'm able to reproduce that.

4. There should be an option to suppress the second console window when running in console. I like to run silently in the background and capture output to a log file, and spawning a new terminal complicates this greatly.

Please refer to the documentation.