OttoFMS 4.14.0 Released!

OttoFMS
1

Hey y’all,

OttoFMS version 4.14.0 was just released! This version includes a UI for the FileMaker Server Triggers that @john_r presented on at EngageU, as well as a number of bug fixes and small improvements. Check out the full changelog here.

This version also upgrades OttoFMS from Node version 20 to Node version 22, and as such there may be some issues on install. We have tested on the major supported operating systems, but unusual environments may cause an issue. Let us know if the install doesn’t work for you, and for now downgrading back to 4.13.1 should let you keep using OttoFMS with no issues.

Thank you, and let us know if you have any issue with the new version!

-Kyle

2 Likes
2

Thanks @kduval
There is likely to be a Server update soon which will bring these out into the open.
For those who want more detail on this, I am presenting at FMDiSC in December 12th and this will be a part (along with some advanced OData stuff)

1 Like
3

I have tried setting up a trigger and I know my receiver endpoint is working fine, but no data is sent when I make changes to data or schema. Any ideas? OData and Data API are enabled, and the connection is successful when setting up the trigger…

4

Are you missing an authentication header or something similar? I’m not clear on how much logging there is for this feature or how easy debugging it is, @john_r may have some thoughts there. This may be worth opening a new thread on for discussion.

-Kyle

5

For testing I just left the endpoint open with no auth… tested sending to it in Postman and it just does one thing… create a record in Supabase and populate a field with the payload received… and that works fine… so no particular headers needed from what I can see… Would be great to see a log of triggers payloads sent, at least maybe the last ten as that log would get huge pretty quick I reckon!

6

Agreed! OttoFMS is just showing you UI for information FileMaker is storing, so we can’t add anything like that unfortunately. Any feature requests for the actual functionality of the triggers would need to go to Claris. We’ve just built the UI to work with them rather than having to use the API yourself.

-Kyle

2 Likes
7

@skywillmott What are you using as the $filter and $select??

And have you done the Webhook.get(n)? what does it return?

8

The endpoint IS the log…

9

I didn’t put anything in for that … just left as default/optional

10

Anyhow, this stuff I’m sure will be great in many circumstances :+1:

11

The $filter needs something to tell the record under what conditions to fire the web-hook though surely.
thisField changes status, thisField is more than zero, these fields etc etc, or ROWMODID > 0 == anything changes
But having something that fires off on each an every change to every record in a mulit-user system is going to fal over at some point. Start small.

1 Like
12

After updating to latest version service does not want to run. Where could be the problem.

ubuntu@ip-xxxxxxx:~$ sudo systemctl status ottofms-proofgeist-com.service

× ottofms-proofgeist-com.service - ottofms-service-proofgeist

Loaded: loaded (/usr/lib/systemd/system/ottofms-proofgeist-com.service; enabled; preset: enabled)

Active: failed (Result: exit-code) since Thu 2025-11-27 13:46:05 PST; 8s ago

Duration: 135ms

Process: 6705 ExecStart=/opt/OttoFMS/bin/ottofms-linux-arm64 (code=exited, status=4)

Main PID: 6705 (code=exited, status=4)

CPU: 137ms

Nov 27 13:46:05 ip-xxxxxxx systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 5.

Nov 27 13:46:05 ip-xxxxxxx systemd[1]: ottofms-proofgeist-com.service: Start request repeated too quickly.

Nov 27 13:46:05 ip-xxxxxxx systemd[1]: ottofms-proofgeist-com.service: Failed with result ‘exit-code’.

Nov 27 13:46:05 ip-xxxxxxx systemd[1]: Failed to start ottofms-proofgeist-com.service - ottofms-service-proofgeist.

1 Like
14

I’m seeing something similar on a few servers, but not all:

/opt/OttoFMS$ sudo systemctl status ottofms-proofgeist-com.service
× 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 2025-12-04 14:17:47 EST; 8min ago
    Process: 108646 ExecStart=/opt/OttoFMS/bin/ottofms-linux-arm64 (code=exited, status=4)
   Main PID: 108646 (code=exited, status=4)
        CPU: 80ms

Dec 04 14:17:47 ip-xx-xx-xx systemd[1]: ottofms-proofgeist-com.service: Scheduled restart job, restart counter is at 5.
Dec 04 14:17:47 ip-xx-xx-xx systemd[1]: Stopped ottofms-service-proofgeist.
Dec 04 14:17:47 ip-xx-xx-xx systemd[1]: ottofms-proofgeist-com.service: Start request repeated too quickly.
Dec 04 14:17:47 ip-xx-xx-xx systemd[1]: ottofms-proofgeist-com.service: Failed with result 'exit-code'.
Dec 04 14:17:47 ip-xx-xx-xx systemd[1]: Failed to start ottofms-service-proofgeist.
Dec 04 14:26:40 ip-xx-xx-xx systemd[1]: /lib/systemd/system/ottofms-proofgeist-com.service:28: Unknown key name 'After' in section 'Install', ignoring.
Dec 04 14:26:40 ip-172-31-8-9 systemd[1]: /lib/systemd/system/ottofms-proofgeist-com.service:29: Unknown key name 'Wants' in section 'Install', ignoring.
15

I’m seeing something similar on a few servers, but not all

Is it possible that you’re seeing this issue on all Ubuntu with ARM architecture? That’s what I’m seeing. 4.14.0 and 4.14.1 will not start on ARM, but work fine on x86.

16

There is an issue with ubuntu 22.04 and 24.04 on ARM, have got/had both and Otto just refuses to run. Initially I though it was Oracle, but it seems more than that.

1 Like