On 12/30/23 12:19, gene heskett wrote:
synopsis phase one:
I have installed ntpsec on this, my main machine, and have successfully
switched 5 of my other networked machines to use this statum 2 server
instead of pestering the debian server pool.
However, I have it restricted to replying only to members of my private
network.
Synopsis phase two: A QIDI X MAX-3 3d printer with a rockchip64 running
armbian 22.05 (buster) as the klipper, moonraker, and fluidd web
interface to control this printer. But its clock is wrong by about an
hour 45 minutes and short of trying to figure out settime, which might
get it within 30 seconds at best, I need to make nptsec behave like the
long since deprecated ntpdate command which could slam the current
timedate into the clock regardless, harmless if done in early boot but
I'm told can be dangerous to a running kernel.
Now I need to get far more familiar with systemd than I am. For those
of you using ntpsec, and it is generating the proper logs in
/var/log/ntpsec, I need to see how you have accomplished this in your
/etc/ntpsec/ntp.conf, enabling the logging of everything it does, I'm
getting nothing here in that properly configured path, and
/lib/ntpsec/ntp,drift is stuck at 00.00000.
While:
root@mkspi:/usr/share# systemctl status ntpsec.service
● ntpsec.service - Network Time Service
Loaded: loaded (/lib/systemd/system/ntpsec.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2023-12-30 09:26:32 EST; 43min ago
Docs: man:ntpd(8)
Process: 15642 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper
(code=exited, status=0/SUCCESS)
Main PID: 15645 (ntpd)
Tasks: 1 (limit: 998)
Memory: 9.0M
CGroup: /system.slice/ntpsec.service
└─15645 /usr/sbin/ntpd -p /run/ntpd.pid -c
/etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
Dec 30 10:00:41 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3
Dec 30 10:00:41 mkspi ntpd[15645]: DNS: dns_take_status:
coyote.coyote.den=>good, 8
Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_probe: coyote.coyote.den,
cast_flags:8, flags:101
Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_check: processing
coyote.coyote.den, 8, 101
Dec 30 10:04:57 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3
Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_take_status:
coyote.coyote.den=>good, 8
Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_probe: coyote.coyote.den,
cast_flags:8, flags:101
Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_check: processing
coyote.coyote.den, 8, 101
Dec 30 10:09:13 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3
Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_take_status:
coyote.coyote.den=>good, 8
root@mkspi:/usr/share#
Which to me looks like it ought to be working but is obviously not working.
Capturing my ntpsec server traffic on port 123 shows mmkspi is accessing
the server and the server is responding at several minute intervals:
11:48:15.267912 IP mkspi.coyote.den.ntp > coyote.coyote.den.ntp: NTPv4,
Client, length 48
11:49:21.274706 IP coyote.coyote.den.ntp > mkspi.coyote.den.ntp: NTPv4,
Server, length 48
11:50:26.267614 IP mkspi.coyote.den.ntp > coyote.coyote.den.ntp: NTPv4,
Client, length 48
11:50:26.267681 IP coyote.coyote.den.ntp > mkspi.coyote.den.ntp: NTPv4,
Server, length 48
But the date 45 seconds later on mkspi is:
Sat 30 Dec 2023 10:24:10 AM EST
I have used systemctl to stop and disable both timesyncd.service and
chrony.service since neither seems to want to access my ntpsec server.
Acc the docs I've read, all 3 of these utilities s/b able to do the job.
And I'm lost w/o any info to debug this, no log files at all. Those
log file locations are NOT on my raid that is being so d_____d
cantankerous.
My thanks to anyone who can help.
Call in the St. Bernards, tap the cask, and have a happy new year, I
found it, it jumped over 6000 seconds and the date output is now
correct. And it did not crash the printer. I'm a happy camper.
Cheers, Gene Heskett.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
