Re: [ntp:questions] Windows time question.
[default pool command uses 10 servers] I agree. It is absurd. It seems to indicate that the ntp folk really really do not trust the pool, and figure that if you get fewer than 10, you have a reasonable chance that a majority will deliver bad time. Ie, they appear to feel that the pool is a pretty useless souce of time. I don't think it's a matter of not-trust. I think it's just using some old code/parameters because the pool code hasn't been working long enough for things like that to get fixed or documented. -- These are my opinions, not necessarily my employer's. I hate spam. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP Issue on Linux Machine
On 2011-04-26, David Woolley wrote: Bogus confidentiality notice Probably added by the outgoing mail-server. but no content. The OP is attempting to forward his original message to the mailing list (i.e. sending the body of his message as an attachment). But the list does not allow attachements I suspect you have a broken email client that sends HTML but no plain text and the HTML is being stripped by the mailing list No. See above. and the mailing list to USENET gateway. No. The attachment is stripped _before_ the message is sent to the gateway. Using confidentiality notices on public mailing lists signals an incompetent organisation. These disclaimers are frequently required by corporate policy on all outgoing mail. Complaining here won't change anything. Yousif Qaddoura wrote: [---=| TOFU protection by t-prot: 14 lines snipped |=---] Top posting ... -- Steve Kostecke koste...@ntp.org NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] NTP/Linux Machine Issue
Dear Support, I have a NTP server, and configure clients on it. I am facing an issue that the offset is too much high so there a difference in the time between the client and the server, it is reaching 1 hour sometimes. NTP client version: ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT 2006 (1) client machine : linux redhat 4.6 [root@dmtestapp1 ~]# ntpq -p remote refid st t when poll reach delay offset jitter == 10.200.37.3785.91.1.180 3 u 35 64 170.898 1194.28 147604. *LOCAL(0)LOCAL(0)10 l 32 64 170.0000.000 0.004 Hope you can help me in that Yousif Qaddoura 00971507272492 DISCLAIMER: The information contained in this e-mail is intended solely for the use of the individual or entity to whom it is addressed. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, use, copying, distribution or taking any action in reliance on the contents of this e-mail is strictly prohibited. If you have received this communication in error, please notify us / the sender immediately by responding to this email and then delete it. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore Daman and / or the sender is neither liable for the proper and complete transmission of the information contained in this e-mail nor for any delay in its receipt or any errors or omissions or any virus transmitted. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
Dear Support, This is a newsgroup, there is no support as such. I have a NTP server, and configure clients on it. I am facing an issue that the offset is too much high so there a difference in the time between the client and the server, it is reaching 1 hour sometimes. NTP client version: ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT 2006 (1) Your client software is five years out of date, I suggest you update it. remote refid st t when poll reach delay offset jitter == 10.200.37.3785.91.1.180 3 u 35 64 170.898 1194.28 147604. *LOCAL(0)LOCAL(0)10 l 32 64 170.0000.000 0.004 Hope you can help me in that Yousif Qaddoura In your ntd.conf, remove the local clock, and add in three pool server lines such as: server 0.pool.ntp.org iburst server 1.pool.ntp.org iburst server 2.pool.ntp.org iburst If your alder NTP complains about the iburst, remove it. Be sure that your PC is fairly near correct time in the BIOS, and that the time zone is correct. Retry NTP. Please note that I run FreeBSD and Windows, not Linux, so the above advice may not be correct in its detail. Good luck, David ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
On 2011-04-26, Yousif Qaddoura yousif.qaddo...@damanhealth.ae wrote: client machine : linux redhat 4.6 [root@dmtestapp1 ~]# ntpq -p remote refid st t when poll reach delay offset jitter 10.200.37.37 85.91.1.1803 u 35 64 17 0.898 1194.28 147604. Is 'dmtestapp1' a Virtual Machine (VM)? *LOCAL(0)LOCAL(0) 10 l 32 64 17 0.000 0.000 0.004 The Undisciplined Local Clock (127.127.1.x) is not a backup for systems which do not serve time to others. -- Steve Kostecke koste...@ntp.org NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
On 2011-04-26, Yousif Qaddoura yousif.qaddo...@damanhealth.ae wrote: Dear Support, I have a NTP server, and configure clients on it. I am facing an issue that the offset is too much high so there a difference in the time between the client and the server, it is reaching 1 hour sometimes. NTP client version: ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT 2006 (1) client machine : linux redhat 4.6 [root@dmtestapp1 ~]# ntpq -p remote refid st t when poll reach delay offset jitter == 10.200.37.3785.91.1.180 3 u 35 64 170.898 1194.28 147604. *LOCAL(0)LOCAL(0)10 l 32 64 170.0000.000 0.004 And you have that LOCAL refclock why? Get rid of it. It is a silly idea. Your system has decided that the local time is better than your server time. Since local is the clock itself, your system will always discover that the error is 0. (How it gets a jitter of .004 from the local clock I have no idea) Hope you can help me in that Yousif Qaddoura 00971507272492 DISCLAIMER: The information contained in this e-mail is intended solely for the use of the individual or entity to whom it is addressed. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, use, copying, distribution or taking any action in reliance on the contents of this e-mail is strictly prohibited. If you have received this communication in error, please notify us / the sender immediately by responding to this email and then delete it. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore Daman and / or the sender is neither liable for the proper and complete transmission of the information contained in this e-mail nor for any delay in its receipt or any errors or omissions or any virus transmitted. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
David wrote: Dear Support, This is a newsgroup, there is no support as such. I have a NTP server, and configure clients on it. I am facing an issue that the offset is too much high so there a difference in the time between the client and the server, it is reaching 1 hour sometimes. NTP client version: ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT 2006 (1) Your client software is five years out of date, I suggest you update it. That date seems to be the *build* date - 4.2.0 was reeased in October of '03, so it's really 8 years old. Since 4.2.0 was release we have produced 3 full releases, 2.2, 2.4, and 2.6. I am expecting 2.8 to be released this summer. remote refid st t when poll reach delay offset jitter === === 10.200.37.3785.91.1.180 3 u 35 64 170.898 1194.28 147604. *LOCAL(0)LOCAL(0)10 l 32 64 170.0000.000 0.004 Hope you can help me in that Yousif Qaddoura In your ntd.conf, remove the local clock, and add in three pool server lines such as: server 0.pool.ntp.org iburst server 1.pool.ntp.org iburst server 2.pool.ntp.org iburst If your alder NTP complains about the iburst, remove it. Be sure that your PC is fairly near correct time in the BIOS, and that the time zone is correct. Retry NTP. Please note that I run FreeBSD and Windows, not Linux, so the above advice may not be correct in its detail. What you wrote looks good to me. H ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote: Attribution Missing wrote: ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT 2006 (1) Your client software is five years out of date, I suggest you update it. Red Herring. remote refid st t when poll reach delay offset jitter = 10.200.37.37 85.91.1.180 3 u 35 64 17 0.898 1194.28 147604. *LOCAL(0) LOCAL(0) 10 l 32 64 17 0.000 0.000 0.004 The problem here is that the client system is running in a VM. In your ntd.conf, remove the local clock, and add in three pool server lines such as: server 0.pool.ntp.org iburst server 1.pool.ntp.org iburst server 2.pool.ntp.org iburst The OP wants to sync this client to his local time server (10.200.37.37). -- Steve Kostecke koste...@ntp.org NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
On Tue, Apr 26, 2011 at 1:32 PM, Steve Kostecke koste...@ntp.org wrote: On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote: Attribution Missing wrote: ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT 2006 (1) Your client software is five years out of date, I suggest you update it. Red Herring. Yes and no. Not many people can help fix problem with software that is this old. Hard to remember what worked and what did not that many years ago. But of course NTP worked back then and should continue to work forever In your ntd.conf, remove the local clock, and add in three pool server lines such as: server 0.pool.ntp.org iburst server 1.pool.ntp.org iburst server 2.pool.ntp.org iburst The OP wants to sync this client to his local time server (10.200.37.37). Yes this is true. We are looking at a client machine here. The OP, we must assume has an NTP server running at 10.200.37.37 that is using pool servers or some others 1) Do get rid of the LOCAL ref clock. It is usless on a client 2) I think the start up script the starts ntpd should use the -g command switch 3) I think you need more than one server line. What if 10.200.37.37 needs to be taken off-line. I'd set up at least two ntp servers and configure al clients to use both 4) do get the new software. It has features you need for your servers, orphan mode and so on. If this is running inside a VM, then don't expect good time keeping. I think VMs can be configure to get the time of day from their host OS. -- = Chris Albertson Redondo Beach, California ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
Steve Kostecke wrote: The problem here is that the client system is running in a VM. That's most likely, however the inappropriate use of the local clock driver isn't helping, by making it virtually impossible for it even to get by with infrequent time steps. Without that, either ntpd would be stepping, or it would have aborted long before the offset reached an hour. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
On 2011-04-26, Steve Kostecke koste...@ntp.org wrote: On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote: Attribution Missing wrote: ntpq 4.2.0a@1.1190-rmailto:4.2.0a@1.1190-r Thu Oct 5 04:11:36 EDT 2006 (1) Your client software is five years out of date, I suggest you update it. Red Herring. remote refid st t when poll reach delay offset jitter = 10.200.37.37 85.91.1.180 3 u 35 64 17 0.898 1194.28 147604. *LOCAL(0) LOCAL(0) 10 l 32 64 17 0.000 0.000 0.004 The problem here is that the client system is running in a VM. Do you know that? I must admit that the jitter makes that highly probable, but I donot believe he ever said that. The other problem is that he has the local server. In your ntd.conf, remove the local clock, and add in three pool server lines such as: server 0.pool.ntp.org iburst server 1.pool.ntp.org iburst server 2.pool.ntp.org iburst The OP wants to sync this client to his local time server (10.200.37.37). Apparently correct. But again we do not know that. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
On Tue, Apr 26, 2011 at 3:01 PM, David Woolley david@ex.djwhome.demon.invalid wrote: Steve Kostecke wrote: The problem here is that the client system is running in a VM. That's most likely, however the inappropriate use of the local clock driver isn't helping, Just wondering how you figured it must be a VM? -- = Chris Albertson Redondo Beach, California ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
Hi Steve, Yes it is virtual machine, the host is linux also with vmware server installed. Kinldy note that the host machine's time is correct and it is synchronizing with my NTP 10.200.37.37 thanks yousif From: questions-bounces+yousif.qaddoura=damanhealth...@lists.ntp.org [questions-bounces+yousif.qaddoura=damanhealth...@lists.ntp.org] On Behalf Of Steve Kostecke [koste...@ntp.org] Sent: Tuesday, April 26, 2011 6:56 PM To: questions@lists.ntp.org Subject: Re: [ntp:questions] NTP/Linux Machine Issue On 2011-04-26, Yousif Qaddoura yousif.qaddo...@damanhealth.ae wrote: client machine : linux redhat 4.6 [root@dmtestapp1 ~]# ntpq -p remote refid st t when poll reach delay offset jitter 10.200.37.37 85.91.1.1803 u 35 64 17 0.898 1194.28 147604. Is 'dmtestapp1' a Virtual Machine (VM)? *LOCAL(0)LOCAL(0) 10 l 32 64 17 0.000 0.000 0.004 The Undisciplined Local Clock (127.127.1.x) is not a backup for systems which do not serve time to others. -- Steve Kostecke koste...@ntp.org NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions DISCLAIMER: The information contained in this e-mail is intended solely for the use of the individual or entity to whom it is addressed. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, use, copying, distribution or taking any action in reliance on the contents of this e-mail is strictly prohibited. If you have received this communication in error, please notify us / the sender immediately by responding to this email and then delete it. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore Daman and / or the sender is neither liable for the proper and complete transmission of the information contained in this e-mail nor for any delay in its receipt or any errors or omissions or any virus transmitted. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP Daemon Stuck in Resolver Jail When Run from Connman
On 4/26/11 9:44 AM, Marcel Holtmann wrote:
I've been experimenting recently, in version 0.71, with connman's ability
to
launch the NTP daemon in one-shot mode when the service state transitions
to
online mode.
However, what I notice in practice is that when the time server is any
named
entity (e.g. time.ubuntu.org or pool.ntp.org), the NTP daemon fails to
resolve the name, ntpd_intres gets forked and launched and then
indefinitely
fails to resolve the name.
If I rework the plugin to delay NTP start up and then periodically retry
several times over time, I see the same results: NTP never successfully
resolves the name.
If I run tcpdump while connman is starting up and bringing up the service,
I
see requests going out for wpad.mydomain to the name server; however, I
never see a resolve request going out on the wire for the time server,
ever.
If I manually run the NTP daemon in one-shot mode, the name resolves
immediately and time is updated. If I run nslookup on the time server while
all these retries and failures are occurring from the instance dispatched
in
connman, the name resolves successfully.
So what I am thinking is that we might have a small race condition here
where the built-in DNS proxy is not yet ready to answer DNS queries
properly. Can you try to run connmand with --nodnsproxy and see if this
changes at all.
We could still have the problem that we do not write /etc/resolv.conf early
enough.
I thought the same thing initially, hence the experiment to introduce a
delay (I tried up to 30 seconds) in starting the NTP daemon once the sync
method is invoked. No matter the length, the delay made no difference.
My default /etc/resolv.conf is the same that connman writes out anyway, so
the only hole that might get hit is truncate before the new file gets
written (see below regarding res_int why this shouldn't matter though).
Other experiments I tried with no success:
[ ... experiments omitted ... ]
In all seven cases, running the NTP daemon in one-shot mode indefinitely
fails to resolve a name. In all seven cases, running the daemon outside of
connman or running nslookup on the name succeeds immediately.
Looking at the ntpd_intres code, it repeatedly calls res_init(), so if there
were a race or some such, I would expect it'd eventually recover on one of
it's subsequent retry attempts.
maybe you are hitting a GLibc bug. The res_init() with a
static /etc/resolv.conf should just work fine.
Any suggestions on other experiments to run would be welcomed.
At this point, my next step may be to try calling the connman
g_resolve_lookup_hostname while building the temporary configuration peer
list.
Try to have ConnMan resolve the name before calling the ntpd one-shot
command line and give the IP address to that one. I am curious if that
would work.
Marcel,
As suggested above, if I set up a new gresolv instance and call
g_resolv_lookup_hostname from ntpdate_add_peer, it works consistently (see
output below). Would you like a patch for this?
# /etc/init.d/connman stop
# ip addr flush dev wlan0
# ip link set wlan0 down
# ip link set wlan0 up
# ./connmand -n -W wext tail -f /var/log/messages | grep -i ntp
connmand[274]: Connection Manager version 0.71
connmand[274]: Checking loopback interface settings
connmand[274]: System hostname is fish
connmand[274]: System domainname is domain.actdsltmp
connmand[274]: Adding profile default
connmand[274]: Failed to open RFKILL control device
connmand[274]: lo {newlink} index 1 operstate 0 UNKNOWN
connmand[274]: wlan0 {create} index 2 type 1 ETHER
connmand[274]: wlan0 {RX} 104 packets 14594 bytes
connmand[274]: wlan0 {TX} 29 packets 6122 bytes
connmand[274]: wlan0 {update} flags 4099 UP
connmand[274]: wlan0 {newlink} index 2 address 00:0c:29:4c:56:a2 mtu 1500
connmand[274]: wlan0 {newlink} index 2 operstate 2 DOWN
connmand[274]: Create interface wlan0 [ wifi ]
connmand[274]: mmap error Invalid argument for
/var/lib/connman/stats/wifi_000c294c56a2_54616e6b_managed_psk.data
connmand[274]:
/var/lib/connman/stats/wifi_000c294c56a2_54616e6b_managed_psk.data might be
on a file system, such as JFFS2, that does not allow shared writable
mappings.
connmand[274]: wlan0 up
connmand[274]: wlan0 lower down
connmand[274]: wlan0 up
connmand[274]: wlan0 lower down
connmand[274]: Skipping disconnect of 54616e6b_managed_psk
connmand[274]: wlan0 {add} route ff00:: gw :: scope 0 UNIVERSE
connmand[274]: wlan0 {add} route fe80:: gw :: scope 0 UNIVERSE
connmand[274]: wlan0 {update} flags 69635 UP,LOWER_UP
connmand[274]: wlan0 {newlink} index 2 address 00:0c:29:4c:56:a2 mtu 1500
connmand[274]: wlan0 {RX} 104 packets 14594 bytes
connmand[274]: wlan0 {TX} 29 packets 6122 bytes
connmand[274]: wlan0 {newlink} index 2 address 00:0c:29:4c:56:a2 mtu 1500
connmand[274]: wlan0 {newlink} index 2 operstate 5 DORMANT
connmand[274]: wlan0 {RX} 106 packets 14872 bytes
connmand[274]: wlan0 {TX} 32 packets 6460 bytes
Re: [ntp:questions] NTP/Linux Machine Issue
On 2011-04-26, unruh un...@wormhole.physics.ubc.ca wrote: On 2011-04-26, Steve Kostecke koste...@ntp.org wrote: On 2011-04-26, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote: In your ntd.conf, remove the local clock, and add in three pool server lines such as: server 0.pool.ntp.org iburst server 1.pool.ntp.org iburst server 2.pool.ntp.org iburst The OP wants to sync this client to his local time server (10.200.37.37). Apparently correct. But again we do not know that. In 196e27ba08412645b507f7a1ed9bc7e829ffe3a...@mbxsrv2.damanhealth.ae Yousif said: I have a NTP server, and configure clients on it. And then proceeded to discuss the problem he is having with a large offset between his server and client (followed by the ntpq peer status billboard). -- Steve Kostecke koste...@ntp.org NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP Daemon Stuck in Resolver Jail When Run from Connman
On Apr 26, 2011, at 6:18 PM, Marcel Holtmann wrote: I've been experimenting recently, in version 0.71, with connman's ability to launch the NTP daemon in one-shot mode when the service state transitions to online mode. However, what I notice in practice is that when the time server is any named entity (e.g. time.ubuntu.org or pool.ntp.org), the NTP daemon fails to resolve the name, ntpd_intres gets forked and launched and then indefinitely fails to resolve the name. At this point, my next step may be to try calling the connman g_resolve_lookup_hostname while building the temporary configuration peer list. Try to have ConnMan resolve the name before calling the ntpd one-shot command line and give the IP address to that one. I am curious if that would work. As suggested above, if I set up a new gresolv instance and call g_resolv_lookup_hostname from ntpdate_add_peer, it works consistently (see output below). Would you like a patch for this? as a short term solution, I am fine with trying to resolve the IP address before calling ntpd. Just keep in mind that you need to check if the server name might be already an IP address. I didn't bother special casing this as it just worked. The resolver simply returns immediately with the IP address and I add it to the peer file. In case of DHCP it is possible that it hands out IP addresses directly. Confirmed. I tested exactly that case. The only small downside I see is that normally pool.ntp.org is round robin DNS server and hands out more than one address. However since we do one shot only anyway, just picking the first address should be fine. The current implementation takes all the results; however, it should be trivial to modify to just take the first result. That all said, I am still curious what happens with ntpd and name resolving that this causes so many problems. I am as well; however, having spent several days on this I am ready to move on. I've CC'd the NTP questions list on this thread in the event they have some insights or experimental suggestions. Thanks for being a sounding board on this. Best, Grant ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP/Linux Machine Issue
Yousif Qaddoura wrote: Yes it is virtual machine, the host is linux also with vmware server installed. Kinldy note that the host machine's time is correct and it is synchronizing with my NTP 10.200.37.37 Here are some links I've run across in the past related to VMware NTP. You'll likely need to look at the support files for your version of VMware. 13.6. VMware and NTP http://psp2.ntp.org/bin/view/Support/VMWareNTP 9.2.2.1. VMware http://psp2.ntp.org/bin/view/Support/KnownOsIssues#Section_9.2.2.1. Timekeeping best practices for Linux guests (by Distro) http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKCexternalId=1006427 http://www.vmware.com/pdf/vmware_timekeeping.pdf -- E-Mail Sent to this address blackl...@anitech-systems.com will be added to the BlackLists. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
