** Changed in: ntp (Ubuntu Hardy)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Server Team (ubuntu-server)
Status: New => Confirmed
** Summary changed:
- ntp is being brought up before network is ready, causing ntp to not resolve
any ip or host names and it app
I suspect that NTP in dynamic mode, together with Proxy DNS
(http://packages.ubuntu.com/gutsy/net/pdnsd) should work.
--
ntp is being brought up before network is ready, causing ntp to not resolve any
ip or host names and it appears ntp does not recover
https://bugs.launchpad.net/bugs/114505
You
The 'dynamic' option didn't work for me.
Appears not to manage lack of DNS.
It is the lack of a valid DNS that causes NTP to fail
And NTP isn't yet designed to cope with DNS changes/missing DNS.
Apparently there has been some discussion of making DNS queries dynamic on one
of the mailing lis
I'm having this problem in gutsy.
But...I've noticed an option to pass to the server entries in ntp.conf that
might work.
>From the ntp documentation it's describe as follows.
dynamic
Allows a server/peer to be configured even if it is not reachable at
configuration time. It is assu
** Changed in: ntp
Status: Unknown => Fix Released
--
ntp is being brought up before network is ready, causing ntp to not resolve any
ip or host names and it appears ntp does not recover
https://bugs.launchpad.net/bugs/114505
You received this bug notification because you are a member of
** Also affects: ntp
Importance: Undecided
Status: New
** Changed in: ntp
Importance: Undecided => Unknown
Bugwatch: None => NTP Bugzilla #51
Status: New => Unknown
--
ntp is being brought up before network is ready, causing ntp to not resolve any
ip or host names and i
I edited the wlan0 section of "/etc/network/interfaces" to add a "pre-
up" line:
iface wlan0 inet dhcp
wpa-psk ...
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA
wpa-ssid ...
pre-up /sbin/ifdown wlan0
That fixed the problem with the wireless not coming up on boot. I think
it's WPA related, bu
ARGH!!!
Just rebooting to test again, and now DHCP isn't starting properly.
I switched the wireless from WEP to WPA, not sure if that's related or
not.
Anyway, "sudo /etc/init.d/networking restart" after booting brings up
DHCP and NTP just fine.
--
ntp is being brought up before network is rea
I'm just finishing a brand new Gutsy install.
I added NTP, moved the hook files:
[EMAIL PROTECTED]:/etc/dhcp3# mv dhclient-enter-hooks.d/*ntp dhclient-exit-
hooks.d
I added "ntp-servers" to the dhclient.conf file (see bug #74164)
Now NTP starts as expected when the system boots. I haven't tried
Guys and Gals,
I updated to Gutsy today, and got the very same issue with ntpd.
WHY does ntpd need to rely on dhcp broadcasts or whatever??? It
DOESN'T.
All that it needs is a network connection via the systems eth0 (or whatever).
The issue is somehow ntpd gets started before any network inte
NTP needs to have some kind of system implemented where if there is no
connection to the internet then it lays in wait until a connection
appears. One problem to consider is that ntp accuracy for intermittent
connections such as on a laptop/notebook is way lower than it would be
on a long term sta
I may be having a different problem than other posters on this bug
report. My internet connection is a WPA-secured wireless connection. The
interface is brought up at boot time, and NTP is started. However, the
wireless card does not connect to the router before I log in and enter
my keyring passwo
Thomas Sprinkmeier wrote:
> @Eric,
>
> "I see the bug on feisty with a fast local network and local dhcp
> server."
>
> Did you move "/etc/dhcp3/dhclient-enter-hooks.d/ntp" to "/etc/dhcp3
> /dhclient-exit-hooks.d/ntp" ?
>
I hadn't when I wrote the message, so I did it right now, rebooted, and
My cable modem does not disconnect and I should not really call it a
modem I suppose. My internet service is always up except for network
outages which are pretty rare. The other possibility is that certain
brands of routers are somehow broken or slow with regards to dhcp. My
router is a Linksys
@Eric,
"I see the bug on feisty with a fast local network and local dhcp
server."
Did you move "/etc/dhcp3/dhclient-enter-hooks.d/ntp" to "/etc/dhcp3
/dhclient-exit-hooks.d/ntp" ?
--
ntp is being brought up before network is ready, causing ntp to not resolve any
ip or host names and it appears
Thomas Sprinkmeier wrote:
> @feisty,
>
> If your DHCP server isn't providing NTP servers then DHCP should have nothing
> to do with NTP.
> "/etc/rcS.d/S40networking" should have the NIC's up and configured long
> before "/etc/rc[2345].d/S23ntp" tries to start NTP.
I see the bug on feisty with a
@feisty,
If your DHCP server isn't providing NTP servers then DHCP should have nothing
to do with NTP.
"/etc/rcS.d/S40networking" should have the NIC's up and configured long before
"/etc/rc[2345].d/S23ntp" tries to start NTP.
Does you modem do 'lazy connects'?
I'm wondering if the DNS queries
Does it work if you comment out the line "exit 0" in /etc/network/if-
up.d/ntp?
To the maintainer(s): Why is this line in there by default? Would it
hurt to restart ntp whenever a network interface comes up, and let users
disable this if they want, instead of doing it the other way around?
--
nt
I would like to add that I tested ntp with a static network setup. NTP
works perfectly with a static network setup. Since I need ntp I will be
using a static network config for now but I would prefer that ntp work
with dhcp.
--
ntp is being brought up before network is ready, causing ntp to not
"As expected. You're using an ADSL gateway as DHCP server?"
Actually I use a cable modem and a router. Anyway I tried to add ntp-
servers to dhclient but doing research I discovered this only works if
the dhcp server is configured to give out ntp server addresses. Since I
have no dhcp servers th
"inet addr:192.168.1.100"
As expected. You're using an ADSL gateway as DHCP server?
"HWaddr 00:05:5D:53:2B:A5" and "inet6 addr: fe80::205:5dff:fe53:2ba5"
No IPv6 configuration (the "fe80::" address is the address IPv6 assigns
when it has no address, sort of like 169.254/24 in IPv4 (see RFC3330))
The lease file and the dhclient file did not contain any entries for
ntp. I use IPv4 and ifconfig says:
eth1 Link encap:Ethernet HWaddr 00:05:5D:53:2B:A5
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::205:5dff:fe53:2ba5/64 Scope:Link
"No Servers" means that the DHCP server didn't pass on any NTP servers
and/or DHCP client doesn't care about them.
Check your lease (/var/lib/dhcp3/dhclient.eth0.leases), does it mention
"option ntp-servers ." ?
Check your dhclient configuration file, does it ask for NTP servers (by
default i
I tried your debug script in both enter & exit and the result was the
same.
ntp(REBOOT): No servers
ntp(REBOOT): Nothing to unconfigure
I also got a couple of log entries I have not seen priviously with 7.04.
Oct 3 18:45:45 ubuntu ntpd[5639]: bind() fd 19, family 10, port 123,
scope 2, addr fe
@feisty_hot_lover
I modified the ntp hook script to add some debugging (see attached).
With the hook script in "-enter-" it was clear from the logs that the
interface wasn't ready when NTP needed it.
Could you try this version of the hook script and post the log files
(/tmp/dhclient-script.*.deb
I 'fixed' this by moving "/etc/dhcp3/dhclient-enter-hooks.d/ntp" to
"/etc/dhcp3/dhclient-exit-hooks.d/ntp".
This did not work for me in Gutsy.
--
ntp is being brought up before network is ready, causing ntp to not resolve any
ip or host names and it appears ntp does not recover
https://bugs.lau
** Description changed:
Binary package hint: ntp
ntp is not resolving host names or ip addresses. I believe ntp is
trying to do it's job before the network is brought up properly. I use
7.04 and is not an upgrade. Below you will find a snippet of my daemon
log containing the releva
Thomas:
Confirmed, yep, that works perfectly - and without moving ntpdate, this
works fine too.
Nick
--
ntp is being brought up before network is ready, causing ntp to not resolve any
ip or host names and it appears ntp does not recover
https://bugs.launchpad.net/bugs/114505
You received this
I 'fixed' this by moving "/etc/dhcp3/dhclient-enter-hooks.d/ntp" to
"/etc/dhcp3/dhclient-exit-hooks.d/ntp".
Before the move a test PING of the new NTP servers failed with "ping: sendmsg:
Network is unreachable".
This makes sends because the -enter- hooks are run before the DHCP stage (in
this ca
Yes, I can replicate this exactly - same issue - please refer:
https://answers.launchpad.net/ubuntu/+question/13064
It seems DHCP is the issue. Here is more info from my system logs:
Sep 9 13:00:58 palantir avahi-daemon[5314]: No service found in
/etc/avahi/services.
Sep 9 13:00:58 palanti
Same issue here.. I'm using Ubuntu 7.10
See attached daemon.log snippet
** Attachment added: "daemon.log"
http://launchpadlibrarian.net/8892698/daemon.log
--
ntp is being brought up before network is ready, causing ntp to not resolve any
ip or host names and it appears ntp does not recover
I edited the bug report to add the daemon.log.txt as an attachment
instead of being in the bug report to make it more readable.
** Attachment added: "A snippet of daemon.log"
http://librarian.launchpad.net/7688524/daemon.log.txt
** Description changed:
Binary package hint: ntp
ntp is n
32 matches
Mail list logo
