For the past several weeks, I’ve been running into this error when going to run a migration or run a build. Several times, a new version of OttoFMS was available, so I just updated, and then migration went as expected.
Tonight, however, this error won’t go away, and I’ve been unable to run a build, or a migration. Any thoughts about where I should look? I’ve done dozens of migrations on the exact same servers, using the same unchanged deployments.
I have restarted OttoFMS, stopped/started it, removed and reinstalled it, rebooted. The calls to the FileMaker Server Admin API are working fine ( closing / opening files, etc ).
FileMaker Server: 20.3.2
Otto Version: 4.6.2
OS: Ubuntu 22.04.4 LTS
Well, yes, it does. But apparently someone moved it to /opt/OttoFMS/...
That’s an easy fix. I did a find for it, but didn’t pay attention to the path. Now to find out why it was moved. ( and yes, I know there is supposed to be an OttoFMS directory there )
It is weird that it would not simply rebuild the folder when OttoFMS restarts, it is supposed to heal from that. Have you moved the default backup location on that server at all? that could cause these folders to move around a bit, although it would probably still leave the old location in place.
No. But I found a cronjob and shell script that someone has running on this server that is moving instead of copying. That’s very annoying. I wish this was just me making a mistake, it would make it an easier fix. ( it’s running every 30 mins )
I must have just restarted it just before the job ran.
I am still facing the same problems as mentioned in this thread.
Build server error: failed - backup failed: IBS_DataStore.fmp12. Error: ENOENT: no such file or directory, scandir ‘/opt/FileMaker/FileMaker Server/Data/Backups/OTTO_IBS_DataStore.fmp12_v7AIF/’
We have put the latest version in both the source and destination server of FMS 4.7.2. We are running on Linux.
Issue resolved. It was a disk space issue on the backups folder. We had to provision more and the error disappeared. It would be great to have better error messages.
Now we are onto the next problem:
Build server error: failed - backup failed: IBS_DataStore.fmp12. Error: Schedule timed out
This has happened after 10 minutes. I see the folder already made on the backups folder.
Is that file just absolutely massive? If its huge and you’re making a copy via backup it might take a long while. You could do one of two things to fix this:
Enable the “close files during build” option. This will close the file and copy it directly rather than using a FileMaker backup schedule. it should be significantly faster.
Thanks for the help. The file I am trying to move accross is quite large. Maybe about 30gb of data from Production to Training so that we have a more relevant data set to train users on.
I have followed your suggestion on “close files during build” and the following error is now showing up:
