MySQL Bugs: #10858: 3.23.52-Max is not stop during upgrade to MySQL 4.1.11

Bug #10858	3.23.52-Max is not stop during upgrade to MySQL 4.1.11
Submitted:	25 May 2005 11:27	Modified:	2 Feb 2013 14:41
Reporter:	Dino Tsoumakis	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S4 (Feature request)
Version:	4.1.11 (and higher)	OS:	Linux (SuSE 8.1 (2.4.21, i686))
Assigned to:		CPU Architecture:	Any

Description:
If I try to install MySQL-server-4.1.11-0.i386.rpm having an running Installation of mysql-Max-3.23.52-106.i586.rpm (default SuSE 8.1 Package).
The Installation doesn't quit the old server processes.
Because of that the new Server cannot be started.

I always have to kill the running processes of the old server manually and then restart MySQL 4.1 server.

Everything else is fine. The old rpm is removed and the new one is completly installed.
I had this problem several times on SuSE 8.1 Installations running the default SuSE mysql-Max-3.23.52-106.i586.rpm.

BTW: I also had the same problem with the latest mysql server version (MySQL-server-4.1.12-1.i386.rpm). MySQL-client, MySQL-shared and MySQL-devel have been also updated of course.

How to repeat:
Install a default SuSE 8.1 with the default SuSE 8.1 MySQL Packages and try to update to MySQL 4.1 using the latest MySQL-server-4.1.12-1.i386.rpm (and the RPMs for client, shared and devel).

rpm -Uvh MySQL*.rpm

Suggested fix:
Kill the mysql-Max server processes completly before the new server version is started.

typo in Synopsis fixed

Please see how it works these days:
http://dev.mysql.com/doc/refman/5.6/en/linux-installation-rpm.html

"In MySQL 5.6, during a new installation, the server boot scripts are installed, but the MySQL server is not started at the end of the installation, since the status of the server during an unattended installation is not known.

In MySQL 5.6, during an upgrade installation using the RPM packages, if the MySQL server is running when the upgrade occurs, the MySQL server is stopped, the upgrade occurs, and the MySQL server is restarted. If the MySQL server is not already running when the RPM upgrade occurs, the MySQL server is not started at the end of the installation."