Mailinglist Archive: opensuse-autoinstall (57 mails)
| < Previous | Next > |
Re: [opensuse-autoinstall] SLES 9 and SLES 10 autoyast NTP client configuration bug?
- From: Lars Stavholm <stava@xxxxxxxxxxx>
- Date: Thu, 29 Mar 2007 12:27:35 +0200
- Message-id: <460B9497.6010705@xxxxxxxxxxx>
Anton Altaparmakov wrote:
> Hi,
>
> Both on SLES 9 and SLES 10 when you configure the NTP client via the
> autoyast profile, when the system is installed the config file
> /etc/ntp.conf is lacking the line:
>
> driftfile /var/lib/ntp/drift/ntp.drift
>
> Which means that every time the machine is rebooted NTP has to establish
> the drift from scratch which means the time oscillates randomly for
> about 15 minutes after booting up. This in turn causes problems with
> time sensitive applications and in particular our web authentication
> servers have a problem as suddenly things start appearing to be in the
> future which is treated as an error...
>
> The autoyast snippet we use to do the ntp client config is (I have
> obfuscated the ip addresses of the NTP servers):
>
> <quote>
> <ntp-client>
> <peers config:type="list">
> <peer>
> <initial config:type="boolean">false</initial>
> <key>server</key>
> <value>blah0.blah.blah</value>
> </peer>
> <peer>
> <initial config:type="boolean">false</initial>
> <key>server</key>
> <value>blah1.blah.blah</value>
> </peer>
> <peer>
> <initial config:type="boolean">false</initial>
> <key>server</key>
> <value>blah2.blah.blah</value>
> </peer>
> </peers>
> <start_at_boot config:type="boolean">true</start_at_boot>
> </ntp-client>
> </quote>
>
> This results in this ntp config file:
>
> <quote>
> server blah0.blah.blah
> server blah1.blah.blah
> server blah2.blah.blah
> # alternate log file
> # logconfig =syncstatus + sysevents
> # logconfig =all
>
> # statsdir /tmp/ # directory for statistics files
> # filegen peerstats file peerstats type day enable
> # filegen loopstats file loopstats type day enable
> # filegen clockstats file clockstats type day enable
>
> #
> # Authentication stuff
> #
> # keys /etc/ntp.keys # path for keys file
> # trustedkey 1 2 3 4 5 6 14 15 # define trusted keys
> # requestkey 15 # key (7) for accessing server variables
> # controlkey 15 # key (6) for accessing server variables
> </quote>
>
> Is this a bug or are we missing some magic line(s) in the autoyast
> profile to cause a drift file to be added so our web authentication
> servers stop being confused when they are rebooted? The autoyast
> documentation does not seem to suggest that there is a way to configure
> a drift file in the autoyast profile so I think this is a bug with
> autoyast...
No idea if it's a bug or not, but we have the following added
to our autoyast.xml (on SuSE Linux 10.2, i.e. !SLES):
[snip]
<peer>
<address>/var/lib/ntp/drift/ntp.drift</address>
<comment></comment>
<initial_sync config:type="boolean">false</initial_sync>
<options></options>
<type>driftfile</type>
</peer>
[snip]
Cheers
/Lars
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
> Hi,
>
> Both on SLES 9 and SLES 10 when you configure the NTP client via the
> autoyast profile, when the system is installed the config file
> /etc/ntp.conf is lacking the line:
>
> driftfile /var/lib/ntp/drift/ntp.drift
>
> Which means that every time the machine is rebooted NTP has to establish
> the drift from scratch which means the time oscillates randomly for
> about 15 minutes after booting up. This in turn causes problems with
> time sensitive applications and in particular our web authentication
> servers have a problem as suddenly things start appearing to be in the
> future which is treated as an error...
>
> The autoyast snippet we use to do the ntp client config is (I have
> obfuscated the ip addresses of the NTP servers):
>
> <quote>
> <ntp-client>
> <peers config:type="list">
> <peer>
> <initial config:type="boolean">false</initial>
> <key>server</key>
> <value>blah0.blah.blah</value>
> </peer>
> <peer>
> <initial config:type="boolean">false</initial>
> <key>server</key>
> <value>blah1.blah.blah</value>
> </peer>
> <peer>
> <initial config:type="boolean">false</initial>
> <key>server</key>
> <value>blah2.blah.blah</value>
> </peer>
> </peers>
> <start_at_boot config:type="boolean">true</start_at_boot>
> </ntp-client>
> </quote>
>
> This results in this ntp config file:
>
> <quote>
> server blah0.blah.blah
> server blah1.blah.blah
> server blah2.blah.blah
> # alternate log file
> # logconfig =syncstatus + sysevents
> # logconfig =all
>
> # statsdir /tmp/ # directory for statistics files
> # filegen peerstats file peerstats type day enable
> # filegen loopstats file loopstats type day enable
> # filegen clockstats file clockstats type day enable
>
> #
> # Authentication stuff
> #
> # keys /etc/ntp.keys # path for keys file
> # trustedkey 1 2 3 4 5 6 14 15 # define trusted keys
> # requestkey 15 # key (7) for accessing server variables
> # controlkey 15 # key (6) for accessing server variables
> </quote>
>
> Is this a bug or are we missing some magic line(s) in the autoyast
> profile to cause a drift file to be added so our web authentication
> servers stop being confused when they are rebooted? The autoyast
> documentation does not seem to suggest that there is a way to configure
> a drift file in the autoyast profile so I think this is a bug with
> autoyast...
No idea if it's a bug or not, but we have the following added
to our autoyast.xml (on SuSE Linux 10.2, i.e. !SLES):
[snip]
<peer>
<address>/var/lib/ntp/drift/ntp.drift</address>
<comment></comment>
<initial_sync config:type="boolean">false</initial_sync>
<options></options>
<type>driftfile</type>
</peer>
[snip]
Cheers
/Lars
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
| < Previous | Next > |