[pca] PCA failling with some inetnum resolutions of a248.e.akamai.net

[Michael Jackson]

Has anyone else noticed any change in the behaviour of the Akamai download
servers in the last couple of days  -- particularly if you're in the UK?

For me it was previously working fine with fixes for the documented wget
gotchas.  But now I get:

# pca -Vl
Option list: 1
Option patchdir: /var/tmp/.
Option user: xxxxxx
Option passwd: xxxxxx
Option syslog: local0
Option debug: 1
ARGV: missing
Version: 20100309-02
Config files: /etc/pca.conf 
Found /usr/local/bin/wget (1.11.4, 11104, https)
Using /usr/local/bin/wget
Found /usr/bin/uname
Prerequisites for threads not met, setting threads to 0
Never update
Expanded patch list: missing
Downloading xref file to /var/tmp/patchdiag.xref
Trying https://sunsolve.sun.com/ (1/1)
/usr/local/bin/wget --progress=dot:binary 
"https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref" 
--ca-certificate=/usr/local/bin/pca -O /var/tmp/patchdiag.xref
--2010-04-05 17:28:56--  
https://a248.e.akamai.net/f/248/21808/15m/sun.download.akamai.com/21808/patches/pa
tchroot/reports/patchdiag.xref?AuthParam=1270485056_885d9d144fb566962646a3876b184a
74&TUrl=L0QdUQV8Z4i0fdED3QTP3SJDWA8FMyaJsHfIWf4X29kTWQpKEzIbwqFuyRPZ&TicketId=D1Ra
+keNWlQ=&GroupName=SWUP&BHost=sdlc3i.sun.com&FilePath=/patches/patchroot/reports/p
atchdiag.xref&File=patchdiag.xref
Resolving a248.e.akamai.net... 92.123.154.75, 92.123.154.48
Connecting to a248.e.akamai.net|92.123.154.75|:443... failed: Connection timed 
out.

Jumping on the border router I can traceroute to either of the hosts, but
hopping back through each hop towards the inside hosts, I eventually reach
a router that doesn't like something it gets back from any host in Akamai's
network:

inetnum:        92.123.152.0 - 92.123.155.255

That was written 2-days ago on the 4th.  Meantime I'd been rebooting routers,
changing and backing-out changes to rules all to no avail.  I notice that the 
hosts that magically succeed now are in a different inetnum... (and before
you ask, there's no rule allowing say 194.217.240 but not 92.123.152).

Martin: As far as PCA is concerned, would it be possible to add something in
the debugging output that showed a) the date/timestamp of the last successful
Akamai download, and b) the a248.e ip address successfully downloaded from.

--2010-04-06 17:21:53--  i.e. just now 
https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref
Resolving sunsolve.sun.com... 192.18.108.40
Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://getupdates2.sun.com/reports/patchdiag.xref [following]
--2010-04-06 17:22:06--  https://getupdates2.sun.com/reports/patchdiag.xref
Resolving getupdates2.sun.com... 198.232.168.157
Connecting to getupdates2.sun.com|198.232.168.157|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: 
https://a248.e.akamai.net/f/248/21808/15m/sun.download.akamai.com/21808/patches/pa
tchroot/reports/patchdiag.xref?AuthParam=1270571047_97c6e0aafe9a461c79cbbc2fcc302b
54&TUrl=L0QdUQV8Z4i0fdED3QTP3SJDWA8FMyaJsHfIWf4X29kTWQpKEzIbwqFuyRPZ&TicketId=D1RY
/k2OV1c=&GroupName=SWUP&BHost=sdlc6g.sun.com&FilePath=/patches/patchroot/reports/p
atchdiag.xref&File=patchdiag.xref [following]
--2010-04-06 17:22:07--  
https://a248.e.akamai.net/f/248/21808/15m/sun.download.akamai.com/21808/patches/pa
tchroot/reports/patchdiag.xref?AuthParam=1270571047_97c6e0aafe9a461c79cbbc2fcc302b
54&TUrl=L0QdUQV8Z4i0fdED3QTP3SJDWA8FMyaJsHfIWf4X29kTWQpKEzIbwqFuyRPZ&TicketId=D1RY
/k2OV1c=&GroupName=SWUP&BHost=sdlc6g.sun.com&FilePath=/patches/patchroot/reports/p
atchdiag.xref&File=patchdiag.xref
Resolving a248.e.akamai.net... 194.217.240.73, 194.217.240.72
Connecting to a248.e.akamai.net|194.217.240.73|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3233879 (3.1M) [text/plain]
Saving to: `/var/tmp/patchdiag.xref'

     0K ................ ................ ................ 12%  130K 21s
   384K ................ ................ ................ 24%  231K 14s
   768K ................ ................ ................ 36%  203K 11s
etc. etc. suddenly now working


Kind regards