Re: current 1.4.2 & up2date 3.0.7 problems

Hunter Matthews <[email protected]> 21 Oct 2002 10:16:52 -0400
Newsgroups gmane.network.up2date.current.devel
Message-ID <[email protected]>
On Mon, 2002-10-21 at 07:35, Barry K. Nathan wrote:
> On Mon, Oct 21, 2002 at 11:32:04AM +0200, Arnaud Abelard wrote:
> > my current.conf file:
> > 
> > [current]
> > valid_channels = redhat-7.3-i386 redhat-7.2-i386 redhat-8.0
> > <snip snip snip>
> > [redhat-8.0]
> > name = Red Hat Linux 8.0
> > parent_channel =
> > arch = i686 i386 athlon
> 
> Isn't this just supposed to say "arch = i386" (athlon and i686 are
> specific types of i386)? Or am I mistaken?

It is. The 'arch' for a channel is not all the arches that you have, its
the "base" arch for your channel.

athlon, i686, i586, i486 AND i386 systems all have "i386" as their base
arch.

To my knowledge, your only choices here are 
i386, alpha, sparc, ia64


> 
> > os_release = 8.0
> > description = Red Hat Linux 8.0
> > srpm_check = 0
> > 
> > rpm_dirs = /opt/ftp/anonymous/mirrors/ftp.redhat.com/updates/8.0/en/os/i386/
> > src_dirs =
> > 
> > my rh8.0 machines are running athlons and PIII processors (up2date will 
> > just report i686 archs). when i run up2date on this machines i get:
> > 
> > [root@arz rhn]# up2date
> > Traceback (most recent call last):
> >   File "/usr/sbin/up2date", line 801, in ?
> >     main()
> >   File "/usr/sbin/up2date", line 494, in main
> >     up2dateAuth.updateLoginInfo()
> >   File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 112, in 
> > updateLoginInfo
> >     loginInfo = login()
> >   File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 100, in login
> >     loginInfo = rpcServer.doCall(server.up2date.login, systemId)
> >   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
> 
> I got this traceback too (with the 20021018 snapshot) but it was due to
> a user error (I forgot to restart Apache after adding the 8.0 channel)
> so I didn't bother reporting it. Did you make sure to restart Apache?
> (AFAIK in theory you should disable Apache, change the current.conf
> file, then re-enable Apache. Similarly, you should make sure Apache is
> disabled whenever you do anything with cadmin.)

This is also completely correct.

> 
> -Barry K. Nathan <[email protected]>
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.