public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: kashani <kashani-list@badapple.net>
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: Wed, 01 Sep 2010 22:10:05 -0700	[thread overview]
Message-ID: <4C7F31AD.9020109@badapple.net> (raw)
In-Reply-To: <201009012200.16350.mailingdotlist@gmail.com>

On 9/1/2010 1:00 PM, Aniruddha wrote:
> On Tuesday 31 August 2010 20:30:55 Mick wrote:
>>> But this is apparently not the proper way, because after
>>> restarting the server, apache does not show my web-page
>>> reporting there is no such a database. I checked it with
>>> phpmyadmin, and really, there is absolutely no database
>>> in mysql!
>>>
>>> I quickly restored backup version which I have done just
>>> before trying mysql-update, so my web-site is up and running.
>>> Now I would like to update mysql the right way, I but do not
>>> know how to do it...
>>
>> Hi Jarry,
>>
>> Some years ago I ran into some similar problem, I can't recall exactly
>> what. Lost in folklore (wiki?) were some instructions to first stop mysql
>> before you update it and I have been following them since.
>>
>> I stop apach&  mysql, run the update,  dispatch-conf and then restart them
>> both.  Haven't had problems since.
>>
>> There may be a better way for doing this - in which case others who know
>> better will hopefully chime in.
>
> I'm curious as well. Imo it shouldn't be necessary to stop mysql server for
> each update.
>

	I did in place upgrades from 5.0.12 or so on up to 5.0.77 or so. You're 
unlikely to have problems upgrading Mysql within 5.0.x. If you're moving 
up to 5.1, I would definitely stop inserts into Mysql, dump mysql, stop 
mysql, make a copy of /var/lib/mysql just in case, then upgrade to 5.1. 
Mysql should be able to upgrade your database in place, but it might 
not. If mysql-update doesn't work, importing a dumb is the most reliable 
way to get your data into 5.1.
	As other people have pointed out you'll need to revdep-rebuild or 
preserve the older client libs.

kashani



  parent reply	other threads:[~2010-09-02  5:11 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 [this message]
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
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=4C7F31AD.9020109@badapple.net \
    --to=kashani-list@badapple.net \
    --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