I have development and production servers hosted by soliant.cloud and both servers are similarly configured. For some reason, the OttoFMS admin page for the production server is intermittently accessible. The admin tool will work for a few minutes and then stop working for like 15 minutes or so. Soliant support has reinstalled and upgraded OttoFMS from version 4.5 to 4.6.1 and the behavior hasn’t changed.
While it was working, I went to the Logs section and downloaded the Event log, attached.
Thanks for the help. I need to migrate today and fixing this issue would be great.
Todd, is there a way to reset the OttoFMS license for this installation, if these issues are related to licensing?
How does licensing work? Is it part of the OttoFMS installation file when it’s first downloaded? Soliant initially installed OttoFMS for the dev and production servers. I’m not sure if the same installation files were used for both servers. I migrated between these servers a few weeks ago so I’m not sure what changed.
It’s strange that OttoFMS appears to work for 2 or 3 minutes and then stops for like 15 minutes and then repeats.
OK, Soliant did a clean install of OttoFMS for the production server. It’s still unresponsive for about 15 minutes but when it is active I’m getting prompted for the license key. I’m assuming the license key would be the same as the one used for the dev server. I don’t have access to Soliant’s proofgeist account to get the license key. Is there a way of getting the license key from dev’s OttoFMS admin pages? I don’t see where it shows, all I find is the Server Info section and there isn’t a license key field.
Thanks for reminding me about the OttoFMS requirements. I’m checking with Soliant, it’s their t3.large instance type but I’m not sure what that translates into CPU cores and RAM. I did notice that the CPU usage from the FMS admin console on the production server is pegged at 60% for about 15 minutes and then drops to 2-4% for a couple of minutes. Even with the database files closed. That tracks with the timeframe when the OttoFMS console is available and unavailable.
The dev server is the same t3.large instance and it’s CPU usage is 3-4% with the database files open and no users logged in.
BTW, there are no script schedules defined for either server and the disk usage is about 20% for both servers.
I closed the production database files and restarted the instance and that didn’t help, the usage went right back up to 60% without even opening the database file.
Working with Soliant to see what’s up with the production server since I don’t have direct access to it.
Todd, Soliant reported that Windows Defender is running amok and taking up CPU resources. So I think it’s probably the cause of the flakey response of OttoFMS. I’m also looking into more RAM for the servers, it’s normally 60% used.
The server was reconfigured with more RAM and 4 CPU cores and OttoFMS is still unresponsive when the anti-malware software is intermittently scanning. Can anti-malware software interfere with OttoFMS? If so, is the only solution to disable the software before a migration?
When the FM server admin tool is reporting CPU usage at 30%, OttoFMS access times out with a 502 error. OttoFMS is fine when the CPU usage is around 10%, which I’m assuming is when the anti-malware is not scanning.
You should configure Malware to exclude the otto folder and the FileMaker backups folder and the FileMaker live database. This is what we do on all of our of windows servers and we have no issues with related to Windows Defender.
Are you using a AWS T-Type servers? If you are then that is likely your problem. T Types are just not great FileMaker servers. Also a T Type will blow through all it’s CPU credits in a few seconds when it starts it’s maleware scan.
The over-scanning issue is finally resolved. It was easier to rebuild the virtual server than to figure out why scanning was misconfigured. The normal CPU usage is down to 2% and OttoFMS is stable again. I’m verifying that the folder exclusions are being done. I certain the FileMaker folders are, but I’m not sure about the otto folder.