I just tried n-m 0.6.4-ubuntu5. Same problem.
Same reaction, an immediate apt-get remove network-manager to restore
working behaviour.
--
ntp starts before the network is up in feisty
https://bugs.launchpad.net/bugs/90267
You received this bug notification because you are a member of Ubuntu
@James: I have just connected to my home wireless (on reboot) and... NTP
came in correctly, after the wireless was connected! I am not sure what
to attribute this to yet, but I can state I am running the stock feisty,
up-to-date.
Would you be able to try it? I do not know about wired interfaces
My prefer fix is still apt-get remove network-manager
I just installed network-manager 0.6.4-6ubuntu4 and it still starts ntpd
before the network is up. I apt-get remove network-manager and ntp works
properly again. With n-m not installed the network gets started THEN any
network services are
James, with the changes that Tollef made for n-m, do you still
experience this problem?
--
ntp starts before the network is up in feisty
https://launchpad.net/bugs/90267
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Still experiencing the problem. The following still shows ntp starting
before the network is up when using n-m.
Mar 16 10:54:46 wilma NetworkManager: information^IDHCP daemon state is now 1
(starting) for interface eth0
Mar 16 10:54:48 wilma rpc.statd[4932]: Version 1.0.10 Starting
Mar 16
I have asked for opinions from the assignee for bug # 82335 (it might
need to be considered for the n-m work there).
--
ntp starts before the network is up in feisty
https://launchpad.net/bugs/90267
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Between that other thread and your comments I was hoping network manager
might be optional. I removed it with apt-get remove network-manager
Getting sane behaviour. Network services being started after the network
is up. Ntp working as expected. Servers specified by IP being added.
Servers
That comment is a good argument for leaving 'exit 0' in /etc/network/if-
up/ntp when the move is made to ntp 4.2.4. I have already been playing
with ntp 4.2.4 and seen the interface scanning in action. I think this
is a solution for a different problem not the problem I am having.
What you said
more digging in required (thanks, Matt, your comments, and of those in
#ubuntu-bugs helped a lot).
I am always amazed by the depth of my ignorance...
/etc/network/if-(up|down|post-down|pre-up).d scripts are the
responsibility of each package: NTP, NTPdate, and others. These scripts
are executed
There is a comment in http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=399905 about this issue, and it refers to an
upstream bug (https://ntp.isc.org/bugs/show_bug.cgi?id=51) where it is
strongly recommended not to bounce ntpd on I/F status changes.
This is (probably) the reason why
No wireless here. As a work around I put a sleep 5 at the top of
/etc/init.d/ntp. This delays the starting of ntp long enough that I now
have a working ntp.
--
ntp starts before the network is up in feisty
https://launchpad.net/bugs/90267
--
desktop-bugs mailing list
This is interesting. NTP should, by default, bind to all local
interfaces, on UDP, and should be able to recover by itself.
Can you attach a 'grep ntp /var/log/daemon.log' piece here, long enough
to show the system startup some few hours of run?
** Changed in: network-manager (Ubuntu)
Ntp seems to go out of it's way to not do a wildcard bind to port 123.
It is only binding to port 123 for each interface. If the interface is
not up it does not get bound to. This is from starting ntp after eth0 is
up.
Mar 9 06:36:46 fred ntpd[2276]: Listening on interface wildcard, 0.0.0.0#123
I just tried ntp 4.2.4 which has code to scan for new interface every 5
minutes. That will bind to eth0 sometime after eth0 is brought up.
There is another problem with ntp starting before eth0 is up. When the
server lines in ntp.conf use hostnames they can not be resolved. So if
ntp does
I will look more closely at what is going on, James. On your last
comment: yes, this is a known, huh, issue/limitation: if there is no
name server resolution available, then fully-qualified hostnames (like
ntp.ubuntu.com, or pool.ntp.org, etc) will not get resolved -- after
all, they do depend on
and... yes indeed. Per chance I had started my laptop with a wireless
connection, driven by n-m.
Here's the NTP messages for the startup:
Mar 8 18:28:00 localhost ntpd[8566]: ntpd [EMAIL PROTECTED] Wed Mar 7
20:43:39 UTC 2007 (1)
Mar 8 18:28:00 localhost ntpd[8567]: precision = 1.000 usec
ntp ought to be restarted when a new interface is brought up, but for
some reason this is disabled by default:
mizar:[/etc/network/if-up.d] cat ntp
#!/bin/sh
# remove (or comment out) the next line if your network addresses change
exit 0
case $ADDRFAM in
inet*)
if [
Hggdh,
I agree with your points.
I tried commenting out the exit 0 in the script Matt mentions. Ntp works at
boot time now. It also gets restarted if I ifdown eth0; ifup eth0. Still have
ntpdate being run after ntp has started and it fails because ntp is running. In
ntp.conf a mix of server
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
--
ntp starts before the network is up in feisty
https://launchpad.net/bugs/90267
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: upstart (Ubuntu)
Status: Unconfirmed = Rejected
** Changed in: ntp (Ubuntu)
Status: Unconfirmed = Rejected
--
ntp starts before the network is up in feisty
https://launchpad.net/bugs/90267
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
20 matches
Mail list logo
