serious mysql problem after upgrade to 10.04

[whitefawn]

Morning people. I will appreciate any help here.

I upgraded from Kubuntu 9.10 to 10.04. 32 bit.

The install had not finished as it barked at tripwire config. I have had to stop it and continue from command prompt.

More or less the install went OK .
After the install, mysql 5.1 does not want to start or stop. Commands

/etc/init.d/mysql stop ( or 'stop mysql' , or service mysql stop' )
/etc/init.d/mysql start

do not finish - do not return to command prompt. No log messages insyslog or mysql logs.

say, I do 'service mysql start', the command does not return, I click Ctrl+C, then repeat the command. This displays : 'start: Job is already running: mysql'. of course mysql is not running.

I've tried to remove and reinstall the packages. No result. There is 'stop mysql' command in one of install scripts that hangs.

Any solution that does not include reinstall ?

Thanks in advance for your help.

[mourngrym1969]

First, backup your data directories for MySQL (your actual databases)... that way, anything you do can be recovered from by just copying these back into their correct locations.

Once you do that, I would reinstall MySQL, making sure it does it completely:

'sudo apt-get install mysqlserver --fix-missing --fix-broken --assume-yes'

This will download and re-install the server. After that is complete, run through the initial mysql configuration (add your users, etc). After that, stop the server, copy over your data files to the old location and restart MySQL. If you created the same users with the same passwords, your databases should all start up and be useable.

Let me know if you have any questions or need more detail.

Mourn

[whitefawn]

I assume you've been talking about mysql-server. I tried it before, didn't help.

[jaxson]

Yes I have the same problem with mysql-server. I upgraded from Karmic where mysql-server was working properly. When I try to start or stop it just hangs until I kill it.
If I try to connect it gives:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

So it's obviously not running. I have not found anything in the logs(messages or syslog) for this either.

Point me in the right direction please.

[bryxal]

Same problem here.... if anyone has suggestions, I would love to hear them. This one was upgraded from Beta 2
there is no PID file. no process that I can find. Nothing gets written to either mysql.err or mysql.log.
somethings get written to syslog, I believe its with the debian sys admin permissions not working anymore..... I tried resetting those with a startup init file as per resetting the root password on mysql.com but still doesn't seem to work.

any other leads would be appreciated.

Thanks

[vewert]

I am having the same problem after upgrading from 9.10 to 10.04. MySQL server does start on boot, and command hangs when I try to start and/or restart it.

I tried:
sudo /etc/init.d/mysql start
sudo service mysql start
sudo mysqld

and maybe a few more along with the stop and restart equivalents and finally did manage to get it to start, but there is definitely a problem.

[biffnix]

Yes, please help. I have the same problem, and it's huge! My LAMP server (Karmic Koala) was upgraded this morning to Lucid, and MySQL fails.

If I type: /etc/init.d/mysql start

Then I see this:

Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mysql start

Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the start(8) utility, e.g. start mysql start: Job failed to start

If I type: service mysql start

Then I get:

start: Job failed to start


If I just type: mysql

Then I get:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Please HELP! My server is dead in the water until I can get MySQL back on its feet!

[darkpills]

Hello,

We had the same problem over here after the ubuntu upgrade.

We solved this by re-creating mysqld.pid with good rights :

touch /var/run/mysqld/mysqld.pid

If it does not solve your problem, try the more verbose command:

sudo /usr/bin/mysqld_safe --user=mysql

Good luck!

[biffnix]

Hello,

We had the same problem over here after the ubuntu upgrade.

We solved this by re-creating mysqld.pid with good rights :

touch /var/run/mysqld/mysqld.pid

If it does not solve your problem, try the more verbose command:

sudo /usr/bin/mysqld_safe --user=mysql

Good luck!

When I tried: touch var/run/mysqld/mysqld.pid

I got: touch: cannot touch `/var/run/mysqld/mysqld.pid' : No such file or directory

When I tried: /usr/bin/mysqld_safe --user=mysql

I got:

root@squishbox:/var/run# /usr/bin/mysqld_safe --user=mysql
100504 09:43:17 mysqld_safe Logging to '/var/lib/mysql/squishbox.squish.us.err'.
100504 09:43:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

And now it's just sitting there. I think mysqld_safe must be running, as Wordpress came back up (although the gallery2 links seem broken). You can see for yourself at http://www.squish.us .

So what do I do to make sure it launches at startup properly? Still doesn't seem to be doing things correctly.

[woj2tas]

Try to run

$ sudo mysqld_safe &

it will turn on Your database.