Duplicate entries in `balena logs` after boot.

#3 is the most critical for us right now since the only way to resolve it is to reboot the device and hope it doesn’t happen again, or to restart Nemo from the dashboard. Our customers can’t restart the service, and having to reboot and cross their fingers is a pretty bad solution. Unfortunately I can’t seem to replicate it reliably or figure out exactly what triggers it. I’ve been able to replicate it occasionally (maybe 1 in 10 times) with a sequence of:

  1. Power cycle with ethernet unplugged
  2. Use date -s to set the date back a month or more (not sure what the actual min time is so just using a lot)
  3. Wait a bit (a minute, a few? sometimes helps, sometimes doesn’t)
  4. Plug the ethernet in

I figured I’d update https://forums.balena.io/t/chronyc-config-is-bad-if-device-comes-online-without-internet to continue tracking this issue. I was waiting until I found a way to replicate it, or at least gathered a little more information. I can update it now, though I’m not sure if maybe it should actually be an entirely new thread?