[LDM #RAN-400269]: intermittent ldmadmin check error

David,

It's likely that one or more of the time servers the "ldmadmin check" command 
is using is incorrect. The servers are set in the registry parameter 
"/check-time/ntpdate/servers". You should have some good time servers at GSFC. 
Try using them instead.

Alternatively, you can disable time-checking by setting the registry parameter 
"/check-time/enabled" to 0. I don't recommend this, however.

> I am getting an intermittent emails from cron ldmadmin check about system 
> clock is more than 10 seconds off.  I ran 4 tests on the command line it will 
> occur randomly.  Also running ntpdate from the command line shows time is not 
> off by 10 seconds.  Thanks for any insight you can give me about this.
> 
> Dave
> 
> 
> nexingest:~>date ; bash -l -c 'ldmadmin check'
> Wed Sep 13 22:03:03 EDT 2017
> Checking for a running LDM system...
> Checking the system clock...
> Checking the most-recent insertion into the queue...
> Vetting the size of the queue against the maximum acceptable latency...
> 
> nexingest:~>date ; bash -l -c 'ldmadmin check'
> Wed Sep 13 22:03:32 EDT 2017
> 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).
> 
> nexingest:~>date ; bash -l -c 'ldmadmin check'
> Wed Sep 13 22:03:35 EDT 2017
> 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).
> 
> nexingest:~>date ; bash -l -c 'ldmadmin check'
> Wed Sep 13 22:03:38 EDT 2017
> Checking for a running LDM system...
> Checking the system clock...
> Checking the most-recent insertion into the queue...
> Vetting the size of the queue against the maximum acceptable latency...
> 
> [ldm@nexingest ldm]# /usr/sbin/ntpdate timehost.gsfc.nasa.gov
> 13 Sep 22:04:44 ntpdate[9248]: adjust time server 128.183.244.196 offset 
> -0.000009 sec
> [ldm@nexingest ldm]# /usr/sbin/ntpdate timehost.gsfc.nasa.gov
> 13 Sep 22:05:44 ntpdate[9601]: adjust time server 128.183.244.196 offset 
> -0.000001 sec
> [ldm@nexingest ldm]# /usr/sbin/ntpdate timehost.gsfc.nasa.gov
> 13 Sep 22:13:18 ntpdate[10094]: adjust time server 128.183.244.196 offset 
> 0.000011 sec

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RAN-400269
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.