Please fix the clock skew of unstable10x

[Dagobert Michelsen]

Hi Yusuke,

Am 25.12.2019 um 15:51 schrieb Jan Holzhüter <jh at baltic-online.de>:
> 10.0.0.19 is offline. Please use ntp1.baltic-online.de. whatever that resolves to. 

Ah, I remember. This should be fixed now.
@Yusuke: Please check and thanks for letting me know!


Best regards

  — Dago

>> Am 25.12.2019 um 15:40 schrieb Dagobert Michelsen via buildfarm <buildfarm at lists.opencsw.org>:
>> 
>> Hi Yusuke,
>> 
>>> Am 25.12.2019 um 14:57 schrieb Yusuke Endoh <mame at ruby-lang.org>:
>>> Looks like the clock of unstable10x has been behind one hour since 21st.
>>> This skew makes our AWS S3 upload script fail due to "Aws::S3::Errors::RequestTimeTooSkewed" error.
>>> 
>>> Could you confirm the clock please?
>> 
>> I can confirm that it is wrong :-/
>> 
>> unstable10x is connected to ncsw (192.168.1.1) which is connected to 10.0.0.19
>> @Jan, Rolf: have you been working on our NTP server or is this an artifact of the VMWare farm migration?
>> 
>> 
>> Best regards
>> 
>> — Dago
>> 
>> 
>> -- 
>> "You don't become great by trying to be great, you become great by wanting to do something,
>> and then doing it so hard that you become great in the process." - xkcd #896
>> 
> 

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896