Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A server operating at stratum 1 belongs to the class of best NTP servers available, because it has a reference clock attached to it. As accurate reference clocks are expensive, only rather few of these servers are publically available.
A stratum 1 server should not only have a precise and well-maintained and calibrated reference clock, but also should be highly available as other systems may rely on its time service. Maybe that's the reason why not every NTP server with a reference clock is publically available.
Thanks abhijeet,
But why it is showing differently (stratum 1 and stratum 2) ? (Pls see my previous post, where I have shown all data)
Last edited by vikas027; 09-10-2009 at 04:41 AM.
Reason: Added one line for more visiblity
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Glad to know you got it going -- one last thing, though...
See if you can find the actual start-up, shut-down script in the initialization directories in /etc. It may be located in /etc/rc.d, /etc/rcn.d, /etc/init.d or some such (it's the file that is executed at boot and shutdown). If you ever need to fiddle with /etc/ntp.conf again, execute that file (as root) with a "stop" or "restart" argument (that will kill the currently running NTP daemon. You may want to edit the logging into that file (/tmp/ntp.log won't get that large and if there's a problem it's a convenient place to look for what's what). Makes life a little easier.
Glad to know you got it going -- one last thing, though...
See if you can find the actual start-up, shut-down script in the initialization directories in /etc. It may be located in /etc/rc.d, /etc/rcn.d, /etc/init.d or some such (it's the file that is executed at boot and shutdown). If you ever need to fiddle with /etc/ntp.conf again, execute that file (as root) with a "stop" or "restart" argument (that will kill the currently running NTP daemon. You may want to edit the logging into that file (/tmp/ntp.log won't get that large and if there's a problem it's a convenient place to look for what's what). Makes life a little easier.
Glad you got it going.
Yes, I am aware about it. I twill manage start/stop with logging.
But why it is showing differently (stratum 1 and stratum 2) ? (Pls see my previous post, where I have shown all data)
I am asking this just for sake of knowledge.
I have same ntp issue on Xenserver
18 Feb 22:05:10 ntpd[16431]: logging to file /tmp/ntp.log
18 Feb 22:05:10 ntpd[16431]: precision = 1.000 usec
18 Feb 22:05:10 ntpd[16431]: ntp_io: estimated max descriptors: 1024, initial so
cket boundary: 16
18 Feb 22:05:10 ntpd[16431]: Listening on interface wildcard, 0.0.0.0#123 Disabl
ed
18 Feb 22:05:10 ntpd[16431]: Listening on interface lo, 127.0.0.1#123 Enabled
18 Feb 22:05:10 ntpd[16431]: Listening on interface xenbr0, 192.168.10.7#123 Ena
bled
18 Feb 22:05:10 ntpd[16431]: Listening on interface xenbr3, 192.168.10.7#123 Ena
bled
18 Feb 22:05:10 ntpd[16431]: kernel time sync status 0040
18 Feb 22:05:10 ntpd[16431]: getaddrinfo: "::1" invalid host address, ignored
18 Feb 22:05:10 ntpd[16431]: frequency initialized 0.000 PPM from /var/lib/ntp/d
rift
This is Xenserver's ntp.conf file looks like
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery
# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
restrict -6 ::1
# Hosts on local network are less restricted.
#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
# Use Xen's public servers.
#broadcast 192.168.1.255 key 42# broadcast server
#broadcastclient# broadcast client
#broadcast 224.0.1.1 key 42# multicast server
#multicastclient 224.0.1.1# multicast client
#manycastserver 239.255.254.254# manycast server
#manycastclient 239.255.254.254 key 42# manycast client
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available.
server127.127.1.0# local clock
fudge127.127.1.0 stratum 10
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
driftfile /var/lib/ntp/drift
# Key file containing the keys and key identifiers used when operating
# with symmetric key cryptography.
keys /etc/ntp/keys
# Specify the key identifiers which are trusted.
#trustedkey 4 8 42
# Specify the key identifier to use with the ntpdc utility.
#requestkey 8
# Specify the key identifier to use with the ntpq utility.
#controlkey 8
# Specify the key identifier to use with the ntpq utility.
#controlkey 8
server 64.90.182.55
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
I do not understand what is the "::1" mean in error log
Can anybody help me? Thank you very much.
I do not know much about your error. But could you please try the below configuration.
Remove your old file and just use these 4 lines in your ntp.conf
Code:
server 64.90.182.55 prefer
restrict 127.0.0.1
driftfile /etc/ntp/drift
broadcastdelay 0.008
Hi vikas027,
After run ntpq -pn 64.90.182.55, i got following result:
ntpq -pn 64.90.182.55
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.1.0 .ACTS. 0 l 17 64 377 0.000 0.000 0.000
Below is my /tmp/ntp.log
Shutting down ntpd: [ OK ]
22 Feb 11:52:48 ntpd[25034]: logging to file /tmp/ntp.log
22 Feb 11:52:48 ntpd[25034]: precision = 1.000 usec
22 Feb 11:52:48 ntpd[25034]: ntp_io: estimated max descriptors: 1024, initial so
cket boundary: 16
22 Feb 11:52:48 ntpd[25034]: Listening on interface wildcard, 0.0.0.0#123 Disabl
ed
22 Feb 11:52:48 ntpd[25034]: Listening on interface lo, 127.0.0.1#123 Enabled
22 Feb 11:52:48 ntpd[25034]: Listening on interface xapi2, 192.168.10.7#123 Enab
led
22 Feb 11:52:48 ntpd[25034]: kernel time sync status 0040
" unknown, line ignored034]: configure: keyword "prefer
I also have this issue posted on Citrix forums at: http://forums.citrix.com/thread.jspa?threadID=258940
From page 2 to the end. It will tell you what i did in the last few days,
My issue is resolved. It was caused by enable "Auto Dos" on my HP Procurve 1810G. When i disable "Auto Dos", ntpd service start without any issue. Thanks for your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.