UPCP - Updating system packages - Conflict

[skratchit]

Hi,

WHM 11.11.0 cPanel 11.15.0-R18264
CENTOS 5 i686 on standard - WHM X v3.1.0

Since 3rd Dec I've been getting the following in my upcp log and I have no idea how to resolve it. Could someone point me in the right direction please?

Updating system packages...Repository base is listed more than once in the configuration
Repository addons is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Setting up Update Process
Setting up repositories
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Resolving Dependencies


<snipped package list to keep post below 10000 characters>


Transaction Summary
=============================================================================
Install      6 Package(s)         
Update     118 Package(s)         
Remove       0 Package(s)         

Total download size: 142 M
Downloading Packages:
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
  file /usr/sbin/sysreport conflicts between attempted installs of sos-1.7-9.1.el5 and sysreport-1.4.3-13.el5
  file /usr/share/sysreport/functions conflicts between attempted installs of sos-1.7-9.1.el5 and sysreport-1.4.3-13.el5

Error Summary
-------------

cheers
Ben

[skratchit]

No ideas anyone? An additional package is in the update list now. I don't want this to grow and grow. If someone could point me in the right direction I'd be very grateful!

Transaction Summary
=============================================================================
Install      6 Package(s)         
Update     119 Package(s)         
Remove       0 Package(s)         

Total download size: 143 M
Downloading Packages:
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
  file /usr/sbin/sysreport conflicts between attempted installs of sos-1.7-9.1.el5 and sysreport-1.4.3-13.el5
  file /usr/share/sysreport/functions conflicts between attempted installs of sos-1.7-9.1.el5 and sysreport-1.4.3-13.el5

[cpanelkenneth]

These errors are from yum. Have you installed any 3rd party RPMs (not counting those cPanel installs)?

The problem is one package is conflicting with another, preventing the upgrade. Sometimes these can be solved by manually removing the conflicting package. Another way to resolve the issue is to forcefully install the new RPM, although that is not encouraged as other problems can arise.

[skratchit]

These errors are from yum. Have you installed any 3rd party RPMs (not counting those cPanel installs)?

The problem is one package is conflicting with another, preventing the upgrade. Sometimes these can be solved by manually removing the conflicting package. Another way to resolve the issue is to forcefully install the new RPM, although that is not encouraged as other problems can arise.

Thanks for your reply Kenneth!

No we haven't installed any third party RPMs (apart from kernel-PAE - we have 8 Gb RAM).

Apart from the initial cPanel install we manually installed Java (jdk-6u2-linux-i586.bin), imapsync (imapsync-1.223.tgz - which required a few additional perl modules) and Rootkit Hunter (rkhunter-1.3.0.tar.gz).

I guess if it's not something obvious I'll open a support ticket with my host.

cheers
Ben

[cpanelkenneth]

What is the sos package, it is what is causing the conflict.

[skratchit]

What is the sos package, it is what is causing the conflict.

I have no idea! It is listed like this in the package lists:

---> Package sos.noarch 0:1.7-9.1.el5 set to be updated

sos                     noarch     1.7-9.1.el5      base              108 k

[cpanelkenneth]

It looks like both those packages do the same, or similar, things:

[root@rhel5current-2 ~]# yum info sos
Loading "rhnplugin" plugin
Loading "installonlyn" plugin
Setting up repositories
rhel-i386-server-5        100% |=========================| 1.4 kB    00:00     
rhel-i386-server-vt-5     100% |=========================| 1.4 kB    00:00     
rhn-tools-rhel-i386-serve 100% |=========================| 1.2 kB    00:00     
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Installed Packages
Name   : sos
Arch   : noarch
Version: 1.7
Release: 9.1.el5
Size   : 381 k
Repo   : installed
Summary: System Support Tools

Description:
SOS is a set of tools that gathers information about system
hardware and configuration. The information can then be used for
diagnostic purposes and debugging. Sos is commonly used to help
support technicians and developers.

[root@rhel5current-2 ~]# yum info sysreport
Loading "rhnplugin" plugin
Loading "installonlyn" plugin
Setting up repositories
rhel-i386-server-5        100% |=========================| 1.4 kB    00:00     
rhel-i386-server-vt-5     100% |=========================| 1.4 kB    00:00     
rhn-tools-rhel-i386-serve 100% |=========================| 1.2 kB    00:00     
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Available Packages
Name   : sysreport
Arch   : noarch
Version: 1.4.3
Release: 13.el5
Size   : 22 k
Repo   : rhel-i386-server-5
Summary: Gathers system hardware and configuration information.

Description:
Sysreport is a utility that gathers information about a system's
hardware and configuration. The information can then be used for
diagnostic purposes and debugging. Sysreport is commonly used to help
support technicians and developers by providing a "snapshot" of a
system's current layout.

On my system, sos was installed during the OS install, but sysreport is not. Likely the same is true in your case (check the output of rpm -q sos and rpm -qa sysreport). If that is the case, it makes we wonder why sysreport is being requested by a yum update. Perhaps CentOS got something wrong?

[skratchit]

A little Googling suggests that sos replaces sysreport in Centos 5.1... but I guess its failing to do so here!

[skratchit]

#rpm -q sos
sos-1.3-1.el5

# rpm -qa sysreport
sysreport-1.4.3-10.el5


erm...

[skratchit]

I did "yum upgrade sysreport" yesterday, to bring that up to date, and then let the automated script run today and yay it all updated.

[cpanelkenneth]

Great! And thanks for the extra info.