Thanks abhijeet,
But why it is showing differently (stratum 1 and stratum 2) ? (Pls see my previous post, where I have shown all data)

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.

There's a pretty concise explanation of stratum 0, stratum 1 and stratum 2 servers at http://www.endruntechnologies.com/stratum1.htm. There's also a pretty good article at http://en.wikipedia.org/wiki/Network_Time_Protocol; everything worth knowing about NTP.

It looks like the server you're using as a time source is a stratum 1 server (your system, by default, is stratum 2).

I have a similar issue
 

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.

Hi newych,

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

Then run the below commands

Verify, after waiting for around 5 mins by
ntpq -pn and post your output here.

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.

ntp service not syncing properly
 

once again i have same issue..i have try almost everything mention here in this post please help me now how can i solve this issue with your help..


thanks