[WBEL-users] Circularity in YUM

[Kay Diederichs]

david wrote:
> Folks
> 
> I am maintaining several systems with WBEL.  Although I tried to perform 
> identical initial installations, the process was manual so I'm sure some 
> differences occurred.  In one and only one of the systems, every time I 
> perform a YUM update, I receive a message notice from the Cron job I use 
> to perform updates.  All of these systems are servers, and no GUI is 
> installed, as far as I know.
> 
> 
> Issuing /usr/bin/yum -y -e 0 update
> Gathering header information file(s) from server(s)
> Server: White Box Enterprise Linux 3.0 - i386 - Base
> Server: White Box Enterprise Linux 3.0 - i386 - Released Updates
> Finding updated packages
> Downloading needed headers
> Resolving dependencies
> .....identical dependency loop exceeded
> package up2date-gnome needs up2date = 4.2.5 (not provided)
> package XFree86-Xvfb needs XFree86 = 4.3.0-62.EL (not provided)
> package redhat-config-network needs redhat-config-network-tui = 1.2.60-1 
> (not provided)
> Issuing /usr/bin/yum -y -e 0 clean
> Gathering header information file(s) from server(s)
> Server: White Box Enterprise Linux 3.0 - i386 - Base
> Server: White Box Enterprise Linux 3.0 - i386 - Released Updates
> Finding updated packages
> Cleaning packages and old headers
> 
> On other systems, I get perfectly clean results.
> 
> On ALL systems, I am using yum.conf as follows:
> 
> ---------------------------  begin yum.conf
> 
> 
> [main]
> cachedir=/var/cache/yum
> debuglevel=2
> logfile=/var/log/yum.log
> pkgpolicy=newest
> distroverpkg=whitebox-release
> tolerant=1
> exactarch=1
> retries=20
> failovermethod=roundrobin
> gpgcheck=1
> 
> [base]
> name=White Box Enterprise Linux $releasever - $basearch - Base
> baseurl=ftp://mirror.physics.ncsu.edu/pub/whitebox/$releasever/en/os/$basearch/ 
> 
> # ftp://ftp.esat.net/mirrors/whiteboxlinux.org/$releasever/en/os/$basearch/
> # 
> ftp://ftp.kspei.com/mirrors/whiteboxlinux.org/whitebox/$releasever/en/os/$basearch/ 
> 
> # ftp://ftp.jach.hawaii.edu/pub/linux/whitebox/$releasever/en/os/$basearch/
> # 
> ftp://gd.tuwien.ac.at/opsys/linux/whiteboxlinux/$releasever/en/os/$basearch/ 
> 
> # 
> ftp://ftp.opensourcemirrors.org/linux/whitebox/$releasever/en/os/$basearch/
> #        http://whitebox.phantomhosting.com/$releasever/en/os/$basearch/
> 
> [updates-released]
> name=White Box Enterprise Linux $releasever - $basearch - Released Updates
> baseurl=ftp://mirror.physics.ncsu.edu/pub/whitebox/$releasever/en/updates/
> #        
> ftp://ftp.esat.net/mirrors/whiteboxlinux.org/$releasever/en/updates/
> # 
> ftp://ftp.kspei.com/mirrors/whiteboxlinux.org/whitebox/$releasever/en/updates/ 
> 
> #        
> ftp://ftp.jach.hawaii.edu/pub/linux/whitebox/$releasever/en/updates/
> # ftp://gd.tuwien.ac.at/opsys/linux/whiteboxlinux/$releasever/en/updates/
> #        
> ftp://ftp.opensourcemirrors.org/linux/whitebox/$releasever/en/updates/
> #        http://whitebox.phantomhosting.com/$releasever/en/updates/
> 
> ---------------------------  end yum.conf
> 
> Also, on all systems, I performed a yum clean headers to allows the 
> databases to regenerate.
> 
> Help?  Is there some other information I could supply?
> 
> David

David,

I would issue 'rpm -qa' on all systems and compare the output. This way 
you'll find where exactly the systems differ, and you could then 'rpm 
-e' those packages on the misbehaving system that exist in addition to 
the common RPMs.

Kay