Otto 4.9.0 - Error during build phase - Timeout exceeded

OttoFMS
1

When performing a migration of a file (of size ~18MB) from the Source server to a Destination server, during the build phase, OttoFMS reports that a build error occurred. Full error message:

Build server error: Timeout exceeded

During an Install operation, the process successfully installs the Source file onto the Destination server without any issue. Performing a migration of the Source file throws the above error.

We have restarted both Source and Destination servers completely, performed any necessary updates to Windows, FMS and the Otto software, created new deployment settings with simple test databases, and are at a loss as to what exactly is going wrong. We’ve adjusted the timeout duration from the default 30 minutes to a full hour, with no change; it simply takes the full time and then times out. Looking at the otto-info.log file on the Source server, it simply repeats the “Getting build status for build” message every 8 seconds until the process times out.

Source Server Specs:
Windows Server 2022 Datacenter (fully updated, version 10.0.20348)
FileMaker Server 24 (version 21.1.1.40)
OttoFMS version 4.9.0.250123458

Destination Server Specs:
Windows Server 2019 Datacenter (fully updated, version 10.0.17763)
FileMaker Server 24 (version 21.1.1.40)
Otto FMS version 4.9.0.250123458

I have the debug logs from the Destination server and the otto-info.log file from the Source server, if those will help.

2

Hey Chris,

Welcome to the community, I’d love to take a look at the logs for this, sounds like your source build is getting hung up somehow. You should be able to DM them to me.

-Kyle

3

Thanks to Kyle’s incredible help, we’ve resolved this issue. There was likely a build file that was stuck in limbo that the OttoFMS process could not properly clean up (stemming from a previous timed-out build phase). Once the OttoFMS process was fully stopped and the erroneous file removed, the build phase was successful and deployments proceeded smoothly.

So, when in doubt… Turn it off and turn it back on again! That just might do the trick if you do it enough times! :laughing:

1 Like