Bug 581673 - update from glibc-2.11.1-1.i686 to glibc-2.11.1-4.i686 breaks getaddrinfo on my dell laptop
Summary: update from glibc-2.11.1-1.i686 to glibc-2.11.1-4.i686 breaks getaddrinfo on ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 12
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-12 22:30 UTC by Maurizio Paolini
Modified: 2010-05-04 06:14 UTC (History)
3 users (show)

Fixed In Version: glibc-2.11.1-6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-04 06:14:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
output of strace -s1024 getent ahosts bugzilla.redhat.com with glibc-2.11.1-4 (22.95 KB, text/plain)
2010-04-14 13:06 UTC, Maurizio Paolini
no flags Details
strace output with glibc-2.11.1-1 (no update to glibc-2.11.1-4) (22.94 KB, text/plain)
2010-04-14 13:08 UTC, Maurizio Paolini
no flags Details

Description Maurizio Paolini 2010-04-12 22:30:51 UTC
Description of problem: many applications stop resolving ipv4 addresses
after upgrade from glibc-2.11.1-1.i686 to glibc-2.11.1-4.i686.
Apparently applications that make use of getaddrinfo are those affected,
I tried konqueror, wget (wget -4 works fine), firefox, yum and ssh.
The "host" command works fine, instead. 
This happens on my laptop, while on my desktop with identical configuration
the problem is not present.
Downgrading glibc, glibc-common, glibc-devel, glibc-headers back to 
version 2.11.1-1 makes the problem disappear again.

Version-Release number of selected component (if applicable):
Fedora 12, glibc-2.11.1-4.i686

How reproducible:
Unfortunately this problem is present on only one of three machines that where
updated to glibc-2.11.1-4: my laptop (Dell latitude E6500).
However it is rather annoying and I hope to find someone else that can confirm such problem in order to find a fix.
I could find a way to avoid ipv6 dns resolution (together with ipv4) as a
default behaviour.
A "tcpdump" correctly show the two queries (A? and AAAA?) and both answers, which
seem good, however the application says that thare is no address associated
to the name.

Comment 1 Maurizio Paolini 2010-04-12 23:12:39 UTC
Oops, I meant: "I could NOT find a way to avoid ipv6 dns resolution (together with ipv4) as a default behaviour"

Comment 2 Andreas Schwab 2010-04-13 09:18:35 UTC
Please provide the output of dig aaaa bugzilla.redhat.com.

Comment 3 Maurizio Paolini 2010-04-13 15:16:08 UTC
The output of "dig aaaa bugzilla.redhat.com" is probably fine:

------------------- using glibc-2.11.1-4.i686 ---------------------------
; <<>> DiG 9.6.2-P1-RedHat-9.6.2-3.P1.fc12 <<>> aaaa bugzilla.redhat.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16754
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;bugzilla.redhat.com.           IN      AAAA

;; AUTHORITY SECTION:
redhat.com.             257     IN      SOA     ns1.redhat.com. noc.redhat.com. 2010041002 3600 1800 604800 86400

;; Query time: 4 msec
;; SERVER: 10.93.16.82#53(10.93.16.82)
;; WHEN: Tue Apr 13 16:54:56 2010
;; MSG SIZE  rcvd: 81
-------------------------------------------------------------------------

It is essentially the same as with glibc-2.11.1-1.i686

On the contrary, if I try "wget bugzilla.redhat.com" I get the following:

-------- glibc-2.11.1-4.i686 -----------
--2010-04-13 16:55:17--  http://bugzilla.redhat.com/
Resolving bugzilla.redhat.com... failed: No address associated with hostname.
wget: unable to resolve host address “bugzilla.redhat.com”
----------------------------------------

while:

-------- glibc-2.11.1-1.i686 -----------
--2010-04-13 16:56:27--  http://bugzilla.redhat.com/
Resolving bugzilla.redhat.com... 209.132.183.69
Connecting to bugzilla.redhat.com|209.132.183.69|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://bugzilla.redhat.com/ [following]
--2010-04-13 16:56:27--  https://bugzilla.redhat.com/
Connecting to bugzilla.redhat.com|209.132.183.69|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “index.html”

     0K .......... .....                                       1.26M=0.01s

2010-04-13 16:56:28 (1.26 MB/s) - “index.html” saved [16289]
--------------------------------------------------

[wget works fine with the new glibc if I force ipv4 only with '-4']

In the above results I always use the same pc and switch back and forth
between glibc-2.11.1-1 and glibc-2.11.1-4 with "rpm -vUh glibc* [--oldpackage]"
giving the appropriate rpm packages (glibc, glibc-common, glibc-devel, glibc-headers).

Thank you for spending your time on this problem!

Comment 4 Andreas Schwab 2010-04-14 11:37:38 UTC
Please attach the output of "strace -s1024 getent ahosts bugzilla.redhat.com".

Comment 5 Maurizio Paolini 2010-04-14 13:06:52 UTC
Created attachment 406505 [details]
output of strace -s1024 getent ahosts bugzilla.redhat.com with glibc-2.11.1-4

Strace output as requested by Andreas Schwab

Comment 6 Maurizio Paolini 2010-04-14 13:08:59 UTC
Created attachment 406506 [details]
strace output with glibc-2.11.1-1 (no update to glibc-2.11.1-4)

The same command as before (strace output) but given with glibc-2.11.1-1
installed instead of glibc-2.11.1-4

Comment 7 Maurizio Paolini 2010-04-14 13:13:33 UTC
(In reply to comment #4)
> Please attach the output of "strace -s1024 getent ahosts bugzilla.redhat.com".    

the command "getent ahosts bugzilla.redhat.com" produced no output if given
after update to glibc-2.11.1-4, whereas it gives the expected output if I go back
to glibc-2.11.1-1.  As noted above I attached the strace output in both cases.

Comment 8 Andreas Schwab 2010-04-14 14:17:27 UTC
Try adding "options single-request" to /etc/resolv.conf.

Comment 9 Maurizio Paolini 2010-04-14 14:51:05 UTC
(In reply to comment #8)
> Try adding "options single-request" to /etc/resolv.conf.    

Tried...
That does not change anything (the result of getent ahosts bugzilla.redhat.com
is still empty) :-(

Comment 10 Andreas Schwab 2010-04-14 15:01:19 UTC
Then try single-request-reopen.

Comment 11 Maurizio Paolini 2010-04-14 16:51:09 UTC
(In reply to comment #10)
> Then try single-request-reopen.    

nope... still no response to getent ahosts bugzilla.redhat.com

are those options to resolv.conf documented somewhere?  The
man page does not mention them.

Comment 12 Andreas Schwab 2010-04-15 12:21:05 UTC
Please try glibc-2.11.1-5.2 from <http://koji.fedoraproject.org/koji/taskinfo?taskID=2116859> with "options debug" and report the output of "getent ahosts bugzilla.redhat.com".

Comment 13 Maurizio Paolini 2010-04-15 17:11:21 UTC
(In reply to comment #12)
> Please try glibc-2.11.1-5.2 from
> <http://koji.fedoraproject.org/koji/taskinfo?taskID=2116859> with "options
> debug" and report the output of "getent ahosts bugzilla.redhat.com".    

Allright, here it is:

$ rpm -q glibc
glibc-2.11.1-5.2.i686
$ getent ahosts bugzilla.redhat.com
;; res_setoptions(" debug
", "conf")..
;;      debug
dots=2, statp->ndots=1, trailing_dot=0, name=bugzilla.redhat.com
;; res_nquerydomain(bugzilla.redhat.com, <Nil>, 1, 62321)
;; res_query(bugzilla.redhat.com, 1, 62321)
;; res_nmkquery(QUERY, bugzilla.redhat.com, IN, A)
;; res_nmkquery(QUERY, bugzilla.redhat.com, IN, AAAA)
;; res_send()
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24227
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;;      bugzilla.redhat.com, type = A, class = IN
;; Querying server (# 1) address = 193.12.150.2
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24227
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0
;;      bugzilla.redhat.com, type = A, class = IN
bugzilla.redhat.com.    4m33s IN A      209.132.183.69
redhat.com.             2m49s IN NS     ns1.redhat.com.
redhat.com.             2m49s IN NS     ns3.redhat.com.
redhat.com.             2m49s IN NS     ns2.redhat.com.
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55866
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;;      bugzilla.redhat.com, type = AAAA, class = IN
redhat.com.             2m49s IN SOA    ns1.redhat.com. noc.redhat.com. (
                                        2010041301      ; serial
                                        1H              ; refresh
                                        30M             ; retry
                                        1W              ; expiry
                                        1D )            ; minimum

209.132.183.69  STREAM bugzilla.redhat.com
209.132.183.69  DGRAM  
209.132.183.69  RAW

===========================================================================
This looks promising...

Comment 14 Fedora Update System 2010-04-16 14:23:17 UTC
glibc-2.11.1-6 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/glibc-2.11.1-6

Comment 15 Maurizio Paolini 2010-04-17 20:53:56 UTC
Mmmh, now I realize that my laptop has "kernel-PAE"; could this explain something?

Comment 16 Fedora Update System 2010-04-20 13:01:28 UTC
glibc-2.11.1-6 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update glibc'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/glibc-2.11.1-6

Comment 17 David Howells 2010-04-20 17:31:46 UTC
Works for me.

Comment 18 Maurizio Paolini 2010-04-25 09:20:49 UTC
Works for me also.

Comment 19 Fedora Update System 2010-05-04 06:13:54 UTC
glibc-2.11.1-6 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.