security.debian.org down?

joe · External Since: Oct 15, 2009 Posts: 5

For the past 2 days, I could not access security.debian.org - every
time I run 'apt-get update' ot bombs out saying it can't access this
url. Is the site down or have I miss something (like praying to the
Linux gods or the need to sacrifice virgins? Smile

)

joe

John Hasler · External Since: Dec 04, 2004 Posts: 192

joe writes:
> For the past 2 days, I could not access security.debian.org...

No problem from here as of about a minute ago. Connected both with a
browser and with apt.

> ...every time I run 'apt-get update' ot bombs out saying it can't
> access this url.

Post your sources.list.
--
John Hasler

atec 7 7 · External Since: Aug 28, 2009 Posts: 3

joe wrote:
> For the past 2 days, I could not access security.debian.org - every
> time I run 'apt-get update' ot bombs out saying it can't access this
> url. Is the site down or have I miss something (like praying to the
> Linux gods or the need to sacrifice virgins? Smile

)
>
> joe
what did you do wrong ?

http://www.debian.org/security/ works fine

joe · External Since: Oct 15, 2009 Posts: 5

John Hasler wrote:

> joe writes:
>> For the past 2 days, I could not access security.debian.org...
>
> No problem from here as of about a minute ago. Connected both with a
> browser and with apt.
>
>> ...every time I run 'apt-get update' ot bombs out saying it can't
>> access this url.
>
> Post your sources.list.

Ok - here's my sources.list

deb http://mirror.nus.edu.sg/Debian/ lenny main
deb-src http://mirror.nus.edu.sg/Debian/ lenny main

deb http://security.debian.org/ lenny/updates main contrib
deb-src http://security.debian.org/ lenny/updates main contrib

# Line commented out by installer because it failed to verify:
#deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib
# Line commented out by installer because it failed to verify:
#deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
contrib

BTW, it is a fresh install of Debian Lenny. Internet connection is OK - I
can browse the web, send e-mail, etc. Every other piece of software works
perfectly. But when I run 'apt-get update' or 'aptitude update' in a
console I get the error message:

Err http://security.debian.org lenny/updates Release.gpg
Could not connect to security.debian.org:80 (32.1.10.120), connection
timed out
Err http://security.debian.org lenny/updates/main Translation-en_US
Unable to connect to security.debian.org http:
Err http://security.debian.org lenny/updates/contrib Translation-en_US
Unable to connect to security.debian.org http:

It's now been 3 days - if the server is busy what the heck is it doing that
takes such a long time?

Any ideas, suggestions?

Any ideas why?

Darren Salt · External Since: Oct 15, 2004 Posts: 359

I demand that joe may or may not have written...

[snip]
> Err http://security.debian.org lenny/updates Release.gpg
> Could not connect to security.debian.org:80 (32.1.10.120), connection
> timed out
> Err http://security.debian.org lenny/updates/main Translation-en_US
> Unable to connect to security.debian.org http:
> Err http://security.debian.org lenny/updates/contrib Translation-en_US
> Unable to connect to security.debian.org http:

> It's now been 3 days - if the server is busy what the heck is it doing that
> takes such a long time?

> Any ideas, suggestions?

traceroute? That should provide some indication of where the problem is...

--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| Kill all extremists!

To give happiness is to deserve happiness.

joe · External Since: Oct 15, 2009 Posts: 5

Darren Salt wrote:

[snip]
>
> traceroute? That should provide some indication of where the problem is...
>

Hmmm, traceroute output:

traceroute to security.debian.org (32.1.6.16), 30 hops max, 40 byte packets
1 mygateway1.ar7 (192.168.42.254) 0.798 ms 1.077 ms 1.328 ms
2 219.93.218.177 (219.93.218.177) 24.863 ms * *
3 219.93.216.181 (219.93.216.181) 59.102 ms 59.927 ms 60.641 ms
4 10.55.32.126 (10.55.32.126) 64.907 ms 10.55.32.130 (10.55.32.130)
72.064 ms 77.622 ms
5 203.106.86.86 (203.106.86.86) 291.128 ms 297.854 ms 304.993 ms
6 ns.de.prserv.net (195.66.224.27) 356.841 ms 356.298 ms 361.932 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

But I can ping security.debian.org ....
If apt-get update can access other repositories, then why can't it access
security.debian.org?. BTW, my install is a 64-bit KDE Lenny. I am going to
try installing the 32-bit GNOME version today.

Darren Salt · External Since: Oct 15, 2004 Posts: 359

I demand that joe may or may not have written...

> Darren Salt wrote:
> [snip]
>> traceroute? That should provide some indication of where the problem is...

> Hmmm, traceroute output:
> traceroute to security.debian.org (32.1.6.16), 30 hops max, 40 byte packets

Hmm. That's not one of the IP addresses which I see for it; then again, it
appears to be handled via GeoIP-type stuff these days.

And that one does indeed seem to be down.

> 1 mygateway1.ar7 (192.168.42.254) 0.798 ms 1.077 ms 1.328 ms
> 2 219.93.218.177 (219.93.218.177) 24.863 ms * *
> 3 219.93.216.181 (219.93.216.181) 59.102 ms 59.927 ms 60.641 ms
> 4 10.55.32.126 (10.55.32.126) 64.907 ms 10.55.32.130 (10.55.32.130)
> 72.064 ms 77.622 ms
> 5 203.106.86.86 (203.106.86.86) 291.128 ms 297.854 ms 304.993 ms
> 6 ns.de.prserv.net (195.66.224.27) 356.841 ms 356.298 ms 361.932 ms
> 7 * * *
[snip * * *]
> 30 * * *

> But I can ping security.debian.org ....

I can, or at least I can ping the ones which are reported here as being
security.d.o. I can't reach 32.1.6.16 from here at all.

I think that you should file a bug report against the meta-package
"security.debian.org" (as you would for a bug in a real package); as a
temporary measure until it's resolved, you could see what other IP addresses
are reported by "host security.debian.org" and put them in /etc/hosts.

(I find it odd, though, that it isn't listed as a security.d.o mirror...)

[snip]
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + Generate power using sun, wind, water, nuclear. FORGET COAL AND OIL.

Keyboard failure. Think Space to continue.

joe · External Since: Oct 15, 2009 Posts: 5

Darren Salt wrote:

[snip]
> I think that you should file a bug report against the meta-package
> "security.debian.org" (as you would for a bug in a real package); as a
> temporary measure until it's resolved, you could see what other IP
> addresses are reported by "host security.debian.org" and put them in
> /etc/hosts.
[snip]

Executing 'host security.debian.org' gave me valid ip addresses but was also
accompanied with a warning 'Message parser reports malformed message
packet' Dunno what this mean but putting one of the ip address
into /etc/hosts solved the 'apt-get update problem'. I need to check why it
gave the warning message ... will keep you informed - but if you have any
ideas why, let me know. Tks for the 'host' suggestion, btw.

joe · External Since: Oct 15, 2009 Posts: 5

joe wrote:

[snip]
> into /etc/hosts solved the 'apt-get update problem'. I need to check why
> it gave the warning message ... will keep you informed - but if you have
> any ideas why, let me know. Tks for the 'host' suggestion, btw.

I solved the problem ... it was a DNS issue after all. My ADSL router
setting somehow got screwed up but once fixed, it solved all the 'host'
and 'apt-get update' problems.