I would like to report an issue and ask for a solution.
We are currently using OttoFMS to update our clients. For some time, we have been facing a recurring issue across various clients. We use the same build on different servers, and some of them do not receive the updates. In fact, the next day we find the databases stuck in a “closing” state. They cannot be closed, nor can they be opened.
Restarting the FileMaker Server is not possible because it is unable to close the files (sometimes even files that are not included in the build but are open). As a result, we eventually have to disconnect users and restart the entire server.
The last time this happened, I noticed that I could not access the Otto console. I kept getting a message that the username or password was incorrect, even though the credentials were correct and worked for accessing the FileMaker Admin Console. I tried reinstalling Otto on the client’s server, but I still could not access the Otto console. The issue was ultimately resolved only after restarting the entire server.
I would appreciate any help and assistance on this matter.
What happens if you try to close the files from the Admin Console or the OttoFMS dashboard? Most of the the issues you’ve described sound like an issue with FileMaker Server, but we can confirm that way.
Can you send the debug logs for the deployment where this is happening?
It actually never closes the files — they either remain in a closing state, or after a while I find them opened again.
In some cases, the deployment fails and stops, but in others, even if closing the files fails, the process keeps running. On the Otto console, we’ve seen deployments running for a very long time (even days if we don’t manually terminate them). For this reason, I don’t have access to logs from the last time this issue happened. However, I found an older deployment that failed and was closed, and I’ve attached those files for you.
Honestly, I’m not sure whether this is a FileMaker Server issue or something caused by Otto. I’m reaching out because we have many clients: some use Otto, others use a different tool, and we’ve never seen this problem in clients who receive updates using the other tool.
As always, I appreciate your help and support.
Alaleh debug-logs-210.zip (6.0 KB)