N2+ Impervious to Timekeeping Applications

[Quantum]

Armbian current:

 

It seems that the N2+ is [i]immune[/i] to Chrony and systemd-timesyncd.  The only way I can set the date/time is manually through date -s.

 

# systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
     Active: active (running) since Mon 2025-11-24 13:06:59 PST; 31min ago
 Invocation: 50da85c1116348dbbd83cca270da6ff8
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 1185 (systemd-timesyn)
     Status: "Idle."
      Tasks: 2 (limit: 4227)
     Memory: 1.6M (peak: 2.3M)
        CPU: 79ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─1185 /usr/lib/systemd/systemd-timesyncd

Nov 24 13:06:59 lab systemd-timesyncd[1185]: System clock time advanced to recorded timestamp: Mon 2025-11-24 13:06:59 PST
Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:07:01 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:07:11 lab systemd-timesyncd[1185]: Timed out waiting for reply from 10.2.1.10:123 (10.2.1.10).

 

No, the network configuration has na-ha-hot, changed, Spastic.  I see via tcpdump, the request going out 123/udp and the response, coming back.  The information arrives at the destination.  But it hits a hard rock head and disintegrates.  Of course if it can't set the system clock, there's no sense trying to make it set the RTC.

 

How is this possible in the 21st Century?  Does time, no longer matter to Gen Z?  Is this the precursor to the Apocalypse?  Should I convert to religion and start praying?

Edited 12 hours ago by Quantum

[laibsch]

10 hours ago, Quantum said:

How is this possible in the 21st Century?

 

What you need to understand is that whatever money you paid, you paid for the hardware not for software support.  So, the hardware vendor does not give you software support.  And we are just a bunch of enthusiasts trying to keep our own boards alive.  I am sure that you can understand that your understandable nonetheless misguided rant does not necessarily help in making us more enthusiastic.  Armbian provides you with some help to maintain your own board yourself.  Whenever somebody does so and provides their work back to the community you are in luck and can freeload off of their work.  Still doesn't give you the right to make demands and rant.

In your case, you are in luck as there is a person donating their expertise and time.  Let's see if @NicoD has anything to say about the issue with your board.  Buy him a coffee on Paypal or Patreon for the time he already donated to keep YOUR board alive while getting 0 cents from you so far?

[eselarm]

12 hours ago, Quantum said:

Chrony and systemd-timesyncd.

2 captains on the same ship is my first note. 

Then there is fake-hwclock and maybe an RTC onchip/silicon and/or your own or PCB vendor added RTC module like DS3231. And the battery can be almost empty. Early Debian Trixie had a bug with fake hwclock script, I already removed it years ago on SBCs where I added DS3231, but if you haven't there is the sort of 3rd captain. RPi/Raspbian users had that issue.

 

[eselarm]

And further, what do you need? I know Armbian and Opensuse use chrony instead of older ntp things. Chrony can serve the time to others, do you need that? If not remove it I would say and keep/use a standard client-only method.