Bug #73728 service restart failing when upgrading from old-style rpms to new-style rpms
Submitted: 26 Aug 2014 15:40 Modified: 22 Apr 2015 15:25
Reporter: Ramana Yeruva Email Updates:
Status: Closed Impact on me:
Category:MySQL Package Repos Severity:S3 (Non-critical)
Version:5.7.5 OS:Any
Assigned to: CPU Architecture:Any

[26 Aug 2014 15:40] Ramana Yeruva
install old-style rpms of 5.6.20/5.5.39 gpl
start service with after above installation
now install sles repo file
install *community* packages from above and make sure old-style rpms are replaced correctly with new-style rpms
try to stop service or restart service which is failing

How to repeat:
zypper --non-interactive remove 'MySQL*'
zypper --non-interactive remove 'mysql*'
zypper --non-interactive remove 'maria*' 'postfix'
zypper --non-interactive remove mysql-community-release
zypper --non-interactive remove mysql-enterprise-release
zypper --non-interactive remove mysql-community-release
zypper --non-interactive clean
zypper --non-interactive refresh
zypper --non-interactive remove mysql-community-bench
zypper --non-interactive remove mysql-community-client
zypper --non-interactive remove mysql-community-common
zypper --non-interactive remove mysql-community-devel
zypper --non-interactive remove mysql-community-embedded
zypper --non-interactive remove mysql-community-embedded-devel
zypper --non-interactive remove mysql-community-libs mysql-community-server
zypper --non-interactive remove mysql-community-test
echo "***checking list of mysql-community packages after uninstall****"
zypper --non-interactive search 'mysql*'
zypper --non-interactive remove mysql
zypper --non-interactive remove mysql-client
zypper --non-interactive remove mysql-tools
zypper --non-interactive remove mysql-connector-java
zypper --non-interactive remove mysql-community-source mysql-community-x86_64 mysql-community-release
zypper --non-interactive remove MyODBC-unixODBC
zypper --non-interactive remove bytefx-data-mysql libgda-3_0-mysql libgda-4_0-mysql perl-DBD-mysql php53-mysql postfix-mysql python-mysql rsyslog-module-mysql ruby-mysql mysql-client mysql mysql-connector-java mysql-tools lighttpd-mod_mysql_vhost libmysqlclient-devel libmysqlclient15 libmysqlclient15-32bit libmysqlclient_r15 libmysqlclient_r15-32bit libqt4-sql-mysql libqt4-sql-mysql-32bit akonadi-runtime

rm -rf /var/lib/mysql/ /etc/my.cnf.rpmsave /usr/my.cnf /root/.mysql_secret
zypper clean --all
zypper refresh
vitro16:~/ramana/repository_code # ls MySQL_rpms/5.6.20/gpl/*.rpm
MySQL_rpms/5.6.20/gpl/MySQL-5.6.20-1.sles11.src.rpm              MySQL_rpms/5.6.20/gpl/MySQL-server-5.6.20-1.sles11.x86_64.rpm
MySQL_rpms/5.6.20/gpl/MySQL-client-5.6.20-1.sles11.x86_64.rpm    MySQL_rpms/5.6.20/gpl/MySQL-shared-5.6.20-1.sles11.x86_64.rpm
MySQL_rpms/5.6.20/gpl/MySQL-devel-5.6.20-1.sles11.x86_64.rpm     MySQL_rpms/5.6.20/gpl/MySQL-shared-compat-5.6.20-1.sles11.x86_64.rpm
MySQL_rpms/5.6.20/gpl/MySQL-embedded-5.6.20-1.sles11.x86_64.rpm  MySQL_rpms/5.6.20/gpl/MySQL-test-5.6.20-1.sles11.x86_64.rpm

*****will be adding more details below
[26 Aug 2014 16:00] Ramana Yeruva
Posted by developer:
This behavior atleast needs to documented if not required to fix
[22 Apr 2015 15:25] Daniel So
Added the following step to the instructions for "Replacing MySQL Installed by an RPM from Other Sources," before the steps for installing with the MySQL SLES repo:

2. Stop your MySQL server, if it is running. If the server is running as a service, you can stop it with the following command:

shell> sudo service mysql stop