Actual OTM not updating for one agent

[beva]

Hello

I have an agent (130787) where the Actual OTM version is not updating in the dashboard.
It is reporting 1.81.2402 in the dashboard but the version running on the device is 1.85.2504.
The agent is running on a Raspberry Pi 4.

The /tmp/log_starter.txt contains the following (sanitized).

=> Function: create_empty_log

   run_curl
   curl --silent --connect-timeout 15 --max-time 30 --request POST https://www.foxymon.com/receiver/receiver2.php -u  -F function=send_starter_version -F version=2023-07-21_0930_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  -F function=receive_binary_location
   Wait 5 seconds
   Attempting execution
   Answer: https://downloads.echonets.com/otm/arm64_otm_1_85_2504
   CURL executed
https://downloads.echonets.com/otm/arm64_otm_1_85_2504
OTM binaries are the same.
Starting OTM binary.
OTM binary started with PID 794

Is there anything I need to do to get the agent version reporting correctly in the dashboard?

Thanks for any help.

[ISPtracker_Support]

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 -v

Just to at least confirm you're getting the actual 1.85 as a starting point.

[beva]

@ISPtracker_Support

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 $

[ISPtracker_Support]

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.

[beva]

@ISPtracker_Support

Thank you!

[ISPtracker_Support]

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.

[beva]

@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.

[SBK]

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

[beva]

@SBK
Perfect - I can reboot anytime in the next 30 minutes. Let me know when you're ready.

[SBK]

Go for it!

[beva]

@SBK
And done.

[SBK]

Let me check the debug info I collected hoping I can confirm what I saw earlier

[SBK]

I opened a chat with you so we can talk there

[SBK]

Thank you again for helping us troubleshoot this bug
All fine, please confirm here

[beva]

@SBK
The dashboard is now displaying the correct version of the agent

Many thanks for fixing that!