Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have CentOS 4.4, kernel 2.6.9-55.ELsmp. Originally, I had installed MySQL-4.4.7 from source. It worked great for months until a couple of days ago I read a message on screen stating that needed to restart server to fix a mysql issue. After restarting server, when I try to start MySQL all I get is:
Number of processes running now: 0
071202 12:03:50 mysqld restarted
Number of processes running now: 0
071202 12:03:50 mysqld restarted
Number of processes running now: 0
071202 12:03:50 mysqld restarted
Number of processes running now: 0
071202 12:03:50 mysqld restarted
Number of processes running now: 0
071202 12:03:50 mysqld restarted
Number of processes running now: 0
071202 12:03:50 mysqld restarted
Number of processes running now: 0
071202 12:03:50 mysqld restarted
Number of processes running now: 0
071202 12:03:50 mysqld restarted
I upgraded with a fresh installation to Mysql-5.0.45.tar.gz, but once I try to start mysql, same error happens. What can I do to fix it please. This is a production server. Thanks God I have a backup of mysql database.
What can I do to fix this problem. All help is greatly appreciated.
I upgraded with a fresh installation to Mysql-5.0.45.tar.gz, but once I try to start mysql, same error happens. What can I do to fix it please. This is a production server. Thanks God I have a backup of mysql database.
What can I do to fix this problem. All help is greatly appreciated.
Did you run "make uninstall" in the source directory for the previous mysql version? If not, you may have all kinds of conflicting files.
I recommend running "make uninstall" in the newest version first, and the "make uninstall" in the older version. Then try building the newer version again.
Also, pore over your mysqld.log file for any other pertinent information. You might find interesting information in "/var/log/debug". There is always useful information in the output of "dmesg" and "/var/log/messages".
Thanks for you help. I uninstaled both versions, 5.0.45 first, then 4.0.27. Then reinstalled mysql-5.0.45. Unfortunately, it still doesn't start. Here is the mysqld.log. Please, advice.
071129 23:28:20 mysqld started
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
071129 23:28:20 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
071129 23:28:20 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
071129 23:28:21 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
071129 23:28:21 InnoDB: Started; log sequence number 0 0
071129 23:28:21 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.22' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
071130 2:49:47 [Note] /usr/libexec/mysqld: Normal shutdown
071202 20:49:12 mysqld started
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
071202 20:50:03 InnoDB: Started; log sequence number 0 43655
071202 20:50:03 [Note] /usr/local/mysql/libexec/mysqld: Normal shutdown
071202 20:50:03 [Note] /usr/local/mysql/libexec/mysqld: ready for connections.
Version: '5.0.45' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
071202 20:50:03 InnoDB: Starting shutdown...
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
071202 21:02:02 mysqld started
071202 21:02:04 InnoDB: Started; log sequence number 0 43655
071202 21:02:05 [Note] /usr/local/mysql/libexec/mysqld: ready for connections.
Version: '5.0.45' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
071202 21:07:20 [Note] /usr/local/mysql/libexec/mysqld: Normal shutdown
Thanks for you help. I uninstaled both versions, 5.0.45 first, then 4.0.27. Then reinstalled mysql-5.0.45. Unfortunately, it still doesn't start. Here is the mysqld.log. Please, advice.
Some slackware users solved their problem by changing the ownership of some files and directories to the mysql user:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.