Hello Eduard, On Sun, Jun 05, 2016 at 09:16:09PM +0200, Helge Kreutzmann wrote: > On Sun, Jun 05, 2016 at 06:14:27PM +0200, Eduard Bloch wrote: > > * Helge Kreutzmann [Sun, Jun 05 2016, 04:37:59PM]: > > > > > > I have seen a similar report from Ubuntu recently... probably this > > > > > > needs > > > > > > to be reassigned to glibc ASAP. > > > > > > > > > > That is probably beyond my knowledge[1], could you reassign? I'm > > > > > willing > > > > > to test and provide information, no problem on that. > > > > > > > > > > Greetings > > > > > > > > > > Helge > > > > > > > > > > [1] Not the commands to reassign, but finding the right package and > > > > > giving the right information for the bug to be proccessed. > > > > > > > > Not sure yet - as said, it smells like a problem of getaddrinfo which > > > > would be libc6. But first, can you confirm there is no bindaddress > > > > directive anywhere in other conf files? What does: > > > > > > > > $ /usr/lib/apt-cacher-ng/acngtool cfgdump | grep --color bind > > > > > > > > print? > > > > > > root@samd:/etc# /usr/lib/apt-cacher-ng/acngtool cfgdump | grep --color > > > bind > > > root@samd:/etc# > > > > > > Also unchanged if I reboot. > > > > Sure, this will be unchanged, I just wanted to be sure that it isn't > > trying to resolve an interface name. Things start getting ugly now. I > > prepared a minimal test case, could you run it? See attachment, just > > "g++ addrinfo.cc" to compile, ./a.out to execute. > > The output is: > Found socket, type: 2 > Found socket, type: 10
I tried to locally trace down more, but I guess I'm far beyond my
knowledge.
So far other programms work (ping, ssh, unison, browsers) so it must
be something rather low level.
What I noticed is that (for some yet unkown reason) the local IP is
not assigned currently to enp2s0 (for some reason that is the name of
the interface, not eth0). I can assign it manually with ifconfig but
this does not change behaviour.
I see where your code is coming from, and in deamon.log I see:
Jul 26 15:01:37 samd apt-cacher-ng[21604]: Error resolving address far binding:
Bad message
Jul 26 15:01:37 samd apt-cacher-ng[21604]: No socket(s) could be
created/prepared. Check the network, check or unset the BindAddress directive.
I did not find out what "Bad message" means and I tried playing with
the directive BindAddress, but I'm not sure I understand what it
actually requires, so in my few attempts did not succeed.
Do you have any further ideas for debugging? Or should I check which
alternatives for acng are available?
Thanks again
Helge
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
