Time and date not working since 3.23.4 release

[ai6bx]

Good morning:

In looking at a number of my nodes I noticed the date and time under setup has not changed since the date and time I updated the firmware. On some I have been able to get it going by hitting the apply settings button, save, and reboot. This is not a consistent fix however.

Keith - AI6BX

[ai6bx]

This is likely linked to ticket 838 which I just closed by mistake. The problem with dropping links an rebooting is not resolved and I now note that upon reboot, the system time and date again revert back to the time and date I applied the 3.23.4 production release. I am attaching the diagnostic
supportdata-AI6BX-1-RM3-East-202304272232.gz
file as the node just rebooted again two hours ago.

[aanon4]

The log file claims the node cannot contact any NTP servers. Is this expected on your mesh?

[ai6bx]

Tom,No, that is not expected on our mesh as plenty of other nodes are setting the appropriate systems time and date values. I will look deeper for a potential contributing factor. It seems odd that the issue began with the update.Sent from my iPadOn May 14, 2023, at 3:56 PM, Tim Wilkinson ***@***.***> wrote: The log file claims the node cannot contact any NTP servers. Is this expected on your mesh? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[aanon4]

I had a quick look at a random sample of M3 nodes in the SoCal network running 3.23.4.0, and all their times were correct.

Of your nodes I see that AI6BX-1-RM3-P2P-Snow is correct, but AI6BX-1-RM3-East is incorrect despite running the same hardware. Anything different between these two?

[aanon4]

Any update on this? The problem seems to be on this specific node, yes?

[ab7pa]

Unable to reproduce, so closing for now. Can reopen if needed.