RE: Unable to connect to RHN

["Richard R. Danielson" <rdan vianet on ca>]

Thanks for the info.  I am not sure that bind is actually running.  There is
no /var/run/named.pid file.  The named.conf file is located at
/etc/log.d/conf/services/named.conf.  Its contents are as follows:


###########################################################################
# $Id: named.conf,v 1.7 2002/10/12 02:08:09 kirk Exp $
###########################################################################

# You can put comments anywhere you want to.  They are effective for the
# rest of the line.

# this is in the format of <name> = <value>.  Whitespace at the beginning
# and end of the lines is removed.  Whitespace before and after the = sign
# is removed.  Everything is case *insensitive*.

# Yes = True  = On  = 1
# No  = False = Off = 0

Title = "Named"

# Which logfile group...
LogFile = messages

# Whether or not to lookup the IPs into hostnames...
# Setting this to Yes will significantly increase runtime
$named_ip_lookup = No

# Only give lines pertaining to the named service...
*OnlyService = named
*RemoveHeaders

########################################################
# This was written and is maintained by:
#    Kirk Bauer <kirk kaybee org>
#
# Please send all comments, suggestions, bug reports,
#    etc, to kirk kaybee org 
########################################################

 
Rick Danielson

-----Original Message-----
From: Beau Henderson [mailto:silentbob gmail com] 
Sent: December 27, 2004 3:19 PM
To: rdan vianet on ca; Discussion of Red Hat Enterprise Linux 3 (Taroon)
Subject: Re: Unable to connect to RHN

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