| Re: [chrony-users] Chrony refclock socket 'disappears' |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony refclock socket 'disappears'
- From: "Kevin P. Fleming" <lists.chrony-users@xxxxxxxxxxxxx>
- Date: Mon, 12 Feb 2024 08:20:01 -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 :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1707744030; x=1707830430; bh=VmGF0WkokY umXDeBRy3ILa4SZapYO+SHgczLieQgUQ4=; b=WHvIbRj05fTHFUp68sRmXTON7a FD4pztojuscDcSQx4XbreQeYds4rKKY3U8TBhQ31/Ij/m+hX9iS9SjRjiRm8QfHb BXiWTuXqceYNZVML2aI+oqWwrVrVf5hYUfMix1R+tNkvUp2H1VDo/IBYQRijWRrh zmtiY5uzubwC4tDGeejcAQi7DbjYEuchy9v6OrajrWotDpyE2e7kE6eriJHbvtN5 fojJbaawVTL1zEkVVPDTqqMfUzPP6YTzkXl6k07W0nYKD1xBKVlBbNLO3tj1g1qE gLQKH6pAyGJLwJ7xNxSeZn2/S2aJrNATlnkIePuA6L4ObLwkIB78xybO9Vag==
- 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:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1707744030; x=1707830430; bh=VmGF0WkokYumXDeBRy3ILa4SZapY O+SHgczLieQgUQ4=; b=wUy/M2dFaSDM9JL2Ocx4YLOSkDN4qfdNtUbL/ILWBCzy pu4OZDrffHP2lB9VuQBhVFVb4uFqFXI3dHwfceLMnxBfU3W0dzz46WgpaMhD/XRD d3w5LLR7OhO6WWn7NexI3PIilrwGHjq3CUTrCITR+jUyioNQ7b3lTbdsHDsOpow/ 8Psh2Ma4G9L3N0kV3jtS5OfVfuO+eaSolfO4JKVVek3fvkSfQ+xdMP/bfWImxBzP kqld9pkoIVHApSN4TO7AgdDkhljJBvf5Kv0Wz8+/3RR0BuHK+SVqOLdz8qTZyMAv e9/d3ZRWLjlnW6eFgjPLZI6hRvuf4jx2cRZ/1B4BJA==
- Feedback-id: i1309466e:Fastmail
On Mon, Feb 12, 2024, at 08:13, Miroslav Lichvar wrote:
> On Mon, Feb 12, 2024 at 07:14:24AM -0500, Kevin P. Fleming wrote:
>> 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)
>
> I'd suspect another gpsd instance started for some reason and
> interfering with this one. Maybe a USB device is plugged in and some
> script starts a new instance instead of adding the device to the
> existing one?
Not in this case, these journal entries were the result of me running 'systemctl restart gpsd'.
>
>> 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.
>
> -L 2 will reduce logging. -L 0 is default. -L -1 would log debug
> messages if they are compiled in.
OK, since it's the Debian package they are probably not.
> You can try attaching to the chronyd process with strace to confirm
> it's not receiving anything on the socket when it happens. It would be
> just waiting in the select() call.
Thanks, I'll do that along with using 'lsof' to see if the socket is open in both processes.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.