LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   Not able to login to mysql (https://www.linuxquestions.org/questions/linux-server-73/not-able-to-login-to-mysql-4175451908/)

TB0ne 03-13-2013 08:44 AM

Quote:

Originally Posted by suresh.k (Post 4910529)
I don't have much experience on mysql, so i din'd understand very much from your links
Can u please briefly explain how to resolve.

We did, but you don't understand the answer. And as you've been asked several times in the past, you need to spell out your words.

Since you want to be spoon-fed:
  • You posted the question, then went on vacation. This obviously can't be that important.
  • Your logs are plainly telling you, that you have corrupted data, possibly from an incorrect DB shutdown.
  • The logs also provided you links to the MySQL site (which kirukan even pointed you to). Those links have several possible solutions.
  • You've been told to start mysql with force recovery enabled.
  • You've not done or tried any of the possible solutions, and don't even want to be bothered to read/understand what was posted.
We can't make things more plain. If you want someone to come type commands in for you, then you need to find a consultant and pay them. Otherwise, since you are the administrator, this will involve you showing some effort on your part. You seem to have left a production database down for about two weeks.

suresh.k 03-19-2013 02:13 AM

Quote:

Originally Posted by Habitual (Post 4910639)
Post #6 gives detailed and exact instructions how to fix this issue.

I have already followed that procedure but i cant get it,
I posted the error which iam getting after executing below command
#mysqld_safe --skip-grant-tables &
Quote:

kirukan is merely asking if you've searched through the mysql bug system.

All 3 links should be bookmarked and read slowly.
Ok i will read those links thoroughly and then i get back u

suresh.k 03-19-2013 02:16 AM

Quote:

Originally Posted by TB0ne (Post 4910737)
We did, but you don't understand the answer. And as you've been asked several times in the past, you need to spell out your words.

Since you want to be spoon-fed:
  • You posted the question, then went on vacation. This obviously can't be that important.
  • Your logs are plainly telling you, that you have corrupted data, possibly from an incorrect DB shutdown.
  • The logs also provided you links to the MySQL site (which kirukan even pointed you to). Those links have several possible solutions.
  • You've been told to start mysql with force recovery enabled.
  • You've not done or tried any of the possible solutions, and don't even want to be bothered to read/understand what was posted.
We can't make things more plain. If you want someone to come type commands in for you, then you need to find a consultant and pay them. Otherwise, since you are the administrator, this will involve you showing some effort on your part. You seem to have left a production database down for about two weeks.

This is not an production database server.

TB0ne 03-19-2013 09:06 AM

Quote:

Originally Posted by suresh.k (Post 4914285)
This is not an production database server.

Not since it's been down for weeks it isn't. And again, have you tried/done ANYTHING that's been suggested to you?? The errors you posted tell you VERY CLEARLY, that you need to start MySQL with force recovery. You were given links on how to do it. Have you actually DONE IT YET???

From the MySQL forums, where you could have easily looked this error up weeks ago:
http://dev.mysql.com/doc/refman/5.5/...-recovery.html

Since you apparently don't want to read anything, the instructions on the page are VERY SIMPLE:
Quote:

Originally Posted by MySQL Website
For example, you can add the following line to the [mysqld] section of your option file before restarting the server:
Code:

  [mysqld]
  innodb_force_recovery = 4


That option file is the my.cnf file. You want to put in a "6".

suresh.k 03-21-2013 12:38 AM

Quote:

Originally Posted by TB0ne (Post 4914494)
Not since it's been down for weeks it isn't. And again, have you tried/done ANYTHING that's been suggested to you?? The errors you posted tell you VERY CLEARLY, that you need to start MySQL with force recovery. You were given links on how to do it. Have you actually DONE IT YET???

From the MySQL forums, where you could have easily looked this error up weeks ago:
http://dev.mysql.com/doc/refman/5.5/...-recovery.html

Since you apparently don't want to read anything, the instructions on the page are VERY SIMPLE:

That option file is the my.cnf file. You want to put in a "6".

Thank you very much
I did it.
I added innodb_force_recovery = 6 in mysqld section in my.cnf file.

And i taken backup of all Databases and freshly installed mysql server.
Now it is Working fine.

Once Again thank you very much for your solutions.

Thanks
Suresh

TB0ne 03-21-2013 08:36 AM

Quote:

Originally Posted by suresh.k (Post 4915699)
Thank you very much
I did it.
I added innodb_force_recovery = 6 in mysqld section in my.cnf file.

And i taken backup of all Databases and freshly installed mysql server.
Now it is Working fine.

There was absolutely no reason to remove/reinstall MySQL. All you had to do is add the option to the file, which is what you were being told from the very beginning. Don't forget to remove it, since you don't normally want it to run.


All times are GMT -5. The time now is 01:11 AM.