Information and Support

You're welcome. Thanks for using the service and please, pass the word on. We live by word of mouth since it's impossible to outbid deep pocket ISPs and outages sites that would rather you don't find a service like ours.

Hi,

Glad to hear it's doing well and you now know what the problems were.

We do not have invoicing options other than subscriptions. We went with Paypal subscriptions because we prefer not to keep cards and other personal details on our end.

Our sister service, www,isptracker.com does have a billing capability but there is also a minimum requirement with discounts as you ramp up.

We also have a monthly flat rate cost but that's when you get into the thousands of agents. The kinds of companies that like this are those which have many remote employees they are supporting or other assets out in the field they want to monitor such as remote security systems, patient/telehealth equipment and so on.

Looks normal. Lots of ICMP blocking/limiting along the way it looks like.

So at this point, we have to assume that something on the host that the agent is running on is still blocking something.

Is there something running on the host that is a security manager or something or virus checker, something along those lines?

If you have another Windows host, you could install another agent, again, be sure you are admin when installing so that the firewall rule can be created then see if the dashboard shows that the agent is ready to be licensed.

Then please share the agent ID so we can look too.

You can test against tpw.outagesio.com, most other things may not have ICMP replies enabled.

Hi, just FYI, we'll take a look at this again on Monday and try to help out.

Yes, on consumer stuff, most times, ICMP is enabled but on business firewalls, typically, ICMP is disabled.

The any/any incoming rule should allow ICMP too. Can you check that to be sure it's any/any.

Hi, yes, there is a delete option under Manage in that agent dashboard.

Glad this was solved and thinks for using OutagesIO.

Hi,

I assume we can close this as solved?

Hi,

Can you share the agent ID please so I can take a look.

The Windows installer sets up an any/any rule if I recall but it only uses ports 80, 443 and ICMP. Our agent uses the most common ports that most ISPs will never block but that said, some still block ICMP.
While we use some custom ICMP methods for some of the tests, ICMP is still needed.

Hi,

Because these are subscriptions using Paypal for example, you simply go to Paypal and cancel the one you don't want.

Then from the dashboard of the one you do want, you can then subscribe for that one.

If it's only within a few days or a week, a refund for the previous is typically given so long as you make it clear here the agent IDs as you have.

So, just let us know when you do that and that will solve this issue.

Hope this helps.

If it's s different topic, best to start a new one otherwise, it gets lost in the thread. If you don't mind :).

Great, let us know how that goes. It should work no problem.

Sorry, I didn't' see your reply before completing mine. Yes, you would need a 64bit OS running on the device for otm to run on this.

Hope this helps to solve the mystery.

The Raspberry Pi 3 B+ typically runs a 32bit operating system by default, even though the hardware is 64bit capable.

If you're using a 32bit OS, the binary cannot work.

The binary is compiled as a 64bit executable, it won't run on a 32bit OS, which is likely the cause of the error you're seeing.

Here’s how you can check:

Confirm OS architecture: Run the following command to confirm if your OS is 32bit or 64bit:

uname -m

If the output is armv7l, it’s a 32bit OS. If it’s aarch64, then it’s 64bit.

Try running this against the binary that gets downloaded;

file /otm/otm_binary

We see that everything is fine, the service is downloading the correct binary. We suspect that the hardware is not compatible with the aarch64 ARM binary.

For a test, please download the binary directly, then make it executable, then just run it like ./arm64_otm_1_81_2401

https://downloads.echonets.com/otm/arm64_otm_1_81_2401

Let us know the make/model of the Pi and what happens when you run it manually.

Question, what hardware exactly are you using? Which version of Pi, make and model please.

Thanks for your patience. We'll certainly fix this tomorrow and update you also.

The reason this is showing us because it is the Linux binary that is being run, not the ARM one.

There might be a bug in the new method we've started using. It seems even when you select Pi, it's giving you the Linux binary.

I can have the developer that works on this look at it tomorrow and fix it. Once it's done, I can update this post.

We appreciate your letting us know because we were not aware of this issue.

Ah, I see that we have to update some articles.
Just follow the steps when creating an agent, don't follow that article please and let me know what happens.