|Re: [chrony-users] Chrony Server Not Listening|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
ls: cannot access '/etc/systemd/system/chrony.service': No such file
$ sudo ss -pan | grep chron
u_dgr ESTAB 0 0 /var/run/chrony/chronyd.sock 150596
* 0 users:(("chronyd",pid=6052,fd=7))
Mar 04 08:11:01 desktop systemd: Stopped Network Time Synchronization.
Mar 04 08:11:01 desktop systemd: Starting Network Time Synchronization...
Mar 04 08:11:01 desktop systemd: Started Network Time Synchronization.
Mar 04 08:11:01 desktop systemd-timesyncd: Synchronized to time
server 192.168.1.1:123 (192.168.1.1).
Odd, maybe I just didn't understand sockets. I figured I would have
seen port 123 and/or 323 listed as listening on the server.
The issue arose yesterday when my server's power supply went into
protection-mode when I was messing with wires to my modem because my
ISP link went down.
Then when I brought my server back up, I was seeing the date was now
set to February 22. That's when I started looking into chrony and
I would manually set the date, reboot and the date would reset back to
Feb 22. So I did hwclock --systohc and that set the time correctly and
didn't switch back to Feb 22 after a reboot.
I then thought that maybe chrony was futzing because my ISP link was
down. At that point, I don't remember what I was checking and when,
but it's all good now and was probably good before. I just don't know.
But my desktop log was showing "Mar 03 13:47:55 desktop
systemd-timesyncd: Timed out waiting for reply from
I'll have to look into the whole sockets/ports thing and see why I'm
not seeing the "listening" entries. I think sshd does the same thing
considering there is "sshd.service" and "ssh@.service" (which I think
the @ is about sockets).
Sorry about the false-report and thanks for the walkthrough.
On Fri, Mar 4, 2016 at 8:03 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> Any chance you have also /etc/systemd/system/chrony.service?
> That looks good.
> Ok, chronyd is responding on the port 323/udp. Does it respond to NTP
> clients now and are the sockets visible in the ss output?
> If yes, it's probably a problem in how the service is started, maybe
> something with systemd, but I'm not sure how to debug that. Maybe
> others will have suggestions.
> Miroslav Lichvar
> 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.
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.