Welcome Guest | Login

MySQL - my.cnf prevents startup + killing old PID

I'm new to a Linux environment so I may be missing something simple but ....  

I've just had real trouble getting MySQL to start up cleanly.  It seems that there is a Linux problem which prevents the MySQL server starting cleanly when a my.cnf exists.  See these two mysql tickets:

http://bugs.mysql.com/bug.php?id=29727
http://bugs.mysql.com/bug.php?id=29595

It took me hours to figure out it was simply the *existence* of a my.cnf which was preventing the server start-up.

We're running CentOS but it doesn't seem to be related to a single distro judging by the other MySQL forum reports.

We kind of need to specify some MySQL server config options but I'm not sure how to do it now!

Any ideas?

2008-04-03 12:59 AM

Hello,

I checked the status of mysql on the server and found that it was running fine.

>>I've just had real trouble getting MySQL to start up cleanly. It seems that there is a Linux problem which prevents the >>MySQL server starting cleanly when a my.cnf exists.

I added the following lines in /etc/my.cnf file
=
[mysqld]
set-variable = max_connections=500
max_allowed_packet=16M
safe-show-database
log-slow-queries
=

And then restarted mysql. I didn't face any issues and the mysql service was up without any issues.

2008-04-03 03:20 AM

Regards,
Rahul

Hello Guest! In order to post you must be an active client with us, please log in or sign up today!