Looking for RETRY option in script

Advertisement

NBGuy
Joined:
Posts:
1
Location:
Eastern Canada

Looking for RETRY option in script

Hello,

Inside a script I am using the command "option batch abort" (I have also tried "continue")

Is there an undocumented way to use RETRY? Something like: "option batch retry"

I read the WinSCP documentation and found this values --> "off|on|abort|continue"



Using WinSCP 5.7.4 on Windows Server 2008 R2 Std SP1
WinSCP Version 5.7.4 (Build 5553) (OS 6.1.7601 Service Pack 1 - Windows Server 2008 R2 Standard)

> 2015-07-29 14:40:17.345 Script: option batch continue
< 2015-07-29 14:40:17.345 Script: batch continue
< 2015-07-29 14:40:17.345 Script: reconnecttime 120
> 2015-07-29 14:40:17.345 Script: option confirm off
< 2015-07-29 14:40:17.345 Script: confirm off
> 2015-07-29 14:40:17.345 Script: option exclude Thumbs.*
< 2015-07-29 14:40:17.345 Script: include |Thumbs.*

. 2015-07-29 14:40:17.345 FTP: FTPS: Implicit TLS/SSL; Passive: Yes [Force IP: A]; MLSD: A [List all: A]
. 2015-07-29 14:40:17.345 Session reuse: Yes
. 2015-07-29 14:40:17.345 TLS/SSL versions: TLSv1.0-TLSv1.2


Thank you

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
27,253
Location:
Prague, Czechia

Re: Looking for RETRY option in script

What do you want to retry?

Reply with quote

Guest

Hello
I have a scheduled FTPs job that has started to fail sometimes. Just sometimes. It can log in and transfer some files. Using WinSCP 574 on Win Srv 2008 R2 Std SP1
I was using "option batch abort" in my script.

I used WinSCP GUI and I was offered the "retry" option. I hit retry and it kept going.
If I use "option batch continue" all of the files will get transferred after multiple scheduled FTPs sessions.

I was wondering if "option batch retry" would help?
I have been unable to find a reason for WinSCP to drop sessions. It started within the last 6 days.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,253
Location:
Prague, Czechia

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

Advertisement

You can post new topics in this forum