I am getting more and more sure that this is something at the cloud provider side. However, I tested WDMRC yesterday as well, and I would say, the issues with the cloud are reproduced synchronously with both WDMRC and the built-in rclone mailru support. So now it has nothing to do with WebDavMRC. I had used WebDavMailRuCloud before I switched to the built-in rclone's mailru support, and in order to not to update my script files I kept the same remote name starting with "wdcmr". Disclaimer: rclone is not affiliated with WDMRC. I'd like to isolate moving parts to be sure what we are fixing here. If yes, does the problem persist if you use rclone with directly (i.e. May the remote name wdcmr mean that you use via webdav protocol available on business plans?Īre you using the WebDavMRC external tool in between to convert API to webdav? Thus, it will be really helpful to detect this situation and stop trying to upload anything immediately, and then resume after a given amount of time. And, damn, while I was writing this, everything began to work again. A single file successfully finds its way to the cloud, but a folder with files does not. Some files had been uploaded correctly but at some point all further files could no longer be uploaded and I found in the morning a lot of 0% lines in the log.Īnd the same thing happens to the "rclone copy" command. Transferred: 0 / 1.993 GBytes, 0%, 0/s, ETA -Īnd this began last night somewhere in the middle of a long sync procedure. I get in the log (for the same file "file.z01") a virtually unending series of lines like this: Rclone.exe sync "X:\my-archive" "wdcmr-admin:\my-archive" -no-update-modtime -vvv -transfers 1 Transferred: 1019.027M / 1.993 GBytes, 49%, 17.024 MBytes/s, ETA 1mĪnd finally I get this file in the cloud. I get in the log a series of lines like this (with gradually increasing percentage value): Rclone.exe sync "X:\my-archive\file.z01" "wdcmr-admin:\my-archive" -no-update-modtime -vvv When I run "rclone sync" for a single file, the file uploads successfully.īut when I run "rclone sync" for the whole folder, nothing gets uploaded. Now, as I have done some more testing, this looks even more weird to me. Because now for a 200-gigabyte archive (split, say, into 100 files) rclone is working for about half a day without actually doing anything. On the other hand, it is at least important to make rclone detect that the uploading is not really happening, and quickly return with an understandable error. it is probably using the same server API, but somehow the server differentiates it's calls from the rclone's calls. So, on the one hand it could be great to know what is the difference between how rclone works with the cloud backend and how the original webapp does, and why the original webapp is not banned - i.e. And when I try to upload the file with another rclone-like tool, it does not work just like rclone does not work. Interestingly, when I try to upload a file to the same cloud through the web, through their own website, the file is uploaded successfully. And I had to wait for a month or so, until it was workable again. I can remember I had such problem in the past, using _another_tool, not rclone. This continues until rclone goes through all files (which may take hours), and finally rclone returns with error level 1. The log fragment above is repeating in cycles for a while (for a big file this can take several minutes or even half an hour or maybe even longer), and then rclone proceeds to the next four files, not uploading anything again. but when files upload starts, it is simply not uploading anything, and in the log there is a series of lines like this:.if I use some reading command, like 'lsd' it operates correctly and returns the expected result.further initial data exchange passess successfully, including checking of the files etc.When I run rclone sync I can see the following: But anyway, after I had uploaded a huge amount of data into the cloud (I would say, about 1 terabyte within a couple of days), I am having the following situation. Or maybe this is a protection from a DDoS attack I don't know. While testing another issue ( #3988) I have discovered that the cloud has a certain limit of how many bytes in total you can transfer within a period of time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |