Ntp Error Log

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super http://superuser.com/questions/181341/how-to-check-if-ntp-adjusted-system-time-on-linux User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site https://www.eecis.udel.edu/~mills/ntp/html/debug.html for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top how to check if NTP adjusted system time on Linux? up vote 14 down vote favorite 3 I have a machine that experienced some troubles with some of the real time ntp offset stuff that I'm running. One lead that I have is that NTP daemon may have moved the time, causing false timeouts. How do I find out if NTP daemon did indeed move time at all? Any logs? I do see NTP daemon restart in /var/log/messages, but I don't know if time adjustment should be there as well. to clarify: I need to understand it from the logs, after the event. May be 2 days after the time was adjusted. Running commands to see the current status doesn't ntp error log help. linux ntp share|improve this question edited Aug 27 '10 at 16:33 asked Aug 27 '10 at 11:35 n-alexander 178227 add a comment| 5 Answers 5 active oldest votes up vote 6 down vote You can use ntpdc -c sysinfo command for querying ntpd status. It returns an output similar to this: system peer: 0.0.0.0 system peer mode: unspec leap indicator: 11 stratum: 16 precision: -20 root distance: 0.00000 s root dispersion: 338.44917 s reference ID: [73.78.73.84] reference time: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000 system flags: auth monitor ntp kernel stats jitter: 0.000000 s stability: 0.000 ppm broadcastdelay: 0.003998 s authdelay: 0.000000 s share|improve this answer answered Aug 27 '10 at 11:50 Janne Pikkarainen 5,2491626 add a comment| up vote 3 down vote you should have a value in the drift file. Its location will be in your /etc/ntp.conf e.g: "driftfile /var/lib/ntp/drift" this file is used to log how far your clock is from what it should be, and slowly ntp should lower this value as time progresses. - It wont do it in one go because that could cause timestamping issues on the system. share|improve this answer answered Aug 27 '10 at 11:44 Sirex 8,65522948 this is good info, thanks. Still, after time has been moved, this will be 0 and I will have lost my information. Doesn't ntp log any messages to tell me it's done it at all? –n-alexander Aug 27 '10 at 14:47 add a comment| up vote 3 down vote ntpq -nc peers will show you your syncronization status with

- standard NTP query program, either on the local server or from a remote machine. In special circumstances the ntpdc - special NTP query program, can be useful, but its use is not covered here. The ntpq program implements the management functions specified in the NTP specification RFC-1305, Appendix A. It is used to read and write the variables defined in the NTP Version 4 specification now navigating the standards process. In addition, the program can be used to send remote configuration commands to the server. The ntpd daemon can operate in two modes, depending on the presence of the -d command-line option. Without the option the daemon detaches from the controlling terminal and proceeds autonomously. With one or more -d options the daemon does not detach and generates special trace output useful for debugging. In general, interpretation of this output requires reference to the sources. However, a single -d does produce only mildly cryptic output and can be very useful in finding problems with configuration and network troubles. Some problems are immediately apparent when the daemon first starts running. The most common of these are the lack of a UDP port for NTP (123) in the Unix /etc/services file (or equivalent in some systems). Note that NTP does not use TCP in any form. Also note that NTP requires port 123 for both source and destination ports. These facts should be pointed out to firewall administrators. Other problems are apparent in the system log, which ordinarily shows the startup banner, some cryptic initialization data and the computed precision value. Event messages at startup and during regular operation are sent to the optional protostats monitor file, as described on the Event Messages and Status Words page. These and other error messages are sent to the system log, as described on the ntpd System Log Messages page. In real emergencies the daemon will sent a terminal error message to the system log and then cease operation. The next most common problem is incorrect DNS names. Check that each DNS name used in the configuration file exists and that the address responds to the Unix ping command. The Unix traceroute or Windows tracert utility can b