Information and Support

Yes, 131124 is connected wirelessly directly to my provider modem as I covered in the very first post. 10.0.0.1 is the gateway IP from the modem.

First hops between 23 and 24.

131123:
2024-10-01 19:27:30 335 1 192.168.50.1 On your local network
2024-10-01 19:27:30 335 2 10.0.0.1 With your Internet provider <---
2024-10-01 19:27:30 335 3 10.61.79.194 With your Internet provider

131124:
2024-10-01 18:53:00 334 1 10.0.0.1 On your local network <---
2024-10-01 18:53:00 334 2 10.61.79.194 With your Internet provider

This shows the discrepency between each agent, can we make them both match to say "With your Internet provider"?

If I need to detail that any further please advise what I missed in describing how both agents are configured.

Checking in regarding this, happened again today.

2024-10-01 12:33:44 - Down (10.0.0.1) for 15s (Internal)
on 131124

Finally happened again, and it is incorrect

2024-09-27 04:05:05 - Down (10.0.0.1) for 7s (Internal) on 131124

On 131124 can we please change .1 to provider since it's the modem itself and no other network component?

Oh no, leave that as external as it's outside of my house's gateway. I mean the history is going to still show "internal" on those and only new events will reflect correctly?

I assume that change will not be retroactive?

Alrighty, sounds good thank you. I think that will clear up what I'm seeing as confusion

Looking at hops on 131124, the second hop is not internal, the .1 is the gateway which means that second hop should be considered something else.

My setup is a bit odd as I'm trying to prove two separate ways to my provider that it's not the house wiring, my router, ect.

The 10.x.x.x is the DHCP pool from the modem, the 192.x.x.x is from the router which is why it is only seen on 131123.

This is for both 131123 and 131124, I have them setup to track my provider in two separate ways, allow me to explain.

131123 - Is on a Pi that's plugged into my home router, it shows repeated "Internal" alerts even though my home network is fine to the point to where I use an app to control my second machine from my first to share keyboard and mouse and it never has an issue. Almost all alerts show internal.

131124 - Is on a Pi with wireless connection straight to my ISPs modem. There is no internal to go down here, this is when the modem stops serving internet access, but I confirm with my third machine that the wireless itself stays functional, it has no route at the times denoted.

The time windows of outages are fairly close as you can see, but that makes that internal flag even more confusing if one agent hard wired behind a router and a wifi straight to modem with no home networking at all are showing the same outage windows.

Can you please check both agent logs and investigate why it is flagging things the way it is? 131124 is most confusing when there's nothing to go down but the modem.

Thank you for the assist in regards to all of this. We are sorted and closed. :)

That works as well. Please refund 131117 and remove 131116 as I am not able to, both of the new agents are now paid up.

I did figure out most of this, the only thing I can't do is remove the 131116 client, and transfer the payments to 131123.

I would like some account cleanup assistance, I cannot figure out if I can do this myself.

Can we please remove 131116 and 131117? I will no longer be using windows clients.

Can we move the one I already paid for which I believe 131116's payment up to 131123?

Can we Nickname as the following

131123 - Inside router
131124 - Outside Router

Once this is sorted, I'll up the second agent to get them both sorted.

Thank you.

Alright, we're in business. Purchased a Pi 5 for the PiHole / OTM client, working grand. The Pi 3 was formatted to the latest OS, and brought up as a purely OTM client.

Should I start a new thread about moving licenses and renaming things to let this be as something searchable for others in case they see this themselves?

All good, cleared up for now. Ordered a Pi 5, will be here tomorrow.

Raspberry Pi 3 B+ with 10 / Buster.

240K -rwxr-xr-x  1 root root 239K Sep 11 15:57 arm64_otm_1_81_2401
root@pihole:/otm# ./arm64_otm_1_81_2401
bash: ./arm64_otm_1_81_2401: cannot execute binary file: Exec format error

I can format it to 11 / Bullseye, but if that's still too old I can grab a new one, as I run a pi-hole I'll maintain a raspberry pi for my installation.

I'm happy to be your test bed for this fix. I already have a script wrote to wipe both logs and the /otm folder.

Okay, so cleared the otm directory completely to allow for a fresh download

root@pihole:/# mkdir otm
root@pihole:/# cd /otm
root@pihole:/otm# cd ~
root@pihole:~# systemctl daemon-reload
root@pihole:~# systemctl start otm.service
root@pihole:~# systemctl status otm.service
● otm.service - Startup of the OutagesIO Internet monitor agent
   Loaded: loaded (/etc/systemd/system/otm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2024-09-15 20:35:46 CDT; 28s ago
  Process: 2839 ExecStartPre=/bin/sleep 30 (code=exited, status=0/SUCCESS)
  Process: 2845 ExecStartPre=/usr/bin/curl -s https://downloads.echonets.com/scripts/starter.sh -o /otm/starter.sh (code=exited, status=0/SUC
  Process: 2847 ExecStartPre=/bin/chmod +x /otm/starter.sh (code=exited, status=0/SUCCESS)
  Process: 2848 ExecStart=/bin/bash /otm/starter.sh start (code=exited, status=0/SUCCESS)
 Main PID: 2874 (code=exited, status=2)

Sep 15 20:35:03 pihole systemd[1]: Starting Startup of the OutagesIO Internet monitor agent...
Sep 15 20:35:34 pihole bash[2848]: => Function: send_starter_version
Sep 15 20:35:46 pihole bash[2848]: Starting OTM then exiting this script
Sep 15 20:35:46 pihole systemd[1]: Started Startup of the OutagesIO Internet monitor agent.
Sep 15 20:35:46 pihole systemd[1]: otm.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Sep 15 20:35:46 pihole systemd[1]: otm.service: Failed with result 'exit-code'.

Popped into the otm directory, and starter was there:

root@pihole:~# cd otm
root@pihole:~/otm# ls
starter.sh

I had cleared the otm log, after this above execution, fresh output.

root@pihole:~/otm# cat /tmp/otm.log
/otm/otm_binary: 1: /otm/otm_binary: ELF��n@X�@8: not found
/otm/otm_binary: 2: /otm/otm_binary: �@: not found
/otm/otm_binary: 3: /otm/otm_binary: T
                                      ��: not found
/otm/otm_binary: 3: /otm/otm_binary: H���gF
                                           M: not found
/otm/otm_binary: 5: /otm/otm_binary: �v5�␦�%
8
 %����Z����: not found
/otm/otm_binary: 7: /otm/otm_binary: ��
                                       �: not found
/otm/otm_binary: 7: /otm/otm_binary: �������: not found
/otm/otm_binary: 1: /otm/otm_binary: Syntax error: word unexpected (expecting ")")