Using the Create New Schedule button rather than the use existing all I get after lots of spinning wheels is:
Hey John,
Is there anything strange in your otto-info.log around that time?
-Kyle
Local Admin API error: Fetch failed: Internal Server Error code: -1 - Unknown error; Path: /fmi/admin/api/v2/schedules/backup; Waiting 15 seconds and trying again
followed by
Admin API token refreshed
Ok so it did try the refresh and failed again. You could try restarting the admin server and creating the schedule again. That’s an error I’ve not seen before.
-Kyle
Haven’t even got past the creating schedule step yet though
I too am having this issue. It never wants to create the schedule and I get the same error as above.
Hey Chris,
I’d recommend starting by restarting the FMS Admin server. The “Unknown Error” leads me to believe that there is something strange going on in the admin server there. Have you tried restarting the admin server?
-Kyle
I’m having this same exact issue. It never creates the new schedule. I have restarted both the admin server and the whole machine.
Local Admin API error: Fetch failed: Internal Server Error code: -1 - Unknown error; Path: /fmi/admin/api/v2/schedules/backup
1 Like
Ok well that is exceedingly weird. I have tested this and I also see it. I am certain I tested this, so I’m not sure why it is not working all of the sudden. I’ll get a fix put together for our next version. Thanks for the reports y’all!
-Kyle
1 Like
Just adding clarity a full system restart doesn’t resolve the issue either.
1 Like
Hey y’all,
I’ve been testing this and it seems to be behaving differently across different FM versions, do y’all mind letting me know which versions of Fm Server you’re running on the servers where you’re having this issue? Thanks!
-Kyle
Currently running all servers on: 21.0.2.202
Thanks Chris!
I have looked into this, it looks like FMS version 21 changed the schedule creation API slightly, and now the folder where the files are going to be stored has to be created before we create the backup schedule, which was not a requirement in previous versions. I’m not sure if this was an intentional change as it does not have a useful error message. However, I have put a fix together that will create the folder at the time of schedule creation. This fix will be released in our next version of OttoFMS. Thanks again for all your help with this everyone!!
-Kyle
1 Like
Wonderful news Kyle - got a ballpark time frame. for that update?
I don’t have a specific timeframe at the moment, but I suspect it will be later this week or early next week. I’ll update y’all here when it is released!
-Kyle
1 Like
I do hate it when this kind of thing happens without any notification, and it happens rather more than is good for us!
And its far enough away from where the problem appears to man root cause difficult
Thanks for the investigation Kyle
2 Likes
Hey y’all,
This issue is fixed with OttoFMS version 4.7.0. Thanks for all of the reports and assistance with the debugging here, this was a strange one. Let me know if you have any issues going forward!
-Kyle
Hey Kyle,
This is great news. It’s working on the current latest version of FMS! Thank you for working this out. I have one question for you - does the offsite backup no longer support ZIP archives of the database backups when pushing to offsite?
Hey Chris,
OttoFMS offsites do not support sending the offsites as a zip file at this time.
-Kyle
Is there any plan to re-add this feature?