Description of problem: I got quite a few emails tonight from my RHN Proxy with a couple different SSL errors connecting with the RHN parent. This seems to be a regular occurance. The date in question is Fri, 18 Jun 2004 06:33:25 -0400 I'm attaching a couple emails of the different tracebacks.
Created attachment 101244 [details] 06/18/04 -- SSL connect error
Created attachment 101245 [details] 06/18/04 -- SSL read error This error happens quite often.
We had a bit of downtime when we upgraded code on the hosted side at those times. If everything is operating smoothly again, then... all should be well. Not overly pretty error messaging I know.. alas... Lemme know if it happens again please. Moving to a NEEDINFO status for the time being.
Created attachment 102761 [details] RHN Traceback I'm assuming there was maintenance on RHN last night. Got several hundred of the attached email. The feature request in this case is to have a system that understands the difference between downtime and failure and have the Proxy servers handle it properly.
Created attachment 102981 [details] RHN Proxy traceback I got 400 copies of the above email this morning.
Again, if there was a maintenance window last night 1) your users would like to know and 2) the RHN PRoxy servers should be able to handle the difference between maintenance and failures.
outage policy is in the midst of revision. I assume you are on rhn-outage-list? Spamming admins: Yup. Changing summary to reflect this is the driving issue here. "socket.sslerror with Proxy connecting to parent" --> "proxy: don't spam during an outage" I.e., we need to figure out a way to inform, but not over-inform. Probably need to digest emails maybe for tracebacks? Dunno. Punting to you misa; it's your bag now.
User bnackash's account has been closed
User pvetere's account has been closed
I think this could we doable. We should request from hosted team some method to indicate that is outage (like definition of sorry page).
Duplicate of 309071 Already fixed in RHN Proxy 5.1 We do not send email if there is connection error, just write up message to log. *** This bug has been marked as a duplicate of 309071 ***