MySQL Bugs: #15104: mysql 5.0 will not start on fedora core 4

Bug #15104	mysql 5.0 will not start on fedora core 4
Submitted:	21 Nov 2005 17:20	Modified:	22 Nov 2005 16:55
Reporter:	[ name withheld ]	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0.15	OS:	Linux (Linux Fedora Core 4)
Assigned to:		CPU Architecture:	Any

Description:
I recently downloaded the following rpms and tried to install them on my fedora 4 system:
MySQL-client-5.0.15-0.glibc23.i386.rpm  
MySQL-server-5.0.15-0.glibc23.i386.rpm
MySQL-devel-5.0.15-0.glibc23.i386.rpm   
MySQL-shared-compat-5.0.15-0.i386.rpm
When I try to install them with 'rpm -i MySQL-client-5.0.15-0.glibc23.i386.rpm MySQL-server-5.0.15-0.glibc23.i386.rpm MySQL-shared-compat-5.0.15-0.i386.rpm MySQL-devel-5.0.15-0.glibc23.i386.rpm', the mysql-server rpm gives an error message of 'Starting MySQL ERROR! Couldn't find MySQL manager or server'.  

Everything installs ok, but mysql will not start.  When I try to start it with 'mysqld_safe&' , I get the messages:
STOPPING server from pid file /var/run/mysqld/mysqld.pid
051121 11:09:59  mysqld ended

How to repeat:
Install the following rpms on a fedora core 4 system:
MySQL-client-5.0.15-0.glibc23.i386.rpm  
MySQL-server-5.0.15-0.glibc23.i386.rpm
MySQL-devel-5.0.15-0.glibc23.i386.rpm   
MySQL-shared-compat-5.0.15-0.i386.rpm

start mysqld with 'mysqld_safe&', or via the system services

Suggested fix:
Would like documentation on how to install mysql5 on a fedora core 4 system, or a fix if this truly is a bug...

Thank you for a problem report. It may be similar to http://bugs.mysql.com/bug.php?id=12676. Please, check and inform about the results. Do you use SELinux? (Then you will be forced to switch it off until the fix...)

Thanks for the feedback, but I am not using selinux.

No SELinux. OK. Then for other similar problem and workarounds, please, read http://bugs.mysql.com/bug.php?id=14457. Is it helpful or similar? Please, inform.

I have found the problem.  I had to delete the /etc/init.d/mysql and /etc/my.cnf files, then reinstall to get it to work.  I can understand that my specific my.cnf file would not be compatable with the new version, but init.d/mysql?  Shouldn't it be overwritten with the new version?  Oh, well... Thanks for the help.

Hi!

I was unable to reproduce this bug using 5.0.16 under FC4