MySQL Forums
Forum List  »  Other Migration

[DONE] Fail to Login after Migration
Posted by: Fabian Zünd
Date: October 18, 2012 07:46AM

Hello.

We're currently Migrating a few MYSQL Databases form an Old MYSQL-Server (4.1.15) to a new MYSQL-Server (5.5.23).

It worked first. I could Import everything, even the Users.

But after the Restart it failed to start with the old known "mysql.user table is not updated to new password Format"

So i did the mysql_upgrade Command.

It fixed everything. Server start without any Errors but when i try to Login with root again, it Fails.

Error 1045 Acess denied for user 'root'@localhost:
I tought maybe the Password of the Old Server was different. I used Pants off to Find it out (GUI Login MasK). I copied & pasted it and altough that didn't work either. Error 1045.

I put in the Orginal Files from the MYSQL Database in again restart it and it works again.

So why does the old MYSQL Database with the Same Password as the new one not work after using the Upgrade Command?

//edit: I realized something. I can delete the whole MYSQL-Database after the Upgrade. That shouldn't be possible when it is in use?

//edit:


Well i came a bit Further.

I can now Login after MYSQL_UPGRADE. I did the following Thing:

Imported old Database.

Got into the Database mysql in the user Table.

Set the Length of Password from CHAR(16) to CHAR(41)

And then Updated the Root Password.

update mysql.user set password=PASSWORD('XXXXX') where user='root';

Then upgraded the Database.

Now i'm able to Login again and the Old Users are all Visible.

So after 6-7h i Finally got it.

So this is finished for the Moment.

LOG:

121018 15:05:50 [Note] Plugin 'FEDERATED' is disabled.
121018 15:05:50 InnoDB: The InnoDB memory heap is disabled
121018 15:05:50 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121018 15:05:50 InnoDB: Compressed tables use zlib 1.2.3
121018 15:05:50 InnoDB: Initializing buffer pool, size = 1013.0M
121018 15:05:52 InnoDB: Completed initialization of buffer pool
121018 15:05:52 InnoDB: highest supported file format is Barracuda.
121018 15:05:53 InnoDB: Waiting for the background threads to start
121018 15:05:54 InnoDB: 1.1.8 started; log sequence number 16248280
121018 15:05:54 [ERROR] Column count of mysql.db is wrong. Expected 22, found 15. The table is probably corrupted
121018 15:05:54 [ERROR] mysql.user has no `Event_priv` column at position 29
121018 15:05:54 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
121018 15:05:54 [Note] C:\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.23' socket: '' port: 3306 MySQL Community Server (GPL)
121018 15:08:28 [Note] C:\MySQL\MySQL Server 5.5\bin\mysqld: Normal shutdown

121018 15:08:28 InnoDB: Starting shutdown...
121018 15:08:28 InnoDB: Shutdown completed; log sequence number 16248280
121018 15:08:28 [Note] C:\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete

After Upgrade Command:

121018 15:09:31 [Note] Plugin 'FEDERATED' is disabled.
121018 15:09:31 InnoDB: The InnoDB memory heap is disabled
121018 15:09:31 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121018 15:09:31 InnoDB: Compressed tables use zlib 1.2.3
121018 15:09:32 InnoDB: Initializing buffer pool, size = 1013.0M
121018 15:09:34 InnoDB: Completed initialization of buffer pool
121018 15:09:34 InnoDB: highest supported file format is Barracuda.
121018 15:09:36 InnoDB: Waiting for the background threads to start
121018 15:09:37 InnoDB: 1.1.8 started; log sequence number 16248280
121018 15:09:37 [Note] Event Scheduler: Loaded 0 events
121018 15:09:37 [Note] C:\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.23' socket: '' port: 3306 MySQL Community Server (GPL)
121018 15:22:10 [Note] C:\MySQL\MySQL Server 5.5\bin\mysqld: Normal shutdown

121018 15:22:10 [Note] Event Scheduler: Purging the queue. 0 events
121018 15:22:10 InnoDB: Starting shutdown...
121018 15:22:11 InnoDB: Shutdown completed; log sequence number 16248290
121018 15:22:11 [Note] C:\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete

Options: ReplyQuote


Subject
Views
Written By
Posted
[DONE] Fail to Login after Migration
5819
October 18, 2012 07:46AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.