Re: Upgrading 4.1.10 to 4.1.14 horrid time - Daniel da Veiga - com.mysql.lists.win32

4 messages in com.mysql.lists.win32Re: Upgrading 4.1.10 to 4.1.14 horrid...

From	Sent On	Attachments
zzapper	20 Oct 2005 14:39
Daniel da Veiga	20 Oct 2005 17:59
zzapper	21 Oct 2005 00:16
Daniel da Veiga	21 Oct 2005 04:33

Subject:	Re: Upgrading 4.1.10 to 4.1.14 horrid time
From:	Daniel da Veiga (dani...@gmail.com)
Date:	10/21/2005 04:33:15 AM
List:	com.mysql.lists.win32

On 10/21/05, zzapper <dav...@tvis.co.uk> wrote:

On Thu, 20 Oct 2005 22:59:22 -0200, wrote:

On 10/20/05, zzapper <dav...@tvis.co.uk> wrote:

Hi, I had a ghastly experience upgrading 4.0.xx to 4.1.xx, but didn't expect one for
just a diddly upgrade 4.1.10 to 4.1.14.

Could no longer connect to localhost by any of the classic ways eg
--skip-grant-tables etc. Googling revealed lots of solutions which didnt help.

Eventually installed to a clean directory (ie no databases) and could get in
with my gui, phew. PHP couldn't connect and had to change mysql passwords to Old password

eg SET PASSWORD FOR 'someuser'@'%' = OLD_PASSWORD('passwordinclear');

I've now just got to rebuild my databases from backups

Upgrading MySql used to be a doddle.

And still is, your problem is not a "general" thing, else we would get more mails like yours.

I upgraded from 3.23, then 4.0 to 4.1.7 then 4.1.11 and finally 4.1.14, following the manual instructions and making backups that were never used (and that's good). It took me like 3 and a half minutes at the last one, the one from 3.23 and 4 to 4.1 was a little longer, like 15 minutes (*lol*) and no problem at all.

Is my PHP 4.3.10 too old

The same version I'm using, both at Lin and Win (Lin was even MORE easy, with rpm -U, took me like 30 seconds to upgrade 4.1.11 to 4.1.14).

The OLD_PASSWORD thingy should appear at 4.0 to 4.1 upgrade (that's when it changed from 8 I guess to 16 bytes encrypted pass).

Guess we need more details to see WHAT caused errors at all. When I googled my errors I only found posts from mysql developer newsgroups!

As as you suggest there are not hordes of internauts grumbling, I would suggest
that my mysql.mysql database was somehow out of date, or corrupt. I had about 30 databases installed
and over the years have done many hacks etc. Is there somekind of utility for checking the health
of your databases?

Yes, you can use the CHECK and REPAIR commands, its a good thing to do before a backup and upgrade, specially with FSs like FAT and NTFS and high demand systems, I noticed many corruptions and errors with those.

Well, THAT is a good cause for an error, you're lucky and smart to have backups, I use a batch to check and rebuild indexes just before Administrador performs backups to ensure its allright. I advice you to do the same.