[Bug 238352] ntpd fails to log fatal error(s)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Jun 5 22:16:35 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238352

            Bug ID: 238352
           Summary: ntpd fails to log fatal error(s)
           Product: Base System
           Version: 12.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs at FreeBSD.org
          Reporter: rfg-freebsd at tristatelogic.com

The man page for ntpd(8) and specifically the portion dealing with the -g
option, says explicitly:

   "Normally, ntpd exits with a message to the system log if the offset
   exceeds the panic threshold..."

In my experience, this appears not to be the case.  Many ntpd messages *do* end
up in /var/log/messages, but when and if ntpd experiences a situation where the
difference between the currently set time and the actual time (as provided by
the configured remote ntp servers) is larger than the "panic threshold" then
ntpd will exit, as expected, but when it does so it appears that it is NOT
actually writing any message or messages first to the syslog and/or to
/var/log/messages.

If this can be reproduced, it should be fixed.  The ntpd daemon should have the
common courtesy to let the user know, via the syslog, that it has decided to
commit suicide, and the reason for that decision.  This information is vitally
necessary in order for the user to understand and then rectify the underlying
problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list