[BlueOnyx:23035] Re: yum update 5108R to 5208R problem
Thomas Petersen
thomas at nsd.dk
Sun Jul 28 00:52:49 -05 2019
-----Oprindelig meddelelse-----
Fra: Blueonyx <blueonyx-bounces at mail.blueonyx.it> På vegne af Michael Stauber
Sendt: 25. juli 2019 08:51
Til: blueonyx at mail.blueonyx.it
Emne: [BlueOnyx:23021] Re: yum update 5108R to 5208R problem
Hi Thomas,
> I was trying to upgrade a 5108R tto 5208R thru yum, went well on 4
> other serveres but the last one has a few complains
>
> --> Finished Dependency Resolution
> Error: Package: MySQL-python-1.2.3-0.3.c1.1.el6.x86_64 (base)
> Requires: libmysqlclient_r.so.16()(64bit)
> Available: mysql-libs-5.1.73-8.el6_8.x86_64 (base)
> libmysqlclient_r.so.16()(64bit)
> Installed: mysql-libs-5.5.34-2.el6.x86_64 (installed)
> Not found
> Error: Package: MySQL-python-1.2.3-0.3.c1.1.el6.x86_64 (base)
> Requires: libmysqlclient_r.so.16(libmysqlclient_16)(64bit)
> Available: mysql-libs-5.1.73-8.el6_8.x86_64 (base)
> libmysqlclient_r.so.16(libmysqlclient_16)(64bit)
> Installed: mysql-libs-5.5.34-2.el6.x86_64 (installed)
> Not found
> You could try using --skip-broken to work around the problem
> ** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
> libgudev1-147-2.73.el6_8.2.x86_64 has missing requires of libudev =
> ('0', '147', '2.73.el6_8.2')
> mysql-test-5.5.34-2.el6.x86_64 has missing requires of
> perl(Time::HiRes)
Yeah, this is a nice Catch-22: The newer MySQL is available for 5208R and the older one you have currently installed via PKG is apparently stopping the yum update dead in its tracks.
If you send me the login details (offlist per Email or here at the Compass ticket system: http://support.compassnetworks.com.au/) I'll fix it for you.
Alternatively try this:
Stop MySQLd. Find out where the database directory is. It could be /home/mysql or it could be /var/lib/mysql
Make a copy of that into a safe place and then uninstall the MySQL PKG.
That will reinstall the stock MySQLd. Do the yum update again and once you're on 5208R grab the MySQL-5.5 from Third Party Software and reinstall that. Once that's back in MySQL should start working again.
--
With best regards
Michael Stauber
Thank you, that worked out nicely 😊.
Will there also be an easy way to upgrade from 5208 to 5209 when 5210 is ready?
/Thomas
More information about the Blueonyx
mailing list