Response Code 409?

david1 · 28 February 2019 12:46

I’ve just recently started using Duplicacy on Windows (the GUI) to backup my User folder on a PC (i.e. C:\Users[me]). Set it to run 3 am every night. When I got up this morning, I noticed it was still running. Checked the logs and since about 3:12 am there were hundreds of entries like this:

03:12:34.802    Response code: 409; retry after 742 milliseconds

Didn’t seem to be stopping after 4 hours or so, so I decided to stop it. However, when I hit the Stop button in the Job tab, everything remained grayed out in the Job tab, with the Stop button saying “Stopping”. I can still switch between the Job and Logs tab, but that’'s about it. The log shows this:

07:35:26.000    program exited with status code -1

I waited a few minutes but eventually decided just to kill Duplicacy from Task Manager.

Tried searching the forums for this but didn’t manage to find anything. If anyone has any suggestions on how this could be fixed I’d very much appreciate them.

I installed Duplicacy as Admin, enabled for all users, and installed the service. Volume Shadow Copy was also turned on for this job. There is only one job running. On Windows 10.

gchen · 1 March 2019 04:03

Which storage backend are you using? The errors could be caused by rate limiting imposed by the storage provider.

As for the other issue – I can confirm this is a bug that a scheduled job can’t be stopped once it starts running. I’ll fix this in the next update.

david1 · 1 March 2019 14:29

Thank you for the quick reply and for letting me know about the bug. I’m using MS OneDrive (personal) for backend storage. Is there any way to diagnose whether it is in fact rate limiting by the storage provider? Or if not, and assuming that is the cause, would you have any suggestions as to how I might be able to avoid running into the error? For example, is there a way to throttle back Duplicacy when that happens?

gchen · 4 March 2019 19:19

What operation caused these 409 errors? Did they happen during a backup operation or a prune operation? Can you post a few log lines before this error?

david1 · 4 March 2019 20:40

I’m terribly sorry Gilbert - I should have checked the detailed logfiles before asking the first part of my question. This happened during backup, specifically during the upload process. Following is from the detailed logfile with a few additional lines:

2019-02-28 03:12:34.802 INFO ONEDRIVE_RETRY Response code: 409; retry after 742 milliseconds
2019-02-28 03:12:35.810 INFO UPLOAD_PROGRESS Uploaded chunk 861 size 3004233, 5.68MB/s 07:30:40 2.6%
2019-02-28 03:12:35.906 INFO UPLOAD_PROGRESS Skipped chunk 862 size 1299304, 5.68MB/s 07:30:32 2.6%
2019-02-28 03:12:36.010 INFO UPLOAD_PROGRESS Skipped chunk 863 size 3901131, 5.68MB/s 07:30:44 2.6%
2019-02-28 03:12:37.092 INFO ONEDRIVE_RETRY Response code: 409; retry after 91 milliseconds
2019-02-28 03:12:37.913 INFO UPLOAD_PROGRESS Uploaded chunk 864 size 2446018, 5.68MB/s 07:31:05 2.6%
2019-02-28 03:12:38.649 INFO UPLOAD_PROGRESS Uploaded chunk 865 size 3898702, 5.67MB/s 07:31:17 2.6%

Any thoughts you may have on how I might be able to avoid the rate-limiting issue would be most appreciated.

gchen · 9 March 2019 03:58

I’m not sure if this 409 code was caused by rate-limiting. They are actually treated as warnings due to the retry mechanism, so it was still making progress.

If you turn on verbose logging you may be able to know which API call returns the 409 code.

david1 · 11 March 2019 13:02

Thank you. I will give that a try, though as an aside, the problem seems to have gone away.

Christoph · 11 March 2019 15:55

For anyone: Feel free to use the button on the posts that you found useful.

For the OP of any #support topic: you can mark the post that solved your issue by ticking the box under the post. That of course may include your own post

manne01 · 30 April 2025 16:14

Hi there,

I am replying to this older topic as I assume I got very similar problems. Feel free to remove my post.

I am using two really similar configured repositories on two different Ondrive accounts (1TB each). They both worked with no trouble for years now.

Duplicacy cmd line version 2.2.3 (58387C)

Account A gives HTTP Return Code 409 and retry messages during backup. Backup does not work at all anymore.
Account B still works like a charm and this is why I assume it is not rate limiting here but something else.
Official ondrive api documentation says status code 409 is “Conflict - The current state conflicts with what the request expects. For example, the specified parent folder might not exist.”
I cannot say I changed anything on Account A. Well, I logged in to the ondrive Account A recently and shared another folder to some people, that should not harm at all?!

My scheduled task (./duplicacy -log backup -threads 4 -stats) logs is

2025-04-30 15:52:13.744 INFO STORAGE_SET Storage set to one://<removedName>
2025-04-30 15:52:17.155 INFO ONEDRIVE_RETRY Response code: 409; retry after 804 milliseconds
2025-04-30 15:52:18.168 INFO ONEDRIVE_RETRY Response code: 409; retry after 954 milliseconds
2025-04-30 15:52:19.313 INFO ONEDRIVE_RETRY Response code: 409; retry after 1564 milliseconds
2025-04-30 15:52:21.057 INFO ONEDRIVE_RETRY Response code: 409; retry after 5739 milliseconds
2025-04-30 15:52:27.015 INFO ONEDRIVE_RETRY Response code: 409; retry after 133 milliseconds
2025-04-30 15:52:27.315 INFO ONEDRIVE_RETRY Response code: 409; retry after 25875 milliseconds
2025-04-30 15:52:53.395 INFO ONEDRIVE_RETRY Response code: 409; retry after 14931 milliseconds
2025-04-30 15:53:08.508 INFO ONEDRIVE_RETRY Response code: 409; retry after 87923 milliseconds
2025-04-30 15:54:36.431 ERROR SNAPSHOT_LIST Failed to list the revisions of the snapshot MySnap: Maximum number of retries reached
r

I used
./duplicacy -debug backup -stats

and got these logs:

Storage set to one://somebackup
Reading the environment variable DUPLICACY_ONE_TOKEN
Reading one_token from preferences
GET https://api.onedrive.com/v1.0/drive/root:/somebackup?select=id,name,size,folder
GET https://api.onedrive.com/v1.0/drive/root:/somebackup/chunks?select=id,name,size,folder
GET https://api.onedrive.com/v1.0/drive/root:/somebackup/fossils?select=id,name,size,folder
GET https://api.onedrive.com/v1.0/drive/root:/somebackup/snapshots?select=id,name,size,folder
Reading the environment variable DUPLICACY_ONE_TOKEN
Reading one_token from preferences
Reading the environment variable DUPLICACY_PASSWORD
Reading password from preferences
GET https://api.onedrive.com/v1.0/drive/root:/somebackup/config?select=id,name,size,folder
GET https://api.onedrive.com/v1.0/drive/items/root:/somebackup/config:/content
Using 16384 iterations for key derivation
GET https://api.onedrive.com/v1.0/drive/root:/somebackup/nesting?select=id,name,size,folder
Chunk read levels: [1], write level: 1
Compression level: 100
Average chunk size: 4194304
Maximum chunk size: 16777216
Minimum chunk size: 1048576
Chunk seed: <removedSeed>
Reading the environment variable DUPLICACY_PASSWORD
Reading password from preferences
top: /volume1/backups/duplicacy-repoA, quick: true, tag:
Downloading latest revision for snapshot MySnap
Listing revisions for snapshot MySnap
GET https://api.onedrive.com/v1.0/drive/root:/somebackup/snapshots?select=id,name,size,folder
POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 63 milliseconds
POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 13 milliseconds
POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 98 milliseconds
POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 3700 milliseconds
POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 6415 milliseconds
POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 18359 milliseconds

POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 24929 milliseconds
POST https://api.onedrive.com/v1.0/drive/items/removedID!removedID/children
Response code: 409; retry after 14858 milliseconds
Failed to list the revisions of the snapshot MySnap: Maximum number of retries reached

I have no clue whats the matter. I already downloaded another tokenfile and replaced the original one with it. No difference. I reduced threads from 4 to 1, no difference.

Is there any advice? Would really appreciate to have it working again.

In case a newer version is needed to clarify - can I just replace the duplicacy file 2.2.3 with 2.7.2 ?

Manne

Droolio · 3 May 2025 11:11

Why are you using such an old version of the CLI? 2.2.3 is nearly 6 years old, we’re up to v3.2.5 now (just released actually; which coincidentally includes a fix for OneDrive backends.)

The only thing you have to be aware of, is once you start making backups with v3.x, the storage might become incompatibly with v2 clients (so you should upgrade all clients at once) - but honestly, v2.x is such an old old version, I can’t see why anyone would use it.

manne01 · 4 May 2025 07:05

Hi Droolio,

thanks for your reply.

To be honest I had no reason to touch anything or upgrade it as it worked so nicely for years.

And regarding to the errors 409 I thought my second backup to a onedrive account is still running. I did not change anything so the executable must have been okay. But in the end I should have upgraded.

You were perfectly right: I updated to 3.2.5 now and the backup is working again!

Resolved! Thank you so much!

What a great peace of software! Thank you to everyone contributing to it!

Kind regards
Manne