mysql botched

[Red Squirrel]

I did the non smart move of performing an upgrade on my debian server. with apt-get it's so easy I figured I might as well regularly do it to stay up to date. BAD IDEA.

Somehow, it botched a bunch of stuff that I managed to fix, but mysql, no go. I can't start the server, or connect to it (obviously, if it ain't started). I can't even access it directly using the mysql command. I can't even find the mysql folder that contains the data folder and all that... I have a feeling the "upgrade" blew away the mysql.

But if it did, it did not bother to remove the traces in php, since php is still trying to connect to it. It's basically acting as if it's just not started, but I can't find the folder or the binary anywhere on the server to start it. Usually there would be a mysql folder in /usr/share or /usr/local or directly in /usr/ etc... looked all over.

Just wondering has anyone ever experienced such issues in debian when doing a full upgrade? If yes how did you fix it?

 

[Red Squirrel]

OMG I never figured it would of been that easy. I just did apt-get install mysql-server and everything magically worked. I only knew to try that because I was trying to setup a php/mysql/apache server at work for development and had read somewhere to install that to make it work, along with a bunch of other things. Given I was in a position to format the server, I had to try a few things first, and it just... worked. And all my data is still there. I have no clue where it's stored though...

 

[Armitage]

Your data is probably under /var/lib/mysql

To find out for sure use the command mysqladmin variables and look for the datadir entry