Upgrading 4.1.10 to 4.1.14 horrid time
Upgrading 4.1.10 to 4.1.14 horrid time
am 20.10.2005 23:40:09 von zzapper
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.
Is my PHP 4.3.10 too old
--
zzapper
Success for Techies and Vim,Zsh tips
http://SuccessTheory.com/
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org
Re: Upgrading 4.1.10 to 4.1.14 horrid time
am 21.10.2005 02:59:22 von Daniel da Veiga
On 10/20/05, zzapper 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'@'%' =3D 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.
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org
Re: Upgrading 4.1.10 to 4.1.14 horrid time
am 21.10.2005 09:17:20 von zzapper
On Thu, 20 Oct 2005 22:59:22 -0200, wrote:
>On 10/20/05, zzapper 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?
--
zzapper
Success for Techies and Vim,Zsh tips
http://SuccessTheory.com/
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org
Re: Upgrading 4.1.10 to 4.1.14 horrid time
am 21.10.2005 13:33:37 von Daniel da Veiga
On 10/21/05, zzapper wrote:
> On Thu, 20 Oct 2005 22:59:22 -0200, wrote:
>
> >On 10/20/05, zzapper wrote:
> >> Hi,
> >> I had a ghastly experience upgrading 4.0.xx to 4.1.xx, but didn't expe=
ct 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 --s=
kip-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'@'%' =3D 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 newsgrou=
ps!
> >
> As as you suggest there are not hordes of internauts grumbling, I would s=
uggest that my mysql.mysql
> database was somehow out of date, or corrupt. I had about 30 databases in=
stalled and over the years
> have done many hacks etc. Is there somekind of utility for checking the h=
ealth 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.
--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org