Looks like this was due to corrupted tables, and there's no indication
as to why they were corrupted.
Kayode, thanks for sharing all the valuable data.
Closing this bug as invalid.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Incomplete = Invalid
--
package mysql-server-5.1
I could not backup the database with the instructions given.
Eventually on the advise of a friend I moved the database:
sudo mv /var/lib/mysql /var/lib/mysql.corrupted
after doing:
sudo apt-get purge mysql-server-5.1
then I was able to reinstall the server:
sudo apt-get install
Please find below the transactions on my terminal with trying to purge
and reinstall the server. Hope it makes sense to someone:
kay...@ubuntu:~$ mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version:
Then two minutes later, without doing anything new:
kay...@ubuntu:~$ mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.1.41-3ubuntu12.6 (Ubuntu)
Type 'help;' or '\h' for help. Type '\c' to clear the current
Even sudo-apt-get remove mysql-server-5.1 did not work:
kay...@ubuntu:~$ sudo apt-get purge mysql-server-5.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
Kayode, thanks for continuing to try to solve this issue.
The databases are stored in /var/lib/mysql
To back it up, do
sudo tar -czf backup-mysql.tar.gz -C /var/lib mysql
If the tarball of those database files is small enough, you can attach
it here, and I will send the crash bug upstream to
Thanks but the purging and installing the mysql-server-5.1 did not help.
My databases were not dropped. I tried dropping one of them after I
login to mysql, then the server was gone as the error recurred.
I would be glad to send my databases to you guys to help find the bug
and help others in
Tried forcing InnoDB recovery by adding innodb_force_recovery = 4 to
my.cnf file under the section [mysqld] as suggested in
http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html but it did
not help.
No change in the grep mysql /var/log/syslog output:
Aug 16 03:26:46 ubuntu
Kayode, thanks for the updates.
The hard innodb crash that you pasted in comment #4 is particularly
concerning.
You may want to try backing up your system, and doing
*** THIS STEP WILL DELETE ALL OF YOUR DATA FILES ***
apt-get purge mysql-server-5.1
apt-get install mysql-server-5.1
And then
Hi Kayode, thanks for reporting this and working with us to make Ubuntu
better!
Can you please paste the output of
'sudo stop mysql'
and also any error messages printed by mysql in /var/log/syslog right
after that? The best way would be to upload the output of
grep mysql /var/log/syslog
in a
This is the output of grep mysql /var/log/syslog:
usr/bin/mysql
Aug 15 19:28:10 ubuntu /etc/mysql/debian-start[32460]: Looking for 'mysqlcheck'
as: /usr/bin/mysqlcheck
Aug 15 19:28:10 ubuntu /etc/mysql/debian-start[32460]: This installation of
MySQL is already upgraded to 5.1.41, use --force if
Don't know if this would be of any help. I copied it from the error.log
-/var/log/mysql/error.log:
100815 19:28:45 InnoDB: Started; log sequence number 1 637983031
InnoDB: Starting in background the rollback of uncommitted transactions
InnoDB: Cleaning up trx with id 0 1738733
100815 19:28:45
The output of grep mysql /var/log/syslog after the error generated by
sudo mysql stop:
usr/bin/mysql
Aug 15 19:28:10 ubuntu /etc/mysql/debian-start[32460]: Looking for 'mysqlcheck'
as: /usr/bin/mysqlcheck
Aug 15 19:28:10 ubuntu /etc/mysql/debian-start[32460]: This installation of
MySQL is
** Attachment added: .etc.apparmor.d.usr.sbin.mysqld.txt
https://bugs.launchpad.net/bugs/617678/+attachment/1489145/+files/.etc.apparmor.d.usr.sbin.mysqld.txt
** Attachment added: AptOrdering.txt
https://bugs.launchpad.net/bugs/617678/+attachment/1489146/+files/AptOrdering.txt
**
14 matches
Mail list logo
