** Changed in: apr (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397393
Title:
can't bind to ::1
To manage notifications about this bug go to:
http
** Branch linked: lp:ubuntu/apr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397393
Title:
can't bind to ::1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
This bug was fixed in the package apr - 1.4.6-3
---
apr (1.4.6-3) unstable; urgency=low
* Fix some issues with resolving loopback addresses of a protocol family
that is not otherwise configured on a host. Many thanks to Jean-Michel
Vourgère and Aurelien Jarno for debugging
** Branch linked: lp:debian/apr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397393
Title:
can't bind to ::1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
Reassigning to apr in Ubuntu, as the problem has been identified as in
apr, not apache.
** Package changed: apache2 (Ubuntu) => apr (Ubuntu)
** Changed in: apr (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Changed in: apr (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397393
Title:
can't bind to ::1
To manage notifications about this bug go to:
https://b
** Bug watch added: Debian Bug tracker #500558
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500558
** Also affects: apr (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500558
Importance: Unknown
Status: Unknown
--
You received this bug notification because you a
Sorry I hadn't got back to this sooner, but this looks to be due to a specific
patch in eglibc which had been disabled due to issues, but was subsequently
re-enabled to fix #417757
Apache uses getaddrinfo with AI_ADDRCONFIG to check whether it can use ipv6,
which has been problematic with libc6
@ajmitch Hi, i just wondered how this was progressing? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397393
Title:
can't bind to ::1
To manage notifications about this bug go to:
https://b
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Andrew Mitchell (ajmitch)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397393
Title:
can't bind to ::1
--
ubuntu-bugs mailing list
u
Same problem with Ubuntu 10.04 and latest Apache with IPv6 enabled:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.2 LTS
Release:10.04
Codename: lucid
$ uname -a
Linux 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 06:07:29 UTC 2010 i
Same problem on Lucid with apache2 2.2.14-5ubuntu8.3.
--
can't bind to ::1
https://bugs.launchpad.net/bugs/397393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
I've got the problem as well, Apache is not listening to IPv6 and any
attempt to add "Listen [::]:80" or anything of the like results in an
error.
FYI, Debian's Apache runs IPv6 with no problem at all, and by default
(did not have to change anything in the conf to get it to listen to
tcp6).
--
c
I'm affected by this bug. Apache2 seems completely unable to bind to
IPv6. Even specifying only port doesn't bind to IPv6 in any way.
--
can't bind to ::1
https://bugs.launchpad.net/bugs/397393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
the interface is always up, but: sometimes there is an routing advertise
daemon available and sometimes not
--
can't bind to ::1
https://bugs.launchpad.net/bugs/397393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
My research is leading me to the believe that the nework interface is
not up when this is happening. Are you using network manager, and if
possible can you try this on karmic?
Thanks
chuck
--
can't bind to ::1
https://bugs.launchpad.net/bugs/397393
You received this bug notification because you
this is not only related to ::1, but happens to fe80::217:::3a85
and [::] , too.
with etc hosts:
127.0.0.1 localhost
127.0.1.1 bradley.lan bradley
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 i
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Triaged
--
can't bind to ::1
https://bugs.launchpad.net/bugs/397393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
Happens also on Jaunty:
uname -a
Linux berlioz 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009
x86_64 GNU/Linux
Let me know if you need more information about my configuration.
--
can't bind to ::1
https://bugs.launchpad.net/bugs/397393
You received this bug notification because
I am seeing this behaviour exactly as described. I've updated the
status to confirmed.
** Changed in: apache2 (Ubuntu)
Status: New => Confirmed
--
can't bind to ::1
https://bugs.launchpad.net/bugs/397393
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28845864/Dependencies.txt
** Description changed:
Binary package hint: apache2
the configuration directive
Listen [::1]:3000
in Server Configuration context in ports.conf line 12 fails with:
[crit] (EAI 9
21 matches
Mail list logo
