My scheduled prune job, which has been running weekly for months and years is suddenly throwing an Initialization failure error:
Usually, when a job fails, I can click on the failure-link and see the logs, but this one is not clickable.
This is version 3.1.0 on a Debian server.
This error indicates that there was something wrong when trying to initialize the repository directory under ~/.duplicacy-web/repositories/locahost. Check the log file ~/.duplicacy-web/logs/duplicacy_web.log for related error messages.
Run out of disk space? 
Indeed, that seems to have been the case, somehow, in a weird way. My duplicacy temporary folder was in tmp/.duplicacy-web/repositories and it has worked fine for months and years. But now it turns out that /tmp only has 12 GB of space (I have no idea why and where this is set on my OMV server, but that’s what it is. I suspect that this setting was changed with some recent OMV update). So It was that temp-folder that became filled up to the brink and since duplicacy is working again now, I suspect that I gave it a new temp folder, I assume that this is what caused the problem.
@gchen perhaps dulplicacy web could output a warning when disk space is running low in a directory that is apparently vital for duplicacy being able to do pretty much anything?
I have this issue today.
I have not run out of disk space.
I’m on Windows and I have no idea where Duplicacy is saving its log files. A search of C: drive for “duplicacy_web.log” returns nothing.
The Web GUI interface has been pretty unreliable in terms of making sure scheduled downloads happen, and now it is basically bricked.
I found this log file from the web gui which shows Duplicacy can’t find my D drive which is missing. So because it can’t find a log file it stops working. This would be a cooler error message to give. Or maybe just don’t log anything if the log path is invalid but keep going.
Failed to open the log file D:\Duplicacy Temp/logs/backup-20250606-020001.log: open D:\Duplicacy Temp/logs/backup-20250606-020001.log: The system cannot find the path specified.