On Jan 13, 2010, at 1:28 PM, Lawrence Sorrillo wrote:
> The issue is that in theory this should work given the facts announced by
> MySQL regarding binary logging and replication.
> I can certainly do it the way you propose, but to my mind I should also be
> able to do it using the fact that bo
On 1/13/10 2:28 PM, "Lawrence Sorrillo" wrote:
> The issue is that in theory this should work given the facts announced
> by MySQL regarding binary logging and replication.
> I can certainly do it the way you propose, but to my mind I should also
> be able to do it using the fact that both machin
The issue is that in theory this should work given the facts announced
by MySQL regarding binary logging and replication.
I can certainly do it the way you propose, but to my mind I should also
be able to do it using the fact that both machines are fully synced and
hence at
that point I should b
Hi,
The step 6 in simple terms is
Here we need to build two server ( both master and slave ). Instead of
building two server as it takes double the time of building in one server.
After building an server, make a copy of the first server files at OS level
and copy it to the server and start the sa
Frankly, I didn't entirely understand what you were proposing. I got lost
around step 6.
Is the issue total time for the procedure or service downtime?
On 1/12/10 12:58 PM, "Lawrence Sorrillo" wrote:
> This is two upgrades done in sequence(the reload takes about three hours
> per machine) . I
On Jan 12, 2010, at 12:36 PM, Lawrence Sorrillo wrote:
> Hi:
>
> I want to ensure that right after the reload that the same data is present in
> both the master and the slave. They are in perfect sync. Then I think its
> safe to consider starting binary logging and replication etc. And after t
Hi:
I want to ensure that right after the reload that the same data is
present in both the master and the slave. They are in perfect sync. Then
I think its safe to consider starting binary logging and replication
etc. And after these are started, changes can start?
And in setting up replicat
Lawrence Sorrillo wrote:
Hi:
I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1.
I want to so something like follows:
1. Stop all write access to the master server.
ok
2. Ensure that replication on the slave is caught up to the last change
on the master.
why? You are
This is two upgrades done in sequence(the reload takes about three hours
per machine) . I can do what I am proposing in parallel.
Do you see it as problematic?
~Lawrence
Tom Worster wrote:
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master, up
: upgrading mysql
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master, upgrade it, restart it, let the slave catch up.
?
On 1/12/10 12:34 PM, "Lawrence Sorrillo" wrote:
> Hi:
>
> I want to upgrade a master and slave serve
How about:
1 shut down the slave, upgrade it, restart it, let it catch up.
2 shut down the master, upgrade it, restart it, let the slave catch up.
?
On 1/12/10 12:34 PM, "Lawrence Sorrillo" wrote:
> Hi:
>
> I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1.
>
> I w
Hi:
I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1.
I want to so something like follows:
1. Stop all write access to the master server.
2. Ensure that replication on the slave is caught up to the last change
on the master.
3. stop binary logging on the master.
4. stop
What I always did since 3.23 upwards is new installation and import.
My tecnique allows me to install as many mysql instances as I want,
I always use specific user, homedir, datadir, my.cnf, for each installation.
In this way I can have theoretically unlimited number of mysql instances on
one host.
See Thread at: http://www.techienuggets.com/Detail?tx=78654 Posted on behalf of
a User
This has proved to be quite challenging. I wasn't able to do the upgrade and
basically created another instance of 5.1 and took a backup of my database from
5.0 and restored it to 5.1. Then added all my users
Has anyone upgraded MySQL 4.0 to 5.0 on a Mac running Mac OS X
Panther, 10.3.9 Sever with Lasso 8.5.4? I'm debating whether to just
upgrade to MySQL to 5.0 or jump to Apples Leopard Server.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http:
Hi !
perl pra schrieb:
> [[...]]
>
> Also please tell me where can i get mysql5.1 enterprise edition.
5.1 is currently labeled "rc" (current version is 5.1.22-rc), so there
is no enterprise edition yet.
When there will be one, it will be for paying customers, and they have
got (or will receive)
://dev.mysql.com/doc/refman/5.1/en/installing.html
Saravanan
--- On Fri, 1/18/08, perl pra <[EMAIL PROTECTED]> wrote:
> From: perl pra <[EMAIL PROTECTED]>
> Subject: upgrading mysql on RHEL4
> To: mysql@lists.mysql.com
> Date: Friday, January 18, 2008, 10:21 PM
> Hi Gurus,
>
Hi Gurus,
I have mysql4.x installed on REHL4.
Can anybody let me know how to upgrade it to 5.1.
Also please tell me where can i get mysql5.1 enterprise edition.
Thanks in advance
Siva
n
ran the mysql_fix_privilege_tables script which gave me some warnings, but
seemed OK. The test forum and databases started up fine.
Soon, I'll upgrade to 4.1 and then later to version 5 of the mysql server.
My question is: When upgrading mysql-server and running suggested/included
update s
On 8/2/06, bruce <[EMAIL PROTECTED]> wrote:
hi..
i have FC3, with 4.1.13, i also have FC4 with 4.1.20. however, i can't seem
to find 5.0.x RPMs for FC3/4. do i have to go ahead and build this from
source for the FC3/4 boxes that i have...
Linux x86 generic RPM at:
http://dev.mysql.com/downloa
hi..
i have FC3, with 4.1.13, i also have FC4 with 4.1.20. however, i can't seem
to find 5.0.x RPMs for FC3/4. do i have to go ahead and build this from
source for the FC3/4 boxes that i have...
thanks
-bruce
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To uns
;$year=substr("$date", 0, 4);
> >$month=substr("$date", 4, 2);
> >$day=substr("$date", 6, 2);
> > ?>
> >
> > All timestamp dependent reports and web pages had
> > problems, on
2. At the
> end I had to downgrade to 3.23 to bring web site
> operation to normal. Is there anyway to preserve old
> timestamp format after upgrading?
>
> MySQL - 3.23
> +++--
> | Field | Type | Default (mmdd)
> ++-
. Below is
static php code that I used numerous places:
All timestamp dependent reports and web pages had problems, once I upgrade to
MySQL 4.1.12. At the end I had to downgrade to 3.23 to bring web site
operation to normal. Is there anyway to preserve old timestamp format after
upgrading
. Below is
static php code that I used numerous places:
All timestamp dependent reports and web pages had problems, once I upgrade to
MySQL 4.1.12. At the end I had to downgrade to 3.23 to bring web site
operation to normal. Is there anyway to preserve old timestamp format after
upgrading
Hassan Schroeder wrote:
Mark Sargent wrote:
ok, I don't fully understand why, but, mysql is still installed in
/usr/bin. What I've done, just for now, is renamed mysql in that dir
to mysqlold. I've added /usr/local/mysql/bin to my path. I then tried
the cmd mysql and also ./mysql from within the
Mark Sargent wrote:
ok, I don't fully understand why, but, mysql is still installed in
/usr/bin. What I've done, just for now, is renamed mysql in that dir to
mysqlold. I've added /usr/local/mysql/bin to my path. I then tried the
cmd mysql and also ./mysql from within the dir /usr/local/mysql/bi
Hassan Schroeder wrote:
Mark Sargent wrote:
h, that is annoying, as I did a yum remove mysql b4 installing
4.1. Shouldn't the yum remove, remove it fully..?
Sorry, can't help there, don't know anything about 'yum'.
[EMAIL PROTECTED] ~]# mysql -p
Enter password:
Welcome to the MySQL monitor.
Mark Sargent wrote:
h, that is annoying, as I did a yum remove mysql b4 installing 4.1.
Shouldn't the yum remove, remove it fully..?
Sorry, can't help there, don't know anything about 'yum'.
[EMAIL PROTECTED] ~]# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \
Hassan Schroeder wrote:
Mark Sargent wrote:
[EMAIL PROTECTED] bluefish-1.0]# mysql -h localhost -u root -pwhatafraka
ERROR 1251: Client does not support authentication protocol
requested by server; consider upgrading MySQL client
What is this..? Why is it asking me to upgrade the client
Mark Sargent wrote:
[EMAIL PROTECTED] bluefish-1.0]# mysql -h localhost -u root -pwhatafraka
ERROR 1251: Client does not support authentication protocol requested
by server; consider upgrading MySQL client
What is this..? Why is it asking me to upgrade the client.? Cheers.
master/client are
-h localhost -u root -pwhatafraka
ERROR 1251: Client does not support authentication protocol
requested by server; consider upgrading MySQL client
What is this..? Why is it asking me to upgrade the client.? Cheers.
Mark Sargent.
See here:
http://dev.mysql.com/doc/mysql/en/password-hashing.html
Mark Sargent wrote:
Simon Garner wrote:
On 2/05/2005 6:05 p.m., Mark Sargent wrote:
Hi All,
master/client are the same machine. I installed via tar.gz, ver 4.1
following this page
http://dev.mysql.com/doc/mysql/en/installing-binary.html
for installation on FC3. Why would it say that the client do
Simon Garner wrote:
On 2/05/2005 6:05 p.m., Mark Sargent wrote:
Hi All,
master/client are the same machine. I installed via tar.gz, ver 4.1
following this page
http://dev.mysql.com/doc/mysql/en/installing-binary.html
for installation on FC3. Why would it say that the client doesn't
support it.?
t -pwhatafraka
ERROR 1251: Client does not support authentication protocol
requested by server; consider upgrading MySQL client
What is this..? Why is it asking me to upgrade the client.? Cheers.
Mark Sargent.
See here:
http://dev.mysql.com/doc/mysql/en/password-hashing.html
Presumably your server
On 2/05/2005 6:05 p.m., Mark Sargent wrote:
Hi All,
master/client are the same machine. I installed via tar.gz, ver 4.1
following this page
http://dev.mysql.com/doc/mysql/en/installing-binary.html
for installation on FC3. Why would it say that the client doesn't
support it.? Cheers.
P.S. I now
ROR 1251: Client does not support authentication protocol requested
by server; consider upgrading MySQL client
What is this..? Why is it asking me to upgrade the client.? Cheers.
Mark Sargent.
See here:
http://dev.mysql.com/doc/mysql/en/password-hashing.html
Presumably your server is running 4.1 with
CTED]
Sent: Sun 5/1/2005 10:37 PM
To: mysql@lists.mysql.com
Subject: Re: ERROR 1251: Client does not support authentication protocol
requested by server; consider upgrading MySQL client
On 2/05/2005 5:21 p.m., Mark Sargent wrote:
> Hi All,
>
> I did this below,
>
> mysql&g
t support authentication protocol requested by
server; consider upgrading MySQL client
What is this..? Why is it asking me to upgrade the client.? Cheers.
Mark Sargent.
See here:
http://dev.mysql.com/doc/mysql/en/password-hashing.html
Presumably your server is running 4.1 with new passwords and
Hi All,
I did this below,
mysql>SET PASSWORD FOR 'root'@'localhost' = PASSWORD('whatafraka');
and then tried logging on,
[EMAIL PROTECTED] bluefish-1.0]# mysql -h localhost -u root -pwhatafraka
ERROR 1251: Client does not support authentication protocol requeste
-
From: Florin Andrei [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 29, 2005 8:40 PM
To: mysql@lists.mysql.com
Subject: Re: upgrading mysql on RH fedora core 3
On Tue, 29 Mar 2005 19:28:56 -0800, bruce <[EMAIL PROTECTED]> wrote:
>
> we're trying to install mysql/mysql-se
On Tue, 29 Mar 2005 20:39:54 -0800, Florin Andrei
<[EMAIL PROTECTED]> wrote:
> On Tue, 29 Mar 2005 19:28:56 -0800, bruce <[EMAIL PROTECTED]> wrote:
> >
> > we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running
> > into some serious problems. we had mysql/server (3.23.52-3.i386
On Tuesday, March 29, 2005 21:29, bruce wrote:
> hi...
>
> we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are
> running into some serious problems. we had mysql/server
> (3.23.52-3.i386) running, but needed to go to the higher version...
>
> can someone tell us how/what we need
bruce wrote:
>hi...
>
>we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running
>into some serious problems. we had mysql/server (3.23.52-3.i386) running,
>but needed to go to the higher version...
>
>can someone tell us how/what we need to do to get this working correctly.
>act
On Tue, 29 Mar 2005 19:28:56 -0800, bruce <[EMAIL PROTECTED]> wrote:
>
> we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running
> into some serious problems. we had mysql/server (3.23.52-3.i386) running,
> but needed to go to the higher version...
I was about to attempt the s
hi...
we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running
into some serious problems. we had mysql/server (3.23.52-3.i386) running,
but needed to go to the higher version...
can someone tell us how/what we need to do to get this working correctly.
actually, if anybody's ma
Hello.
Install MySQL-client-4.1.10-0.i386.rpm.
"Troy Richard" <[EMAIL PROTECTED]> wrote:
> I have upgraded from mysql 3.23 to 4.1.10 everything seems to be working.
> I'm trying to run the mysql_fix_privilege_tables script to update the
> privileges and I'm getting the following error:
I have upgraded from mysql 3.23 to 4.1.10 everything seems to be working.
I'm trying to run the mysql_fix_privilege_tables script to update the
privileges and I'm getting the following error:
/usr/bin/mysql_fix_privilege_tables: line 185: /usr/bin/mysql: No such
file or directory
/usr/bin/mysql e
ontents of the mentioned documents and hints, there is
> > nothing else. Just start the new server in place of the old server with
> > the same options unless told otherwise in the mentioned documents.
> >
> > Am Mo, den 15.11.2004 schrieb GH um 15:06:
> >
> >
the same options unless told otherwise in the mentioned
>> documents.
>>
>> Am Mo, den 15.11.2004 schrieb GH um 15:06:
>>
>>
>> > when I go to both 2.10 Upgrading MySQL
>> > (http://dev.mysql.com/doc/mysql/en/Upgrade.html) and 2.10.2
>> Upg
mentioned documents.
>
> Am Mo, den 15.11.2004 schrieb GH um 15:06:
>
>
> > when I go to both 2.10 Upgrading MySQL
> > (http://dev.mysql.com/doc/mysql/en/Upgrade.html) and 2.10.2 Upgrading
> > from Version 4.0 to 4.1
> > (http://dev.mysql.com/doc/mysql/en/Upgradin
Hi GH,
apart of the contents of the mentioned documents and hints, there is
nothing else. Just start the new server in place of the old server with
the same options unless told otherwise in the mentioned documents.
Am Mo, den 15.11.2004 schrieb GH um 15:06:
> when I go to both 2.10 Upgrad
TED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Tuesday, November 16, 2004 9:34 PM
> Subject: RE: Mysql-4.1.7 and client library - Client does not support
> authentication protocol requested by server; consider upgrading MySQL
client
>
>
> > You n
://www.friendster.com
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 16, 2004 11:38 AM
> To: [EMAIL PROTECTED]
> Subject: Mysql-4.1.7 and client library - Client does not support
> authentication protocol requested by server; consid
On Tuesday 16 November 2004 02:15 pm, William R. Mussatto wrote:
> I had a similar problem with DBI/DBD. The solution I used was to create
> the passwords using OLD_PASSWORD('plaintextPassword') function
> Look at http://dev.mysql.com/doc/mysql/en/Password_hashing.html for the
> details as well a
protocol
> requested by server; consider upgrading MySQL client"
>
>>From shell it works all the solution to the problem exists? Or it
>> is better install the version 4.0.21?
>
>
> Thank's
> Alessio
I had a similar problem with DBI/DBD. The so
d
by server; consider upgrading MySQL client"
>From shell it works all the solution to the problem exists? Or it is
>better install the version 4.0.21?
Thank's
Alessio
when I go to both 2.10 Upgrading MySQL
(http://dev.mysql.com/doc/mysql/en/Upgrade.html) and 2.10.2 Upgrading
from Version 4.0 to 4.1
(http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.0.html) it does
not tell me how to upgrade it only tells me about important changes
and recomendation. I am
this one will be usefull ...
2.10.2 Upgrading from Version 4.0 to 4.1
- http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.0.html
On Sun, 14 Nov 2004 09:30:49 -0500, GH <[EMAIL PROTECTED]> wrote:
> I would like to know how to upgrade mySql from 4.0 to 4.1?
>
> I am running mandrake 10
>
> I am
I would like to know how to upgrade mySql from 4.0 to 4.1?
I am running mandrake 10
I am using the preinstalled versions of both mySQL and PHP (php4).
I am a newbie to Linux and am a bit nervous.
Thanks.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubsc
The directory mysql is a symbolic link to one of the other dirs.
If mysql points to old one rename it and make a new one:
mv mysql mysqlold
ls -s mysql-max-4.1.7-apple-darwin7.5.0-powerpc mysql
Do not remove
mysql-max-4.0.20-apple-darwin7.3.0-powerpc/data
it contains your old databases!!!
Santino
I was running ver 4.0.15 and just upgraded to the latest version of 4.1.7. In
between I had done an upgrade to ver. 4.0.20. I can get the server to start and
stop via the Preferences panel but before and after any upgrade it indicates
that 4.0.15 is running. In Navicat which I use as the gui fro
Thanks. I passed this on and he found what was lost. I guess since the data
directory was owned by mysql, he could not find the databases when doing a
MacOS file search. I impressed upon him to use a separate datadir as we do
with our servers, thus bypassing this whole thing.
Thanks again!
-steve
Are you sure?
/usr/local/mysql is a symbolic link to another direcory (
/usr/local/mysql(version).
I think the installer overwrite the symbolic link so if you open a
terminal and type:
ls -l /usr/local
Santino
At 16:20 -0700 28-10-2004, Steven Roussey wrote:
Installing MySQL 4.1.7 (upgrading f
So, do you have a question or are you just bragging? ;-)
Rhino
- Original Message -
From: "Steven Roussey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 28, 2004 7:20 PM
Subject: Upgrading MySQL erased all data
> Installing MySQL 4.1.7
Installing MySQL 4.1.7 (upgrading from 4.1.3) on MacOS X erased the contents
of /usr/local/mysql/data -- the privs and data of the previous installation.
FYI
Luckily (and unfortunately) we have a backup of that database from last
week. (The guy that did it here in the office is still in a bit of
.1.5g may have packaged the libs with the
tarball, I don't know.
Thanks,
Mike
-Original Message-
From: Tim Johnson [mailto:[EMAIL PROTECTED]
Sent: 18 September 2004 03:43
To: [EMAIL PROTECTED]
Subject: Upgrading MySQL. Caveats or Cautions anyone?
Hello:
Am currently using
Tim Johnson <[EMAIL PROTECTED]> wrote:
The simpliest way:
Download and install MySQL Official Binary RPMs from www.mysql.com.
They will install on your server and run fine.
You'd also want to install the shared-compat RPM in case you have
something compiled with older libmysqlclient.
The lin
You can ignore both of those if you use the binaries.
-Eric
On Fri, 17 Sep 2004 18:43:02 -0800, Tim Johnson <[EMAIL PROTECTED]> wrote:
> Hello:
> Am currently using Ver 11.18 Distrib 3.23.58
> on Linux 2.4.20-20.9. (RH 9.0).
>
> I'd like to upgrade to the current version. I would
> like to
Hello:
Am currently using Ver 11.18 Distrib 3.23.58
on Linux 2.4.20-20.9. (RH 9.0).
I'd like to upgrade to the current version. I would
like to know if there are any cautions to observe,
or any prepartory steps to take.
If I look at the following URL:
http://dev.mysql.com/downloads/mysql/4.0.
nect(...) failed: Client does not support authentication protocol
requested by server; consider upgrading MySQL client at connect_test.pl line
19
All the connect_test.pl tries to do is create a db connection to each server
separately.
Any insight would be greatly appreciated
thanks much
sean
y server; consider upgrading MySQL client at connect_test.pl line
19
All the connect_test.pl tries to do is create a db connection to each server
separately.
Any insight would be greatly appreciated
thanks much
sean peters
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archiv
Can you give me a bit more detailed instructions on what i am
uninstalling and what I should back up?
Thanks
Wolfgang Riedel wrote:
[EMAIL PROTECTED] schrieb:
I am trying to upgrade to the new version of mySQL on Fedora Core 2
Linux. I have "mysql Ver 11.18 Distrib 3.23.58, for
redhat-linux-
On Mon, 02 Aug 2004 17:31:03 -0400
[EMAIL PROTECTED] wrote:
> I am now getting
>
> [EMAIL PROTECTED] Desktop]# mysql -u root -pmypasshere
> ERROR 2002: Can't connect to local MySQL server through socket
> '/var/lib/mysql/mysql.sock' (2)
>
> any thoughts...
>
> once again thanks for the assist
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Upgrading mySQL 3.23 to 4.0
Date: Mon, 02 Aug 2004 18:26:05 -0400
in my Linux Services... the mysqld entry is missing
i have mysql and that is supposedly running.
- Original Message -
From: Carlos Proal <[EMAIL PROTECTED]>
Date: Monday, Augu
in my Linux Services... the mysqld entry is missing
i have mysql and that is supposedly running.
- Original Message -
From: Carlos Proal <[EMAIL PROTECTED]>
Date: Monday, August 2, 2004 6:19 pm
Subject: Re: Upgrading mySQL 3.23 to 4.0
>
> The upgrade shutdown the database,
D]
Date: Monday, August 2, 2004 5:26 pm
Subject: Re: Upgrading mySQL 3.23 to 4.0
> I wound up having to do the following:
>
> [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-compat-4.0.20-
> 0.i386.rpm
> warning: MySQL-shared-compat-4.0.20-0.i386.rpm: V3 DSA signature:
> N
day, August 2, 2004 5:12 pm
Subject: Re: Upgrading mySQL 3.23 to 4.0
> At 01:58 PM 8/2/2004, [EMAIL PROTECTED] wrote:
> >Greetings:
> >
> > I am trying to upgrade to the new version of mySQL on Fedora
> Core 2
> > Linux. I have "mysql Ver 11.18 Distrib 3.23.5
At 01:58 PM 8/2/2004, [EMAIL PROTECTED] wrote:
Greetings:
I am trying to upgrade to the new version of mySQL on Fedora Core 2
Linux. I have "mysql Ver 11.18 Distrib 3.23.58, for redhat-linux-gnu (i386)"
I downloaded the following files:
MySQL-client-4.0.20-0.i386.rpm
MySQL-server-4.0.20-0.i3
Greetings:
I am trying to upgrade to the new version of mySQL on Fedora Core 2 Linux. I have
"mysql Ver 11.18 Distrib 3.23.58, for redhat-linux-gnu (i386)"
I downloaded the following files:
MySQL-client-4.0.20-0.i386.rpm
MySQL-server-4.0.20-0.i386.rpm
and as root ran the following:
[EMAI
Dear All,
Hello
is it advised not to do an upgrade on a Mysql 4.x to latest MySQL?
What if the 4.x version is installed at installation time of say, RHL8, can an upgrade
then be done afterwards to latest version?
Just looking for any recommendations, etc
Thanks in advance!~
Carlos
Hi,
I'd recommend you PHP 4.3.2 or newer, if you're already using 4.3.0. Latest
stable should be 4.3.4, see www.php.net . Upgrading is described there,
depends on you type of installation (Apache module/CLI/CGI).
Latest MySQL of 3.23 series is 3.23.57 or so, don't know exactly, see
www.mysql.com .
I'm on a Macintosh G3 PowerBook with OS 10.2.1. PHP is version 4.3.0;
MySQL, 3.23.53; and phpmyAdmin, 2.4.0.
What are the latest available post-beta, stable, fully-baked versions? Is
upgrading as big a project as deleting old versions and then reinstalling
newer? Or are there instructs for upgradi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Wed, 2 Jul 2003, Paul DuBois wrote:
> At 11:33 -0400 7/2/03, Andrew Pierce wrote:
> >I am getting ready to try to upgrade MySQL on my RedHat 9 box. I want to
> >go from the version that came with the distro (version 3.23.54) to the
> >latest
At 11:33 -0400 7/2/03, Andrew Pierce wrote:
I am getting ready to try to upgrade MySQL on my RedHat 9 box. I want to
go from the version that came with the distro (version 3.23.54) to the
latest (verion 4.0).
Just thought I'd post to get a heads-up on any known issues or
prerequisites. I just hate
I am getting ready to try to upgrade MySQL on my RedHat 9 box. I want to
go from the version that came with the distro (version 3.23.54) to the
latest (verion 4.0).
Just thought I'd post to get a heads-up on any known issues or
prerequisites. I just hate it when I try something like this and screw
lleman [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2003 2:14 PM
To: [EMAIL PROTECTED]
Subject: RE: upgrading mysql
[EMAIL PROTECTED] wrote:
> Can someone help
> point me in the right direction? Thanks
I just finished a practice upgrade (on a back-up server) myself and will
be upgra
our VA Linux
> box
> and have used the binaries for the last two or three upgrades. Our builds
> were really unstable and buggy under a high load, but the binaries have
> been
> great.
>
> Hope that helps
>
> -Original Message-
> From: Tab Alleman [mailto:
upgrades. Our builds
were really unstable and buggy under a high load, but the binaries have been
great.
Hope that helps
-Original Message-
From: Tab Alleman [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2003 2:14 PM
To: [EMAIL PROTECTED]
Subject: RE: upgrading mysql
[EMAIL PROTECTED
[EMAIL PROTECTED] wrote:
> Can someone help
> point me in the right direction? Thanks
I just finished a practice upgrade (on a back-up server) myself and will
be upgrading the real server during off-peak hours soon. We are running
win2k servers so I can't speak directly to any linux issues, but
I currently am running linux 7.1 and have MySQL 3.23.54 running on my box. I have
heard that there are some security issues with the version of mysql that I am running,
plus, phpnuke 6.5 needs the newer version of mysql.
I am a newbie to linux and mysql, and need a bit of hand holding I think.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Dec 2002, John P wrote:
> I want to upgrade my MySQL version (3.23.51) because of the recently
> revealed exploit; the only binary dist on mysql.com for solaris 2.7 is
> 3.23.53; will there be a problem compiling from source on this platfor
I want to upgrade my MySQL version (3.23.51) because of the recently
revealed exploit; the only binary dist on mysql.com for solaris 2.7 is
3.23.53; will there be a problem compiling from source on this platform or
should I wait for the binaries to be updated? There is a .54 release for 2.8
and 2.9
I'm trying to update mysql 3.23.49 up to 4.0.5 on a RedHat 7.3 system,
and I'm having some problems. I may be able to solve those problems by
my own, but I'm running out of time and any tip or advice would be
appreciated. I have to solve this today or I will forget updating mysql
at this time.
Fir
Is there any reason I should use my MySQL supplies binaries to upgrade
my currently installed version? I compile the running version (3.23.49).
Is there any difficulty in doing this? Any pitfalls to watch out for, or
should I just continue to compile my own and upgrade via that path?
- Greg
--
At 13:47 2002-11-13 -0500, Rick Root wrote:
[root@frodo MySQL]# rpm --install MySQL-3.23.53a-1.i386.rpm
error: failed dependencies:
MySQL conflicts with mysql-3.23.41-1
MySQL-server conflicts with mysql-server-3.23.41-1
[root@frodo MySQL]# rpm -U MySQL-3.23.53a-1.i386.rpm
error: fa
You might need to use rpm -e to uninstall previous version first.
Check the documentation.
~Kelly W. Black
-Original Message-
From: Rick Root [mailto:rroot@;wakeinternet.com]
Sent: Wednesday, November 13, 2002 10:47 AM
To: mysql
Subject: Upgrading MySQL from 3.23.41 to 3.23.53a
I
I would like to upgrade MySQL to the latest production release
(3.23.53a) from my current 3.23.41
I have the following packages installed already:
mysql-devel-3.23.41-1
mysqlclient9-3.23.22-6
mysql-3.23.41-1
mysql-server-3.23.41-1
What do I need to do in order to upgrade to the newest version?
Perhaps a simple question. The solaris server we have has an older mysql. I
don't know which version since I did not install it. The mysql main file is
now segment faulting for some reason. I restored a backup but its not
working either. It just worked a few days ago. I assume the file is now
c
Hi,
On Tue, 2002-03-19 at 11:41, Campbell McLeay wrote:
> I wish to upgrade mysql server from 3.22 to 3.23 running on Linux and
> had a few basic questions which I am hoping someone can help me with.
> My plan is simply to download and unpack the binary distribution, stop
> mysqld, move the symli
1 - 100 of 130 matches
Mail list logo
