Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #268166
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: strange time problem with bullseye/buster |
| Date | 2024-03-08 04:30 +0100 |
| Message-ID | <Ifz5L-facn-1@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <Ifok1-f3lm-7@gated-at.bofh.it> <IfoWJ-f3N4-7@gated-at.bofh.it> <Ifpzr-f4fH-1@gated-at.bofh.it> <Ifw7T-f8m0-1@gated-at.bofh.it> <Ifyjn-f9BJ-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 3/7/24 21:30, David Wright wrote: > On Thu 07 Mar 2024 at 19:17:02 (-0500), gene heskett wrote: >> On 3/7/24 12:19, David Wright wrote: >>> On Thu 07 Mar 2024 at 11:29:47 (-0500), gene heskett wrote: >>>> On 3/7/24 10:59, Greg Wooledge wrote: >>> >>>>> You should be able to verify that the systemd-timesyncd package is >>>>> removed. >>>>> >>>> >>>>> In some older versions of Debian, systemd-timesyncd was part of the >>>>> systemd package, and was always installed, even if you installed ntp >>>>> or chrony. In these versions, the systemd unit file for timesync >>>>> had checks for the existence of the binaries belonging to ntp, chrony >>>>> and openntpd, and would prevent timesync from running if any of those >>>>> was found. >>>>> >>>>> I don't remember which version did which thing. >>>>> >>>>> And of course, if you are not actually running Debian, then all bets are >>>>> off. You're on your own with Armbian, Raspbian, etc. >>>>> >>>> and because the printer is arm stuff, its old armbian buster vintage. >>>> mks@mkspi:/etc/init.d$ sudo apt purge systemd-timesyncd >>>> Reading package lists... Done >>>> Building dependency tree >>>> Reading state information... Done >>>> Package 'systemd-timesyncd' is not installed, so not removed >>>> 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. >>>> mks@mkspi:/etc/init.d$ >>>> yet timedatectl is still there and shows: >>>> mks@mkspi:/etc/init.d$ timedatectl >>>> Local time: Thu 2024-03-07 11:15:53 EST >>>> Universal time: Thu 2024-03-07 16:15:53 UTC >>>> RTC time: Thu 2024-03-07 11:04:39 >>>> Time zone: America/New_York (EST, -0500) >>>> System clock synchronized: no >>>> NTP service: inactive >>>> RTC in local TZ: no >>>> mks@mkspi:/etc/init.d$ >>>> And the local time shown above is correct to the second. >>> >>> Debian's buster's systemd (241) has timesyncd built-in, so you may >>> find that ls -l /lib/systemd/systemd-timesyncd still finds it. >>> >>> The output from timedatectl is worrying. I would monitor chrony and >>> check its logs to see if it it's doing anything. After all, you had >>> ntpsec running until a "moment" ago, so you'd hardly expect the clock >>> to be wrong by now. >> >> At the instant I removed ntpsec and minute later whem I re-installed >> chrony, the time on that printer was around 20 hours stale. By about a >> minute after chrony started, which the install did, time was >> synchronized. >> >> And still is. Somehow, it resurrected the customized >> /etc/chrony/chrony.conf which pointed it at this machines ntpsec >> server. So I didn't have to re-invent that wheel. It just Worked. >> Memory in the u-sd card? IDK. >> >> I have NDI how to extract chrony's logs from journalctl. > > You could run these commands as an ordinary user instead: > > $ chronyc sources > $ chronyc sourcestats > $ chronyc tracking > > which will give you an idea of what it is doing. > > Cheers, > David. > > . mks@mkspi:/etc/init.d$ chronyc tracking Reference ID : C0A84703 (coyote.coyote.den) Stratum : 4 Ref time (UTC) : Fri Mar 08 03:23:48 2024 System time : 0.000006175 seconds slow of NTP time Last offset : -0.000005491 seconds RMS offset : 0.000007778 seconds Frequency : 6.590 ppm slow Residual freq : -0.002 ppm Skew : 0.036 ppm Root delay : 0.034696314 seconds Root dispersion : 0.054448538 seconds Update interval : 64.5 seconds Leap status : Normal Looks good to me. ;o)> Thanks David. Take care & stay well. Cheers, Gene Heskett, CET. -- "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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: strange time problem with bullseye Teemu Likonen <tlikonen@iki.fi> - 2024-03-06 06:40 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-06 13:10 +0100
Re: strange time problem with bullseye Jeffrey Walton <noloader@gmail.com> - 2024-03-06 19:10 +0100
Re: strange time problem with bullseye David Wright <deblis@lionunicorn.co.uk> - 2024-03-06 20:30 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-06 18:20 +0100
Re: strange time problem with bullseye Teemu Likonen <tlikonen@iki.fi> - 2024-03-06 18:40 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-06 18:50 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 00:00 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 00:10 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 02:40 +0100
Re: strange time problem with bullseye John Hasler <john@sugarbit.com> - 2024-03-07 03:10 +0100
Re: strange time problem with bullseye <tomas@tuxteam.de> - 2024-03-07 06:30 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 14:40 +0100
Re: strange time problem with bullseye <tomas@tuxteam.de> - 2024-03-07 14:50 +0100
Re: strange time problem with bullseye Jeffrey Walton <noloader@gmail.com> - 2024-03-07 17:20 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 17:40 +0100
Re: strange time problem with bullseye Teemu Likonen <tlikonen@iki.fi> - 2024-03-07 15:10 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-07 20:40 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 20:50 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-08 18:30 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 17:00 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 17:40 +0100
Re: strange time problem with bullseye/buster David Wright <deblis@lionunicorn.co.uk> - 2024-03-07 18:20 +0100
Re: strange time problem with bullseye/buster gene heskett <gheskett@shentel.net> - 2024-03-08 01:20 +0100
Re: strange time problem with bullseye/buster David Wright <deblis@lionunicorn.co.uk> - 2024-03-08 03:40 +0100
Re: strange time problem with bullseye/buster gene heskett <gheskett@shentel.net> - 2024-03-08 04:30 +0100
Re: strange time problem with bullseye/buster Max Nikulin <manikulin@gmail.com> - 2024-03-08 17:20 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 03:40 +0100
Re: strange time problem with bullseye <tomas@tuxteam.de> - 2024-03-07 06:30 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-07 20:20 +0100
Re: strange time problem with bullseye Dan Ritter <dsr@randomstring.org> - 2024-03-07 20:50 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-08 01:30 +0100
Re: strange time problem with bullseye Jeffrey Walton <noloader@gmail.com> - 2024-03-06 18:50 +0100
csiph-web