ENOENT Error. HTTP Status Code: 500

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

Hey Josh,

Does that folder exist on that server? Could you send along your otto-info.log for the source server there? You can DM it to me or Todd.

-Kyle

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.

-Kyle

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.

1 Like

oh yeah that would do it. I’m glad we found it!

-Kyle

1 Like

Yeah. Sorry to distract you, but appreciate the pointer. Saved me a minimum of 30 mins. LOL

1 Like