[Bug]: If system time changes significantly after meshtasticd starts, API goes incommunicado

[noon92]

Category

Other

Hardware

Linux Native

Firmware Version

2.5.11

Description

On the Femtofox:
This took some time to track down. We were having issues with meshtasticd not responding to CLI commands after boot until the service was restarted. Looks like the issue is that at boot, the system time defaults to nov 2023. A bit after boot, an NTP service (chrony) sets the time from either an RTC module or network, and the current time jumps to jan 2025. Meshtasticd no longer responds to commands after this, until service is restarted.

@vidplace7 @jp-bennett

Relevant log output

[noon92]

Link to discussion:
https://discord.com/channels/867578229534359593/1302945239689990185/1332776805740056649