What do NTP message codes 90000:1 and 90000:96 mean?

book

Article ID: 167224

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

The following are examples of NTP messages in the event log:

2012-04-04 12:13:48+09:00JST "NTP: Periodic query of server ..... Updated system clock."  0 90000:1   ../ntp.cpp:682

2012-04-04 14:13:11+09:00JST "NTP: Periodic query of server..... Updated system clock."  0 90000:96   ../ntp.cpp:682

In messages such as the one above:

  • 9000 is the numeric code for NTP messages
  • 1 and 96 indicate event severity level, where
    • 1 CM_SEVERITY_SEVERE indicates an event with high severity
    • 96 CM_SEVERITY_NORMAL_EVENT indicates an event with normal severity

When might the event log show these message codes?

The event log may show these messages, for example, if the system clock is offset from the NTP server time. In addition, If the offset is large, log shows an event with severity code 1:

2012-04-04 12:13:48+09:00JST "NTP: Periodic query of server xx.xx.xx.xx, system clock is 31 seconds 110 ms fast compared to NTP time. Updated system clock."  0 90000:1   ../ntp.cpp:682

If you then acquire the UTC time from the server, the severity code changes to 96:

2012-04-04 14:13:11+09:00JST  "NTP: Periodic query of server xx.xx.xx.xx, system clock is 0 seconds 257 ms fast compared to NTP time. Updated system clock."  0 90000:96   ../ntp.cpp:682