"logconfig" has no effect

Hal Murray halmurray at sonic.net
Sun Apr 27 21:34:28 UTC 2025


> But I am not even able to disable all logging with
>> logconfig -allall 

That only effects some low level logging.


> - the log messages are always the same and are not reduced. Every couple
> of minutes I get:

> ntpd[1656]: DNS: dns_probe: 3.debian.pool.ntp.org, cast_flags:8, flags:101
> ntpd[1656]: DNS: dns_check: processing 3.debian.pool.ntp.org, 8, 101 
...

That's just telling you what the DNS lookups are finding.

Under normal conditions, you will get a lot of logging at startup but then 
it will settle down and only log something occasionally.

The pool stuff will drop hosts that aren't responding and get new ones 
when it needs them.  That could turn into "every couple of minutes" if 
your network is broken so that every host it tries iends up not responding.

The DNS lookup worked so the network is basically working.  Is somebody 
filtering NTP packets?  That could be your ISP or your local firewall or 
something like apparmor.

What does ntpq -p show?
The reach column is a bitmask (octal) of the last 8 packets.  Each 1 is a 
response.  If the delay and offset columns are 0, that's an indication 
that the host hasn't ever received a response.



-- 
These are my opinions.  I hate spam.





More information about the users mailing list