Your message dated Sun, 27 Jul 2025 00:02:08 +0200
with message-id <aIVQYHiO8yd5FBeO@lamella>
and subject line Re: Bug#1109689: Fwd: Re: Bug#1109689: chrony fails on boot
when using a pps device created by gpsd
has caused the Debian Bug report #1109689,
regarding chrony fails on boot when using a pps device created by gpsd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1109689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109689
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 4.6.1-3
Severity: normal
If the package gpsd is installed and chrony is configured to use a pps
device it fails to start on boot because the /dev/pps device isn’t
available.
-- System Information:
Debian Release: 13.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.35+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chrony depends on:
ii adduser 3.152
ii init-system-helpers 1.68
ii iproute2 6.15.0-1
ii libc6 2.41-10
ii libcap2 1:2.75-9
ii libedit2 3.1-20250104-1
ii libgnutls30t64 3.8.9-3
ii libnettle8t64 3.10.1-1
ii libseccomp2 2.6.0-2
ii tzdata 2025b-4
ii ucf 3.0052
chrony recommends no packages.
Versions of packages chrony suggests:
ii bind9-dnsutils [dnsutils] 1:9.20.9-1
pn networkd-dispatcher <none>
-- no debconf information
# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usable directives.
# Use Debian vendor zone.
#pool 2.debian.pool.ntp.org iburst
# Use time sources from DHCP.
sourcedir /run/chrony-dhcp
# Use NTP sources found in /etc/chrony/sources.d.
sourcedir /etc/chrony/sources.d
# reference clock
refclock SHM 0 refid GPS precision 1e-3 poll 4 offset 0.122 delay 0.2
refclock PPS /dev/pps2 lock GPS refid PPS poll 0 precision 1e-9 rate 5 width
0.1 maxlockage 32 prefer
# This directive specifies the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
# This directive specifies the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
# Save NTS keys and cookies.
ntsdumpdir /var/lib/chrony
# Uncomment the following line to turn logging on.
#log tracking measurements statistics
# Log files location.
logdir /var/log/chrony
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile'
directive.
rtcsync
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3
# Get TAI-UTC offset and leap seconds from the system tz database.
# This directive must be commented out when using time sources serving
# leap-smeared time.
leapseclist /usr/share/zoneinfo/leap-seconds.list
# Include configuration files found in /etc/chrony/conf.d.
confdir /etc/chrony/conf.d
--- End Message ---
--- Begin Message ---
Le 2025-07-25 09:06, Ben Corby a écrit :
> On Fri, 2025-07-25 at 01:01 +0200, Vincent Blut wrote:
> > Control: tags -1 - moreinfo
> >
> > Le 2025-07-24 08:03, Ben Corby a écrit :
> > > Date: Wed, 23 Jul 2025 08:55:54 +1000
> > > From: Ben Corby <[email protected]>
> > > To: Vincent Blut <[email protected]>
> > > Subject: Re: Bug#1109689: chrony fails on boot when using a pps
> > > device
> > > created by gpsd
> > > User-Agent: Evolution 3.52.3-0ubuntu1
> > >
> > > Hi Vincent, thanks for getting back to me.
> > >
> > > sudo systemctl status chrony.service output is in attachment
> > > chrony.status.txt.xz
> > >
> > > /etc/chrony/chrony.conf is in attachment chrony.conf.xz
> > > /etc/default/gpsd is in attachment gpsd.xz
> > >
> > > sudo dmesg is in attachment dmesg.xz
> > > You can see the message "PPS line discipline registered" for
> > > pps_ldisc
> > > in this.
> > >
> > > sudo journalctl -t chronyd -t kernel | tail -15 is in attachment
> > > journalctl.chronyd.txt.xz
> > >
> > > If you would like me to try any config change or compile any patch
> > > to
> > > test just let me know.
> >
> > So you configured chronyd so that it gets connected to gpsd using the
> > SHM method. For this to work, you must edit the 'gpsd.service' unit
> > to let
> > gpsd start before chronyd. You can accomplish this using the
> > 'systemctl edit gpsd.service' command.
> >
> > However, may I suggest you to use the SOCK protocol to get chronyd to
> > connect to gpsd? It should be preferred over SHM as it offers better
> > security. Moreover by choosing this method, you don't need to modify
> > 'gpsd.service' as mentioned above.
> > For example:
> > refclock SOCK /run/chrony.ttyS0.sock refid GPS (plus any of the
> > options supported by the refclock directive)
> >
> > > Cheers,
> > > Ben.
> >
> > Cheers,
> > Vincent
>
> Vincent, thanks very much. Sorry for raising it as a bug.
> Cheers,
> Ben.
No worries, Ben. I'm closing the bug.
Cheers,
Vincent
signature.asc
Description: PGP signature
--- End Message ---
