On Wed, Jun 14, 2017 at 10:34 AM, Vladimir Zakharov
wrote:
> On Wed, Jun 14, 2017, Alan Somers wrote:
>> On Wed, Jun 14, 2017 at 9:57 AM, Vladimir Zakharov
>>
>> This is by design. Your offset is so large (more than a year), that
>> ntpd fails its basic sanity test. You need to do one of the
>>
On Wed, Jun 14, 2017, Alan Somers wrote:
> On Wed, Jun 14, 2017 at 9:57 AM, Vladimir Zakharov
>
> This is by design. Your offset is so large (more than a year), that
> ntpd fails its basic sanity test. You need to do one of the
> following:
> 1) Manually set the time before starting ntpd for the
On Wed, Jun 14, 2017 at 9:57 AM, Vladimir Zakharov
wrote:
> Hello!
>
> I have ntpd enabled to start during boot. I see, that it starts. But
> querying it after booting fails:
> # ntpq -p
> ntpq: read: Connection refused
>
> After manual start, it works for several seconds and then dies.
> root@vza
Hello!
I have ntpd enabled to start during boot. I see, that it starts. But
querying it after booting fails:
# ntpq -p
ntpq: read: Connection refused
After manual start, it works for several seconds and then dies.
root@vzakharov:~ # service ntpd start
Starting ntpd.
root@vzakharov:~ # ntpq -p
