502 Bad Gateway at /otto/ - OttoFMS not starting? fresh install

Mickc · August 8, 2024, 7:23am

Hi All

So I’ve just tried to set this up on some of our Ubuntu 22 servers.
Both have the same issue where it seems OttoFMS insn’t starting.

I’ve tried restarting the http server, and the whole server.
I used the linux command line from the docs to install in both cases.
FMS 20.3.205
Ubuntu 22.04.4
OttoFMS 4.6
/opt/OttoFMS/logs is empty
I ran some commands from another forum post

I can’t see anything jumping out as to the cause
Any ideas?

Server 1

sudo service ottofms-proofgeist-com status
× ottofms-proofgeist-com.service - ottofms-service-proofgeist
     Loaded: loaded (/lib/systemd/system/ottofms-proofgeist-com.service; enable>
     Active: failed (Result: exit-code) since Thu 2024-08-08 14:02:07 AEST; 8mi>
    Process: 1120 ExecStart=/opt/OttoFMS/bin/ottofms-linux-x64 (code=exited, st>
   Main PID: 1120 (code=exited, status=1/FAILURE)
        CPU: 1.047s

Aug 08 14:02:07 s1 systemd[1]: ottofms-proofgeist-com.service: >
Aug 08 14:02:07 s1 systemd[1]: Stopped ottofms-service-proofgei>
Aug 08 14:02:07 s1 systemd[1]: ottofms-proofgeist-com.service: >
Aug 08 14:02:07 s1 systemd[1]: ottofms-proofgeist-com.service: >
Aug 08 14:02:07 s1 systemd[1]: ottofms-proofgeist-com.service: >
Aug 08 14:02:07 s1 systemd[1]: Failed to start ottofms-service->




journalctl -u ottofms-proofgeist-com

Aug 08 13:53:20 s1 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:53:21 s1 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:53:21 s1 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:53:21 s1 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.641s CPU time.
Aug 08 13:53:22 s1 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 1.
Aug 08 13:53:22 s1 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:53:22 s1 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.641s CPU time.
Aug 08 13:53:22 s1 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:53:22 s1 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:53:22 s1 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:53:23 s1 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 2.
Aug 08 13:53:23 s1 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:53:23 s1 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:53:24 s1 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:53:24 s1 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:53:24 s1 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.032s CPU time.
Aug 08 13:53:24 s1 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 3.
Aug 08 13:53:24 s1 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:53:24 s1 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.032s CPU time.
Aug 08 13:53:24 s1 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:53:25 s1 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:53:25 s1 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:53:25 s1 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 4.
Aug 08 13:53:25 s1 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:53:25 s1 systemd[1]: Started ottofms-service-proofgeist.

Server 2

sudo service ottofms-proofgeist-com status

× ottofms-proofgeist-com.service - ottofms-service-proofgeist
     Loaded: loaded (/lib/systemd/system/ottofms-proofgeist-com.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2024-08-08 14:06:37 AEST; 16min ago
    Process: 1455 ExecStart=/opt/OttoFMS/bin/ottofms-linux-x64 (code=exited, status=1/FAILURE)
   Main PID: 1455 (code=exited, status=1/FAILURE)
        CPU: 1.331s

Aug 08 14:06:37 s2 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.331s CPU time.
Aug 08 14:06:37 s2 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 5.
Aug 08 14:06:37 s2 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 14:06:37 s2 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.331s CPU time.
Aug 08 14:06:37 s2 systemd[1]: ottofms-proofgeist-com.service: Start request repeated too quickly.
Aug 08 14:06:37 s2 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 14:06:37 s2 systemd[1]: Failed to start ottofms-service-proofgeist.




journalctl -u ottofms-proofgeist-com

Aug 08 13:52:10 s2 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:52:11 s2 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:52:11 s2 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:52:11 s2 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.280s CPU time.
Aug 08 13:52:11 s2 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 1.
Aug 08 13:52:11 s2 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:52:11 s2 systemd[1]: ottofms-proofgeist-com.service: Consumed 1.280s CPU time.
Aug 08 13:52:11 s2 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:52:12 s2 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:52:12 s2 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:52:12 s2 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 2.
Aug 08 13:52:12 s2 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:52:12 s2 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:52:13 s2 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:52:13 s2 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:52:13 s2 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 3.
Aug 08 13:52:13 s2 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:52:13 s2 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:52:14 s2 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:52:14 s2 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:52:14 s2 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 4.
Aug 08 13:52:14 s2 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:52:14 s2 systemd[1]: Started ottofms-service-proofgeist.
Aug 08 13:52:15 s2 systemd[1]: ottofms-proofgeist-com.service: Main process exited, code=exited, status=1/FAILURE
Aug 08 13:52:15 s2 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:52:15 s2 systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 5.
Aug 08 13:52:15 s2 systemd[1]: Stopped ottofms-service-proofgeist.
Aug 08 13:52:15 s2 systemd[1]: ottofms-proofgeist-com.service: Start request repeated too quickly.
Aug 08 13:52:15 s2 systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Aug 08 13:52:15 s2 systemd[1]: Failed to start ottofms-service-proofgeist.

kduval · August 8, 2024, 4:04pm

Hey Mick,

Welcome to the community!

Do you have an “OttoFMS” folder inside your server’s default backup location? If that is not getting created it could look something like your issue. You may want to double check the backup folders permissions to ensure the fmserver user is the owner.

Is this your first install of OttoFMS on these servers?

-Kyle

phcranston · August 8, 2024, 5:22pm

In my experience, OttoFMS failing to start has always ended up being some permissions issue.

Mickc · August 8, 2024, 11:42pm

Hi @kduval
This is the first install on both machines. I’ve been running OttoFMS on some windows servers, but this is my first time trying with Linux.
Both are dedicated FileMaker Servers. The only installations are FMS, SimpleBackups and NetData.

Yep I see the OttoFMS folder in the backups folder. Backups and OttoFMS are owned by fmserver
drwxr-xr-x 4 fmserver fmsadmin 4096 Aug 9 00:00 Backups

toddgeist · August 9, 2024, 12:06am

Are you using a second drive as your default Backup location on those servers?

If you are, try switching it back to the initial location in the FileMaker Server directory, and then restart OttoFMS.

Let us know what you find out.

Todd

Mickc · August 9, 2024, 12:21am

Hi Todd
Nup, it’s just the one drive (plus swap). Default FMS Backup location in the Data folder. Over 100gb free

toddgeist · August 9, 2024, 3:20pm

Hello

Is there anything else unusual about your setup? Did you install FileMaker Server with the defaults?

What are your server specs?

Any chance you are on Ubuntu ARM?

Are you using a cloud provider? Which one?

Todd

Peter_Wagemans · August 10, 2024, 6:17pm

I had exactly the same issue when installing on my Ubuntu 22 dev server.
I stupidly uninstalled cups which uninstalled FileMaker Server so I had fun for an hour re-installing FMS, the Certbot certificate scripts and OttoFMS

Result: exactly the same issue, exactly the same errors. Even after a thorough cleanup, reboot and re-install.
On my personal FMS (a RPI 4) I had no problem installing 4.6.

And then I tried installing the previous 4.5 version using
curl -sSL “https://downloads.ottomatic.cloud/ottofms/install-scripts/install-linux.sh” | bash -s – -v 4.5.0
after removing the 4.6 version and all its directories (also in FMS Backups).

And it worked! OttoFMS came with the login screen, and later the license screen, filled in the license code and everything was peachy.

So I thought: now I wil break it by installing 4.6.0
I did
sudo curl -sSL “https://downloads.ottomatic.cloud/ottofms/install-scripts/install-linux.sh” | bash
And everything still worked afterwards.

I’m stumped. But maybe this works for you as well.
The only reason I can think of, is that 4.5 made sure something was installed, and 4.6 didn’t.

kduval · August 12, 2024, 4:19pm

Hey y’all,

I have confirmed the issue is with fresh installs of version 4.6.0. Peter is correct that installing the previous version and upgrading should work. I’m investigating a fix for this and the next version will work properly. Thank you!

-Kyle

kduval · August 12, 2024, 5:27pm

We’ve confirmed that this issue affects all Operating Systems with the new version. To reiterate, upgrading from a previous version where you have already logged in will not cause a problem. If you are installing on a new machine: install version 4.5.0, navigate to the OttoFMS console and log in, then upgrade to 4.6.0. I’m working on a fix as we speak. Thanks y’all!

-Kyle

Mickc · August 13, 2024, 5:30am

Thanks Peter and Kyle!
Followed your instructrions and I’ve got 4.6 up and running now

kduval · August 13, 2024, 1:40pm

Hey y’all,

This issue is fixed in version 4.6.1. Upgrading from installed 4.6.0 to 4.6.1 should allow OttoFMS to start properly, and installing a new copy of 4.6.1 will work properly going forward.

Thanks y’all for the reports and the assistance in debugging! I also put in place a fix which will make issues like this significantly easier to debug going forward, especially on Linux, which now ships with a stderr.log and stdout.log in the log folder, making logs easier to access and send to us than they were in the journal.

-Kyle