| [chrony-users] Chrony refclock socket 'disappears' |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Chrony refclock socket 'disappears'
- From: "Kevin P. Fleming" <lists.chrony-users@xxxxxxxxxxxxx>
- Date: Mon, 12 Feb 2024 07:14:24 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=km6g.us; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm1; t=1707740087; x=1707826487; bh=3X3K57TR2+6S+6xOiy9OiAoExoGI3SFX L2FxXG1oveI=; b=AT3LeVbrOiEwOnb0UwiyLFP9iJ0dzMMvjYwvRe5tonxq2IzU arUaFtvC4IuipOPZ/kBjRKQ4Nt/S4KQk1rlnhqQ9LDFYH/d/Y4SEC8uducrXypUw I/62xA/G0ds28A6uBqFvuCLSvz8ckr/VLa2h/CBGRQVrNikEcB6Ij2sbcVlXW8KC nFgNSEWnHST7NRCvkRC07X3vM3U1MplWMHwlAyVQVqpOrgOXovdVY+kGbY8nDZHG XdrVjk6uKIORTA9/JuUhiSTyOE1jRS4Jv+M9pnrnEdFf4zS0AUppEJEsCaf6vQR9 8DVvJ8Eaz+sO7TJBe1kS0VwjszuGy1Go5TYSZA==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1707740087; x=1707826487; bh=3X3K57TR2+6S+6xOiy9OiAoExoGI3SFXL2F xXG1oveI=; b=LY2B9UyuCLRra+Evtscie7WEuS03kr7cF3+MI8Elp2rHliPy94S 5HbK3cAlgstILkqCT2fefx5C3CYcsiPw3f0qdYnzGql4KsB14zW/fjDw1dhiEyIA rE/O4uCwSWtFq4d7Ms++MK5AAm/9fPrpOwUFC9EPsdOJUrjw4yz+JsnBm4xPc75V 0eqWAGyIAY09hw5HXrt1SUaim22hz6+M8LSLM4VJ2lkAKFbQICypJdQGnqfYL/8/ LsWXuWsJi3C1unPlESEDE1l2V2VTn2DYRoX8zyEWeyzdGcBBtDVWjzoURnsjwIba T1X0Cvb6TJyd62yErjqz0vR45vQalmb17TQ==
- Feedback-id: i1309466e:Fastmail
I've got a pair of systems running Chrony 4.3-2+deb12u1 (Debian Bookworm package) along with gpsd (built from source from the 'master' branch).
The chrony.conf file looks like this:
bindaddress 192.168.255.1
bindaddress 2001:470:8afe:255::1
bindacqaddress 192.168.86.20
bindacqaddress 2001:470:8afe:86::20
refclock SOCK /var/run/chrony.gpsd0.sock refid GPS
pool us.pool.ntp.org iburst
keyfile /etc/chrony/chrony.keys
driftfile /var/lib/chrony/chrony.drift
logdir /var/log/chrony
leapsectz right/UTC
rtcsync
makestep 0.1 3
allow all
gpsd is using /dev/gpsd0, so it finds this socket created by Chrony and feeds in both time and PPS, and life is good.
However, randomly, the GPS source just stops, and Chrony starts tracking one of the servers from us.pool.ntp.org. With the current configuration files there is nothing output in any logs (either for Chrony or gpsd) when this happens, but if I restart gpsd then I see this:
Feb 12 06:16:56 core23-a systemd[1]: Starting gpsd.service - GPS (Global Positioning System) Daemon...
Feb 12 06:16:56 core23-a gpsd[2349564]: gpsd:ERROR: SHM: shmget(0x47505344, 29416, 0666) SHM export failed: Invalid argument(22)
Feb 12 06:16:56 core23-a systemd[1]: Started gpsd.service - GPS (Global Positioning System) Daemon.
The only fix is to restart Chrony as well, and then gpsd restarts, reconnects, and Chrony starts receiving data again.
What can I do to figure what may be causing this? Is it safe/wise to run chronyd in 'production' mode with "-L 2"? This situation only occurs about once per week across the two machines, so I'll have to run with logging enabled for quite some time to catch it.