Re: Unable to connect to RHN

[Beau Henderson <silentbob gmail com>]

Do you have bind running on this machine ? I've had a couple reports
from a few clients the update whiping out their named.conf and perhaps
messing with their resolver config. If thats not the case.. please
ignore me :)


On Mon, 27 Dec 2004 14:40:20 -0500, Richard R. Danielson
<rdan vianet on ca> wrote:
> Sorry.  The problem seems to be with the connection to up2date.  On the gui
> screen the RHN icon is grayed out and in the up2date log file the message is
> 
> [Sun Dec 26 11:25:48 2004] up2date A socket error occurred: (110,
> 'Connection timed out'), attempt #5
> [Sun Dec 26 11:25:48 2004] up2date Error communicating with server. The
> message was:
> 
> It could be related to our main university network.  However I wondered if
> it could also be something related to the Red Hat network.
> Rick Danielson
> 
> 
> -----Original Message-----
> From: taroon-list-bounces redhat com [mailto:taroon-list-bounces redhat com]
> On Behalf Of Jussi Silvennoinen
> Sent: December 27, 2004 10:52 AM
> To: taroon-list redhat com
> Subject: Re: Unable to connect to RHN
> 
> > Ever since the upgrade to U4, I have not been able to connect to RHN.
> > Is this possibly related to the bind issue, or something else?
> 
> You might want to share some details on what is not working. Up2date, https
> to rhn.redhat.com or perhaps something else. And then, how does the problem
> manifest itself.
> 
> --
> 
>   Jussi
> 
> --
> Taroon-list mailing list
> Taroon-list redhat com
> http://www.redhat.com/mailman/listinfo/taroon-list
> 
> --
> Taroon-list mailing list
> Taroon-list redhat com
> http://www.redhat.com/mailman/listinfo/taroon-list
> 


-- 
Beau Henderson
http://www.iminteractive.net