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

Bug#807371: marked as done (apt hostname resoloution failure)



Your message dated Tue, 8 Dec 2015 22:40:42 +0100
with message-id <20151208224001.GA9758@debian.org>
and subject line Re: Bug#807371: apt hostname resoloution failure
has caused the Debian Bug report #807371,
regarding apt hostname resoloution failure
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
807371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807371
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.1.3
Severity: grave

When running apt in a Debian stretch armhf chroot on my odriod u2 DNS resoloution fails. ping is able to resolve the hostname.

root@odroidu2:/# apt-get update
Err:1 http://mirror.bytemark.co.uk/debian stretch InRelease
  Could not resolve 'mirror.bytemark.co.uk'
Reading package lists... Done
W: Failed to fetch http://mirror.bytemark.co.uk/debian/dists/stretch/InRelease Could not resolve 'mirror.bytemark.co.uk' W: Some index files failed to download. They have been ignored, or old ones used instead.
root@odroidu2:/# ping mirror.bytemark.co.uk
PING mirror.bytemark.co.uk (212.110.161.69) 56(84) bytes of data.
64 bytes from mirror.bytemark.co.uk (212.110.161.69): icmp_seq=1 ttl=57 time=20.8 ms

The chroot is on a host system running a vendor 3.0.90 kernel, no idea if that is relavent. At the very least if there is a problem running on older kernels there should be a warning before the updated packages are installed.

The issue seems to be new in the 1.1 series of apt versions.

The issue definately seems to be somehow related to dns lookups. If I add the hostname to /etc/resolv.conf then apt seems to work.

Any thoughts on how to debug this.

--- End Message ---
--- Begin Message ---
On Tue, Dec 08, 2015 at 09:39:22PM +0000, peter green wrote:
> On 08/12/15 09:42, Julian Andres Klode wrote:
> >You might want to try running the ping as the _apt user and check
> >if that works. Maybe the _apt user does not have access to
> >/etc/resolv.conf?
> Indeed that seems to be the issue, the resolv.conf in the chroots in
> question is not world readable for some reason. It's not world readable on
> the host system either, so I presume debootstrap copied the broken
> permissions into the chroots.
> 
> Did the user used to run aptmethods change recently?

Yes, it's one of the big new APT 1.1 features.

I'll close it then, as that's a config issue.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

--- End Message ---

Reply to: