|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 sw_single / aria2c takes a very long time to download anything. An ipv6 problem? | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Guillaume van Baalen <postdoc38> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | ma, tatsuhiro.t |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast2 logs | ||
|
Description
Guillaume van Baalen
2009-11-27 14:07:20 UTC
Please attach the yast logfiles (see http://en.opensuse.org/Bugs/YaST). Created attachment 330579 [details]
yast2 logs
aria2c doesn't have an option to disable ipv6. Even if ipv6 is disabled by kernel, getaddrinfo() in glibc issues AAAA request, and this takes lots of time here. aria2c supports asynchronous DNS using c-ares library and only supports ipv4. But it seems aria2 build in opensuse are not compiled with c-ares. Indeed, installing libcares2 (and libcares-devel) seems to solve the problem. No need to rebuild aria2c? Is it just a runtime recommendation? My mistake, I had (compiled and) installed aria2c version 1.6.3 in the mean time. Removing version 1.6.3 and using stock aria2c still gives long timeout. So yes, installation of libcares2 and libcares-devel and then rebuild of aria2c is necessary, at least on my side. aria2c has to be rebuilt with libcares and libcares-devel to enable IPV4 only async DNS. It has --async-dns=false option, when specified, it falls back to glibc getaddrinfo(). @Coolo: Wait for getaddrinfo fix in glibc (#556299), or update aria to introduce libcares, or both? Updating to aria2 1.7.0 and using the newly intrduced --disable-ipv6 should solve this. *** This bug has been marked as a duplicate of bug 556299 *** |