[ntp:questions] leap second status/action items for Sept 1
Folks, and especially people who know the ntpd code,
We are now nearly halfway through August, and I'm wondering where we
stand on the issue of bogus leap seconds. We had one at the beginning
of this month for unknown reasons - but they seem like they could have
stemmed from an ntpd bug: http://bugzilla.ntp.org/show_bug.cgi?id=2246
("sys_leap is sticky").
Questions in what I think are priority order:
1. How can administrators ensure that they will not experience another
bogus leap second at the end of August? Will proper installation of a
current leap second file suffice?? Closely related to this is: Can
someone who knows or can read the ntpd code, and/or who is clear on the
intent (and hopefully the implementation) of the code, answer this
question from Martin a previous thread:
- from which sources [does ntpd accept] a leap warning under which
conditions: from
a single upstream server (earlier NTP versions) or only from a majority
(current NTP versions), from refclocks, from a leap second file, and *which
priorities come into effect if there are upstream servers *and* one or more
refclocks *and* a leap second file, or another combination of those*.
2. When can the answers to the above questions be clearly documented,
presumably at or near
http://support.ntp.org/bin/view/Support/ConfiguringNTP ?
3. What is the current status of the stratum 1 servers vis-a-vis the
leap-second bits? I don't know a good way to survey the servers to see
what the current status is; at last check in an earlier threads
(sometime this month), a substantial fraction of those servers were
still advertising a (bogus) leap second. Can anyone check and/or
provide a script that can be run to acquire that info?
4. What are the next steps to tracking down the issue(s) leading to the
bogus leap second at the end of July 2012? Is someone who is familiar
with the ntpd code willing/able to address that?
Thanks very much,
--Jeff
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
[ntp:questions] ntp stops running
Hi, The ntp service stops running after I use this command: "ntpd -p /var/run/ntpd.pid" What the problem can be? Thanks, Ali ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] ntp stops running
Ali Nikzad writes: > The ntp service stops running after I use this command: "ntpd -p > /var/run/ntpd.pid" > What the problem can be? Check your syslog output. I suspect you want to use the -g flag for the initial startup, at least. Please see http://support.ntp.org/Support/StartingNTP4 for more information. -- Harlan Stenn http://networktimefoundation.org - be a member! ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] ntp stops running
Thank you. This is the error message : unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING So, can't we use "ntpd -p /var/run/ntpd.pid" with ntpd -g ? even after I do a reboot, without using "ntpd -g" and after applying the pID file, ntp will be stoped. Regards, Ali On Mon, Aug 13, 2012 at 5:06 PM, Harlan Stenn wrote: > Ali Nikzad writes: > > > The ntp service stops running after I use this command: "ntpd -p > > /var/run/ntpd.pid" > > What the problem can be? > > Check your syslog output. > > I suspect you want to use the -g flag for the initial startup, at least. > > Please see http://support.ntp.org/Support/StartingNTP4 for more > information. > > -- > Harlan Stenn > http://networktimefoundation.org - be a member! > ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] NTP and VMware
Hi, I have a cluster which its computers are not connected to Internet. One Linux based and five ESXi based servers which host virtual machines in a vSphere cluster. I need time synchronization between the hosts. Since ESXi supports NTP, I configured the Linux based node to serve as the NTP server and the ESXi nodes as NTP clients. I configured the server's ntp.conf as follows: #192.168.2.10 driftfile /etc/ntp.drift server 127.127.1.0 fudge 127.127.1.0 stratum 10 tos cohort 1 orphan 11 restrict source nomodify restrict 192.168.2.0 mask 255.255.255.0 nomodify notrap and the clients' ntp.conf file: #192.168.2.X driftfile /etc/ntp.drift server 192.168.2.10 tos cohort 1 orphan 11 restrict source nomodify restrict default kod nomodify notrap nopeer restrict 127.0.0.1 The problem is clients do not synchronize their times with the server. What can be the cause of the problem? Thank you, Ali ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP and VMware
Hi Ali, when you state ' do not synchronize their times with the server', what do you mean? if you run 'ntpq -p' on the client side, you should see something like this remote refid st t when poll reach delay offset jitter == SHM(3) .XPPS. 0 l-800.0000.000 0.000 SHM(2) .XZDA. 0 l-800.0000.000 0.000 +172.23.21.221 .PPSE. 1 u78 3770.2601.631 0.532 *172.23.21.9 .GPS.1 u88 3770.4431.386 0.448 172.23.21.244 .STEP. 16 u 4d800.0000.000 0.000 TD-GITCENTRAL 172.23.21.9 2 u48 3770.1630.196 1.284 172.23.21.243 .PPSI. 1 u78 3770.1981.976 0.864 The important part here (for now) is the reach to the server. if 377, you have a good connection between the client and the server. Once connection is proven, we can deal with the clock selection process. regards -Original Message- From: questions-bounces+p.kennedy=fugro.com...@lists.ntp.org [mailto:questions-bounces+p.kennedy=fugro.com...@lists.ntp.org] On Behalf Of Ali Nikzad Sent: Tuesday, 14 August 2012 12:35 PM To: questions@lists.ntp.org Subject: [ntp:questions] NTP and VMware Hi, I have a cluster which its computers are not connected to Internet. One Linux based and five ESXi based servers which host virtual machines in a vSphere cluster. I need time synchronization between the hosts. Since ESXi supports NTP, I configured the Linux based node to serve as the NTP server and the ESXi nodes as NTP clients. I configured the server's ntp.conf as follows: #192.168.2.10 driftfile /etc/ntp.drift server 127.127.1.0 fudge 127.127.1.0 stratum 10 tos cohort 1 orphan 11 restrict source nomodify restrict 192.168.2.0 mask 255.255.255.0 nomodify notrap and the clients' ntp.conf file: #192.168.2.X driftfile /etc/ntp.drift server 192.168.2.10 tos cohort 1 orphan 11 restrict source nomodify restrict default kod nomodify notrap nopeer restrict 127.0.0.1 The problem is clients do not synchronize their times with the server. What can be the cause of the problem? Thank you, Ali ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
