[ntp:questions] NTPD silently not tracking

unruh unruh at invalid.ca
Sat Aug 31 12:13:07 UTC 2013

On 2013-08-31, E-Mail Sent to this address will be added to the BlackLists <Null at BlackList.Anitech-Systems.invalid> wrote:
> Magnus Danielson wrote:> BlackLists wrote:
>>> What ntpdc commands did you issue, and what results did you get?
>> Unfortunatly no. I got the call after the fact,
>>  but lack of remote login due to time error would prohibit
>>  me from doing anything anyway.
>> The server needed to be operational rather than optimize
>>  for NTP debugging.

I doubt that it needed to operational and badly wrong. Ie, if it is
misbehaving so badly, debugging is only option.

> What ntpdc commands did the other people issue?
> Kinda hard to try and duplicate / troubleshoot with no real info,
>  except its broke.
>>> Have you tried a newer version of NTP ?
>> No, I listed the affected version as packaged by Debian.
> Supposing there is an real issue,
>  perhaps it has already been fixed in a more recent version.

Sorry, but I have always found this to be a complete copout. You can
keep the complainer busy till doomsday trying out different version and
different configs. Do you know that others have had this person's
problem? Do you know thatthe latest version fixes them? Otherwise you
are simply sending him on a fishing expidition. 

ntpd being 6 days out and claiming it is on time is such a HUGE bug,
that others would have reported it and it does not sound like the kind
of bug that would be fixed by accident.

>> It has 2 stratum 1 and 3 stratum 2 unicast servers configured.
>>  NTP wise this machine is a client with 5 configured servers.
>> The problem was that it was way off time with no apparent indication,
>>  which is wrong.
> Don't use Undisciplined Local Clock

I certainly agreee with that suggestion. And it may be his problem,
although I thought that the local clock was dumped to the bottom of the
heap if there are other servers.

>  It can run away all by itself, and there is nothing wrong with that.
>   If that is a issue change to orphan.

I think you mean "If your ssytem always needs to be up and present time
to other computers it serves, use the orphan mode"

> Provide all information necessary to duplicate & troubleshoot the issue?
>  ntp.conf, (obstruficate as necessary);
>   ntpdc commands issued to monitor the server.
> Without those, I don't think anyone can hope to guess if there really is a issue,
>  or even begin to troubleshoot the issue if it does exist.

More information about the questions mailing list