[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #XQC-361661]: LDM Question

Hi Bob,

> Thanks for your suggestions. Per your instructions. I made the following
> changes:
> 
> (ldm.ipa.unca.edu /ldm-home > diff etc/registry.xml.INSTALL etc/registry.xml
> 12c12
> <       <command>ntpdate</command>
> ---
> >       <command>chronyd -Q 'pool pool.ntp.org iburst'</command>

Good.

> and:
> 
> (ldm.ipa.unca.edu /ldm-home > diff bin/ldmadmin.INSTALL bin/ldmadmin
> 1694c1694
> < if (/offset\s+([+-]?\d*\.\d*)/) {
> ---
> > if (/ [+-]?(\d*\.\d*) sec/) {

Good.

> When I ran the "ldmadmin checktime" command, the output is below.
> Not quite what I expected.
> 
> Here's the settings for NTP servers in the registry output:
> 
> (ldm.ipa.unca.edu /ldm-home > regutil |grep ntp
> /check-time/ntpdate/command : chronyd -Q 'pool pool.ntp.org iburst'
> /check-time/ntpdate/servers : ntp.ucsd.edu ntp1.cs.wisc.edu ntppub.tamu.edu
> otc1.psu.edu pool.ntp.org
> /check-time/ntpdate/timeout : 5

With the change to the "/check-time/ntpdate/command" parameter, the other 
parameters should have not effect.

> When I run the chronyd command both as LDM and as root, I get essentially
> the same output -- I thought it might be a permissions problem:
> 
> [root@ldm ~]# chronyd -Q 'pool pool.ntp.org iburst'
> 2021-09-29T19:16:37Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK
> +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)
> 2021-09-29T19:16:37Z Disabled control of system clock
> 2021-09-29T19:16:43Z System clock wrong by -0.000662 seconds (ignored)
> 2021-09-29T19:16:43Z chronyd exiting
> [root@ldm ~]#

Your clock is off by 662 us. Not bad. Clock offsets that small won't have a 
significant effect on the LDM.

> (ldm.ipa.unca.edu /ldm-home/bin > chronyd -Q 'pool pool.ntp.org iburst'
> 2021-09-29T19:16:57Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK
> +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)
> 2021-09-29T19:16:57Z Disabled control of system clock
> 2021-09-29T19:17:02Z System clock wrong by -0.000797 seconds (ignored)
> 2021-09-29T19:17:02Z chronyd exiting
> 
> The RedHat KB article suggested stopping the chronyd service, running
> chronyd -Q, and restarting the chronyd service. I tried that, and still
> don't see a difference:

In what were you expecting a difference? Output from the "ldmadmin checktime" 
command?

> [root@ldm ~]# systemctl stop chronyd.service ; chronyd -Q 'pool pool.ntp.org
> iburst' ; systemctl start chronyd.service
> 2021-09-29T19:28:28Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK
> +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)
> 2021-09-29T19:28:28Z Disabled control of system clock
> 2021-09-29T19:28:33Z System clock wrong by -0.002917 seconds (ignored)
> 2021-09-29T19:28:33Z chronyd exiting
> 
> -- Bob
> 
> (ldm.ipa.unca.edu /ldm-home/bin > ldmadmin checktime
> Checking accuracy of system clock ...
> Couldn't get time from time-server at ntppub.tamu.edu using the ntpdate(1)
> utility, "chronyd -Q 'pool pool.ntp.org iburst'".  If the utility is
> valid and this happens often, then remove ntppub.tamu.edu from registry
> parameter "/check-time/ntpdate/servers".

My mistake. I forgot to have you make one more edit to ldmadmin(1). Do this
    1. Edit the file "~/bin/ldmadmin" again
    2. In the same function as before, change the sequence "$ntpdate -q -t 
$ntpdate_timeout $timeServer" to just "$ntpdate"
    3. Test with "ldmadmin checktime"

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: XQC-361661
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.