I’ve tried restarting Otto and FMS and the issue persists. The deployments page (otto/app/deployments) fails and constantly gives the error code 500. This is on a Linux Server and it’s running FMS 20.3.2.205 and OttoFMS Version: 4.3.5.240506499.
I don’t know if the following is related but I believe it all started as I was doing some API tests to start deployments, following these steps OttoFMS Developer API
Hey Martin,
If you open up your browser console(right click and inspect) and go to the console tab, do you see errors there? If so, what are the error messages?
You could also try listing your deployments via the api to see if there is an error coming back from that api call. I suspect that one of your deployments somehow got saved improperly, but I’ll need to see the errors to know how.
-Kyle
We also fixed a similar issue to this in a more recent version, upgrading OttoFMS is likely to fix your issue as well.
-Kyle
Thanks for your reply @kduval. I do see errors, as in the screenshot.
Do you think that upgrading will fix these issues?
Yes upgrading should fix those.
-Kyle
I’m seeing the same issue with OttoFMS 4.7.0 running with FMS 21.0.2.202 on Ubuntu 22.04
This is a new install and as with @martin , I’ve just been testing custom calls to the API to start ‘otto4jit’ deployments.
Snippet from the web console in Safari:
Hey Erik,
Does restarting the OttoFMS service fix the issue? Would you be able to send me the details of the deployment you started via the API (the JSON you sent to OttoFMS with secrets hidden would work). I’d like to try and replicate this.
Are you scheduling these deployments?
Also, are there any errors in the otto-info.log file that you see?
-Kyle
After service ottofms-proofgeist-com restart the Deployments page loads as expected.
{
"deployments" :
[
{
"fileOperations" :
[
{
"clone" :
{
"fileName" : "speed452.fmp12",
"password" : "•••redacted•••",
"user" : "•••redacted•••"
},
"dataMigrationOptions" :
{
"-ignore_accounts" : false,
"-ignore_fonts" : false,
"-ignore_valuelists" : true,
"-rebuildindexes" : false,
"-reevaluate" : false
},
"dataSource" :
{
"fileName" : "1163.fmp12",
"password" : "•••redacted•••",
"user" : "•••redacted•••"
},
"operation" : "migrate",
"target" :
{
"fileName" : "1163.fmp12"
}
}
],
"name" : "Lars_Heise",
"postDeploymentScript" :
{
"file" :
{
"name" : "1163.fmp12",
"password" : "•••redacted•••",
"user" : "•••redacted•••"
},
"rollbackIfScriptFails" : false,
"script" :
{
"name" : "otto"
}
},
"source" :
{
"auth" :
{
"apiKey" : "•••redacted•••",
"type" : "apiKey"
},
"serverUrl" : "https://server99.ipos.dk",
"type" : "otto4jit"
}
}
],
"label" : "•••redacted•••",
"scheduled" : false
}
…not scheduled…
Hmm that is strange. I’m glad the protections I put into the database caught that on restart. When I get back from pause I’ll make sure that the log gets created at the beginning of the deployment, I’m not sure how it missed one. Thanks for the report!!
-Kyle
Hey y’all,
This issue is fixed with OttoFMS version 4.7.1! Let me know if you have any issues with it going forward.
-Kyle