ONEDRIVE_RETRY Response code: 503

[djdomi]

Dear All,

I am using onedrive as backup storage, since couple of weeks i have trouble to check the content on these.

Options: [-log check -storage PVE-ONEDRIVE-BKP2 -fossils -resurrect -files -chunks -tabular -threads 30 -a -tabular]
2020-05-05 19:30:01.909 INFO STORAGE_SET Storage set to one://duplicacy-bkp
2020-05-05 19:30:05.177 INFO SNAPSHOT_CHECK Listing all chunks
2020-05-05 19:38:11.501 INFO SNAPSHOT_CHECK 17 snapshots and 160 revisions
2020-05-05 19:38:11.505 INFO SNAPSHOT_CHECK Total chunk size is 410,549M in 143296 chunks
2020-05-05 19:39:30.863 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 1 have been successfully verified
2020-05-05 19:40:45.314 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 5 have been successfully verified
2020-05-05 19:41:54.663 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 6 have been successfully verified
2020-05-05 19:43:08.777 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 7 have been successfully verified
2020-05-05 19:44:26.632 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 8 have been successfully verified
2020-05-05 19:45:36.810 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 9 have been successfully verified
2020-05-05 19:46:51.513 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 10 have been successfully verified
2020-05-05 19:48:08.987 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 11 have been successfully verified
2020-05-05 19:49:20.850 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 12 have been successfully verified
2020-05-05 19:50:30.283 INFO SNAPSHOT_VERIFY All files in snapshot bkp2-media at revision 13 have been successfully verified
2020-05-05 21:00:46.128 INFO ONEDRIVE_RETRY Response code: 503; retry after 487 milliseconds

i dont know what i can still do to fix this, i am using a paid version of duplicacy on a Debian 10

[gchen]

This is not an error – the log level is INFO instead of ERROR for an error message. This only means one of OneDrive servers was not working at that moment and Duplicacy retried and recovered from the error (assuming there wasn’t other error messages further down the log).

[djdomi]

Running check command from /root/.duplicacy-web/repositories/localhost/all
Options: [-log check -storage PVE-ONEDRIVE-BKP2 -fossils -resurrect -files -chunks -tabular -threads 30 -a -tabular]
2020-04-29 16:02:59.824 INFO STORAGE_SET Storage set to one://duplicacy-bkp
2020-04-29 16:03:04.662 INFO SNAPSHOT_CHECK Listing all chunks
2020-04-29 16:10:53.319 INFO SNAPSHOT_CHECK 17 snapshots and 160 revisions
2020-04-29 16:10:53.323 INFO SNAPSHOT_CHECK Total chunk size is 410,549M in 143296 chunks
2020-04-29 18:58:15.861 INFO ONEDRIVE_RETRY Response code: 503; retry after 829 milliseconds
2020-04-30 00:17:46.808 INFO ONEDRIVE_RETRY Response code: 503; retry after 160 milliseconds
2020-04-30 03:10:13.188 INFO ONEDRIVE_RETRY Response code: 503; retry after 251 milliseconds
2020-04-30 03:14:38.446 ERROR DOWNLOAD_CHUNK Failed to download the chunk 9881fbbf8065cae07e53b16453482d470c93e1b83c865f42bb99fe40ffd6b780: read tcp 213.109.xxx.xx7:33442->13.107.42.12:443: read: connection reset by peer
Failed to download the chunk 9881fbbf8065cae07e53b16453482d470c93e1b83c865f42bb99fe40ffd6b780: read tcp 213.109.xxx.xx7:33442->13.107.42.12:443: read: connection reset by peer

this ends it up all the time. i am unable to check the storage

[gchen]

You’re using too many threads. Connection resets could be a result of OneDirve rate-limiting your connections.

Another thing is the use of -files and -chunks together (sorry I didn’t notice that in your first post otherwise I would have pointed it out last time). -files is less efficient – it may download a file multiple times if it appears in multiple revisions. -chunks should be enough to detect any file corruption. If you want to use -files, copy to a local storage and run it against the local storage.

[djdomi]

Hi

Thanks for the response, sorry for my late answer.
I am new to all these options, so what’s the best case and settings for checking the repository?

[gchen]

I would suggest something like check -chunks -threads 8.