This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Paul, > We are getting this error mailed to us. As far as I know we are on the > correct time with all the time clocks (within a few milliseconds). > ldmadmin checktime says OK > > Do you know why we would suddenly get these messages? The "ldmadmin check" command checks the system clock against a pseudo-randomly chosen NTP host from those listed in the "/check-time/ntpdate/servers" registry parameter (regutil /check-time). So, either your system clock is off or one of the NTP hosts is off. > Thanks > > Paul > > > __________________________________ > Checking for a running LDM system... > Checking the system clock... > > The system clock is more than 10 seconds off, which is specified by > registry parameter "/check-time/limit". > > You should either fix the problem (recommended) or disable time-checking > by executing the command "regutil -u 0 /check-time/enabled" (not > recommended). Regards, Steve Emmerson Ticket Details =================== Ticket ID: HET-831881 Department: Support LDM Priority: Normal Status: Closed