On Tue, Oct 12, 2010 at 3:16 PM, Rich Graves <[email protected]> wrote: > This was resolved yesterday morning. > > My frustration level was enhanced by problems creating a new support case. > That issue > no longer exists (whether it was an actual RedHat customer portal issue or a > transient bug > in my browser, I don't know). > > The general troubleshooting/workaround points remain valid: > > 1) You almost always want "Location-aware updates" turned on because > downloads will > be faster. > > 2) If you have that turned OFF, then downloads always come from > xmlrpc.rhn.redhat.com > with a stable IP address. > > 3) At this time, the technical meaning of "Location-aware updates" is that > the client does > a DNS lookup for content-xmlrpc.rhn.redhat.com, which will return a different > proxy server > in the Akamai cloud depending on your DNS server's network location. > > 4) Circumstances where you want "Location-aware updates" turned OFF include: > a) A strict default-deny outbound firewall policy, such that you need the > stable > destination IP address > b) Transient failure of portions of the RedHat/Akamai content delivery > network(s), as in > this case > c) If your DNS server is non-local, and you know that xmlrpc.rhn gives > better performance > than content-xmrlpc.rhn (rare) > > 5) Another possible workaround is to obtain another IP address for content- > xmlrpc.rhn.redhat.com from a different ISP's DNS server and stick that in > /etc/hosts.
How about someone fixing the bad content? John _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
