[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#740674: installation-reports: netinst fails to query network mirrors



Yuriy Grishin <ygrishin@pyramidheadgroup.ca> (2014-03-03):
> Cyril Brulebois <kibi@debian.org> (2014-03-04):
> > any chance you could extract /var/log/syslog when that happens so that
> > we have a better idea of what's actually tried, and so that we get a
> > better idea of the failure mode?
> > 
> > If you have a near-by machine with IP $foo, you could listen using nc:
> >   nc -l -p 1234 > syslog
> > 
> > and send /var/log/syslog from d-i to the other machine this way:
> >   nc $foo 1234 < /var/log/syslog
> 
> Attached.
> 
> I first tried to access ftp.ca.debian.org which failed right away
> ("bad mirror" message)

This might be:
Mar  4 02:02:29 choose-mirror[30164]: DEBUG: command: wget -q http://ftp.ca.debian.org/debian/dists/wheezy/Release -O - | grep -E '^(Suite|Codename):'
Mar  4 02:02:34 choose-mirror[30164]: WARNING **: mirror does not support the specified release (wheezy)

Unfortunately the error isn't exactly explicit. Maybe that was the
same kind of errors as below, but in busybox's wget instead of the
target's apt, which might explain different error reporting.

> then switched to MIT's mirror which and it
> was downloading files for a while and then failed with "Cannot
> access repository".

A very quick (it's past 3am here) look in the file gives:
Mar  4 02:04:16 in-target: Failed to fetch http://debian.lcs.mit.edu/debian/dists/wheezy/Release.gpg  Something wicked happened resolving 'debian.lcs.mit.edu:http' (-5 - No address associated with hostname)
Mar  4 02:04:35 in-target: W: Failed to fetch http://security.debian.org/dists/wheezy/updates/Release.gpg  Something wicked happened resolving 'security.debian.org:http' (-5 - No address associated with hostname)
Mar  4 02:04:42 in-target: W: Failed to fetch http://debian.lcs.mit.edu/debian/dists/wheezy-updates/Release.gpg  Something wicked happened resolving 'debian.lcs.mit.edu:http' (-5 - No address associated with hostname)

which suggests some network-related issues.

You may want to double-check what ends up in your /etc/resolv.conf,
and whether your DNS is working fine.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: