Automatically monitor your Internet service and provider with alerts to problems
Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.isptracker.com
Notice: If you created an account on app.isptracker.com, simply use the same credentials to log into these support forums.
Actual OTM not updating for one agent
-
Hi,
That is interesting.
Both Pi and Arm versions are definitely 1.85.2504 and you seem to be getting that version manually.
Can you try one small thing please. Go to the same directory where the binary gets downloaded to, make sure it's executable (chmod +x binary_name) then run;
./binary_name -vJust to at least confirm you're getting the actual 1.85 as a starting point.
Hello
The binary is executable and is reporting as version 1.85.2504.
bevaadmin@bevarpi01:/otm $ ls -la total 400 drwxr-xr-x 2 root root 4096 Jan 9 08:46 . drwxr-xr-x 19 root root 4096 Dec 23 14:04 .. -rwxr-xr-x 1 root root 396384 Dec 23 14:09 otm_binary -rwxr-xr-x 1 root root 3672 Jan 9 01:31 starter.sh bevaadmin@bevarpi01:/otm $ ./otm_binary -v OTM version: 1.85.2504 bevaadmin@bevarpi01:/otm $ -
I'm not 100% sure but that seems like a possible bug in the ARM version of the binary itself.
I'll have to ask the devs for their thoughts but this will take a while to confirm so please be patient and we'll solve it. -
I'm not 100% sure but that seems like a possible bug in the ARM version of the binary itself.
I'll have to ask the devs for their thoughts but this will take a while to confirm so please be patient and we'll solve it.Thank you!
-
Hi,
Just as an update. We're still digging into this but cannot find any reason for the problem so far. Yours is the only agent not reporting its version so there is nothing to compare to.
We might need to get on a live chat so we can have you restart the service/binary while we're watching at our end. That might be about the only way we can get a lead on this.
-
Hi,
Just as an update. We're still digging into this but cannot find any reason for the problem so far. Yours is the only agent not reporting its version so there is nothing to compare to.
We might need to get on a live chat so we can have you restart the service/binary while we're watching at our end. That might be about the only way we can get a lead on this.
@ISPtracker_Support
No problem I can do that. We just need to work out a time that suits everyone. I'm in New Zealand so UTC+13 time. -
Maybe we can solve it without a live chat
If you could reboot in the next 30 min or so and let me know here when it can be done I can setup few tools to confirm the bug affecting your agent
It is 10:20 AM now there so plenty of time to test it -
I ISPtracker_Support has marked this topic as solved
