MySQL update failed
-
- Forum User
- Posts: 5
- Joined: Wed Nov 21, 2012 2:38 pm
- Location: Kelowna, BC
MySQL update failed
Good Morning,
My Atomic Secured Linux Control Panel informed me that there was a new update and I used yum list updates to find that there was an update for MySQL server available. Everything went normally, as it has done before, except that this time, it gave me the following result:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[root@zeus ~]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* asl-3.0: www3.atomicorp.com
* atomic: www3.atomicorp.com
* base: mirror.its.sfu.ca
* extras: mirror.its.sfu.ca
* updates: mirror.its.sfu.ca
Excluding Packages in global exclude list
Finished
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package mysql.x86_64 0:5.5.28-13.el5.art set to be updated
---> Package mysql-libs.x86_64 0:5.5.28-13.el5.art set to be updated
---> Package mysql-server.x86_64 0:5.5.28-13.el5.art set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
=====================================================================================================================================================================
Package Arch Version Repository Size
=====================================================================================================================================================================
Updating:
mysql x86_64 5.5.28-13.el5.art atomic 7.5 M
mysql-libs x86_64 5.5.28-13.el5.art atomic 1.1 M
mysql-server x86_64 5.5.28-13.el5.art atomic 13 M
Transaction Summary
=====================================================================================================================================================================
Install 0 Package(s)
Upgrade 3 Package(s)
Total download size: 21 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): mysql-libs-5.5.28-13.el5.art.x86_64.rpm | 1.1 MB 00:00
(2/3): mysql-5.5.28-13.el5.art.x86_64.rpm | 7.5 MB 00:01
(3/3): mysql-server-5.5.28-13.el5.art.x86_64.rpm | 13 MB 00:02
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 3.4 MB/s | 21 MB 00:06
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 signature: NOKEY, key ID 4520afa9
atomic/gpgkey | 1.3 kB 00:00
Public key for mysql-server-5.5.28-13.el5.art.x86_64.rpm is not installed
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have never seen that a public key was required, does anyone3 know what this is about and how to resolve this?
Thanks,
Peter
My Atomic Secured Linux Control Panel informed me that there was a new update and I used yum list updates to find that there was an update for MySQL server available. Everything went normally, as it has done before, except that this time, it gave me the following result:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[root@zeus ~]# yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* asl-3.0: www3.atomicorp.com
* atomic: www3.atomicorp.com
* base: mirror.its.sfu.ca
* extras: mirror.its.sfu.ca
* updates: mirror.its.sfu.ca
Excluding Packages in global exclude list
Finished
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package mysql.x86_64 0:5.5.28-13.el5.art set to be updated
---> Package mysql-libs.x86_64 0:5.5.28-13.el5.art set to be updated
---> Package mysql-server.x86_64 0:5.5.28-13.el5.art set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
=====================================================================================================================================================================
Package Arch Version Repository Size
=====================================================================================================================================================================
Updating:
mysql x86_64 5.5.28-13.el5.art atomic 7.5 M
mysql-libs x86_64 5.5.28-13.el5.art atomic 1.1 M
mysql-server x86_64 5.5.28-13.el5.art atomic 13 M
Transaction Summary
=====================================================================================================================================================================
Install 0 Package(s)
Upgrade 3 Package(s)
Total download size: 21 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): mysql-libs-5.5.28-13.el5.art.x86_64.rpm | 1.1 MB 00:00
(2/3): mysql-5.5.28-13.el5.art.x86_64.rpm | 7.5 MB 00:01
(3/3): mysql-server-5.5.28-13.el5.art.x86_64.rpm | 13 MB 00:02
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 3.4 MB/s | 21 MB 00:06
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 signature: NOKEY, key ID 4520afa9
atomic/gpgkey | 1.3 kB 00:00
Public key for mysql-server-5.5.28-13.el5.art.x86_64.rpm is not installed
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have never seen that a public key was required, does anyone3 know what this is about and how to resolve this?
Thanks,
Peter
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4149
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: MySQL update failed
You might have hit the mirrors while they were still syncing. So flush your cache and try again:
yum clean all
yum upgrade mysql
yum clean all
yum upgrade mysql
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
-
- Forum User
- Posts: 5
- Joined: Wed Nov 21, 2012 2:38 pm
- Location: Kelowna, BC
Re: MySQL update failed
I cleaned my cache and tried to upgrade mySQL. Apparently, there are no updates available now - neither when I use yum list updates nor are there any indicated on my Atomic Secured Linux CP ...
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4149
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: MySQL update failed
What version is installed on your system? Perhaps you have yum setup to automatically update the system, or someone else updated it? 5.5.28-13 is the latest.
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
Re: MySQL update failed
I also have a MySQL Upgrade problem but not the "public key" issue listed above.
My issue is package conflict?
My issue is package conflict?
Code: Select all
# yum upgrade mysql
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* asl-3.0: www3.atomicorp.com
* atomic: www3.atomicorp.com
* base: mirrors.sin3.sg.voxel.net
* extras: mirrors.sin3.sg.voxel.net
* updates: mirrors.sin3.sg.voxel.net
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: mysql = 5.1.54-1.el5.art for package: mysql-server
---> Package mysql.i386 0:5.5.29-14.el5.art set to be updated
--> Processing Dependency: mysql-libs = 5.5.29-14.el5.art for package: mysql
--> Running transaction check
---> Package mysql-libs.i386 0:5.5.29-14.el5.art set to be updated
---> Package mysql-server.i386 0:5.5.29-14.el5.art set to be updated
--> Processing Dependency: libaio.so.1(LIBAIO_0.4) for package: mysql-server
--> Processing Dependency: libaio.so.1 for package: mysql-server
--> Processing Dependency: libaio.so.1(LIBAIO_0.1) for package: mysql-server
--> Running transaction check
---> Package libaio.i386 0:0.3.106-5 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
============================================================================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================================================================
Updating:
mysql i386 5.5.29-14.el5.art atomic 7.6 M
Installing for dependencies:
libaio i386 0.3.106-5 base 19 k
Updating for dependencies:
mysql-libs i386 5.5.29-14.el5.art atomic 1.1 M
mysql-server i386 5.5.29-14.el5.art atomic 13 M
Transaction Summary
============================================================================================================================================================================================================
Install 1 Package(s)
Upgrade 3 Package(s)
Total size: 22 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Check Error:
file /usr/lib/mysql/libmysqlclient.so.18.0.0 from install of mysql-libs-5.5.29-14.el5.art.i386 conflicts with file from package mysqlclient18-5.5.28-6.el5.art.i386
Error Summary
-------------
# exit
They say that good intentions, pave the road to hell;
If a thing is not worth doing, it's not worth doing well.
If a thing is not worth doing, it's not worth doing well.
-
- Atomicorp Staff - Site Admin
- Posts: 8355
- Joined: Wed Dec 31, 1969 8:00 pm
- Location: earth
- Contact:
Re: MySQL update failed
You wouldnt need mysqlclient18 and mysql-libs-5.5.29. They're the same mysql 5.5 client library
Re: MySQL update failed
Thank you for your reply.
How do I solve the conflict and upgrade MySQL?
Will this version of MySQL conflict with my current PHP Version: 5.2.17 or should I upgrade that first?
How do I solve the conflict and upgrade MySQL?
Will this version of MySQL conflict with my current PHP Version: 5.2.17 or should I upgrade that first?
They say that good intentions, pave the road to hell;
If a thing is not worth doing, it's not worth doing well.
If a thing is not worth doing, it's not worth doing well.
-
- Atomicorp Staff - Site Admin
- Posts: 8355
- Joined: Wed Dec 31, 1969 8:00 pm
- Location: earth
- Contact:
Re: MySQL update failed
Remove the mysqlclient18 package
Re: MySQL update failed
See https://www.atomicorp.com/forum/viewtop ... f=1&t=5941 for follow-up on MySQL issues.scott wrote:Remove the mysqlclient18 package
They say that good intentions, pave the road to hell;
If a thing is not worth doing, it's not worth doing well.
If a thing is not worth doing, it's not worth doing well.