On 2013-12-07 17:29, unruh wrote:
On 2013-12-07, Antonio Marcheselli <[email protected]> wrote:
Hello all,
I've got another strange issue with NTP. Last week I found that the logs
were not populating anymore, last entry was a few days before.
Stopped the NTP service, deleted the log file and restarted the service
fixed it.
Today found that the log file is not populating again.
As you may know I'm using an old version, 4.2.4p4
Anything I should know?
which logfile? ntp retires each log file, renaming it with the current
date-- at the end of each day UTC as I understand. Thus
-rw-r--r-- 2 ntp ntp 3140 2013-12-07 15:49 loopstats
-rw-r--r-- 1 ntp ntp 12729 2013-12-03 15:55 loopstats.20131203
-rw-r--r-- 1 ntp ntp 11560 2013-12-04 15:57 loopstats.20131204
-rw-r--r-- 1 ntp ntp 4192 2013-12-05 15:36 loopstats.20131205
-rw-r--r-- 1 ntp ntp 8637 2013-12-06 15:54 loopstats.20131206
-rw-r--r-- 2 ntp ntp 3140 2013-12-07 15:49 loopstats.20131207
I do not know how you are reading the files to see if it not populating
them?
Those files are normally referred to as stats rather than logs.
The ntp.log file contents depends on logging options, normally set at the
very top of ntp.conf to:
# Log everything
logconfig =allall
as ntpd is not very chatty, except after startup, and when problems happen
if you have relevant logging enabled.
For your release "By default, logconfig output is set to allsync" (from
http://doc.ntp.org/4.2.4/miscopt.html)
which will only log sync events, so your log may not be appended often.
See current stable doc http://doc.ntp.org/4.2.6p5/decode.html about events,
as your release docs do not include this info.
Even better, update to current stable from download sources, keep your
current config file (with the change above), and many problems will
disappear.
--
Take care. Thanks, Brian Inglis
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
