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.

[daveman67]

I upgraded from 9.10 to 10.04 and had the same problem - mysql not starting.

Morning people. I will appreciate any help here.
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.

Tried this to give me error messages.

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

and found this in syslog

May  7 12:03:22 saturn mysqld_safe: Starting mysqld daemon with databases from /home/dave/dev/data/mysql
May  7 12:03:22 saturn mysqld: 100507 12:03:22 [Warning] option 'thread_stack': unsigned value 128 adjusted to 131072
May  7 12:03:22 saturn mysqld: 100507 12:03:22 [Warning] The syntax '--log' is deprecated and will be removed in MySQL 7.0. Please use '--general_log'/'--general_log_file' instead.
May  7 12:03:22 saturn mysqld: 100507 12:03:22 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set
May  7 12:03:22 saturn mysqld: 100507 12:03:22 [Note] Plugin 'FEDERATED' is disabled.
May  7 12:03:22 saturn mysqld: /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
May  7 12:03:22 saturn mysqld: 100507 12:03:22 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
May  7 12:03:22 saturn mysqld: 100507 12:03:22  InnoDB: Started; log sequence number 0 2140736324
May  7 12:03:22 saturn mysqld: 100507 12:03:22 [ERROR] /usr/sbin/mysqld: unknown option '--skip-bdb'
May  7 12:03:22 saturn mysqld: 100507 12:03:22 [ERROR] Aborting

Clue was --skip-bdb. When I had run my upgrade I kept the /etc/mysql/my.cnf file, which contains

# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb

Commenting out that option allowed mysql to start again. Remaining errors in the log were fixed by running mysql_upgrade.

This thread was quite useful in pointing out the red herrings in the error output above. http://lists.mysql.com/mysql/216042

Cheers, Dave

[Thomas Gutzmann]

You may also have a look at http://ubuntuforums.org/showthread.php?t=1475798.

HTH

Thomas

[hotbelgo]

http://ubuntuforums.org/showpost.php...75&postcount=6

[mansonthomas]

Hi,

first use the service mysql start/stop instead of /etc/init.d/mysql...

normally if you user /etc/init.d script it complains and tell you to use 'service'.

ex:

thomas@home:/etc/mysql$ sudo /etc/init.d/mysql status
[sudo] password for thomas:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql status

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status mysql
mysql start/running, process 13020



I had a similar issue, of mysql starting and did not return the hand, if you try again you get a message that mysql is running while it's not.

The reason was that in /etc/mysql/my.cnf some directory, files (loggin, bin log, relay log) did not exists.

Also I had an issue on upgrade to 10.04 on a server : see this bug :

https://bugs.launchpad.net/ubuntu/+s....1/+bug/573318

the /etc/mysql/my.cnf disappear on upgrade.

Regards,
Thomas.