From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Proper way of updating mysql from 5.0.90-r2 to 5.1.50?
Date: Sat, 4 Sep 2010 23:30:55 +0100 [thread overview]
Message-ID: <201009042331.25204.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4C82BD65.4060501@badapple.net>
[-- Attachment #1: Type: Text/Plain, Size: 1357 bytes --]
On Saturday 04 September 2010 22:43:01 kashani wrote:
> On 9/3/2010 10:53 PM, Jarry wrote:
> > On 31. 8. 2010 20:30, Mick wrote:
> >> I stop apach& mysql, run the update, dispatch-conf and then restart them
> >> both. Haven't had problems since.
> >
> > I tried it that way:
> >
> > /etc/init.d/apache2 stop
> > /etc/init.d/mysql stop
> > emerge --ask --update --deep --newuse world
> > emerge --depclean
> > revdep-rebuild
> > /etc/init.d/mysql start
> > /etc/init.d/apache2 start
> >
> > Still the same: databases are gone, mysql is empty. Only users
> > are there. This is strange: how can updating mysql from one stable
> > version to higher stable cause complete loss of databases???
> >
> > Jarry
>
> IIRC the default my.cnf changed for the worse in Gentoo's 5.1.x ebuild.
> Try making a copy of your original my.cnf and put it into place once
> you've upgraded. Else you may need to modify the mysql home and data
> paths in the new my.cnf to reflect where the database are actually
> installed.
I just updated to mysql-5.1.50-r1 on a x86 box, ran revdep-rebuild which
amidst others rebuilt apache and php and all is good now. dispatch-conf
updated only a couple of lines on the config file.
The default paths were not affected on any of the 5 mysql databases I'm
running currently.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-04 22:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 17:32 [gentoo-user] Proper way of updating mysql from 5.0.90-r2 to 5.1.50? Jarry
2010-08-31 18:30 ` Mick
2010-09-01 20:00 ` Aniruddha
2010-09-01 20:15 ` Mick
2010-09-01 21:05 ` Alan McKinnon
2010-09-01 21:05 ` Dale
2010-09-01 21:18 ` Alex Schuster
2010-09-01 21:25 ` Tanstaafl
2010-09-01 21:38 ` Mick
2010-09-02 9:55 ` Dale
2010-09-02 18:09 ` Mick
2010-09-01 22:45 ` Alex Schuster
2010-09-01 23:09 ` Dale
2010-09-02 5:10 ` kashani
2010-09-02 18:12 ` Mick
2010-09-03 3:40 ` kashani
2010-09-04 5:53 ` Jarry
2010-09-04 21:43 ` kashani
2010-09-04 22:30 ` Mick [this message]
2010-09-05 9:29 ` Mick
2010-09-05 10:08 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201009042331.25204.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox