-
Notifications
You must be signed in to change notification settings - Fork 36
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 upload stuck at 100%, then file is deleted on server #116
Comments
Seems to be a WT problem (https://redmine.emweb.be/boards/2/topics/18414). Which is unfortunate, rendering the purpose of this app ineffective/useless: There is an proposed workaround, using chunk based uploads for large files. I researched it by adding additional log messages to fileshelter. The uploaded event of WT is never triggered. Trying version 4.11.0 of WT instead of 4.9.1. Hopefully fileshelter compiles with dat... I wonder if we can steal the spooled file after progress is == 100% and awaiting the secondary copy of the uploaded file. This would be a workaround that is based on polling the copy process. |
I am using version 6.2.0
I am uploading a file ~4.9GB to my raspberry Pi. The files are stored to an USB stick (working directory of fileshelter). The max file limit is set to 32GB. I already successfully uploaded a file of size ~600MB.
In the logfile, I think the upload starts at ~Oct 24 22:17:17 and probably finishes around ~Oct 24 23:03:01. Is this a filesystem (NTFS) syncing issue? The download seems to be finished the 4 spawned threads that were active during upload have terminated and cpu load is reducing again. It's just, that I do not see the result on the website and the file is deleted after a few minutes.
fileshelter.log.
The file that is affected is the wtQ5nzHd (snapshot from during the upload process):
Do you need additional information to analyze this issue?
Update:
WebController: timeout: expiring
,Wt: signal from dead session, sending reload.
messages in logfileThe text was updated successfully, but these errors were encountered: