chronyc: 501 not authorised

berndbausch · 02-28-2020, 07:36 PM

Ubuntu 16.04 on an Odroid C1 (ARM-based credit-card-sized server), rebooting after a power failure. I need to update the time, since the computer has no battery-backed clock.

Code:

$ sudo chronyc makestep
501 Not authorised
$ sudo chronyc clients
Hostname                   Client    Peer CmdAuth CmdNorm  CmdBad  LstN  LstC
=========================  ======  ======  ======  ======  ======  ====  ====
501 Not authorised

chronyd is running. I restarted it, but chronyc continues to hate me even though I am root. There is a -d option for debugging, but this version of chronyc doesn't seem to be compiled with debug support.

I managed to update the time with ntpdate, but chrony is much better. If it worked.

What's going on here? Where should I look?

michaelk · 02-28-2020, 09:05 PM

What version of chrony is running. Could it be related to this FAQ?
https://chrony.tuxfamily.org/faq.htm...uthorised_code

Do either of the following commands run successfully?
sudo chronyc tracking

sudo chronyc sources

berndbausch · 02-28-2020, 11:24 PM

Quote:

Originally Posted by michaelk

What version of chrony is running. Could it be related to this FAQ?
https://chrony.tuxfamily.org/faq.htm...uthorised_code

Thanks, michaelk. I saw this FAQ, but it just points out one has to be root to access the Unix Domain Socket chronyd is using. I am root.

Quote:

Do either of the following commands run successfully?
sudo chronyc tracking

sudo chronyc sources

Yes, both. I should have tried sources.
What I really want to make work is makestep, since I need it to update the clock. I do have a manual workaround with ntpdate, it just baffles me where the not authorised comes from.

michaelk · 02-29-2020, 04:44 AM

My understanding is the makestep directive in the chrony.conf should force a time correction when first started.

makestep 0.1 3

Would correct time if the difference was greater then .1 second and within first 3 clock updates.

ondoho · 02-29-2020, 04:44 AM

Is it possible some files became corrupt from the power outage (hard shutdown, I suppose)?

Config files, or the mentioned socket?