Closed kumarharsh closed 9 years ago
Should we contact Microsoft? lol
But let me try reproducing the problem later (later may mean winter break... too much course stuff pending recently...).
I'll try the reproduce the error today, but from what I can remember it almost always goes wrong in either the get()
or get_access_token()
.
Update:
Ran the daemon for the whole day and both errors occurred at some point. The Internal Server Error is always caused by the merge_dir()
(even when no directories are merged).
For the Connection reset by peer, I noticed MS Exchange does the same thing if to much traffic flows over the same connection. I've started to suspect that all Microsoft servers use some sort of firewall rule to block the connection if to much traffic is requested. I'm unable to find any kind of information or documentation about it.
@xybu Just had the winter(?) break, you mean Christmas? :P
From #42 there seem two related params: MaxClientMBTransferredPerDay = 537600 MaxClientRequestsPerDay = 2500000 But they seem hard to reach.
It is definitely not per day as the daemon continues where it dropped out after a restart. After the SkyDrive to OneDrive update some settings have changed and I've looked into them again. Possible parameters related to these issues could be:
# Policy Settings
NumConcurrentDownloads = 1
NumberOfConcurrentUploads = 3
# User Settings
maxNumRequests = 10
PS: I do quite well with Python :) Just let me know if I can be of any help.
Don't know how much BITS API and other stuff will help solve issues in this thread. But most "server_internal_error"s happen when you upload large (just a few MiB) files. Could you check how well future
branch (ver > 1.0) works for you?
I'll try this afternoon on Debian
This one time, I was running the daemon with
and I deleted a file from my online OneDrive, and the daemon stopped the syncing. The error thrown was: