Request: auto refresh node cache on upload conflict #349
Comments
animetosho
changed the title from
Request: auto refresh node to Request: auto refresh node cache on upload conflict
Jun 18, 2016
yadayada
added the
CLI
label
Jun 18, 2016
vb0
commented
Oct 24, 2016
|
This is actually getting critical since the cache seems to get out of sync (at least with a couple files) at each interrupted sync (which happens more and more often recently - I suspect because of #416 ). |
jerblack
commented
Oct 28, 2016
•
|
I'm getting the same thing, but it's not possible for it to be a cache out of sync issue since I am manually deleting your database before I sync and it still happens. To be clear, these are the steps I take to see this error:
Then I get this error:
When I attempt to
This folder is not visible from an acd_cli mount on another machine, but it is visible from the web interface. From the web interface, If I move the files out of that folder, delete and recreate the folder with the same same, and then attempt |
yadayada
referenced
this issue
Dec 13, 2016
Closed
acd_cli cache not updated after a failed upload #487
shadycuz
commented
Apr 7, 2017
|
Do we have a fix for this? I see it mentioned several places here on github
Thhe files were created on my ACD but they are blank... If I delete them. They still don't reupload? Thanks, |

animetosho commentedJun 18, 2016
•
edited
I have a script which automatically uploads to ACD via the stream option. Before it does so, it always checks whether the file already exists, before uploading.
When the upload fails, the script will attempt to re-upload it later. Unfortunately, if the upload "failed" due to an ACDCLI crash, ACD failure or otherwise, retries may also fail as ACD may have the file, but ACDCLI's local DB cache does not, and the following error occurs:
To the uploading script, it sees it as a failure (non-zero return code) and will try to re-submit the upload at some later point.
It would be nice if ACDCLI could detect this error and automatically cache the details for the referenced node ID, since it's obviously out of sync at this point.
Thank you for the great tool!