View previous topic :: View next topic |
Author |
Message |
simbad Senior Member
Joined: 30 Jun 2011 Posts: 106
|
Posted: Fri Jun 01, 2012 12:00 pm Post subject: mysql update bug |
|
|
After update mysql x68 & x64 we have Bug to stat mysql. Can you please check
Click this button to start the MySQL database server on your system with the command cd /usr ; (/usr/bin/safe_mysqld || /usr/bin/mysqld_safe) &. This Webmin module cannot administer the database until it is started. |
|
Back to top |
|
gerasimos_h Site Admin
Joined: 09 Aug 2007 Posts: 1757 Location: Greece
|
Posted: Fri Jun 01, 2012 5:33 pm Post subject: |
|
|
did you upgrade mysql-data too?
What /var/lib/mysql/$(hostname).err says?
gerasimos_h _________________ Superb! Mini Server Project Manager
http://sms.it-ccs.com |
|
Back to top |
|
simbad Senior Member
Joined: 30 Jun 2011 Posts: 106
|
Posted: Fri Jun 01, 2012 6:03 pm Post subject: |
|
|
i have upgrade only packet in update,... and try with new install,... it is the same problem.
root@xenya:/var/lib/mysql# pico xenya.err
UW PICO 5.04 File: xenya.err
120601 19:35:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120601 19:35:55 InnoDB: Compressed tables use zlib 1.2.6
120601 19:35:55 InnoDB: Using Linux native AIO
120601 19:35:55 InnoDB: Initializing buffer pool, size = 128.0M
120601 19:35:55 InnoDB: Completed initialization of buffer pool
120601 19:35:55 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120601 19:35:55 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
120601 19:35:55 InnoDB: Waiting for the background threads to start
120601 19:35:56 InnoDB: 1.1.8 started; log sequence number 1589339
120601 19:35:56 [Note] Recovering after a crash using mysql-bin
120601 19:35:56 [Note] Starting crash recovery...
120601 19:35:56 [Note] Crash recovery finished.
120601 19:35:56 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
120601 19:35:56 [Note] - '0.0.0.0' resolves to '0.0.0.0';
120601 19:35:56 [Note] Server socket created on IP: '0.0.0.0'.
120601 19:35:56 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect key file for table '$
120601 19:35:56 mysqld_safe mysqld from pid file /var/lib/mysql/xenya.pid ended |
|
Back to top |
|
gerasimos_h Site Admin
Joined: 09 Aug 2007 Posts: 1757 Location: Greece
|
Posted: Fri Jun 01, 2012 6:42 pm Post subject: |
|
|
This was an upgrade from mysql-5.1.63?
gerasimos_h _________________ Superb! Mini Server Project Manager
http://sms.it-ccs.com |
|
Back to top |
|
gerasimos_h Site Admin
Joined: 09 Aug 2007 Posts: 1757 Location: Greece
|
Posted: Fri Jun 01, 2012 6:55 pm Post subject: |
|
|
I can recreate it , if I upgrade mysql-data package, that's normal...
Upgrading only mysql package from 5.1.63 -> 5.5.x I have no problems.
gerasimos_h _________________ Superb! Mini Server Project Manager
http://sms.it-ccs.com |
|
Back to top |
|
simbad Senior Member
Joined: 30 Jun 2011 Posts: 106
|
Posted: Fri Jun 01, 2012 7:26 pm Post subject: |
|
|
ok, what can i do now to fix this? |
|
Back to top |
|
gerasimos_h Site Admin
Joined: 09 Aug 2007 Posts: 1757 Location: Greece
|
Posted: Sat Jun 02, 2012 12:23 am Post subject: |
|
|
remove
/var/lib/mysql/mysql/user.MYI
/var/lib/mysql/mysql/user.MYD
and re-install mysql-data package.
or if you have your old databases before upgrading mysql-data package restore them.
gerasimos_h _________________ Superb! Mini Server Project Manager
http://sms.it-ccs.com |
|
Back to top |
|
simbad Senior Member
Joined: 30 Jun 2011 Posts: 106
|
Posted: Sat Jun 02, 2012 9:30 am Post subject: |
|
|
What happens to my databases and with databases of users?
Why has this happened? The update has been poorly prepared? |
|
Back to top |
|
gerasimos_h Site Admin
Joined: 09 Aug 2007 Posts: 1757 Location: Greece
|
Posted: Sat Jun 02, 2012 9:52 am Post subject: |
|
|
The initial database, (mysql) which has all users permissions has user tables as user.MYI.new and user.MYD.new, so in case of an upgrade it will not replace user table, and you end up with mysql database v5.5 and user table v5.1.
That it's indent for a new install, and it's going to take years I believe to switch to another branch.
Usually a server has it's databases already so no need to upgrade mysql-data package, only mysql package and run 'mysql_upgrade' to upgrade tables.
Same problem happened away back when we switch from mysql-5.0.x to mysql-5.1.x
I'll put mysql-data to excludes in slapt-get to ignore it.
gerasimos_h _________________ Superb! Mini Server Project Manager
http://sms.it-ccs.com |
|
Back to top |
|
|