The bug is still not solved!
I have similar experience with an up-to-date Gutsy system, installed
about 2 weeks ago.
So first ntp can't start, because /etc/network/if-up.d/ntpdate runs in
the same time. If I disable the ntpdate script (write an "exit 0" in the
beginning) then ntp starts, but _bef
"Me too" on this situation. Clean installation of the latest Gutsy, with
all updates applied.
My fix has been to disable the ntp daemon startup in the ntp scripts,
and have the daemon started through an if-up.d script, which simply
sends a 'start' signal to /etc/init.d/ntp. This is workable, altho
Attaching daemon.log for 15th October. Complete with successful restart
of ntp at tail end.
** Attachment added: "daemon_trimmed.log"
http://launchpadlibrarian.net/10032143/daemon_trimmed.log
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/902
I'm afraid that the problem has persisted for me right through to using
Gutsy updated to release candidate plus today's updates.
That's network-manager 0.6.5-0ubuntu15
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/90267
You received this bug not
The problem is fixed for me in Gutsy Tribe 5. My wired ethernet
interface is up when I log in the GUI. Before I had to use the network
manager applet and pick "wired interface" for it to come up.
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/9026
network-manager (0.6.5-0ubuntu7) gutsy; urgency=low
[Alexander Sack <[EMAIL PROTECTED]>]
* prefetch bugfix from svn - not-connected wired interface is if-upped:
1. 24a_svn2578-gnome354565-fix-ethernet-link-detection-races.patch:
- prefetch patch from 0.6.0 release branch (rev 2578)
Today's full daemon.log as requested.
I've not trimmed it at all, just in case...
The problem is still present on the system, with NTP not running
properly ("No association IDs returned")
At 19:34:10 I manually restarted ntp, just for completenes. It works
fine, as you can see at the end of the
Hi,
can you please post a complete daemon.log (or syslog) I need a
complete log starting with the line where NetworkManager is initially
started up.
Thanks,
- Alexander
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/90267
You received thi
** Changed in: network-manager (Ubuntu)
Target: obsolete-milestone => tribe-3
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/90267
You received this bug
Result of /var/log/daemon.log | grep ntp | less, last seven lines are
after a restart of ntpd.
My wireless connection is on eth1.
Jun 19 10:19:47 neilw-laptop ntpd[5345]: ntpd [EMAIL PROTECTED] Wed Mar 7
20:43:30 UTC 2007 (1)
Jun 19 10:19:47 neilw-laptop ntpd[5346]: precision = 1.000 usec
Jun 1
Also a "me to". Exactly the same as Joey Stanford. My (one) wireless
laptop with 7.04 and Network-Manager needs 'sudo /etc/intit.d/ntp
restart' to get ntp running.
The cabled workstation, also with 7.04 and Network-Manager works fine
after normal booting.
Happy to test fixes, provide logs etc i
This is a "me too" post. It's causing "issues" on my two wireless
laptops but is not an issue on my static ip'd and cabled desktop. Thanks
for looking into this.
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/90267
You received this bug notificat
** Changed in: ntp (Ubuntu)
Status: Confirmed => Rejected
** Changed in: network-manager (Ubuntu)
Importance: Medium => Critical
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/90267
You received this bug notification because you are a m
Confirmed at UDS that this is a high-priority bug fix.
Right now, n-m assumes that all interfaces are down and uninitialized at
startup. It needs to detect the state of interfaces and initialize the
internal model accordingly. This should happen by looking at
ifconfig/iwconfig to remain upstream c
Let's fix this for gutsy.
** Changed in: network-manager (Ubuntu)
Target: None => ubuntu-7.10
--
network-manager stops and restarts already ifup'ed interfaces
https://bugs.launchpad.net/bugs/90267
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
James, I am just presenting what I have found. I myself have my own
stratum 1 at home, but this still does not resolve the issue between n-m
and ntpd. In fact, for me it is even worse, since my laptop fluctuates
betwen hotel, cellular-based, and home LANs. Using n-m, for me, is
easier that hand-ada
I would not use those steps. The 2 other solutions I remember from the
comp.protocols.time.ntp archive which allow you to run ntp with a
dynamic ip are
1. Use /etc/ppp/if-up.local to restart ntp each time ppp0 got a new ip.
Does lose many hours of history but still keeps ntp working and the
machin
There are some comments, in the ntp mailing lists, that on dynamic
network environments, the following sequence should be used:
1. bring up the network
2. if this is boot time, run ntpdate as soon as possible during boot.
3. run ntpd -qg every so often (like every hour or so).
But I certainly cou
The ntp devs refuse to do a normal wild card bind and stick with what
they have done. This has come up in comp.protocols.time.ntp quite a few
times. Which I think led to the new interface scanning code in ntp 4.2.4
which has it's own problems when ntp is started before the network is
up. I mentione
The n-m side of the problem is that it tears down and re-dhcdbd's
interfaces which are already ifup'ed by /etc/init.d/networking. This
definitively needs to be fixed, but is not release-critical.
The ntpd side of the problem is that it should be configured to just
listen on * instead of per-interf
20 matches
Mail list logo
