Re: RH 8.0 Client

Here are the relevant parts of the current config:

valid_channels = redhat-7.3-i386 redhat-8.0-i386
access_check_type = user
access_check_arg = apache
current_dir = /home/current


############################################################################
[redhat-7.3-i386]
name = Red Hat Linux 7.3
parent_channel = 
arch = i386
os_release = 7.3
description = Red Hat Linux 7.3
srpm_check = 0

rpm_dirs = /mnt/sws1/7.3/en/os/i386/RedHat/RPMS
           /mnt/sws1/updates/7.3/en/os/athlon
           /mnt/sws1/updates/7.3/en/os/i386
           /mnt/sws1/updates/7.3/en/os/i486
           /mnt/sws1/updates/7.3/en/os/i586
           /mnt/sws1/updates/7.3/en/os/i686
           /mnt/sws1/updates/7.3/en/os/noarch

src_dirs =


############################################################################
[redhat-8.0-i386]
name = Red Hat Linux 8.0
parent_channel = 
arch = i386
os_release = 8.0
description = Red Hat Linux 8.0
srpm_check = 0

rpm_dirs = /mnt/sws1/8.0/en/os/i386/RedHat/RPMS
           /mnt/sws1/updates/8.0/en/os/athlon
           /mnt/sws1/updates/8.0/en/os/i386
           /mnt/sws1/updates/8.0/en/os/i486
           /mnt/sws1/updates/8.0/en/os/i586
           /mnt/sws1/updates/8.0/en/os/i686
           /mnt/sws1/updates/8.0/en/os/noarch

src_dirs =

#############################################################################

The 7.3 channel works fine.  The permissions check fine, with all files
under /home/current owned by apache:apache and cadmin checkperms and
checkdb report success.

When I attempt to run up2date on the RH8.0 client, the current server
log gets this entry:

Nov 26 12:17:07 ERROR: New module called: servers with function list
Nov 26 12:17:07   params were: []


On Tue, 2002-11-26 at 11:36, Hunter Matthews wrote:
> On Tue, 2002-11-26 at 11:21, Lawrence MacIntyre wrote:
> > Here is a list of the up2date/rhn stuff included in RH8.0:
> > 
> > up2date-3.0.7-1.i386.rpm
> > up2date-gnome-3.0.7-1.i386.rpm
> > rhn-applet-2.0.0-28.i386.rpm
> > rhnlib-1.0-1.noarch.rpm
> > 
> > Note that there is no rhn_register, so this, at least, is different.  I
> > edited /etc/sysconfig/rhn/up2date as you would before RH8.0, but, as
> > there is no rhn_register, I couldn't edit that.  When I tried to run
> > up2date, I got this:
> > 
> > [root@karabou rhn]# up2date
> > Traceback (most recent call last):
> >   File "/usr/sbin/up2date", line 801, in ?
> >     main()
> >   File "/usr/sbin/up2date", line 463, in main
> >     ret = configdlg.main(options.firstboot)
> >   File "/usr/share/rhn/up2date_client/configdlg.py", line 365, in main
> >     gui = Gui(firstboot)
> >   File "/usr/share/rhn/up2date_client/configdlg.py", line 79, in
> > __init__
> >     self.setInitialValues()
> >   File "/usr/share/rhn/up2date_client/configdlg.py", line 95, in
> > setInitialValues
> >     self.serverUrls = configUtils.getServerUrls()
> >   File "/usr/share/rhn/up2date_client/configUtils.py", line 40, in
> > getServerUrls    serverUrls = rpcServer.doCall(s.servers.list)
> >   File "/usr/share/rhn/up2date_client/rpcServer.py", line 107, in doCall
> >     ret = apply(method, args, kwargs)
> >   File "/usr/lib/python2.2/xmlrpclib.py", line 821, in __call__
> >     return self.__send(self.__name, args)
> >   File "/usr/lib/python2.2/site-packages/rhn/rpclib.py", line 126, in
> > _request
> >     verbose=self._verbose
> >   File "/usr/lib/python2.2/site-packages/rhn/transports.py", line 141,
> > in request
> >     return self.parse_response(fd)
> >   File "/usr/lib/python2.2/site-packages/rhn/transports.py", line 160,
> > in parse_response
> >     p.close()
> >   File "/usr/lib/python2.2/xmlrpclib.py", line 393, in close
> >     self._parser.Parse("", 1) # end of data
> > xml.parsers.expat.ExpatError: no element found: line 1, column 0
> 
> The last few times we've seen this on the list, it was 
> "There is no matching channel for this release/arch"
> 
> Make sure 
> a) that there is a 8.0/i386 channel on the server fully configured 
> b) the permissions on the filesystem are completely correct for apache 
>    to read them.
> 
> 
> > 
> > Then I tried to run the rhn-applet.  It died with a traceback that was
> > in a window with scrollbars but they didn't work, so I couldn't get the
> > traceback.  However, the following message was on the terminal window I
> > ran it from:
> > 
> > [root@karabou rhn]# /usr/bin/rhn-applet-gui
> > could not figure out kernel
> > 
> > The machine is running a custom kernel, but the kernel rpms are still
> > there.
> 
> THis is a bug in rhn-applet, which we don't support anyway.
> 
> And I'm not sure its really a bug - rhn_applet just might not support
> that.
> 
> 
> > 
> > On Mon, 2002-11-25 at 23:58, Barry K. Nathan wrote:
> > > On Mon, Nov 25, 2002 at 04:04:56PM -0500, Lawrence MacIntyre wrote:
> > > > Is there a way to get a RH8.0 machine to work with the current server
> > > > with the version of up2date that ships with it, or do I need to remove
> > > > the up2date and redhat network software that comes with it:
> > > [snip]
> > > 
> > > The 8.0 up2date stuff should work reasonably well as a client. Sometimes
> > > it explodes with a traceback after it finishes applying the updates (due
> > > to some new server-side thing that's not implemented in current yet --
> > > look back at the archives earlier this month for a subject line
> > > mentioning "weird traceback"). It actually applies the updates properly,
> > > though. AFAIK setup is no different than with 7.x clients.
> > > 
> > > -Barry K. Nathan <[email protected]>
> > > _______________________________________________
> > > Current-server mailing list
> > > [email protected]
> > > http://lists.dulug.duke.edu/mailman/listinfo/current-server
> > -- 
> >      Lawrence MacIntyre     865.574.8696     [email protected]
> >                 Oak Ridge National Laboratory
> > Center for High Performance Information Infrastructure Technology
-- 
     Lawrence MacIntyre     865.574.8696     [email protected]
                Oak Ridge National Laboratory
Center for High Performance Information Infrastructure Technology

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA9464vCNjP8rawCW4RAqwnAJ42xbbjIWvcVMG3FUTEIj+JrWrefQCeNeQv
eDWPFzN1AniF4U37EtGONcg=
=ccNn
-----END PGP SIGNATURE-----