FileMaker Server 21.1.1.40, WIndows Server 2019 Standard 1809
OttoFMS 4.8.0
After a successful data migration the log shows OttoFMS backing up the original files, and at the same time installing files.
Then it encounters an error with one of the files (same millisecond of a file it is installing):
unknown phase - Unknown deployment error: SyntaxError: G:\Backups\OttoFMS\deployment-backups\deploy-30\sub-deploy-31\backup-meta.json: Unexpected non-whitespace character after JSON at position 66
Then the log continues to show OttoFMS is backing up original files.
After OttoFMS has done backing up original files, it fails at reverting
reverting - Error reverting deployment: G:\Backups\OttoFMS\deployment-backups\deploy-30\sub-deploy-31\backup-meta.json: Unexpected non-whitespace character after JSON at position 66
Wich seems exactly the same error to me.
Then it logs
File •••.fmp12 not found while opening files
followed by all the rest of the files not being found while opening files
Followed by
opening - Starting to open files
opening - Files opened successfully
Deployment process failed. Original files are unmodified.
I look on the FileMaker Server and I see that only 6 of 24 files are reverted, the rest is gone.
When trying to manually undo the deployment:
unknown phase Unknown deployment error: Error: EBUSY: resource busy or locked, rename ‘G:\Backups\OttoFMS\deployment-backups\deploy-30\sub-deploy-31’ → ‘G:\Backups\OttoFMS\inbox\BFbcBiPcdO’
I stopped both FMS and OttoFMS and restored manually from that 31 folder
I restarted both the production and the development server and retried everything.
This time it fails at another position in the json file:
Unknown deployment error: SyntaxError: G:\Backups\OttoFMS\deployment-backups\deploy-34\sub-deploy-35\backup-meta.json: Unexpected non-whitespace character after JSON at position 58
And the revert doesn’t work either, but this time 11 of the 24 files are reverted, the rest of them is gone.
That particular file looks written incorrectly indeed, it contains the following:
{“AFL.fmp12”:{“originalPath”:“E:\Databases\AFL.fmp12”}}
dits.fmp12"}}
The strange thing is that the migration has worked fine, it’s just that at the end of the migration things go south and the result is that the migrated files are gone as well.
In the end - it’s past midnight now so I tried deploying for a few hours now - I deployed using Otto V3, which did it perfectly and in 436 seconds.
Luckily that still worked, because I was to tired to deploy using command line instructions.
If you want the log files, I can send them via email.