The latest upload was successful again. I deleted the old non working files and the ones that were created today didn't trigger the error.
- erf-mschroeder
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- erf-mschroeder
Failure reading network stream
Hello,
I have a program that creates two csv files daily. A script that I wrote using WinSCP assembly uploads those to a FTP server. Since yesterday this task fails.
I tried using the GUI version, but that fails, too. So it is not a problem with the assembly. I updated both to the latest version.
Some information:
The server uses vsftp with explicit encryption.
FileZilla uses extended passive mode and WinSCP "only" passive mode. As far as I see that shouldn't be the cause.
The error message on the server side:
WinSCP logs (I translated some entries into English myself):
The file gets created on the server and has the same size (in bit) as the local file. So it seems that the transfer itself was a success but it failed to successfully finish.
If further data is required I will gladly provide that.
I have a program that creates two csv files daily. A script that I wrote using WinSCP assembly uploads those to a FTP server. Since yesterday this task fails.
I tried using the GUI version, but that fails, too. So it is not a problem with the assembly. I updated both to the latest version.
Some information:
- - only one of the two csv files fail
- aside from some changes in lines I see no difference between the old (working) file and the new one that fails (start and end are identical in editor and hex editor)
- using FileZilla works, but that lacks the automation function
The server uses vsftp with explicit encryption.
FileZilla uses extended passive mode and WinSCP "only" passive mode. As far as I see that shouldn't be the cause.
The error message on the server side:
Tue Jul 23 10:03:31 2019 [pid 10202] [user] FTP response: Client "IP address", "200 Switching to Binary mode."
Tue Jul 23 10:03:31 2019 [pid 10202] [user] FTP command: Client "IP address", "PASV"
Tue Jul 23 10:03:31 2019 [pid 10202] [user] FTP response: Client "IP address", "227 Entering Passive Mode (138,201,251,140,239,139)."
Tue Jul 23 10:03:31 2019 [pid 10202] [user] FTP command: Client "IP address", "STOR file.csv"
Tue Jul 23 10:03:31 2019 [pid 10202] [user] FTP response: Client "IP address", "150 Ok to send data."
Tue Jul 23 10:03:31 2019 [pid 10201] [user] DEBUG: Client "IP address", "DATA connection terminated without SSL shutdown. Buggy client! Integrity of upload cannot be asserted."
Tue Jul 23 10:03:31 2019 [pid 10202] [user] FTP response: Client "IP address", "426 Failure reading network stream."
Tue Jul 23 10:03:31 2019 [pid 10202] [user] FAIL UPLOAD: Client "IP address", "/folder/file.csv", 327390 bytes, 3849.51Kbyte/sec
WinSCP logs (I translated some entries into English myself):
< 2019-07-23 11:48:36.028 200 Switching to Binary mode.
> 2019-07-23 11:48:36.028 PASV
< 2019-07-23 11:48:36.060 227 Entering Passive Mode (138,201,251,140,102,40).
> 2019-07-23 11:48:36.060 STOR file.csv
. 2019-07-23 11:48:36.060 connecting to IP_address:26152 ...
. 2019-07-23 11:48:36.075 Data connection opened
< 2019-07-23 11:48:36.106 150 Ok to send data.
. 2019-07-23 11:48:36.106 Data connection opened
. 2019-07-23 11:48:36.106 Trying reuse main TLS session ID
. 2019-07-23 11:48:36.106 TLS layer changed state from none to connected
. 2019-07-23 11:48:36.138 Session ID reused
. 2019-07-23 11:48:36.138 TLS connect: SSLv3 read server hello A
. 2019-07-23 11:48:36.138 TLS connect: SSLv3 read finished A
. 2019-07-23 11:48:36.138 TLS connect: SSLv3 write change cipher spec A
. 2019-07-23 11:48:36.138 TLS connect: SSLv3 write finished A
. 2019-07-23 11:48:36.138 TLS connect: SSLv3 flush data
. 2019-07-23 11:48:36.138 Using TLSv1.2, cipher TLSv1/SSLv3: ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA, ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD
. 2019-07-23 11:48:36.138 TLS connection established
< 2019-07-23 11:48:36.388 426 Failure reading network stream.
. 2019-07-23 11:48:36.388 file copy to remote machine failed.
. 2019-07-23 11:48:36.388 Got reply 4 to the command 4
* 2019-07-23 11:48:36.388 (ExtException) **file copy to remote machine failed.**
* 2019-07-23 11:48:36.388 Failure reading network stream.
The file gets created on the server and has the same size (in bit) as the local file. So it seems that the transfer itself was a success but it failed to successfully finish.
If further data is required I will gladly provide that.