Sharpe, Sam J wrote:
On Tue, 7 Oct 2008, Arthur Kao wrote:
For past two months, the frequency of getting "Error communicating
with server. The message was: Service Temporarily Unavailable" error
message seems to be going up, often I have to retry several times
before RHN would respond. I do have a RHN proxy, but I get the same
error on my RHN proxy therefore I don't think it's the problem.
Anyone else experiencing the same issue?
To quote Red Hat SR# 1862538 which we opened on 2nd October with regard
to this issue:
"RHN 5642 2008/10/07 02:36:33 +01:00: ('rpclib.ProtocolError',
<ProtocolError for xmlrpc.rhn.redhat.com /XMLRPC: 503 Service
Temporarily Unavailable>)
This is an error directly from the RHN hosted server. I have done some
investigation and unfortunately the RHN service is currently undergoing
a prolonged period of disruption and so to a certain extent we are
expecting to see errors of this type. I can assure you that our
engineers are working hard to resolve the issue.
The large number of 503 type errors that you are seeing in the
ssl_access_logs are not actually directly from xmlrpc.rhn.redhat.com,
but from your RHN proxy itself. I believe that these are an artifact of
the problems communicating with RHN hosted"
So, 5 days of back and forth (on a Premium Support subscription) leads
to the admission that RHN is having unadvertised disruption. The fact
this disruption hasn't been advertised to anyone we know of, and that it
took 5 days of sending debug logs back and forth to confirm there is
nothing wrong with our proxy and that this is a known error is something
that we are chasing up through the Support channels.
--
Sam
When you get that kind of run around in the support channels, that's
when you start escalating in the sales channels.
Hugh
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
