Host is not communicating for more than 15 seconds

Hi,

we recently experienced problems connecting to linux servers with winscp:

we get a message "host is not communicating for more than 15 seconds" and the transfer is interrupted

this happens with multiple servers and multiple clients

the servers are on Centos 5 with OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008

client is on windows 7 with winscp 5.7

we tried disabling the "optimize buffer size" option as it is mentioned in the error message but it doesn't help

the log on the server looks like this:

Mar 16 13:10:09 av950 sftp-server[20279]: open "/abc/def" flags READ mode 0666
Mar 16 13:10:10 av950 sftp-server[20279]: close "/abc/def" bytes read 3276800 written 0
Mar 16 13:10:10 av950 sftp-server[20279]: open "/abc/xyz.txt" flags READ mode 0666

then it stops

on the client side we have:

. 2015-03-16 13:10:08.308 File: '/abc/xyz.txt' [2014-07-15T08:07:07.000Z] [669]
. 2015-03-16 13:10:08.309 Copying "/abc/xyz.txt" to local directory started.
. 2015-03-16 13:10:08.309 Binary transfer mode selected.
. 2015-03-16 13:10:08.309 Opening remote file.
> 2015-03-16 13:10:08.309 Type: SSH_FXP_OPEN, Size: 83, Number: 214275
< 2015-03-16 13:10:08.310 Type: SSH_FXP_STATUS, Size: 24, Number: 214020
. 2015-03-16 13:10:08.310 Discarding reserved response
. 2015-03-16 13:10:23.437 Waiting for data timed out, asking user what to do.
. 2015-03-16 13:10:23.437 Asking user:
. 2015-03-16 13:10:23.437 **Der entfernte Rechner kommuniziert seit 15 Sekunden nicht.
. 2015-03-16 13:10:23.437
. 2015-03-16 13:10:23.437 Weitere 15 Sekunden warten?** ()

this only happens with version 5.7, when we use 5.5.5 everything is fine

can you help us to fix this problem

thank you

Martin

Thanks for your report.

Can we try to find out what version introduced the problem?
Can you try 5.6.5 RC and 5.6.2 beta for a start?

https://sourceforge.net/projects/winscp/files/WinSCP/

Hi,

I tested it with 1.5 GB of files, 3 times

5.6.2 no errors
5.6.5 all 3 failed
5.7.0 all 3 failed
5.7.1 all 3 failed

we are going to use an older version for the time being

I'm going to check this thread in case you need more information

thank you

Martin

FWIW I'm experiencing the same issue. Exact same version of openssh, although on redhat 5, not centos. I had tried disabling the

Rolling back to winscp 5.6.5 RC it seemed less common, although still occurs. If I repeatedly copy a file or directory it'll cause the error.

johanno wrote:

FWIW I'm experiencing the same issue. Exact same version of openssh, although on redhat 5, not centos. I had tried disabling the

Rolling back to winscp 5.6.5 RC it seemed less common, although still occurs. If I repeatedly copy a file or directory it'll cause the error.

Sorry, had meant to say "I had tried disabling the optimize buffer which didn't help". I've also tried switching from sftp to scp and it still occurred then.

Martin H wrote:

5.6.2 no errors
5.6.5 all 3 failed
5.7.0 all 3 failed
5.7.1 all 3 failed

Thanks for the tests.
Can you also try 5.6.3 beta and 5.6.4 RC?

Also, can any of you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

(I'm johanno from before 8) )

5.6.3 and 5.6.4 have the problem, 5.6.2 does not. I will email you momentarily. Thanks.

Same issue but different logs. Changed the shell from "Default" to "/bin/sh" in "Advanced Site Settings > Environment > SCP/Shell"

I found this while looking on debug logs, it seems to freeze here, after trying return code :


. 2015-03-30 16:32:06.208 Trying "$status".
> 2015-03-30 16:32:06.208 echo "$status" ; echo "WinSCP: this is end-of-file:0"
. 2015-03-30 16:32:06.208 Sent 54 bytes
. 2015-03-30 16:32:06.208 There are 0 bytes remaining in the send buffer
. 2015-03-30 16:32:06.208 Looking for network events
. 2015-03-30 16:32:06.208 Timeout waiting for network events

hth,
ian

same here: 5.6.3 and 5.6.4 both have the same problem

I just sent you an email

This bug has been added to the tracker:
https://winscp.net/tracker/1306