** Branch linked: lp:~james-page/ubuntu/lucid/ntp/fix-715152
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/715152
Title:
ntp wont run on IPv6 only host unless lo has 127.0.0.1 address
Minimal patch to fix running with no IPv4
** Description changed:
+ IMPACT:
+ Ubuntu instances running in pure IPv6 environments (including 127.0.0.1)
cannot run ntp as it dies when scanning for available interfaces.
+
+ FIX:
+ IPv6/IPv4 scanning has been improved in later releases; patch
** Branch linked: lp:~james-page/ubuntu/maverick/ntp/fix-715152
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/715152
Title:
ntp wont run on IPv6 only host unless lo has 127.0.0.1
** Description changed:
IMPACT:
Ubuntu instances running in pure IPv6 environments (including 127.0.0.1)
cannot run ntp as it dies when scanning for available interfaces.
FIX:
IPv6/IPv4 scanning has been improved in later releases; patch created from
later release to resolve this
** Also affects: ntp (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Maverick)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
I've done some further investigation into this issue.
maverick exhibits the same symptoms as lucid; i.e. if the 127.0.0.1
address is not bound ntp exits on startup.
natty appears to deal with this scenario OK; removing 127.0.0.1 in a
post-up step does not impact ntp.
Looks like this issue was
Output from running ntpd -n on a maverick host with no ipv4 enabled
including localhost.
This code has changed maverick-natty to deal with ipv6 better (by the
looks of it).
** Attachment added: ntp-error.log
So this issue related to upstrem bug
http://bugs.ntp.org/show_bug.cgi?id=397
** Bug watch added: bugs.ntp.org/ #397
http://bugs.ntp.org/show_bug.cgi?id=397
** Also affects: ntp via
http://bugs.ntp.org/show_bug.cgi?id=397
Importance: Unknown
Status: Unknown
--
You received this
** Changed in: ntp (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: ntp (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/715152
Ehm, well exactly like you did, I manually removed it, although it's
done automatically from interfaces with 'pre-up'.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
https://bugs.launchpad.net/bugs/715152
Title:
ntp
On Fri, 2011-02-11 at 12:04 +, /usr/local/dick wrote:
Ehm, well exactly like you did, I manually removed it, although it's
done automatically from interfaces with 'pre-up'.
Guessed that might be the case. I'll get this configured in my test
rig.
--
James Page
Software Engineer, Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 715152
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the
Confirmed on a Lucid image; however the only way I was able to remove
the 127.0.0.1 address from lo was to use the following command:
ip addr del 127.0.0.1/32 dev lo
ntp then fails to start. As stated in the original bug report, adding
the address back to the interface fixes the issue.
How
13 matches
Mail list logo
