I occasionally encounter a post-deployment error stating, ‘Just in time build failed to delete from source server outbox,’ which leads to disk storage filling up.
This, in turn, causes subsequent deployments to fail due to insufficient storage, as indicated by the error message, ‘Not enough space on the backup disk. Required: 69.48 GB, available: 66.69 GB.’
I am using OttoDeploy v4.11.0 with FileMaker Server 22.0.2.
Could you please clarify what might be causing the just-in-time build to fail in deleting the deployment backups initially? I appreciate your assistance.
The message you’re seeing in the deployment logs is it failing to delete the JIT build from the source server, not the destination. If I were to hazard a guess it could be due to ottofms keeping the file open for some reason. I would try at least restarting your source OttoFMS service to see if it is just holding a lock. You can also try clearing out the outbox manually, sometimes theres a corrupted file (due to ottofms crashing or other reasons) that causes errors.
As for your deployments failing due to disk space issues, I would need to know more about where the disk space build up is coming from. You could decrease the number of deployment backups OttoFMS keeps or move some backups offsite with the offsite backups. Where is the disk space build up coming from? I don’t think its from the error you sent since that is for the source server. (unless you’re seeing the issue with the disk space on that server, in which case try the above for fixing that issue).
Thank you for your response.
The disk space is building up because the deployment backups were not getting deleted from the backup drive. I have reduced the number of deployments as well to help with the disk space issue. The disk space issue occurs on the destination server and not the source server.
I will try to restart the OttoFMS service on the source server and keep an eye out.
