[ntp:bugs] [Bug 434] Event clk_fault for refclocks at ntpd startup

bugzilla at ntp.isc.org bugzilla at ntp.isc.org
Tue May 24 06:49:47 PDT 2005


http://bugs.ntp.isc.org/show_bug.cgi?id=434





------- Additional Comments From mills at udel.edu  2005-05-24 13:49 -------
Subject: New: Event clk_fault for refclocks at ntpd startup

Martin,

I didn't add these weeds and would just as well avoid them. However, 
these are the kinds of things some folks consider politically 
(in)correct, so I will avoid making judgements.

Dave

bugzilla at ntp.isc.org wrote:

>http://bugs.ntp.isc.org/show_bug.cgi?id=434
>
>           Summary: Event clk_fault for refclocks at ntpd startup
>           Product: ntp
>           Version: dev
>          Platform: Other
>        OS/Version: Linux
>            Status: NEW
>          Severity: normal
>          Priority: P3
>         Component: ntpd
>        AssignedTo: stenn at ntp.org
>        ReportedBy: martin.burnicki at meinberg.de
>                CC: bugs at ntp.isc.org,mills at udel.edu
>
>
>Every time ntpd is started, it immediately prints a syslog msg saying: 
>clock LOCAL(0) event 'clk_fault' (0x03) 
> 
>running ntpd with "-ddd" prints: 
> 
>report_event: system event 'event_restart' (0x01) status 'sync_alarm, 
>    sync_unspec, 1 event, event_unspec' (0xc010) 
>refclock_transmit: at 1 127.127.1.0 
>refclock_receive: at 1 127.127.1.0 
>addto_syslog: clock LOCAL(0) event 'clk_fault' (0x03) 
>peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, 
>    event_reach' (0x8014) 
> 
>The example above is for the local clock, but this also happens for other 
>refclocks, e.g. using the parse driver. Earlier versions of ntpd did not show 
>this behaviour.  
> 
>It's not really a bug, but it's annoying, and users are asking why e.g. the 
>local clock is considered to be faulty. 
> 
>Best regards, 
> 
>Martin
>
>
>
>------- You are receiving this mail because: -------
>You are on the CC list for the bug, or are watching someone who is.
>





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


More information about the bugs mailing list