I tried running a deployment but couldn’t get it to work.
At first, the OttoFMS web portal wasn’t responsive and OttoDeploy wasn’t able to schedule the deployment. After restarting the Otto service on the prod server, I was able to schedule the deployment, but once it ran, it failed with “Build server timeout: Timeout exceeded”
Then I restarted the Otto service on the dev server and re-ran the deployment. It failed with “Build server error. http Status: 409. FMS Error 18000: build already in progress”.
Then I restarted both servers and reran the deployment, and it failed with “Error closing files: unknown error”.
I’m running OttoFMS 4.7.2 and FMS 21.0.2.202 on Windows Server 2022 Datacenter. The prod server is an m6i.2xlarge EC2 instance.
If so then this is a known issue. Currently Soliant-hosted servers default setup is incompatible with OttoFMS. We’re actively working on solutions to enable Soliant servers to run OttoFMS smoothly. If your server needs immediate attention, please note that the Soliant hosting team is aware of these challenges and is currently the only party capable of resolving them.
Hi Todd, thanks for your response. Yes, it’s on a Soliant.cloud hosted server.
Over the past few weeks, we had been seeing a different issue where restarting the Otto service would allow the deployment to run. That’s the issue that our hosting team is aware of. What I was describing is new behavior after installing OttoFMS 4.7.2 where the deployment does not run even after restarting it. But of course it could be tied to the same underlying root cause.