-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large file transfer stopped #279
Comments
Is this consistent? Could you use |
It seems to be consistent: This is the receiver log, followed by the sender log. �[0;36m[debug] �[0m07:52:02 cli.go:126: debug mode on I started the sender like this: croc --debug Sage50.zip > croc-debug.txt [debug] 07:51:19 cli.go:123: debug mode on |
Is your large file being written by another program while it is being read (i.e. like alog file)? |
No, it is a .zip file and the same file I had the problem with I reported 1st. |
Is this problem bidirectional? |
I can reproduce the problem only by sending from Win10 to Linux. That never goes through in one go. Sending from Linux to Win10 was no problem. I thought it might be a problem with the Win10 disk drive or filesystem. So I made a test from a new USB connected drive. Same problem. Again all the time both systems were connected by a ssh tunnel, so I assume the connection was stable. I had to ^c on the Linux side. This resulted in (on the Win10 = sending side): Sage50.zip 17% |¦¦¦ | (86/478 MB, 86.370 kB/s) [22m45s:1h17m28s]panic: wanted to write 32814 but wrote 0: write tcp 192.168.192.15:53566->142.93.177.120:9010: wsasend: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. goroutine 15 [running]: The tail of the Linux side logfiles: [debug] 08:41:45 message.go:43: writing recipientready message (encrypted) |
Same issue, not only when sending large files, but also when sending small files. |
Problem while transfering a 500 MB file (.zip) from Win10 to Manjaro (Arch) Linux.
Manjaro Version: croc version v8.3.1-f2af0b7
Win10 Version was just downloaded via scoop
The transfer stopped multiple times (3-4x). The 1st around 25% worked without problems. After I noticed I killed the connection on the receiving side (Linux) and re-connected. The re-connect worked without problems.
The connection was stable since I was using VNC over ssh at the same time.
One way of getting around would be an auto reconnect as described in #151
BTW: croc is a very nice program. Well done!
The text was updated successfully, but these errors were encountered: