Your message dated Sat, 14 Oct 2006 00:48:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#392673: AF_INET breaking nameserver lookups
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: curl
Version: 7.13.2-2sarge5
Severity: grave
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages curl depends on:
ii libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii libcurl3 7.13.2-2sarge5 Multi-protocol file transfer libra
ii libidn11 0.5.13-1.0 GNU libidn library, implementation
ii libssl0.9.7 0.9.7e-3sarge4 SSL shared libraries
ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime
-- no debconf information
Apt-get upgrade last night and now curl is timing out on
hostname resolution. Other applications are working fine.
I found this thread which describes a problem with AF_INET being used
by curl instead of PF_INET:
http://curl.haxx.se/mail/archive-2002-02/0106.html
To confirm, I ran straces on curl and host - indeed, curl looks to be
using AF_INET while host (which is working fine), uses PF_INET:
rockenboxen:/etc# strace curl -O http://somehost.com/this.php 2>&1 |grep -i inet
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family not
supported by protocol)
read(3, "search rockenboxen.com\nnameserver 20"..., 4096) = 69
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
connect(3, {sa_family=AF_INET,
sin_port=htons(80),sin_addr=inet_addr("1.2.3.4")}, 16) = -1 EI PROGRESS
(Operation now in progress)
[...]
rockenboxen:/etc# strace host somehost.com 2>&1 |grep -i inet
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family not
supported by protocol)
read(7, "search rockenboxen.com\nnameserver 20"..., 4096) = 69
rockenboxen:/etc#
--- End Message ---
--- Begin Message ---
On Thu, Oct 12, 2006 at 12:48:34PM -0700, Mark Symonds wrote:
> Apt-get upgrade last night and now curl is timing out on
> hostname resolution.
No, your strace shows nothing of the kind; it shows a timeout while
connecting to an http server.
> I found this thread which describes a problem with AF_INET being used
> by curl instead of PF_INET:
> http://curl.haxx.se/mail/archive-2002-02/0106.html
That thread is about differences between PF_UNSPEC and PF_INET, not between
PF_INET and AF_INET. PF_INET and AF_INET are two defines that map to the
same value, there is no difference between them in practice.
I don't believe you've shown any bug here at all. The only problem shown by
the strace is a failure to connect to a server, and you haven't given any
evidence in your log that the server in question is up.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
