Dear Sandro, On Mon, Jul 22, 2013 at 01:54:28PM +0200, Sandro Tosi wrote: > On Mon, Jul 22, 2013 at 1:35 PM, Olaf Zaplinski <o...@zaplinski.de> wrote: > > then internet access still fails. > > whta part of the "internet access" fails? doing what operation? > fetching updated versions? bugs? you can run reportbug from the > terminal and report the transcript. >
reportbug and querybts fail for me, too (w/ normal http-proxy settings).
Running querybts with strace results in:
nicolas@my-machine:~$ strace -e trace=connect querybts
--proxy=http://172.16.0.66:8080/ -b reportbug
--- SIGCHLD (Child exited) @ 0 (0) ---
connect(7, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X0"}, 20) = 0
Querying Debian BTS for reports on reportbug...
connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1
ENOENT (No such file or directory)
connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1
ENOENT (No such file or directory)
connect(3, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("172.16.0.66")}, 16) = 0
syscall_307(0x3, 0x7fff5b9d0220, 0x2, 0x4000, 0, 0x3, 0x27b67930,
0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930,
0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930,
0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930,
0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930, 0x27b67930,
0x27b67930) = 0x2
connect(3, {sa_family=AF_INET, sin_port=htons(80),
sin_addr=inet_addr("206.12.19.140")}, 16) = 0
connect(3, {sa_family=AF_UNSPEC,
sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(80),
sin_addr=inet_addr("140.211.166.26")}, 16) = 0
connect(3, {sa_family=AF_INET6, sin6_port=htons(80),
inet_pton(AF_INET6, "2607:f8f0:610:4000:6564:a62:ce0c:138c", &sin6_addr),
sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ENETUNREACH (Network is unreachable)
connect(3, {sa_family=AF_INET, sin_port=htons(80),
sin_addr=inet_addr("206.12.19.140")}, 16^C <unfinished ...>
I have no clue, what this 'syscall_307' means, but what I can see is that
reportbug connects successfully the proxy (172.16.0.66:8080), but afterwards
attempts to connect bugs.debian.org directly (which has to fail).
Since reportbug builds on python-debianbts, I assume that the bug does not come
from reportbug directly...
Does that help? Do you need something more?
Kind regards,
Nicolas
--
gpg public key: ID 0xACBC3B35, jabber: nico...@jabber.no
-- frykten for herren er opphav til kunnskap --
pgpWfdgafl18B.pgp
Description: PGP signature
