Arch Linux

vindicator

Member

Registered: 2016-02-25

Posts: 43

Chrony Server Not Listening

$ cat /etc/chrony.conf
maxupdateskew 5
driftfile /var/lib/chrony/drift
dumponexit
dumpdir /var/lib/chrony
allow 192.168.1.0/24
local stratum 10
rtcfile /var/lib/chrony/rtc
rtconutc
#rtcsync

$ sudo chronyd -u chrony -d -f /etc/chrony.conf
2016-03-04T01:57:03Z chronyd version 2.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH +ASYNCDNS +IPV6 -DEBUG)
2016-03-04T01:57:03Z Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/drift

$ sudo ss -pant | grep chron
$ //nothing returned

Reading other threads here, it looks like chrony is just plain problematic and none of the threads are showing it being used as a server.
Debug sure doesn't look to be providing any clues why it isn't listening at all.

vindicator

Member

Registered: 2016-02-25

Posts: 43

Re: Chrony Server Not Listening

This false issue can be ignored.
I don't know what the problem was, but it's working now.

I just find it odd that "ss" doesn't show ports 123 or 323 being listened to, which is what I was expecting:

$ sudo ss -pan |grep chron
u_dgr  ESTAB      0      0         * 153535                * 0                   users:(("chronyd",pid=6180,fd=0))
u_dgr  ESTAB      0      0      /var/run/chrony/chronyd.sock 153541                * 0                   users:(("chronyd",pid=6180,fd=6))

I think sshd behaves in the same way. "ss" shows "u_str" and "u_dgr" entries, and when I'm connected, it'll show port 22 being active/consumed by my connection.

Can someone explain WHY "ss" doesn't show "LISTEN" like this? I'd be able to use the information to know what port needs to be open.