Sorry but that made me laugh out loud.

I hope it's just a breaker or something :).

I had issues getting it running at boot too, i actually just hacked it in the end and ran a Cron job to check if it's running and start if not.

I've concluded I'm fine with this since I want it running all the time.

If we get loads more people with the same issue I'll take a proper look at it

Unfortunately, we don't have a developer that works on the agent full time. Agent changes are the slowest part of everything that we offer.

Mainly because we never intended to support a large number of OS's, just a couple because developing and maintaining agents on top of everything else is a lot of work load. However, we do recognize the value of offering many different variations and that will come when we see some critical mass in terms of members and usage. We're not there yet, not enough word of mouth.

We'll do what we can once you know a little more. BSD has been brought up but I do not have an estimated time on this. I believe it would be freebsd if we did it as it is the most widely used.

Great, thank you for letting us know.

That's fantastic and I'm sure will be very helpful to others.

Once a couple people confirm this works, maybe we could make a sticky post and put the link in the download information where you create a new ARM based agent.

I'm not sure we could offer perpetual as this service is in constant flux so making long term promises we cannot keep would not be good.

However, let me know what the device ID is and I'm sure I can upgrade that for you.

@OutagesIO_Support Thank you. I appreciate the time it took to troubleshoot this one with me.

@OutagesIO_Support –

Yup, good to go for now.
Thanks again.

Sorry, but almost all hardware has gone to 64bit. We supported 32bit for a long time but there are costs associated with maintaining so many versions.

We clearly show the bit version in the available agent list of downloads as well to ensure that you're not wasting your time. Sorry that you didn't notice that.

We were happy to help you but as you've asked, your account and data have been removed.

Thanks for trying our service, sorry it didn't work out.

Hello Ed,

I followed to the letter. all with pretty much the same results

Agent 1 ) downloaded for Pi3 B+ (didn't have a Pi3 however, had a Pi4) eventually ran updates for Pi, but didnt' help
Agent 2) after updates, downloaded for Pi4 (got the above referenced error)
Agent 3) downloaded for Generic ARM (got the above referenced error)

I updated the /etc/agentid file each time and changed the permissions on /otm/starter.sh (chmod 775) each time.

/tmp/log_starter.txt output 3rd agent

Function: create_empty_log

=> Function: check_to_download_new_starter
STARTER scripts are the same.

run_curl
curl --silent --connect-timeout 15 --max-time 30 --request POST https://www.foxymon.com/receiver/receiver2.php -u 7QIjl8aACi:mutByrSpZkbU7AOvq1Gx84CfQoj2WwPs0nYD3JHK -F function=send_starter_version -F version=2023-12-28_0700_Phoenix_TZ
Wait 5 seconds
Attempting execution
Answer: 1
CURL executed

=> Function: check_to_download_new_otm

run_curl
curl --silent --connect-timeout 15 --max-time 30 --request POST https://www.foxymon.com/receiver/receiver2.php -u 7QIjl8aACi:mutByrSpZkbU7AOvq1Gx84CfQoj2WwPs0nYD3JHK -F function=receive_binary_location
Wait 5 seconds
Attempting execution
Answer: https://downloads.echonets.com/otm/arm64_otm_1_80_2303
CURL executed
https://downloads.echonets.com/otm/arm64_otm_1_80_2303
OTM binaries are different.
Downloading the OTM binary.
Download successful.