First migration gets stuck in closing the files

Hi,

I am trying to make a deployment, the first one on OttoFMS v4. Previously used v3 without issues.

I used the same settings as in v3. The migration fails with an “unknown error” when it tried to close the files.

I am not sure what else to do. Some help please?

queued Deployment queued
starting 1 files
pre-deployment script No pre deployment script to run
closing Error closing files: unknown error
opening since files didn’t close, waiting 45 seconds before trying to open files
done Deployment process failed. Original files are unmodified.

{
“source”: {
“type”: “otto4jit”,
“serverUrl”: “https://app…”,
“auth”: {
“type”: “apiKey”,
“apiKey”: “encrypted7a4…"
},
“buildOptions”: {
“closeFiles”: false,
“compressionLevel”: 0,
“memoryLevel”: 1
},
“pushBuild”: false
},
“name”: “RMA”,
“fileOperations”: [
{
“operation”: “migrate”,
“clone”: {
“fileName”: “RiskLabHq_Dev.fmp12”,
“user”: "encrypted982…
”,
“password”: “encryptedf42b…",
“encryptionKey”: "encrypted08…

},
“dataSource”: {
“fileName”: “RiskLabHq.fmp12”,
“user”: “encrypted5f…",
“password”: "encrypted57b…
”,
“encryptionKey”: “encrypted60ff…"
},
“target”: {
“fileName”: “RiskLabHq.fmp12”,
“encryptionKey”: "encrypted58254…

},
“dataMigrationOptions”: {
“-force”: true,
“-ignore_valuelists”: false,
“-ignore_accounts”: false,
“-ignore_fonts”: false,
“-reevaluate”: false,
“-rebuildindexes”: false
}
}
],
“concurrency”: 1,
“options”: {
“closeFilesAfterBuild”: false,
“keepFilesClosedAfterComplete”: false
},
“batchId”: 10,
“status”: “queued”,
“batchName”: “RMA”
}

Hello Christos,

Welcome to the community! What Operating System and version of OttoFMS is your destination server running? Also, could you send me the Troubleshooting Logs for your deployment?

Could you try closing your files via the OttoFMS console? Do they properly close there?

-Kyle

Hi Kyle,

Thanks for your response.

  1. Closing and opening files via to OttoFMS console works fine

  2. OS Version: Ubuntu 22.04.4 LTS (GNU/Linux 6.8.0-1019-aws x86_64)
    OttoFMS Version: 4.7.2

[Files added but removed]

EDIT:
I noticed there was an update to OttoFMS to v4.8.0. I had updated OttoDeploy earlier before the trying the deployment. This did initiate the deployment however it failed again since the “ClonesOnly” folder wasn’t created on the server. I manually created it and changed permissions. The deployment worked fully after this.

It might be good to include it as part of your scripts to create this folder if not present?

Ah yes, the ClonesOnly folder issue is a known issue, it is getting fixed in the next version to be released. I’m glad everything is working now!! Especially glad it was an issue that is fixable by you and that I have already fixed in our next version haha.

Let us know if you have any more questions, requests, or issues going forward!

-Kyle