Optimize connection buffer size

Advertisement

srjones67
Joined:
Posts:
4

Optimize connection buffer size

I am receiving the message that I have noted in the subject:

Host is not communicating for more than 15 seconds.
Still waiting...
Note: If the problem repeats, try turning off 'Optimize connection buffer size'.
Warning: Aborting this operation will close connection!
(A)bort (58 s):

I made what I thought was the proper adjustment but it's still occurring. The transfer completes but I repeatedly get the error. This is the command that I am executing:

"C:\Support\Utils\WinSCP\winscp" /script=C:\Support\Scripts\CorrectAddress\CA_Update_Get.txt /parameter "user:pw" "site.url.com" "/CorrectAddress/Geocoder" "C:\Support\Scripts\CorrectAddress\incoming\Geocoder\" "*.*" /rawconfig SendBuf=0 /loglevel=0 /loglevel=0 /log=C:\Support\Logs\CA_Update_Get_2017-09-15.log

Any help would be appreciated.

Reply with quote

Advertisement

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

Re: Optimize connection buffer size

You have to add -rawconfig SendBuf=0 to the open command within the CA_Update_Get.txt

Reply with quote

srjones67
Joined:
Posts:
4

I'm getting this error with that change: Too many parameters for command 'open'.

This is my open command in CA_Update_Get.txt: open sftp://%1%@%2% -rawconfig SendBuf=0

I did remove the /rawconfig SendBuf=0 from the calling command. If I change -rawconfig SendBuf=0 to -rawsettings SendBuf=0 it seems to work.

Update: -rawconfig on open command yields too many parameters. -rawsettings gives no parameter error but still get try turning off 'Optimize connection buffer size.

Reply with quote

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

Are you using the latest version of WinSCP?

If you are, please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session 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

Vann_the_Red
Guest

Eerie Solution?

martin wrote:

Are you using the latest version of WinSCP?

If you are, please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session 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.

I found this thread because I was experiencing the exact same problem as the OP. I turned on logging as Martin directed. It immediately started working. No idea why logging the session mattered, but that seems to have done it.

VtR

Reply with quote

srjones67
Joined:
Posts:
4

Log File

Here is a log of what is occurring. I'm using WinSCP, Version 5.7.2 (Build 5316).
  • CA_Update_Get_2018-01-17.log (1.36 MB, Private file)

Reply with quote

Advertisement

You can post new topics in this forum