Old MySQL Update Stuck?

10 posts / 0 new
Last post
#1 Tue, 08/09/2011 - 02:56
Dingo

Old MySQL Update Stuck?

Hello

I have an old MySQL update stuck in the package updates part of Webmin/Virtualmin.

Package ↓ Description Version
mysql MySQL client programs and shared libraries 5.0.77-4.el5_6.6

I have a newer version of MySQL that was installed from the Atomic repo. The above update fails because the newer version is present.

I have excluded this update from yum so it does not try to update from the command line any more but it will not disappear from Webmin.

Is there anything I can do to get rid of it?

Please be gentle, I am not a Linux guru but do know my way around a little.

Regards

Dingo

Tue, 08/09/2011 - 09:17
andreychek

Howdy,

Can you verify that if you type "yum update" on the command line, it doesn't show any available MySQL updates?

-Eric

Wed, 08/10/2011 - 02:44 (Reply to #2)
Dingo

Hi, thank you for your reply

Yes I can confirm there are no updates. Here is the output from yum update. I excluded the update from Yum after I noticed it failing in VM/WM.

Loaded plugins: allowdowngrade, fastestmirror, priorities
Loading mirror speeds from cached hostfile
* addons: archive.cs.uu.nl
* base: archive.cs.uu.nl
* centosplus: mirror.sov.uk.goscomb.net
* contrib: centos.mirror.transip.nl
* extras: mirror.yourwebhoster.eu
* updates: mirror.nl.leaseweb.net
Excluding Packages in global exclude list
Finished
645 packages excluded due to repository priority protections
Setting up Update Process
No Packages marked for Update

Regards

Dingo

Fri, 08/19/2011 - 12:22 (Reply to #3)
Dingo

Hi again.

Is there any more info you need to help?

Regards

Dingo

Fri, 08/19/2011 - 15:16
sfatula

As far as I have seen, webmin and/or virtualmin caches the yum check-update info in collectinfo process, so, assuming you have those turned on, when they eventually run again, it should go away.

Fri, 08/19/2011 - 19:47 (Reply to #5)
Dingo

Hello

Thank you for the reply.

It has been stuck like this for over 6 months now. I was hoping it would be some sort of cache that may clear eventually but it has not so far. I was hoping that it may be as simple as deleting a cache file or folder that may cure it.

Regards

Dingo

Fri, 08/19/2011 - 21:08
sfatula

I recall I used to have some stuck ones, but that was fixed in a later Virtualmin. You current?

What does cat /etc/yum.repos.d/CentOS-Base.repo show? I presume the mysql is showing from the Centos base, right?

Sat, 08/20/2011 - 18:04 (Reply to #7)
Dingo

Yes I always update to the new releases when they appear & yes it is from the Centos Base. The source is listed as Updates.

Here is the response from /etc/yum.repos.d/CentOS-Base.repo

[root@sb2 admin]# cat /etc/yum.repos.d/CentOS-Base.repo
# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

#released updates
[updates]
name=CentOS-$releasever - Updates
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
priority=1

#packages used/produced in the build but not released
[addons]
name=CentOS-$releasever - Addons
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=addons
#baseurl=http://mirror.centos.org/centos/$releasever/addons/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
priority=1

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
priority=1

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
priority=2

#contrib - packages by Centos Users
[contrib]
name=CentOS-$releasever - Contrib
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib
#baseurl=http://mirror.centos.org/centos/$releasever/contrib/$basearch/
gpgcheck=1
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
priority=2

Regards

Dingo

Sat, 08/20/2011 - 19:42
sfatula

Let's say I updated MySQL with some other repository (in my case Jason Litkas). The beginning of mine looks like this:

[base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os exclude=mysql,apr,http,postfix

baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/

gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5

released updates

[updates] name=CentOS-$releasever - Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates exclude=mysql,apr,http,postfix ...

So, the exclude line works, probably better would be my guess. Seems like you are using priorities, always had trouble with those.

Give it a try, remove anything you don't want to exclude from the exclude lines.

Sun, 08/21/2011 - 10:27 (Reply to #9)
Dingo

Hello

Good news, looks like you hit the nail on the head there.

I had excluded the package using /etc/yum.conf which worked perfectly for yum via command line. It seems wm/vm does not use the excludes in that file.

So I added the line Exclude=mysql to the repo file as you suggested and did a package refresh inside wm/vm and it disappeared. It was still on the main system information screen so clicked on refresh modules and it went away there too.

Thank you very much for your assistance ;o)

Regards

Dingo

Topic locked