Operating System - Linux
1752307 Members
5198 Online
108786 Solutions
New Discussion юеВ

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

 
zauer
Advisor

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

as you can see my ver is 4.1.2
BUPA IS
Respected Contributor

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

Zauer ,
Sorry your second post crossed over while I was constructing my reply and I did not see it until it was finished ,
orphan mode should work on 4.1.2
the drift file value 132.005 is not too bad but I would be inclined to clear it anyway .

mike

Help is out there always!!!!!
zauer
Advisor

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

so basicly if i'll delete the /var/lib/ntp/drift adn restart the ntpd
the ntpd should create the drift file again ?
thanks
BUPA IS
Respected Contributor

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

Zauer,
It will not fix the problem on its own!
If you remove the drift file and NTP will recreate it for you with new values , but to fix the problem you need to do all the other things as well.

The problem, I think, is that your system is flip flopping between being in synch with itself and in synch with the NTP server.
You can see this by monitoring the ntpq -p output which will vary from being in synch with LOCAL to in synch with ntpd1. One of the side effects of this is an incorrect frequency drift value another is the messages you have seen.
The orphan mode in NTP V4 provides a cure for this but the lines
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
have to come out of the ntp.conf file and be replaced with

tos orphan 7

(7 is two more than 5 from your rv output )

The setting of the system clock with ntpdate, followed by the setting of the hardware clock, and emptying the drift file give NTP a clean starting point to work from.

Mike
Help is out there always!!!!!
zauer
Advisor

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

so the changes need to be made are:
fudge 127.127.1.0 stratum 10
tos orphan 7



please tell me if im correct:
the orphan designed to replace the local clock driver if the local clock failed.

the fudge is the priority of the redundancy
if so what is fudge 10 for local clock ?
thanks
zauer
Advisor

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

sorry i meant
is this the new configuration suppose to be like:

#server 127.127.1.0 # local clock
#fudge 127.127.1.0 stratum 10
tos orphan 7
BUPA IS
Respected Contributor

Re: NTP .increase the 128ms treshold to avoid "synchronisation lost" alarm

Zauer ,
Your last post is correct but I would just delete the lines.
Please try all of the updates and suggetions in my 9.24 post and let me know how you get on .

to answer the other two questions.

orphan mode in fact replaces the need to use the local clock driver when you become disconnected from all other reliable time sources.

The fudge command sets the stratum layer for your local clock to 10. Briefly this means that your local time is now considered by NTP be less reliable than time from other sources.
Help is out there always!!!!!