| 1 |
On Sunday 05 September 2010 10:29:29 you wrote: |
| 2 |
> On Saturday 04 September 2010 23:30:55 you wrote: |
| 3 |
> > On Saturday 04 September 2010 22:43:01 kashani wrote: |
| 4 |
> > > On 9/3/2010 10:53 PM, Jarry wrote: |
| 5 |
> > > > On 31. 8. 2010 20:30, Mick wrote: |
| 6 |
> > > >> I stop apach& mysql, run the update, dispatch-conf and then restart |
| 7 |
> > > >> them both. Haven't had problems since. |
| 8 |
> > > > |
| 9 |
> > > > I tried it that way: |
| 10 |
> > > > |
| 11 |
> > > > /etc/init.d/apache2 stop |
| 12 |
> > > > /etc/init.d/mysql stop |
| 13 |
> > > > emerge --ask --update --deep --newuse world |
| 14 |
> > > > emerge --depclean |
| 15 |
> > > > revdep-rebuild |
| 16 |
> > > > /etc/init.d/mysql start |
| 17 |
> > > > /etc/init.d/apache2 start |
| 18 |
> > > > |
| 19 |
> > > > Still the same: databases are gone, mysql is empty. Only users |
| 20 |
> > > > are there. This is strange: how can updating mysql from one stable |
| 21 |
> > > > version to higher stable cause complete loss of databases??? |
| 22 |
> > > > |
| 23 |
> > > > Jarry |
| 24 |
> > > |
| 25 |
> > > IIRC the default my.cnf changed for the worse in Gentoo's 5.1.x ebuild. |
| 26 |
> > > Try making a copy of your original my.cnf and put it into place once |
| 27 |
> > > you've upgraded. Else you may need to modify the mysql home and data |
| 28 |
> > > paths in the new my.cnf to reflect where the database are actually |
| 29 |
> > > installed. |
| 30 |
> > |
| 31 |
> > I just updated to mysql-5.1.50-r1 on a x86 box, ran revdep-rebuild which |
| 32 |
> > amidst others rebuilt apache and php and all is good now. dispatch-conf |
| 33 |
> > updated only a couple of lines on the config file. |
| 34 |
> > |
| 35 |
> > The default paths were not affected on any of the 5 mysql databases I'm |
| 36 |
> > running currently. |
| 37 |
> |
| 38 |
> Oops! I spake too soon! :-( |
| 39 |
> |
| 40 |
> I cannot access two databases. Both have #mysql50# infront of the name of |
| 41 |
> the original database. What does this mean? How do I fix it? Other |
| 42 |
> databases are fine, their names appearing without this strange prefix. |
| 43 |
|
| 44 |
I found the solution: |
| 45 |
|
| 46 |
mysql > ALTER DATABASE `#mysql50#dbname` UPGRADE DATA DIRECTORY NAME; |
| 47 |
|
| 48 |
as described here: |
| 49 |
|
| 50 |
http://mattiasgeniar.be/2010/08/07/mysql-upgrade-to-5-1-database-name-prefix- |
| 51 |
mysql50/ |
| 52 |
|
| 53 |
I am not sure if this is related with the problem that the O/P had - |
| 54 |
disappearing databases. The symptoms when the database with the new prefix is |
| 55 |
used to drive a CMS, was an error by apache saying that the database does not |
| 56 |
exist. Of course, it does exist but its name now has a funny prefix. |
| 57 |
|
| 58 |
Running mysql -u root -p and SHOW DATABASES; led me to finding out that the |
| 59 |
name had changed. BTW, /var/lib/mysql still showed the non-prefixed db names. |
| 60 |
|
| 61 |
Anyway, the above link was very helpful in resolving my problem. |
| 62 |
-- |
| 63 |
Regards, |
| 64 |
Mick |
Archives