Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 599616

Summary: mirrorselect: error in finding the fastest mirror, python error
Product: Portage Development Reporter: Oscar Andrea Merandi <oscar.andrea>
Component: ToolsAssignee: Portage Tools Team <tools-portage>
Status: RESOLVED DUPLICATE    
Severity: normal CC: amd64, oscar.andrea
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
URL: https://arin.ga/EsYIAJ
Whiteboard:
Package list:
Runtime testing required: ---

Description Oscar Andrea Merandi 2016-11-12 20:27:40 UTC
as advised wiki I launched the command mirrorselect -s3 -b10 -D
unfortunately as you can see I assume mirrorselect not reisca to handle the error in python

Reproducible: Always

Steps to Reproduce:
1.sudo mirrorselect -s3 -b10 -D
2.
3.
Actual Results:  
error python:
https://arin.ga/EsYIAJ
Comment 1 Oscar Andrea Merandi 2016-11-12 20:30:35 UTC
*reisca = be able
Comment 2 DJ Dunn 2016-11-14 04:07:10 UTC
I'm seeing the same error only happens with mirrorselect -D
Comment 3 Zac Medico gentoo-dev 2016-11-14 05:29:40 UTC
(In reply to oscar.andrea@hotmail.it from comment #0)
> https://arin.ga/EsYIAJ

In the future, please post or attach things like this directly on the bug report. I've pasted it below:

 sudo mirrorselect -s3 -b10 -D
Password: 
* Using url: https://api.gentoo.org/mirrors/distfiles.xml
* Downloading a list of mirrors...
 Got 155 mirrors.
* Downloading mirrorselect-test files from each mirror... [68 of 155]Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/mirrorselect/selectors.py", line 305, in deeptime
    addr_family, socket.SOCK_STREAM, 0, socket.AI_ADDRCONFIG):
  File "/usr/lib64/python3.4/socket.py", line 537, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.4/mirrorselect", line 61, in <module>
    MirrorSelect().main(sys.argv)
  File "/usr/lib64/python3.4/site-packages/mirrorselect/main.py", line 375, in main
    urls = self.select_urls(hosts, options)
  File "/usr/lib64/python3.4/site-packages/mirrorselect/main.py", line 324, in select_urls
    selector = Deep(hosts, options, self.output)
  File "/usr/lib64/python3.4/site-packages/mirrorselect/selectors.py", line 226, in __init__
    self.deeptest()
  File "/usr/lib64/python3.4/site-packages/mirrorselect/selectors.py", line 253, in deeptest
    mytime, ignore = self.deeptime(host, maxtime)
  File "/usr/lib64/python3.4/site-packages/mirrorselect/selectors.py", line 305, in deeptime
    addr_family, socket.SOCK_STREAM, 0, socket.AI_ADDRCONFIG):
  File "/usr/lib64/python3.4/site-packages/mirrorselect/selectors.py", line 199, in timeout_handler
    raise TimeoutException()
mirrorselect.selectors.TimeoutException
Comment 4 Zac Medico gentoo-dev 2016-11-14 06:58:03 UTC
I have reproduced the problem on my first try, but not on later tries. It looks like the issue is that both exceptions occur at approximately the same time.
Comment 5 Zac Medico gentoo-dev 2016-11-14 07:00:59 UTC

*** This bug has been marked as a duplicate of bug 523312 ***
Comment 6 Oscar Andrea Merandi 2016-11-15 18:30:36 UTC
(In reply to Zac Medico from comment #5)
> 
> *** This bug has been marked as a duplicate of bug 523312 ***

so it was resolved? I currently still have this problem
Comment 7 Brian Dolbec (RETIRED) gentoo-dev 2016-11-15 22:21:14 UTC
(In reply to oscar.andrea@hotmail.it from comment #6)
> (In reply to Zac Medico from comment #5)
> > 
> > *** This bug has been marked as a duplicate of bug 523312 ***
> 
> so it was resolved? I currently still have this problem

Yes, this bug is resolved.  You have been added to the other bug mentioned that this bug is a duplicate of.

If you click on bug 523312, you will get your answers.
Comment 8 Oscar Andrea Merandi 2016-11-16 14:44:02 UTC
(In reply to Brian Dolbec from comment #7)
> (In reply to oscar.andrea@hotmail.it from comment #6)
> > (In reply to Zac Medico from comment #5)
> > > 
> > > *** This bug has been marked as a duplicate of bug 523312 ***
> > 
> > so it was resolved? I currently still have this problem
> 
> Yes, this bug is resolved.  You have been added to the other bug mentioned
> that this bug is a duplicate of.
> 
> If you click on bug 523312, you will get your answers.

thanks!