Re: upgrading mysql

[Lawrence Sorrillo]

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 be able to to local respective dumps and restores 
and still be in sync.


Anyone knows anything special about position 106? It seems to be the 
very initial position in MySQL 5.1 servers?


mysql show master status;
+---+--+--+--+
| File  | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+---+--+--+--+
| X-bin.01 |  106 |  |  |
+---+--+--+--+
1 row in set (0.00 sec)



r...@:/usr/local/mysql/data ] /usr/local/mysql/bin/mysqlbinlog 
mssdb2-bin.01

/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 4
#100113 13:50:40 server id 5  end_log_pos 106   Start: binlog v 4, 
server v 5.1.42-log created 100113 13:50:40 at startup

# Warning: this binlog is either in use or was not closed properly.
ROLLBACK/*!*/;
BINLOG '
ABZOSw8FZgAAAGoBAAQANS4xLjQyLWxvZwAA
Fk5LEzgNAAgAEgAEBAQEEgAAUwAEGggICAgC
'/*!*/;
DELIMITER ;
# End of log file
ROLLBACK /* added by mysqlbinlog */;
/*!50003 SET completion_ty...@old_completion_type*/;
r...@:/usr/local/mysql/data ]

~Lawrence




Tom Worster wrote:

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 sorri...@jlab.org wrote:

  

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, upgrade it, restart it, let the slave catch up.

?





On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org 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.
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 replication on the slave.
5. dump the master, stop old 4.1 server, start new 5.1 server and reload
master dump file under 5.1 server ( binary logging is turned off)
6. dump the slave, stop old 4.1 server, start new 5.1 server and reload
slave dump file under 5.1 server.
7. After loading is complete, test then start binary logging on master
while still preventing updates to updates.
8. After loading slave, test then start slave (get configs in place and
restart server).

I am thinking that in this scenario I dont have to bother with recording
binlog file names and position etc etc.
That both servers will have the same databases abd replication and
binary logging will start on the two databases with no data loss and
continue forward.


Comments?

~Lawrence





  
  





  




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[fsb]

On 1/13/10 2:28 PM, Lawrence Sorrillo sorri...@jlab.org 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 machines are fully synced and
 hence at
 that point I should be able to to local respective dumps and restores
 and still be in sync.

i can't point at anything in your recipe and say that it doesn't work. it
might work. i'd be nervous that something in steps 5 and 6 might involve a
change on the master that needs to be replicated. since your using a dump
and not a binary copy of myisam file, i suppose this ought to be safe. but i
would be nervous all the same.

on the other hand, i do know that the recipe i gave works because i've used
it often. it also has the virtue of no need for recording binlog file names
and position etc etc. plus it's the procedure recommended by the mysql folk
themselves, which is worth something to me.

the other thing i've done is:

initial status: A is the master and B is the slave. service is operating off
the master.

1 stop B, upgrade it, restart it, let it catch up.

2 stop service and then stop A

3 change B's conf file to make it the master. restart it

4 resume service using B

5 upgrade A and bring it online as a slave

this has the virtue of very short service outage. with some rehearsal, it
isn't beyond my skills.


 Anyone knows anything special about position 106? It seems to be the
 very initial position in MySQL 5.1 servers?

the manual says:

If the master has been running previously without binary logging enabled,
the log name and position values displayed by SHOW MASTER STATUS or
mysqldump --master-data will be empty. In that case, the values that you
need to use later when specifying the slave's log file and position are the
empty string ('') and 4.

perhaps you have an init-file that advances it to position 106?



 mysql show master status;
 +---+--+--+--+
 | File  | Position | Binlog_Do_DB | Binlog_Ignore_DB |
 +---+--+--+--+
 | X-bin.01 |  106 |  |  |
 +---+--+--+--+
 1 row in set (0.00 sec)
 
 
 
 r...@:/usr/local/mysql/data ] /usr/local/mysql/bin/mysqlbinlog
 mssdb2-bin.01
 /*!40019 SET @@session.max_insert_delayed_threads=0*/;
 /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
 DELIMITER /*!*/;
 # at 4
 #100113 13:50:40 server id 5  end_log_pos 106   Start: binlog v 4,
 server v 5.1.42-log created 100113 13:50:40 at startup
 # Warning: this binlog is either in use or was not closed properly.
 ROLLBACK/*!*/;
 BINLOG '
 ABZOSw8FZgAAAGoBAAQANS4xLjQyLWxvZwAA
 Fk5LEzgNAAgAEgAEBAQEEgAAUwAEGggICAgC
 '/*!*/;
 DELIMITER ;
 # End of log file
 ROLLBACK /* added by mysqlbinlog */;
 /*!50003 SET completion_ty...@old_completion_type*/;
 r...@:/usr/local/mysql/data ]
 
 ~Lawrence
 
 
 
 
 Tom Worster wrote:
 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 sorri...@jlab.org wrote:
 
   
 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, upgrade it, restart it, let the slave catch up.
 
 ?
 
 
 
 
 
 On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org 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.
 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 replication on the slave.
 5. dump the master, stop old 4.1 server, start new 5.1 server and reload
 master dump file under 5.1 server ( binary logging is turned off)
 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload
 slave dump file under 5.1 server.
 7. After loading is complete, test then start binary logging on master
 while still preventing updates to updates.
 8. After loading slave, test then start slave (get configs in place and
 restart server).
 
 I am thinking that in this scenario I dont have to bother with recording
 binlog file names and position etc etc.
 That both servers will have the same databases abd replication and
 binary logging will start on the two databases with no data loss and
 continue forward.
 
 
 Comments?
 
 ~Lawrence
 
 
 
 

Re: upgrading mysql

[Paul DuBois]

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 both machines are fully synced and hence at
 that point I should be able to to local respective dumps and restores and 
 still be in sync.
 
 Anyone knows anything special about position 106? It seems to be the very 
 initial position in MySQL 5.1 servers?

It's not. 4 is still the initial position, as shown by the at 4 in your 
mysqlbinlog output below. The 106 that you observe is the position *after* the 
server writes the initial event to the binary log. It writes this event 
immediately after opening the file, even before executing any statements.

If you want the gory details: This event is the format description event that 
identifies in the binary log file the server version and other information. See 
http://forge.mysql.com/wiki/MySQL_Internals_Binary_Log#Binary_Log_Versions if 
you have a high tolerance for pain. :-)

 
 mysql show master status;
 +---+--+--+--+
 | File  | Position | Binlog_Do_DB | Binlog_Ignore_DB |
 +---+--+--+--+
 | X-bin.01 |  106 |  |  |
 +---+--+--+--+
 1 row in set (0.00 sec)
 
 
 
 r...@:/usr/local/mysql/data ] /usr/local/mysql/bin/mysqlbinlog 
 mssdb2-bin.01
 /*!40019 SET @@session.max_insert_delayed_threads=0*/;
 /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
 DELIMITER /*!*/;
 # at 4
 #100113 13:50:40 server id 5  end_log_pos 106   Start: binlog v 4, server v 
 5.1.42-log created 100113 13:50:40 at startup
 # Warning: this binlog is either in use or was not closed properly.
 ROLLBACK/*!*/;
 BINLOG '
 ABZOSw8FZgAAAGoBAAQANS4xLjQyLWxvZwAA
 Fk5LEzgNAAgAEgAEBAQEEgAAUwAEGggICAgC
 '/*!*/;
 DELIMITER ;
 # End of log file
 ROLLBACK /* added by mysqlbinlog */;
 /*!50003 SET completion_ty...@old_completion_type*/;
 r...@:/usr/local/mysql/data ]
 
 ~Lawrence
 
 
 
 
 Tom Worster wrote:
 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 sorri...@jlab.org wrote:
 
  
 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, upgrade it, restart it, let the slave catch up.
 
 ?
 
 
 
 
 
 On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org 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.
 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 replication on the slave.
 5. dump the master, stop old 4.1 server, start new 5.1 server and reload
 master dump file under 5.1 server ( binary logging is turned off)
 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload
 slave dump file under 5.1 server.
 7. After loading is complete, test then start binary logging on master
 while still preventing updates to updates.
 8. After loading slave, test then start slave (get configs in place and
 restart server).
 
 I am thinking that in this scenario I dont have to bother with recording
 binlog file names and position etc etc.
 That both servers will have the same databases abd replication and
 binary logging will start on the two databases with no data loss and
 continue forward.
 
 
 Comments?
 
 ~Lawrence
 
 
 



 
 
 
  
 
 
 
 -- 
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/mysql?unsub=paul.dub...@sun.com
 

-- 
Paul DuBois
Sun Microsystems / MySQL Documentation Team
Madison, Wisconsin, USA
www.mysql.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

upgrading mysql

[Lawrence Sorrillo]

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 replication on the slave.
5. dump the master, stop old 4.1 server, start new 5.1 server and reload 
master dump file under 5.1 server ( binary logging is turned off)
6. dump the slave, stop old 4.1 server, start new 5.1 server and reload 
slave dump file under 5.1 server.
7. After loading is complete, test then start binary logging on master 
while still preventing updates to updates.
8. After loading slave, test then start slave (get configs in place and 
restart server).


I am thinking that in this scenario I dont have to bother with recording 
binlog file names and position etc etc.
That both servers will have the same databases abd replication and 
binary logging will start on the two databases with no data loss and 
continue forward.



Comments?

~Lawrence




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[Tom Worster]

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 sorri...@jlab.org 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.
 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 replication on the slave.
 5. dump the master, stop old 4.1 server, start new 5.1 server and reload
 master dump file under 5.1 server ( binary logging is turned off)
 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload
 slave dump file under 5.1 server.
 7. After loading is complete, test then start binary logging on master
 while still preventing updates to updates.
 8. After loading slave, test then start slave (get configs in place and
 restart server).
 
 I am thinking that in this scenario I dont have to bother with recording
 binlog file names and position etc etc.
 That both servers will have the same databases abd replication and
 binary logging will start on the two databases with no data loss and
 continue forward.
 
 
 Comments?
 
 ~Lawrence
 
 
 



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

RE: upgrading mysql

[Joshua Gordon]

Also see http://dev.mysql.con/doc/refman/5.0/en/mysql-upgrade.html.
And make sure you make a backup before you do anything :)

-Original Message-
From: Tom Worster [mailto:f...@thefsb.org] 
Sent: Tuesday, January 12, 2010 10:47 AM
To: Lawrence Sorrillo; mysql@lists.mysql.com
Subject: Re: 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 sorri...@jlab.org 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.
 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 replication on the slave.
 5. dump the master, stop old 4.1 server, start new 5.1 server and
reload
 master dump file under 5.1 server ( binary logging is turned off)
 6. dump the slave, stop old 4.1 server, start new 5.1 server and
reload
 slave dump file under 5.1 server.
 7. After loading is complete, test then start binary logging on master
 while still preventing updates to updates.
 8. After loading slave, test then start slave (get configs in place
and
 restart server).
 
 I am thinking that in this scenario I dont have to bother with
recording
 binlog file names and position etc etc.
 That both servers will have the same databases abd replication and
 binary logging will start on the two databases with no data loss and
 continue forward.
 
 
 Comments?
 
 ~Lawrence
 
 
 



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=jgor...@westernwats.com


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[Lawrence Sorrillo]

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, upgrade it, restart it, let the slave catch up.

?





On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org 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.
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 replication on the slave.
5. dump the master, stop old 4.1 server, start new 5.1 server and reload
master dump file under 5.1 server ( binary logging is turned off)
6. dump the slave, stop old 4.1 server, start new 5.1 server and reload
slave dump file under 5.1 server.
7. After loading is complete, test then start binary logging on master
while still preventing updates to updates.
8. After loading slave, test then start slave (get configs in place and
restart server).

I am thinking that in this scenario I dont have to bother with recording
binlog file names and position etc etc.
That both servers will have the same databases abd replication and
binary logging will start on the two databases with no data loss and
continue forward.


Comments?

~Lawrence







  




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[Shawn Green]

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 just going to replace it later.


3. stop binary logging on the master.


why? You can just disconnect the slave



4. stop replication on the slave.


You can do this at step 2. Just issue STOP SLAVE IO_THREAD;  The SQL 
thread can keep moving along.


5. dump the master, stop old 4.1 server, start new 5.1 server and reload 
master dump file under 5.1 server ( binary logging is turned off)


Yes. No need to create binary logs for the rebuild.

6. dump the slave, stop old 4.1 server, start new 5.1 server and reload 
slave dump file under 5.1 server.


There is a faster way.

7. After loading is complete, test then start binary logging on master 
while still preventing updates to updates.


Once you have QA-ed your new 5.1 master, you can shut it down then copy 
the entire image (binaries and all) directly to the slave machine.  This 
is much faster than rebuilding from a dump and it ensures that you have 
identical data to start replication with.


After the copy, then restart the master with binary logging.


8. After loading slave, test then start slave (get configs in place and 
restart server).




Yes, it's always good to test any server image before putting it online.

The CHANGE MASTER TO command to use for the slave will be at position 4 
of the first binary log created after the binary image was captured.



I am thinking that in this scenario I dont have to bother with recording 
binlog file names and position etc etc.
That both servers will have the same databases abd replication and 
binary logging will start on the two databases with no data loss and 
continue forward.


You are correct. Because you are re-imaging your slave from your master, 
there is no need to track binary log or relay log positions.


See also:
http://dev.mysql.com/doc/refman/5.1/en/replication-howto-rawdata.html

** SAFETY ADVICE ** - always ensure you have a clean binary backup of 
any server you want to perform major maintenance to. In the off-chance 
that something does happen to go wrong, you will have it available for 
the fastest possible restore-to-original-state


--
Shawn Green, MySQL Senior Support Engineer
Sun Microsystems, Inc.
Office: Blountville, TN



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[Lawrence Sorrillo]

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 replication in this manner I would not use the CHANGE 
MASTER... I will just


master-host=xxx.xxx.xxx.xxx
master-connect-retry=60
master-user=auser
master-password=apassword

in the my.cnf file and restart the slave server. From there it should 
start reading the binary logs and committing changes properly.


Is this correct?

~Lawrence


Shawn Green wrote:

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 just going to replace it later.


3. stop binary logging on the master.


why? You can just disconnect the slave



4. stop replication on the slave.


You can do this at step 2. Just issue STOP SLAVE IO_THREAD;  The SQL 
thread can keep moving along.


5. dump the master, stop old 4.1 server, start new 5.1 server and 
reload master dump file under 5.1 server ( binary logging is turned off)


Yes. No need to create binary logs for the rebuild.

6. dump the slave, stop old 4.1 server, start new 5.1 server and 
reload slave dump file under 5.1 server.


There is a faster way.

7. After loading is complete, test then start binary logging on 
master while still preventing updates to updates.


Once you have QA-ed your new 5.1 master, you can shut it down then 
copy the entire image (binaries and all) directly to the slave 
machine.  This is much faster than rebuilding from a dump and it 
ensures that you have identical data to start replication with.


After the copy, then restart the master with binary logging.


8. After loading slave, test then start slave (get configs in place 
and restart server).




Yes, it's always good to test any server image before putting it online.

The CHANGE MASTER TO command to use for the slave will be at position 
4 of the first binary log created after the binary image was captured.



I am thinking that in this scenario I dont have to bother with 
recording binlog file names and position etc etc.
That both servers will have the same databases abd replication and 
binary logging will start on the two databases with no data loss and 
continue forward.


You are correct. Because you are re-imaging your slave from your 
master, there is no need to track binary log or relay log positions.


See also:
http://dev.mysql.com/doc/refman/5.1/en/replication-howto-rawdata.html

** SAFETY ADVICE ** - always ensure you have a clean binary backup of 
any server you want to perform major maintenance to. In the off-chance 
that something does happen to go wrong, you will have it available for 
the fastest possible restore-to-original-state







--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[Paul DuBois]

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 these 
 are started, changes can start?
 
 And in setting up replication in this manner I would not use the CHANGE 
 MASTER... I will just
 
 master-host=xxx.xxx.xxx.xxx
 master-connect-retry=60
 master-user=auser
 master-password=apassword
 
 in the my.cnf file and restart the slave server. From there it should start 
 reading the binary logs and committing changes properly.
 
 Is this correct?

You're upgrading to MySQL 5.1, for which several of those options no longer 
have any effect.  Better to use CHANGE MASTER. See:

http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-17.html

-- 
Paul DuBois
Sun Microsystems / MySQL Documentation Team
Madison, Wisconsin, USA
www.mysql.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[Tom Worster]

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 sorri...@jlab.org wrote:

 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, upgrade it, restart it, let the slave catch up.
 
 ?
 
 
 
 
 
 On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org 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.
 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 replication on the slave.
 5. dump the master, stop old 4.1 server, start new 5.1 server and reload
 master dump file under 5.1 server ( binary logging is turned off)
 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload
 slave dump file under 5.1 server.
 7. After loading is complete, test then start binary logging on master
 while still preventing updates to updates.
 8. After loading slave, test then start slave (get configs in place and
 restart server).
 
 I am thinking that in this scenario I dont have to bother with recording
 binlog file names and position etc etc.
 That both servers will have the same databases abd replication and
 binary logging will start on the two databases with no data loss and
 continue forward.
 
 
 Comments?
 
 ~Lawrence
 
 
 
 
 
 
   
 
 



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: upgrading mysql

[Suresh Kuna]

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 same. Configure the replication
between the two server.

By doing this, We will save the import time in second server.

Thanks
Suresh Kuna
MySQL DBA

On Wed, Jan 13, 2010 at 3:58 AM, Tom Worster f...@thefsb.org wrote:

 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 sorri...@jlab.org wrote:

  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, upgrade it, restart it, let the slave catch up.
 
  ?
 
 
 
 
 
  On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org 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.
  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 replication on the slave.
  5. dump the master, stop old 4.1 server, start new 5.1 server and
 reload
  master dump file under 5.1 server ( binary logging is turned off)
  6. dump the slave, stop old 4.1 server, start new 5.1 server and reload
  slave dump file under 5.1 server.
  7. After loading is complete, test then start binary logging on master
  while still preventing updates to updates.
  8. After loading slave, test then start slave (get configs in place and
  restart server).
 
  I am thinking that in this scenario I dont have to bother with
 recording
  binlog file names and position etc etc.
  That both servers will have the same databases abd replication and
  binary logging will start on the two databases with no data loss and
  continue forward.
 
 
  Comments?
 
  ~Lawrence
 
 
 
 
 
 
 
 
 



 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/mysql?unsub=sureshkumar...@gmail.com




-- 
Thanks
Suresh Kuna
MySQL DBA

Re: Upgrading MySQL from 5.0 to 5.1

[Claudio Nanni]

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.
In your case I would install the new 5.1 in a custom home (e.g.
/home/mysql5123)
use your previous my.cnf from the 5.0 installation to get all previous
settings and make it use the same datadir.
To force one installation to use ONE AND ONLY ONE my.cnf start the instance
with the command line option:
(E.g. --defaults-file=/home/mysql5123/my.cnf)
in this way no side effects will take place (as long you configure correctly
my.cnf to work from the new home)

let me know if this is enough, enough clear or just was better for me to
shut up!

Claudio




2009/3/22 s...@twinix.com

 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, etc.
 There's got to be a better way?

 I couldn't figure out how to get the new version 5.1 to see the file system
 (containing the database) that was in use by 5.0. I looked at all the
 documents and nowhere (or at least I couldn't see it) does it talk about
 upgrading the database. When you install the new version how do you get it
 ot upgrade and use the 5.0 database? Any pointers/help on this would be
 great for the next time I have to do this.

 Thanks.



 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com

Upgrading MySQL from 5.0 to 5.1

[samk]

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, etc. There's got to be a 
better way?

I couldn't figure out how to get the new version 5.1 to see the file system 
(containing the database) that was in use by 5.0. I looked at all the documents 
and nowhere (or at least I couldn't see it) does it talk about upgrading the 
database. When you install the new version how do you get it ot upgrade and use 
the 5.0 database? Any pointers/help on this would be great for the next time I 
have to do this.

Thanks.



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Upgrading MySQL 4.0 to 5.0

[John Pacylowski]

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://lists.mysql.com/[EMAIL PROTECTED]

upgrading mysql on RHEL4

[perl pra]

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

Re: upgrading mysql on RHEL4

[Saravanan]

Hi,

Take backup of the existing data before upgrading for safety. There is RHEL 4 
specific  rpm binary is existing in the downloading section. After installing 
run the required tools comes with mysql.


Before upgrading with existing datas read the documentation carefully.

http://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,
 
 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


  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: upgrading mysql on RHEL4

[Joerg Bruehe]

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) the download instructions.


HTH,
Jörg

-- 
Joerg Bruehe, Senior Production Engineer
MySQL AB, www.mysql.com


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading mysql questions

[Andreas Widerøe Andersen]

Hi,
I'm currently running several Joomla websites and phpBB forums on an old
FreeBSD server running mysql-server 3.23. Yesterday I upgraded the mysql
installation to 4.0.27 successfully. No problems at all. First I made
backups, then deinstalled mysql 3.23 and finally installed 4.0.27. I then
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 scripts etc, do they only affect the base mysql server (and
associated files)? What about all the databases (Ie. phpBB/Joomla) that was
created under 3.23, should I run some sort of upgrading script on these
also? Need some advice here. Sounds logic to me that they also need to be
updated/optimized for the new system - somehow.

I hope someone will be able to assist me a little here.

Thanks and best regards,
Andreas

Re: upgrading mysql...

[Daniel da Veiga]

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/downloads/mysql/5.0.html

It wasnt that hard...

--
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 General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

upgrading mysql...

[bruce]

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 unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Problems with timestamp field after upgrading MySQL Server.

[Yesmin Patwary]

Dear All,
   
  First of all, I would like to thank to Josh and Peter Brawley for their kind 
help on previous issue. 
   
  Here is another Issue:
  There are many tables that have timestamp field with 8 char (mmdd). I use 
this format all over our website and to create various reports.  Below is 
static php code that I used numerous places:
  ? 
   $year=substr($date, 0, 4);
   $month=substr($date, 4, 2);
   $day=substr($date, 6, 2); 
  ?
   
  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?
  
MySQL - 3.23
+++--
|  Field |   Type | Default (mmdd)
+++--
|log_date|timestamp(8)| 
  
MySQL - 4.1.12
++---+
|  Field |   Type| Default 
++---+
|log_date| timestamp |-00-00 00:00:00
   
  
Josh [EMAIL PROTECTED] wrote:
  You could rotate the output... basically get 1 row
with 11 columns (CA01_count,CA02_count,...,CA12_count)
(leaving out CA10) joining all 12 tables together...

Or... perhaps we can help with the timestamp issues
you are having and get you upgraded to later version
of mysql that supports nested SELECT statements.

--- Yesmin Patwary wrote:

 Dear All,
 
 I had some issues in past with timestamp fields as a
 result I am unable to upgrade to mysql 4.1 version. 
 I am sure below the query recommended by Josh works
 with 4.1 or above. Would it be possible to rewrite
 this query for 3.23 version? 
 
 Again, thank you Josh and all others for your kind
 help and comments.
 
 Josh wrote:
 Here's one method:
 
 SELECT cl1.list_name, count(*) as count
 FROM customerList cl1
 WHERE cl1.id IN (SELECT cl2.id FROM customerList cl2
 WHERE cl2.list_name='CA10')
 and cl1.list_name != 'CA10'
 GROUP BY cl1.list_name
 
 --- Yesmin Patwary wrote:
 
  Good morning all,
  
  We have 12 customer lists: CA01, CA02, ….,CA12. 
  
  Table: customerList
  +---+--+
  | list_name | id |
  +---+--+
  | CA10 | 20BE |
  | CA07 | 20BE |
  | CA11 | 20BE |
  | CA03 | 20BE |
  | CA10 | NQCR |
  | CA04 | NQCR |
  | CA02 | MVYK |
  | CA10 | 0BEC |
  | …AND SO ON. |
  +---+--+
  
  Each list has 25 to 350 customers. Same
  customer_id may exist in multiple lists. We need
 to
  compare CA10 list customer_id’s with other 11
 lists
  to find matching id count by list_name. The query
  output should be something similar below:
  +--+---+
  | list_name |count |
  +--+---+
  | CA05 | 60 |
  | CA07 | 42 |
  | CA01 | 35 |
  | CA03 | 28 |
  | CA09 | 15 |
  | …AND SO ON… |
  +---+--+
  
  Can this be done with a SELECT statement without
  using perl or php? 
  
  Thanks in advance for any help.
 
 
 -
 Yahoo! Mail
 Bring photos to life! New PhotoMail makes sharing a
 breeze. 


__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]




-
 Yahoo! Mail
 Use Photomail to share photos without annoying attachments.

Problems with timestamp field after upgrading MySQL Server.

[Yesmin Patwary]

Dear All,
   
  First of all, I would like to thank to Josh and Peter Brawley for their kind 
help on previous issue. 
   
  Here is another Issue:
  There are many tables that have timestamp field with 8 char (mmdd). I use 
this format all over our website and to create various reports.  Below is 
static php code that I used numerous places:
  ? 
   $year=substr($date, 0, 4);
   $month=substr($date, 4, 2);
   $day=substr($date, 6, 2); 
  ?
   
  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?
  
MySQL - 3.23
+++--
|  Field |   Type | Default (mmdd)
+++--
|log_date|timestamp(8)| 
  
MySQL - 4.1.12
++---+
|  Field |   Type| Default 
++---+
|log_date| timestamp |-00-00 00:00:00
   
  
Josh [EMAIL PROTECTED] wrote:
  You could rotate the output... basically get 1 row
with 11 columns (CA01_count,CA02_count,...,CA12_count)
(leaving out CA10) joining all 12 tables together...

Or... perhaps we can help with the timestamp issues
you are having and get you upgraded to later version
of mysql that supports nested SELECT statements.

--- Yesmin Patwary wrote:

 Dear All,
 
 I had some issues in past with timestamp fields as a
 result I am unable to upgrade to mysql 4.1 version. 
 I am sure below the query recommended by Josh works
 with 4.1 or above. Would it be possible to rewrite
 this query for 3.23 version? 
 
 Again, thank you Josh and all others for your kind
 help and comments.
 
 Josh wrote:
 Here's one method:
 
 SELECT cl1.list_name, count(*) as count
 FROM customerList cl1
 WHERE cl1.id IN (SELECT cl2.id FROM customerList cl2
 WHERE cl2.list_name='CA10')
 and cl1.list_name != 'CA10'
 GROUP BY cl1.list_name
 
 --- Yesmin Patwary wrote:
 
  Good morning all,
  
  We have 12 customer lists: CA01, CA02, ….,CA12. 
  
  Table: customerList
  +---+--+
  | list_name | id |
  +---+--+
  | CA10 | 20BE |
  | CA07 | 20BE |
  | CA11 | 20BE |
  | CA03 | 20BE |
  | CA10 | NQCR |
  | CA04 | NQCR |
  | CA02 | MVYK |
  | CA10 | 0BEC |
  | …AND SO ON. |
  +---+--+
  
  Each list has 25 to 350 customers. Same
  customer_id may exist in multiple lists. We need
 to
  compare CA10 list customer_id’s with other 11
 lists
  to find matching id count by list_name. The query
  output should be something similar below:
  +--+---+
  | list_name |count |
  +--+---+
  | CA05 | 60 |
  | CA07 | 42 |
  | CA01 | 35 |
  | CA03 | 28 |
  | CA09 | 15 |
  | …AND SO ON… |
  +---+--+
  
  Can this be done with a SELECT statement without
  using perl or php? 
  
  Thanks in advance for any help.
 
 
 -
 Yahoo! Mail
 Bring photos to life! New PhotoMail makes sharing a
 breeze. 


__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]




-
 Yahoo! Mail
 Use Photomail to share photos without annoying attachments.

Re: Problems with timestamp field after upgrading MySQL Server.

[Josh]

Sure is...

SELECT DATE_FORMAT(dateField,'%Y%m%d') as dateField

Take a look at:
http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html

-Josh

--- Yesmin Patwary [EMAIL PROTECTED] wrote:

 Dear All,

   First of all, I would like to thank to Josh and
 Peter Brawley for their kind help on previous issue.
 

   Here is another Issue:
   There are many tables that have timestamp field
 with 8 char (mmdd). I use this format all over
 our website and to create various reports.  Below is
 static php code that I used numerous places:
   ? 
$year=substr($date, 0, 4);
$month=substr($date, 4, 2);
$day=substr($date, 6, 2); 
   ?

   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?
   
 MySQL - 3.23
 +++--
 |  Field |   Type | Default (mmdd)
 +++--
 |log_date|timestamp(8)| 
   
 MySQL - 4.1.12
 ++---+
 |  Field |   Type| Default 
 ++---+
 |log_date| timestamp |-00-00 00:00:00

   
 Josh [EMAIL PROTECTED] wrote:
   You could rotate the output... basically get 1 row
 with 11 columns
 (CA01_count,CA02_count,...,CA12_count)
 (leaving out CA10) joining all 12 tables together...
 
 Or... perhaps we can help with the timestamp issues
 you are having and get you upgraded to later version
 of mysql that supports nested SELECT statements.
 
 --- Yesmin Patwary wrote:
 
  Dear All,
  
  I had some issues in past with timestamp fields as
 a
  result I am unable to upgrade to mysql 4.1
 version. 
  I am sure below the query recommended by Josh
 works
  with 4.1 or above. Would it be possible to rewrite
  this query for 3.23 version? 
  
  Again, thank you Josh and all others for your kind
  help and comments.
  
  Josh wrote:
  Here's one method:
  
  SELECT cl1.list_name, count(*) as count
  FROM customerList cl1
  WHERE cl1.id IN (SELECT cl2.id FROM customerList
 cl2
  WHERE cl2.list_name='CA10')
  and cl1.list_name != 'CA10'
  GROUP BY cl1.list_name
  
  --- Yesmin Patwary wrote:
  
   Good morning all,
   
   We have 12 customer lists: CA01, CA02, ….,CA12. 
   
   Table: customerList
   +---+--+
   | list_name | id |
   +---+--+
   | CA10 | 20BE |
   | CA07 | 20BE |
   | CA11 | 20BE |
   | CA03 | 20BE |
   | CA10 | NQCR |
   | CA04 | NQCR |
   | CA02 | MVYK |
   | CA10 | 0BEC |
   | …AND SO ON. |
   +---+--+
   
   Each list has 25 to 350 customers. Same
   customer_id may exist in multiple lists. We need
  to
   compare CA10 list customer_id’s with other 11
  lists
   to find matching id count by list_name. The
 query
   output should be something similar below:
   +--+---+
   | list_name |count |
   +--+---+
   | CA05 | 60 |
   | CA07 | 42 |
   | CA01 | 35 |
   | CA03 | 28 |
   | CA09 | 15 |
   | …AND SO ON… |
   +---+--+
   
   Can this be done with a SELECT statement without
   using perl or php? 
   
   Thanks in advance for any help.
  
  
  -
  Yahoo! Mail
  Bring photos to life! New PhotoMail makes sharing
 a
  breeze. 
 
 
 __
 Do You Yahoo!?
 Tired of spam? Yahoo! Mail has the best spam
 protection around 
 http://mail.yahoo.com 
 
 -- 
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:

http://lists.mysql.com/[EMAIL PROTECTED]
 
 
 
   
 -
  Yahoo! Mail
  Use Photomail to share photos without annoying
attachments.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Problems with timestamp field after upgrading MySQL Server.

[SGreen]

Alternatively, you might be able to re-render times and dates in their 
condensed format by auto-converting them to a numeric value. Try adding 
zero to your date columns in your select clauses. Once condensed, your 
substring code should begin working as before.

SELECT datecol +0 as  datecol
FROM ...

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


Josh [EMAIL PROTECTED] wrote on 03/13/2006 12:42:32 PM:

 Sure is...
 
 SELECT DATE_FORMAT(dateField,'%Y%m%d') as dateField
 
 Take a look at:
 http://dev.mysql.com/doc/refman/5.0/en/date-and-time-functions.html
 
 -Josh
 
 --- Yesmin Patwary [EMAIL PROTECTED] wrote:
 
  Dear All,
  
First of all, I would like to thank to Josh and
  Peter Brawley for their kind help on previous issue.
  
  
Here is another Issue:
There are many tables that have timestamp field
  with 8 char (mmdd). I use this format all over
  our website and to create various reports.  Below is
  static php code that I used numerous places:
? 
 $year=substr($date, 0, 4);
 $month=substr($date, 4, 2);
 $day=substr($date, 6, 2); 
?
  
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?
  
  MySQL - 3.23
  +++--
  |  Field |   Type | Default (mmdd)
  +++--
  |log_date|timestamp(8)| 
  
  MySQL - 4.1.12
  ++---+
  |  Field |   Type| Default 
  ++---+
  |log_date| timestamp |-00-00 00:00:00
  
  
  Josh [EMAIL PROTECTED] wrote:
You could rotate the output... basically get 1 row
  with 11 columns
  (CA01_count,CA02_count,...,CA12_count)
  (leaving out CA10) joining all 12 tables together...
  
  Or... perhaps we can help with the timestamp issues
  you are having and get you upgraded to later version
  of mysql that supports nested SELECT statements.
  
  --- Yesmin Patwary wrote:
  
   Dear All,
   
   I had some issues in past with timestamp fields as
  a
   result I am unable to upgrade to mysql 4.1
  version. 
   I am sure below the query recommended by Josh
  works
   with 4.1 or above. Would it be possible to rewrite
   this query for 3.23 version? 
   
   Again, thank you Josh and all others for your kind
   help and comments.
   
   Josh wrote:
   Here's one method:
   
   SELECT cl1.list_name, count(*) as count
   FROM customerList cl1
   WHERE cl1.id IN (SELECT cl2.id FROM customerList
  cl2
   WHERE cl2.list_name='CA10')
   and cl1.list_name != 'CA10'
   GROUP BY cl1.list_name
   
   --- Yesmin Patwary wrote:
   
Good morning all,

We have 12 customer lists: CA01, CA02, ….,CA12. 

Table: customerList
+---+--+
| list_name | id |
+---+--+
| CA10 | 20BE |
| CA07 | 20BE |
| CA11 | 20BE |
| CA03 | 20BE |
| CA10 | NQCR |
| CA04 | NQCR |
| CA02 | MVYK |
| CA10 | 0BEC |
| …AND SO ON. |
+---+--+

Each list has 25 to 350 customers. Same
customer_id may exist in multiple lists. We need
   to
compare CA10 list customer_id’s with other 11
   lists
to find matching id count by list_name. The
  query
output should be something similar below:
+--+---+
| list_name |count |
+--+---+
| CA05 | 60 |
| CA07 | 42 |
| CA01 | 35 |
| CA03 | 28 |
| CA09 | 15 |
| …AND SO ON… |
+---+--+

Can this be done with a SELECT statement without
using perl or php? 

Thanks in advance for any help.
   
   
   -
   Yahoo! Mail
   Bring photos to life! New PhotoMail makes sharing
  a
   breeze. 
  
  
  __
  Do You Yahoo!?
  Tired of spam? Yahoo! Mail has the best spam
  protection around 
  http://mail.yahoo.com 
  
  -- 
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe:
 
 http://lists.mysql.com/[EMAIL PROTECTED]
  
  
  
  
  -
   Yahoo! Mail
   Use Photomail to share photos without annoying
 attachments.
 
 
 __
 Do You Yahoo!?
 Tired of spam?  Yahoo! Mail has the best spam protection around 
 http://mail.yahoo.com 
 
 -- 
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

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.  Commands end with ; or \g.
Your MySQL connection id is 5 to server version: 4.1.11-standard

and, if it's the older 1, why does it state ver 4.1.11-standard, if 
it's the original..?  Which showed that mysql is also at 
/usr/bin/mysql, the older, I guess, that you alluded to, so, when 
typing mysql -p it is using the older client to connect to ver 
4.1.11-standard which is at /usr/local/mysql, yes..? Sorry, I'm still 
rather a newb at Linux also. 

`mysql` is the client, which as you surmise is the old version; the
MySQL daemon (server) process is `mysqld`, frequently started using
a script called `mysqld_safe` or `safe_mysqld` ; look in the 'bin'
directory of your MySQL install...
You may also find it useful to run something like:
prompt# find / -type f -name 'mysql*' -print
:: to see what-all's scattered around your system :-)
HTH!
Hi All,
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/bin, and 
after entering the correct password, I get the following,

[EMAIL PROTECTED] bin]# ./mysql -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/tmp/mysql.sock' (2)

If I run ./usr/bin/mysqlold I can connect. What am I not understanding 
with this..? Cheers, again.

Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Hassan Schroeder]

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/bin, and 
after entering the correct password, I get the following,

[EMAIL PROTECTED] bin]# ./mysql -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/tmp/mysql.sock' (2)

If I run ./usr/bin/mysqlold I can connect. What am I not understanding 
with this..? 
If it were me, I'd remove all traces of mysql* anything from the
system and start fresh. :-)
But in any case, which mysqld process is now running? I'm guessing
it's the old one. If so, kill it, and start up your new version
using an unambiguous path (e.g., /usr/local/mysql/bin/mysqld_safe).
Then try to connect with your new client.
HTH,
--
Hassan Schroeder - [EMAIL PROTECTED]
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com
  dream.  code.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

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 dir 
/usr/local/mysql/bin, and after entering the correct password, I get 
the following,

[EMAIL PROTECTED] bin]# ./mysql -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through 
socket '/tmp/mysql.sock' (2)

If I run ./usr/bin/mysqlold I can connect. What am I not 
understanding with this..? 

If it were me, I'd remove all traces of mysql* anything from the
system and start fresh. :-)
But in any case, which mysqld process is now running? I'm guessing
it's the old one. If so, kill it, and start up your new version
using an unambiguous path (e.g., /usr/local/mysql/bin/mysqld_safe).
Then try to connect with your new client.
HTH,
Hi All,
yeah, I'm seriously considering removing all trace of mysql. The startup 
script points to /usr/local/mysql/bin/mysqld_safe. That was why I was 
having the original problem. Running the latest mysql shouldn't be 
experiencing connection problems. What I don't understand, is, the old 
mysql can connect, but not the latest. Weird. Cheers.

Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

Simon Garner wrote:
On 2/05/2005 5:21 p.m., Mark Sargent wrote:
Hi All,
I did this below,
mysqlSET 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 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 your 
client is an older version.

-Simon
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 can't log onto the server as root. So, I tried following this 
page,

http://dev.mysql.com/doc/mysql/en/resetting-permissions.html
but got this,
[EMAIL PROTECTED] bin]# ./mysqld_safe --skip-grant-tables -u root 
[1] 5005
[EMAIL PROTECTED] bin]# Starting mysqld daemon with databases from 
/var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld.pid
050502 14:46:36  mysqld ended

[1]+  Done./mysqld_safe --skip-grant-tables -u root
But, jobs shows no running mysql.
Where am I..? Cheers.
Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Simon Garner]

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 can't log onto the server as root. So, I tried following this 
page,

I would suggest you start again by deleting the mysql database (ie 
/var/lib/mysql/mysql) and running mysql_install_db to reinitialise the 
privilege tables.

Alternatively try adding
old-passwords
to the [mysqld] section in your my.cnf file.
-Simon
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

Mark Sargent wrote:
Simon Garner wrote:
On 2/05/2005 5:21 p.m., Mark Sargent wrote:
Hi All,
I did this below,
mysqlSET 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 
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 your 
client is an older version.

-Simon
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 can't log onto the server as root. So, I tried following 
this page,

http://dev.mysql.com/doc/mysql/en/resetting-permissions.html
but got this,
[EMAIL PROTECTED] bin]# ./mysqld_safe --skip-grant-tables -u root 
[1] 5005
[EMAIL PROTECTED] bin]# Starting mysqld daemon with databases from 
/var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld.pid
050502 14:46:36  mysqld ended

[1]+  Done./mysqld_safe --skip-grant-tables -u root
But, jobs shows no running mysql.
Where am I..? Cheers.
Mark Sargent.
Hi All,
ok, I restarted, then did service mysql stop to stop the running mysql 
that is started at boot. I then ran, again, ./mysqld_safe 
--skip-grant-tables -u root  and then connected using mysql with 
success. Still don't understand why the client can't authenticate, when 
the master/client is the same machine. I also don't understand why jobs 
doesn't show the current running mysql as I thought appending  at the 
end of the cmd makes it run as a background, which jobs shows. Also, 
using kill 'process id' doesn't stop it either. Cheers.

Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

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.? Cheers.

P.S. I now can't log onto the server as root. So, I tried following 
this page,

I would suggest you start again by deleting the mysql database (ie 
/var/lib/mysql/mysql)
done
and running mysql_install_db to reinitialise the privilege tables.
get the following,
[EMAIL PROTECTED] scripts]# ./mysql_install_db
Could not find help file 'fill_help_tables.sql' in ./support-files or
inside ..
Alternatively try adding
old-passwords
to the [mysqld] section in your my.cnf file.
-Simon
Cheers.
Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

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 doesn't 
support it.? Cheers.

P.S. I now can't log onto the server as root. So, I tried following 
this page,

I would suggest you start again by deleting the mysql database (ie 
/var/lib/mysql/mysql)

done
and running mysql_install_db to reinitialise the privilege tables.

get the following,
[EMAIL PROTECTED] scripts]# ./mysql_install_db
Could not find help file 'fill_help_tables.sql' in ./support-files or
inside ..
Strange, had to move the script up 1 level to get it to run...then, when 
trying to run mysqld_safe, I get this,

[EMAIL PROTECTED] bin]# ./mysqld_safe
Starting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld.pid
050502 18:53:33  mysqld ended
and the startup script fails at boot now. What's going on, I can't even 
get it to run now..? Cheers.

Alternatively try adding
old-passwords
to the [mysqld] section in your my.cnf file.
-Simon
Cheers.
Mark Sargent.

Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

Mark Sargent wrote:
Mark Sargent wrote:
Simon Garner wrote:
On 2/05/2005 5:21 p.m., Mark Sargent wrote:
Hi All,
I did this below,
mysqlSET 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 
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 your 
client is an older version.

-Simon
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 can't log onto the server as root. So, I tried following 
this page,

http://dev.mysql.com/doc/mysql/en/resetting-permissions.html
but got this,
[EMAIL PROTECTED] bin]# ./mysqld_safe --skip-grant-tables -u root 
[1] 5005
[EMAIL PROTECTED] bin]# Starting mysqld daemon with databases from 
/var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld.pid
050502 14:46:36  mysqld ended

[1]+  Done./mysqld_safe --skip-grant-tables -u root
But, jobs shows no running mysql.
Where am I..? Cheers.
Mark Sargent.
Hi All,
ok, I restarted, then did service mysql stop to stop the running mysql 
that is started at boot. I then ran, again, ./mysqld_safe 
--skip-grant-tables -u root  and then connected using mysql with 
success. Still don't understand why the client can't authenticate, 
when the master/client is the same machine. I also don't understand 
why jobs doesn't show the current running mysql as I thought appending 
 at the end of the cmd makes it run as a background, which jobs 
shows. Also, using kill 'process id' doesn't stop it either. Cheers.

Mark Sargent.
Hi All,
ok, had to reboot, after removing the old table/running mysql_install_db 
--user=mysql for it to be ok. Now, can someone please explain why I am 
having this client/server problem in the 1st place, since I am using ver 
4.1 and the machine is both server/client..? Cheers.

Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Hassan Schroeder]

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 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.? 
Because you almost certainly have an existing, older version of
MySQL already installed with FC3, and it's first in your path; try:
prompt# which mysql
:: and see if it's the 4.1 version you installed. I'll bet it's not :-)
If so, remove it or set your PATH appropriately.
HTH,
--
Hassan Schroeder - [EMAIL PROTECTED]
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com
  dream.  code.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

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.? Cheers.


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.? 

Because you almost certainly have an existing, older version of
MySQL already installed with FC3, and it's first in your path; try:
prompt# which mysql
:: and see if it's the 4.1 version you installed. I'll bet it's not :-)
If so, remove it or set your PATH appropriately.
HTH,
Hi All,
h, that is annoying, as I did a yum remove mysql b4 installing 4.1. 
Shouldn't the yum remove, remove it fully..? Rather redundant if it 
doesnt, eh. Cheers.

[EMAIL PROTECTED] ~]# mysql -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5 to server version: 4.1.11-standard
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql
and, if it's the older 1, why does it state ver 4.1.11-standard, if it's 
the original..?  Which showed that mysql is also at /usr/bin/mysql, the 
older, I guess, that you alluded to, so, when typing mysql -p it is 
using the older client to connect to ver 4.1.11-standard which is at 
/usr/local/mysql, yes..? Sorry, I'm still rather a newb at Linux also. 
Cheers, again.

Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Hassan Schroeder]

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 \g.
Your MySQL connection id is 5 to server version: 4.1.11-standard

and, if it's the older 1, why does it state ver 4.1.11-standard, if it's 
the original..?  Which showed that mysql is also at /usr/bin/mysql, the 
older, I guess, that you alluded to, so, when typing mysql -p it is 
using the older client to connect to ver 4.1.11-standard which is at 
/usr/local/mysql, yes..? Sorry, I'm still rather a newb at Linux also. 
`mysql` is the client, which as you surmise is the old version; the
MySQL daemon (server) process is `mysqld`, frequently started using
a script called `mysqld_safe` or `safe_mysqld` ; look in the 'bin'
directory of your MySQL install...
You may also find it useful to run something like:
prompt# find / -type f -name 'mysql*' -print
:: to see what-all's scattered around your system :-)
HTH!
--
Hassan Schroeder - [EMAIL PROTECTED]
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com
  dream.  code.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Mark Sargent]

Hi All,
I did this below,
mysqlSET 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 requested by 
server;  consider upgrading MySQL client

What is this..? Why is it asking me to upgrade the client.? Cheers.
Mark Sargent.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Simon Garner]

On 2/05/2005 5:21 p.m., Mark Sargent wrote:
Hi All,
I did this below,
mysqlSET 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 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 your client 
is an older version.

-Simon
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: ERROR 1251: Client does not support authentication protocol requested by server; consider upgrading MySQL client

[John Schmidt]

Sounds like the MySQL 4.x Password hashing. Use this :
sET PASSWORD FOR 'root'@'localhost' = old_PASSWORD('whatafraka');\
Sheck out the  4.x doc about Pasword hashing for more
//jjs
www.intechgra.com

-Original Message-
From: Simon Garner [mailto:[EMAIL PROTECTED]
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,
 
 mysqlSET 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 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 your client 
is an older version.

-Simon

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: upgrading mysql on RH fedora core 3

[bruce]

hey...

i now have FC2 running mysql-4.1.10a, php5, apache 2.0.51.

for some reason, the mysql rpms that i got from rpmfind.net/rpm.pbone,
etc...  didn't seem to work, as i kept getting weird lib related errors...

i started using mysql-3.23 on FC2.

i basically followed the path/instructions from
http://www.whoopis.com/howtos/php5-mysql4-FC3-rpm.html, replacing my
system/requirements where applicable.

basic steps:
 1) use 'rpm -qa | grep -i mysql' to get all rpms dealing with mysql
 2) remove these rpms 'rpm -e ...'
 3) get the replacement rpms from www.mysql.com
 4) upgrade using 'rpm -Uvh '
 5) resolve any errors/issues...

for my system, i only needed to focus on the mysql, as i already had php5
up/running.

i chose this approach, as i didn't want to deal with rebuilding from source
at this time.

good luck!!




-Original Message-
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-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 same thing. My thinking was to grab the
mysql src.rpm from Fedora Core 4 test 1 and rebuild it on FC3:

rpmbuild --rebuild mysql...src.rpm

Please try that and see how it goes.

 also, this has to be running with apache/php/perl/etc...

My feeling is that apache does not need to be rebuilt.
PHP certainly does, from src.rpm, after the new mysql is installed
(including mysql-devel). I am not sure whether it would just work to
grab the PHP src.rpm from FC3 updates and rebuild it on top of the new
mysql, or get the PHP src.rpm from FC4-test and rebuild.
Perl is in the same situation, but it's probably even more complex.

If i were you, i would probably post on the fedora-test mailing list
and ask the same question.

Anyway, good luck and let us know how it goes.

--
Florin Andrei

http://florin.myip.org/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

upgrading mysql on RH fedora core 3

[bruce]

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 managed to do this, can you tell us exactly what rpm
packages you used? as you know, dealing with the rpms gets into dependency
hell, which we believe has a lot to do with our issues...

if you managed to get this version of mysql running on FC3, and you built it
from source, can you provide directions/pointers on what you did, where you
placed the resulting libs/etc...

also, this has to be running with apache/php/perl/etc...

thanks

bruce


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: upgrading mysql on RH fedora core 3

[Florin Andrei]

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 same thing. My thinking was to grab the
mysql src.rpm from Fedora Core 4 test 1 and rebuild it on FC3:

rpmbuild --rebuild mysql...src.rpm

Please try that and see how it goes.

 also, this has to be running with apache/php/perl/etc...

My feeling is that apache does not need to be rebuilt.
PHP certainly does, from src.rpm, after the new mysql is installed
(including mysql-devel). I am not sure whether it would just work to
grab the PHP src.rpm from FC3 updates and rebuild it on top of the new
mysql, or get the PHP src.rpm from FC4-test and rebuild.
Perl is in the same situation, but it's probably even more complex.

If i were you, i would probably post on the fedora-test mailing list
and ask the same question.

Anyway, good luck and let us know how it goes.

-- 
Florin Andrei

http://florin.myip.org/

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: upgrading mysql on RH fedora core 3

[Daniel Kasak]

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.
actually, if anybody's managed to do this, can you tell us exactly what rpm
packages you used? as you know, dealing with the rpms gets into dependency
hell, which we believe has a lot to do with our issues...

if you managed to get this version of mysql running on FC3, and you built it
from source, can you provide directions/pointers on what you did, where you
placed the resulting libs/etc...

also, this has to be running with apache/php/perl/etc...

thanks

bruce
  

I would strongly suggest backing up your databases first :)
I would also ( if possible ) do the import and testing on another PC,
while the production server continues.
You may have to recompile php and Perl's DBI drivers, or you *may* be
able to find some RPMs that will just 'drop in', but I don't use rpms so
I couldn't say. The DBI drivers aren't marked as stable yet on my distro
( Gentoo ), so be careful there.
If you use ODBC, you will have to upgrade to the latest version of
MyODBC - which has some bugs so scan the MyODBC mailing list first.

-- 
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: http://www.nusconsulting.com.au

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: upgrading mysql on RH fedora core 3

[Tom Crimmins]

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 to do to get this working
 correctly. actually, if anybody's managed to do this, can you tell us
 exactly what rpm packages you used? as you know, dealing with the
 rpms gets into dependency hell, which we believe has a lot to do with
 our issues... 
 
 if you managed to get this version of mysql running on FC3, and you
 built it from source, can you provide directions/pointers on what you
 did, where you placed the resulting libs/etc...
 
 also, this has to be running with apache/php/perl/etc...
 
 thanks
 
 bruce

I use mysql primarily on RHEL3, but I just upgraded a FC2 box just to try 
it. I was able to upgrade it using the rpm's from dev.mysql.com. I did
notice
one thing. The rpm install didn't seem to kill the old mysqld properly, so I

got an access denied right after the install. I ran the following as root:

#killall mysqld
#service mysql start

After that I was then able to connect just fine.

As far as perl, php, and apache, everything will continue to work without 
modification if you continue to use the old password hashes. You can force 
this. Refer to http://dev.mysql.com/doc/mysql/en/old-client.html,
specifically 
the old-password option.

To make perl work with the new passwords, all you need to do is build
DBD::mysql 
from source. To do this, uninstall the dbd-mysql rpm if you have it
installed. I 
can't remember the exact name because I don't use it. Then as root run:

#perl -e shell -MCPAN
cpaninstall DBD::mysql

Regards,

-- 
Tom Crimmins
Interface Specialist
Pottawattamie County, Iowa

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: upgrading mysql on RH fedora core 3

[Florin Andrei]

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) running,
  but needed to go to the higher version...
 
 I was about to attempt the same thing. My thinking was to grab the
 mysql src.rpm from Fedora Core 4 test 1 and rebuild it on FC3:
 
 rpmbuild --rebuild mysql...src.rpm

Hey, whaddayaknow, it worked! :-) I just rebuilt the FC4t1 mysql src.rpm on FC3.

It's just that i cannot try it, not today. I'll see if i can play with
it tomorrow. Ideally, i'd like to get a spare system, nuke all it's
content, do a fresh minimal install of FC3 (unselect all package
categories except development), apply all updates (yum update),
rebuild mysql-4, install it, then play with Perl and PHP and see if
they need to be rebuilt as well (hopefully not).

-- 
Florin Andrei

http://florin.myip.org/

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading mySql from 3.23 to 4.1.10

[Gleb Paharenko]

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:

 

 /usr/bin/mysql_fix_privilege_tables: line 185: /usr/bin/mysql: No such

 file or directory

 

 /usr/bin/mysql existed before I upgraded.

 

 I'm not sure what happen to it. I just downloaded the rpms and ran the

 upgraded.

 

 Files downloaded:

 MySQL-server-4.1.10-0.i386.rpm

 MySQL-shared-compat-4.1.10-0.i386.rpm

 

 Command:

 rpm -Uvh MySQL*

 

 Any help would be a big hand,

 

 Thanks

 Troy

 

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading mySql from 3.23 to 4.1.10

[Troy Richard]

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 existed before I upgraded.

I'm not sure what happen to it. I just downloaded the rpms and ran the
upgraded.

Files downloaded:
MySQL-server-4.1.10-0.i386.rpm
MySQL-shared-compat-4.1.10-0.i386.rpm

Command:
rpm -Uvh MySQL*

Any help would be a big hand,

Thanks
Troy


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: [PHP-DB] Upgrading mySQL

[Ingo Strüwing]

Hi,

your question suggests that you have installed MySQL already. Just
install the upgrade in the same way. Start reading at chapter 2.2.

If you got MySQL pre-installed with your operating system, you will need
an upgrade from your distributor anyway. The paths built in the official
MySQL binaries will most probable not match your distribution.

Am Mo, den 22.11.2004 schrieb GH um 22:02:
 What I have been asking for... is that the upgrade does not tell me
 *HOW* to install this upgrade. WHich file I should download etc I
 do not see this under the UPGRADE section... That is what I have been
 asking
 
 Also, it says on the manual (section 2.10) It is a good idea to
 rebuild and reinstall the Perl DBD::mysql module
 whenever you install a new release of MySQL. The same applies to other
 MySQL interfaces as well, such as the PHP mysql extension and the
 Python MySQLdb module. However I do not know how to do this and
 was asking how to for PHP 4.
 
 
 
 
 On Mon, 22 Nov 2004 15:55:25 +0100, Ingo Strüwing [EMAIL PROTECTED] wrote:
  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 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 looking for a guide of what commands I need to
   use and so forth. As I said in the inital mailing I made, I am a
   newbie to Linux.
  
   It also says that
   It is a good idea to rebuild and reinstall the Perl DBD::mysql module
   whenever you install a new release of MySQL. The same applies to other
   MySQL interfaces as well, such as the PHP mysql extension and the
   Python MySQLdb module.  [But now how to]
  
  Regards,
  Ingo
  --
  Ingo Strüwing, Senior Software Developer
  MySQL AB, www.mysql.com
  Office: +49 30 43672407
  
  Are you MySQL certified?  www.mysql.com/certification
  
 

Regards,
Ingo
-- 
Ingo Strüwing, Senior Software Developer
MySQL AB, www.mysql.com
Office: +49 30 43672407

Are you MySQL certified?  www.mysql.com/certification


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: [PHP-DB] Upgrading mySQL

[Ingo Strüwing]

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 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 looking for a guide of what commands I need to
 use and so forth. As I said in the inital mailing I made, I am a
 newbie to Linux.
 
 It also says that
 It is a good idea to rebuild and reinstall the Perl DBD::mysql module
 whenever you install a new release of MySQL. The same applies to other
 MySQL interfaces as well, such as the PHP mysql extension and the
 Python MySQLdb module.  [But now how to]

Regards,
Ingo
-- 
Ingo Strüwing, Senior Software Developer
MySQL AB, www.mysql.com
Office: +49 30 43672407

Are you MySQL certified?  www.mysql.com/certification


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: [PHP-DB] Upgrading mySQL

[GH]

What I have been asking for... is that the upgrade does not tell me
*HOW* to install this upgrade. WHich file I should download etc I
do not see this under the UPGRADE section... That is what I have been
asking

Also, it says on the manual (section 2.10) It is a good idea to
rebuild and reinstall the Perl DBD::mysql module
whenever you install a new release of MySQL. The same applies to other
MySQL interfaces as well, such as the PHP mysql extension and the
Python MySQLdb module. However I do not know how to do this and
was asking how to for PHP 4.




On Mon, 22 Nov 2004 15:55:25 +0100, Ingo Strüwing [EMAIL PROTECTED] wrote:
 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 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 looking for a guide of what commands I need to
  use and so forth. As I said in the inital mailing I made, I am a
  newbie to Linux.
 
  It also says that
  It is a good idea to rebuild and reinstall the Perl DBD::mysql module
  whenever you install a new release of MySQL. The same applies to other
  MySQL interfaces as well, such as the PHP mysql extension and the
  Python MySQLdb module.  [But now how to]
 
 Regards,
 Ingo
 --
 Ingo Strüwing, Senior Software Developer
 MySQL AB, www.mysql.com
 Office: +49 30 43672407
 
 Are you MySQL certified?  www.mysql.com/certification
 


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: [PHP-DB] Upgrading mySQL

[William R. Mussatto]

Warning!! Make sure the php module will handle the new password scheme in
4.1.  DBD::mysql from AS will not.  There are work arounds.  I'm having to
fall back to 4.0 because I can't get .jsp to work with 4.1 database (no
connection).

GH said:
 What I have been asking for... is that the upgrade does not tell me
 *HOW* to install this upgrade. WHich file I should download etc I do
 not see this under the UPGRADE section... That is what I have been
 asking

 Also, it says on the manual (section 2.10) It is a good idea to
 rebuild and reinstall the Perl DBD::mysql module
 whenever you install a new release of MySQL. The same applies to other
 MySQL interfaces as well, such as the PHP mysql extension and the
 Python MySQLdb module. However I do not know how to do this and was
 asking how to for PHP 4.




 On Mon, 22 Nov 2004 15:55:25 +0100, Ingo Strüwing [EMAIL PROTECTED]
 wrote:
 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 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 looking for a guide of what commands I need
 to use and so forth. As I said in the inital mailing I made, I am a
 newbie to Linux.
 
  It also says that
  It is a good idea to rebuild and reinstall the Perl DBD::mysql
 module whenever you install a new release of MySQL. The same applies
 to other MySQL interfaces as well, such as the PHP mysql extension
 and the Python MySQLdb module.  [But now how to]

 Regards,
 Ingo
 --
 Ingo Strüwing, Senior Software Developer
 MySQL AB, www.mysql.com
 Office: +49 30 43672407

 Are you MySQL certified?  www.mysql.com/certification



 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Fw: Mysql-4.1.7 and client library - Client does not support authentication protocol requested by server; consider upgrading MySQL client

[webmaster]

 Yare sure that this resolves my problem?
 My problem is the client graphical (webmin or phpmyadmin), working from
 shell (SSH) is all to place.
 Thanks
 Alessio


 - Original Message -
 From: Dathan Vance Pattishall [EMAIL PROTECTED]
 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 need to reinstall your mysql api library to talk to mysql-4.1.7:
4.1.7
  has a different auth implementation that is more secure then the 3.23
 mysql
  protocol which your using. I suggest you link against the C-api that
comes
  with 4.1.7.
 
 
 
  DVP
  
  Dathan Vance Pattishall http://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; consider upgrading MySQL
   client
  
   They are successful to install mysql-4.1.7 on o.s. solaris 8 thanks to
 the
   suggestions
   of Gleb Paharenko. Now when use webmin (last version 1.170) o
phpmyadmin
   (last version -2.6.0-pl2) I have this problem:
  
   DBI connect failed : Client does not support authentication 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
 
 
 



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Mysql-4.1.7 and client library - Client does not support authentication protocol requested by server; consider upgrading MySQL client

[webmaster]

They are successful to install mysql-4.1.7 on o.s. solaris 8 thanks to the 
suggestions
of Gleb Paharenko. Now when use webmin (last version 1.170) o phpmyadmin (last 
version -2.6.0-pl2) I have this problem:

DBI connect failed : Client does not support authentication 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

Re: Mysql-4.1.7 and client library - Client does not support authentication protocol requested by server; consider upgrading MySQL client

[William R. Mussatto]

 They are successful to install mysql-4.1.7 on o.s. solaris 8 thanks to
 the suggestions of Gleb Paharenko. Now when use webmin (last version
 1.170) o phpmyadmin (last version -2.6.0-pl2) I have this problem:

 DBI connect failed : Client does not support authentication 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 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 as work arounds.  When they update DBD::mysql this should
go away.

-- 
William R. Mussatto, Senior Systems Engineer
Ph. 909-920-9154 ext. 27
FAX. 909-608-7061



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Mysql-4.1.7 and client library - Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Jeff Smelser]

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 as work arounds.  When they update DBD::mysql this should
 go away.

There is a new version for this..

DBD-mysql-2.9004

I think thats the version that started supporting it.

Jeff


pgp06SFsJVeZj.pgp
Description: PGP signature

RE: Mysql-4.1.7 and client library - Client does not support authentication protocol requested by server; consider upgrading MySQL client

[Dathan Vance Pattishall]

You need to reinstall your mysql api library to talk to mysql-4.1.7: 4.1.7
has a different auth implementation that is more secure then the 3.23 mysql
protocol which your using. I suggest you link against the C-api that comes
with 4.1.7.



DVP

Dathan Vance Pattishall http://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; consider upgrading MySQL
 client
 
 They are successful to install mysql-4.1.7 on o.s. solaris 8 thanks to the
 suggestions
 of Gleb Paharenko. Now when use webmin (last version 1.170) o phpmyadmin
 (last version -2.6.0-pl2) I have this problem:
 
 DBI connect failed : Client does not support authentication 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



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: [PHP-DB] Upgrading mySQL

[GH]

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 looking for a guide of what commands I need to
use and so forth. As I said in the inital mailing I made, I am a
newbie to Linux.

It also says that
It is a good idea to rebuild and reinstall the Perl DBD::mysql module
whenever you install a new release of MySQL. The same applies to other
MySQL interfaces as well, such as the PHP mysql extension and the
Python MySQLdb module.  [But now how to]


Please Assist...
Thank You.

On Sun, 14 Nov 2004 19:55:52 -0800, Ardilla Roja [EMAIL PROTECTED] wrote:
 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 using the preinstalled versions of both mySQL and PHP (php4).
 
  I am a newbie to Linux and am a bit nervous.
 
  Thanks.
  
  --
  PHP Database Mailing List (http://www.php.net/)
  To unsubscribe, visit: http://www.php.net/unsub.php
 
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading mySQL

[GH]

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 unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: [PHP-DB] Upgrading mySQL

[Ardilla Roja]

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 using the preinstalled versions of both mySQL and PHP (php4).
 
 I am a newbie to Linux and am a bit nervous.
 
 Thanks.
 
 --
 PHP Database Mailing List (http://www.php.net/)
 To unsubscribe, visit: http://www.php.net/unsub.php
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading MySql on OSX 10.3.6

[karigna]

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 front end it also 
indicates that 4.0.15 is running. 

In /usr/local I have 3 MySql related directories: 

mysql 
mysql-max-4.1.7-apple-darwin7.5.0-powerpc 
mysql-max-4.0.20-apple-darwin7.3.0-powerpc 

My question is how do I get Navicat and the preferences panel to recognize 
4.1.7 and do I need to remove 4.0.20 and 4.0.15? 

Thanks. 

Kevin




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading MySql on OSX 10.3.6

[Santino]

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
At 11:17 -0600 10-11-2004, [EMAIL PROTECTED] wrote:
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 front end it also
indicates that 4.0.15 is running.

In /usr/local I have 3 MySql related directories:
mysql
mysql-max-4.1.7-apple-darwin7.5.0-powerpc
mysql-max-4.0.20-apple-darwin7.3.0-powerpc
My question is how do I get Navicat and the preferences panel to recognize
4.1.7 and do I need to remove 4.0.20 and 4.0.15?
Thanks.
Kevin

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: Upgrading MySQL erased all data

[Steven Roussey]

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--




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading MySQL erased all data

[Santino]

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 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 a frenzy
though).
-s

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading MySQL erased all data

[Steven Roussey]

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 a frenzy
though).

-s



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading MySQL erased all data

[Rhino]

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 (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 a
frenzy
 though).

 -s



 -- 
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading MySQL. Caveats or Cautions anyone?

[Egor Egorov]

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 link to read carefully: 
http://dev.mysql.com/doc/mysql/en/Upgrading-from-3.23.html

 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.html
 
 I see some things that confuse me a bit:
 I see this label:
 
 Linux (x86, glibc-2.2, static, gcc)
 ## Well, I've got glibc-2.3
 
 And I see this label:
 Linux (x86, glibc-2.3, dynamic, Intel C++ Compiler)
 ## Well, glibc-2.3 looks good, *but* I don't have
 ## the Intel C++ Compiler. Just gcc (GCC) 3.2.2
 
 Comments and pointers to docs would be appreciated.
 
 Thanks much
 tim





-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

RE: Upgrading MySQL. Caveats or Cautions anyone?

[Michael McTernan]

Hi,

I found that the Intel C++ version needed some libraries which weren't on my
RH9.0 system (this was when upgrading to 4.1.4g):

  libcprts.so.5
  libcxa.so.5
  libunwind.so.5

This seems to have been reported many times e.g.
http://bugs.mysql.com/bug.php?id=4408

The resolve was to get the libs from:

ftp://ftp.mysql.com/pub/mysql/download/icc-8.0-libs.tar.gz
MD5 checksum: 0970bbfb9fb076dfe995b3176bf90fad

Then extract them and put them somewhere sensible (I chose /usr/local/lib)
and then run ldconfig to find them.  Without these libs none of the mysql
apps would start.  I guess 4.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 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.html

I see some things that confuse me a bit:
I see this label:

Linux (x86, glibc-2.2, static, gcc)
## Well, I've got glibc-2.3

And I see this label:
Linux (x86, glibc-2.3, dynamic, Intel C++ Compiler)
## Well, glibc-2.3 looks good, *but* I don't have
## the Intel C++ Compiler. Just gcc (GCC) 3.2.2

Comments and pointers to docs would be appreciated.

Thanks much
tim
--
Tim Johnson [EMAIL PROTECTED]
  http://www.alaska-internet-solutions.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]







-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading MySQL. Caveats or Cautions anyone?

[Tim Johnson]

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.html

I see some things that confuse me a bit:
I see this label:

Linux (x86, glibc-2.2, static, gcc)
## Well, I've got glibc-2.3

And I see this label:
Linux (x86, glibc-2.3, dynamic, Intel C++ Compiler)
## Well, glibc-2.3 looks good, *but* I don't have
## the Intel C++ Compiler. Just gcc (GCC) 3.2.2

Comments and pointers to docs would be appreciated.

Thanks much
tim
-- 
Tim Johnson [EMAIL PROTECTED]
  http://www.alaska-internet-solutions.com

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading MySQL. Caveats or Cautions anyone?

[Eric Bergen]

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 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.html
 
 I see some things that confuse me a bit:
 I see this label:
 
 Linux (x86, glibc-2.2, static, gcc)
 ## Well, I've got glibc-2.3
 
 And I see this label:
 Linux (x86, glibc-2.3, dynamic, Intel C++ Compiler)
 ## Well, glibc-2.3 looks good, *but* I don't have
 ## the Intel C++ Compiler. Just gcc (GCC) 3.2.2
 
 Comments and pointers to docs would be appreciated.
 
 Thanks much
 tim
 --
 Tim Johnson [EMAIL PROTECTED]
   http://www.alaska-internet-solutions.com
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 



-- 
Eric Bergen
[EMAIL PROTECTED]

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading Mysql and Perl DBD

[sean c peters]

I now have MySQL 4.0.2 and MySQL 4.1.3 beta both installed and running on one 
machine. I want to be able to use the Perl DBI / DBD to connect to both 
servers. I understand that there have been some changes between the MySQL 
4.0.X and 4.1.X series that may require differently compiled DBD's.

So my question is, do i need to have 2 separate DBD versions, or will the 
newer one work for both MySQL servers. The old DBD does not work for the new 
server. This is demonstrated by the error message:

DBI-connect(...) 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 peters
[EMAIL PROTECTED]



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading Mysql and Perl DBD

[Michael Stassen]

This is covered in the manual 
http://dev.mysql.com/doc/mysql/en/Password_hashing.html: A 4.1 client can 
connect to a pre-4.1 server, because the client understands both the old and 
new password hashing mechanisms.  So, if you build the Perl modules against 
the 4.1.x library, you should be able to connect to either server.

Michael
sean c peters wrote:
I now have MySQL 4.0.2 and MySQL 4.1.3 beta both installed and running on one 
machine. I want to be able to use the Perl DBI / DBD to connect to both 
servers. I understand that there have been some changes between the MySQL 
4.0.X and 4.1.X series that may require differently compiled DBD's.

So my question is, do i need to have 2 separate DBD versions, or will the 
newer one work for both MySQL servers. The old DBD does not work for the new 
server. This is demonstrated by the error message:

DBI-connect(...) 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 peters
[EMAIL PROTECTED]


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading mySQL 3.23 to 4.0

[GH - CF]

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-gnu (i386) 
some days ago, I had the same problem.
Redhat's rpm packages mysql-3* and MySQL's new packages MySQL-4.0.20* 
are not compatible, because the are build in different ways - 
different nameing scheme and different content. Thatswhy this is no 
good idea to try rpm -Uvh 
I've deinstalled the old packages by rpm -e ... (save /etc/my.cnf 
and /var/lib/mysql before) and installed the new one on a 
'mysql-clean' base.

Bye, Wolfgang

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading mySQL 3.23 to 4.0

[environmentalny]

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:
[EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm 
MySQL-client-4.0.20-0.i386.rpm
warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5
error: Failed dependencies:
libmysqlclient.so.10 is needed by (installed) perl-DBD-MySQL-2.9003-4
libmysqlclient.so.10 is needed by (installed) mod_auth_mysql-20030510-4.1
libmysqlclient.so.10 is needed by (installed) php-mysql-4.3.4-11
[EMAIL PROTECTED] Desktop]#

I am not sure what I need to do can someone please assist. 

Thank You
Gary


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading mySQL 3.23 to 4.0

[Japheth Cleaver]

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.i386.rpm
and as root ran the following:
[EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm 
MySQL-client-4.0.20-0.i386.rpm
warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 
5072e1f5
error: Failed dependencies:
libmysqlclient.so.10 is needed by (installed) perl-DBD-MySQL-2.9003-4
libmysqlclient.so.10 is needed by (installed) 
mod_auth_mysql-20030510-4.1
libmysqlclient.so.10 is needed by (installed) php-mysql-4.3.4-11
[EMAIL PROTECTED] Desktop]#

I am not sure what I need to do can someone please assist.
Thank You
Gary

Install
- MySQL-shared-4.0.20-0.i386.rpm, and
- MySQL-shared-compat-4.0.20-0.i386.rpm as well.
And probably MySQL-devel-4.0.20-0.i386.rpm just for kicks.
The 2nd one is the specific package that should solve the problem, 
especially with the php-mysql package.

HTH,
Japheth J.C. Cleaver
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading mySQL 3.23 to 4.0

[environmentalny]

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: NOKEY, key ID 
5072e1f5
Preparing...### [100%]
   1:MySQL-shared-compat### [100%]

[EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm

warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5
Preparing...### [100%]
package MySQL-shared-4.0.20-0 is already installed

[EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm

warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5
Preparing...### [100%]
file /usr/bin/comp_err from install of MySQL-devel-4.0.20-0 conflicts with 
file from package mysql-3.23.58-9
file /usr/bin/mysql_config from install of MySQL-devel-4.0.20-0 conflicts with 
file from package mysql-3.23.58-9

[EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm 
MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm

warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5
Preparing...### [100%]
   1:MySQL-server   ### [ 33%]
Installing all prepared tables
040802 17:21:17  Warning: Asked for 196608 thread stack, but got 126976
040802 17:21:17  /usr/sbin/mysqld: Shutdown Complete
   
  
   
  
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h localhost.localdomain password 'new-password'
See the manual for more instructions.
   
  
NOTE:  If you are upgrading from a MySQL = 3.22.10 you should run
the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be
able to use the new GRANT command!
   
  
Please report any problems with the /usr/bin/mysqlbug script!
   
  
The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at https://order.mysql.com
   
  
   2:MySQL-client   ### [ 67%]
   3:MySQL-devel### [100%]
[EMAIL PROTECTED] Desktop]#
   
  
Does this mean success? Also, what does this line mean? 040802 17:21:17  Warning: 
Asked for 196608 thread stack, but got 126976

Thanks for the help

- Original Message -
From: Japheth Cleaver [EMAIL PROTECTED]
Date: Monday, 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.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:
 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm 
 MySQL-client-4.0.20-0.i386.rpm
 warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, 
 key ID 
 5072e1f5
 error: Failed dependencies:
  libmysqlclient.so.10 is needed by (installed) perl-DBD-
 MySQL-2.9003-4
  libmysqlclient.so.10 is needed by (installed) 
  mod_auth_mysql-20030510-4.1
  libmysqlclient.so.10 is needed by (installed) php-mysql-
 4.3.4-11
 [EMAIL PROTECTED] Desktop]#
 
 I am not sure what I need to do can someone please assist.
 
 Thank You
 Gary
 
 
 Install
 - MySQL-shared-4.0.20-0.i386.rpm, and
 - MySQL-shared-compat-4.0.20-0.i386.rpm as well.
 
 And probably MySQL-devel-4.0.20-0.i386.rpm

Re: Upgrading mySQL 3.23 to 4.0

[environmentalny]

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 assistance

- Original Message -
From: [EMAIL PROTECTED]
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: 
 NOKEY, key ID 5072e1f5
 Preparing...
 ### [100%]
   1:MySQL-shared-compat
 ### [100%]
 
 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm
 
 warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, 
 key ID 5072e1f5
 Preparing...
 ### [100%]
package MySQL-shared-4.0.20-0 is already installed
 
 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm
 
 warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, 
 key ID 5072e1f5
 Preparing...
 ### [100%]
file /usr/bin/comp_err from install of MySQL-devel-4.0.20-0 
 conflicts with file from package mysql-3.23.58-9
file /usr/bin/mysql_config from install of MySQL-devel-
 4.0.20-0 conflicts with file from package mysql-3.23.58-9
 
 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm 
 MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm
 
 warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, 
 key ID 5072e1f5
 Preparing...
 ### [100%]
   1:MySQL-server   
 ### [ 33%]
 Installing all prepared tables
 040802 17:21:17  Warning: Asked for 196608 thread stack, but got 
 126976040802 17:21:17  /usr/sbin/mysqld: Shutdown Complete


 


 
 PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
 To do so, start the server, then issue the following commands:
 /usr/bin/mysqladmin -u root password 'new-password'
 /usr/bin/mysqladmin -u root -h localhost.localdomain password 'new-
 password'See the manual for more instructions.


 
 NOTE:  If you are upgrading from a MySQL = 3.22.10 you should run
 the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be
 able to use the new GRANT command!


 
 Please report any problems with the /usr/bin/mysqlbug script!


 
 The latest information about MySQL is available on the web at
 http://www.mysql.com
 Support MySQL by buying support/licenses at https://order.mysql.com


 
   2:MySQL-client   
 ### [ 67%]
   3:MySQL-devel
 ### [100%]
 [EMAIL PROTECTED] Desktop]#


 
 Does this mean success? Also, what does this line mean? 040802 
 17:21:17  Warning: Asked for 196608 thread stack, but got 126976
 
 Thanks for the help
 
 - Original Message -
 From: Japheth Cleaver [EMAIL PROTECTED]
 Date: Monday, 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.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:
  [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-
 0.i386.rpm 
  MySQL-client-4.0.20-0.i386.rpm
  warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: 
 NOKEY, 
  key ID 
  5072e1f5
  error: Failed dependencies:
   libmysqlclient.so.10 is needed

Re: Upgrading mySQL 3.23 to 4.0

[environmentalny]

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, i think you must restart it 
 manually, 
 maybe using some of the init scripts.
 
 Carlos
 
 
 From: [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 CC: Japheth Cleaver [EMAIL PROTECTED]
 Subject: Re: Upgrading mySQL 3.23 to 4.0
 Date: Mon, 02 Aug 2004 17:31:03 -0400
 
 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 assistance
 
 - Original Message -
 From: [EMAIL PROTECTED]
 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:
   NOKEY, key ID 5072e1f5
   Preparing...
   ### [100%]
 1:MySQL-shared-compat
   ### [100%]
  
   [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm
  
   warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY,
   key ID 5072e1f5
   Preparing...
   ### [100%]
  package MySQL-shared-4.0.20-0 is already installed
  
   [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm
  
   warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY,
   key ID 5072e1f5
   Preparing...
   ### [100%]
  file /usr/bin/comp_err from install of MySQL-devel-
 4.0.20-0
   conflicts with file from package mysql-3.23.58-9
  file /usr/bin/mysql_config from install of MySQL-devel-
   4.0.20-0 conflicts with file from package mysql-3.23.58-9
  
   [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm
   MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm
  
   warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY,
   key ID 5072e1f5
   Preparing...
   ### [100%]
 1:MySQL-server
   ### [ 33%]
   Installing all prepared tables
   040802 17:21:17  Warning: Asked for 196608 thread stack, but got
   126976040802 17:21:17  /usr/sbin/mysqld: Shutdown Complete
  
  
  
  
  
  
   PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
   To do so, start the server, then issue the following commands:
   /usr/bin/mysqladmin -u root password 'new-password'
   /usr/bin/mysqladmin -u root -h localhost.localdomain password 
 'new-
   password'See the manual for more instructions.
  
  
  
   NOTE:  If you are upgrading from a MySQL = 3.22.10 you should run
   the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be
   able to use the new GRANT command!
  
  
  
   Please report any problems with the /usr/bin/mysqlbug script!
  
  
  
   The latest information about MySQL is available on the web at
   http://www.mysql.com
   Support MySQL by buying support/licenses at 
 https://order.mysql.com 
  
  
 2:MySQL-client
   ### [ 67%]
 3:MySQL-devel
   ### [100%]
   [EMAIL PROTECTED] Desktop]#
  
  
  
   Does this mean success? Also, what does this line mean? 040802
   17:21:17  Warning: Asked for 196608 thread stack, but got 126976
  
   Thanks for the help
  
   - Original Message -
   From: Japheth Cleaver [EMAIL PROTECTED]
   Date: Monday, 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.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:
[EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-
   0.i386.rpm
MySQL-client-4.0.20-0.i386.rpm
warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature:
   NOKEY,
key ID
5072e1f5
error: Failed dependencies:
 libmysqlclient.so.10 is needed by (installed) perl-
 DBD-
MySQL-2.9003-4
 libmysqlclient.so.10 is needed by (installed)
 mod_auth_mysql-20030510-4.1
 libmysqlclient.so.10 is needed by (installed) php-
 mysql-
4.3.4-11
[EMAIL PROTECTED] Desktop]#

I am not sure what I need to do can someone please assist.

Thank You
Gary
   
   
Install
- MySQL-shared-4.0.20-0.i386.rpm

Re: Upgrading mySQL 3.23 to 4.0

[Carlos Proal]

supposedly ?, you can check if the mysqld daemon is running with:
ps -ef | grep mysql
if the daemon is running then the error is something else but my first bet 
is that is not running.

Carlos
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Carlos Proal [EMAIL PROTECTED]
CC: [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, August 2, 2004 6:19 pm
Subject: Re: Upgrading mySQL 3.23 to 4.0

 The upgrade shutdown the database, i think you must restart it
 manually,
 maybe using some of the init scripts.

 Carlos


 From: [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 CC: Japheth Cleaver [EMAIL PROTECTED]
 Subject: Re: Upgrading mySQL 3.23 to 4.0
 Date: Mon, 02 Aug 2004 17:31:03 -0400
 
 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 assistance
 
 - Original Message -
 From: [EMAIL PROTECTED]
 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:
   NOKEY, key ID 5072e1f5
   Preparing...
   ### [100%]
 1:MySQL-shared-compat
   ### [100%]
  
   [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm
  
   warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY,
   key ID 5072e1f5
   Preparing...
   ### [100%]
  package MySQL-shared-4.0.20-0 is already installed
  
   [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm
  
   warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY,
   key ID 5072e1f5
   Preparing...
   ### [100%]
  file /usr/bin/comp_err from install of MySQL-devel-
 4.0.20-0
   conflicts with file from package mysql-3.23.58-9
  file /usr/bin/mysql_config from install of MySQL-devel-
   4.0.20-0 conflicts with file from package mysql-3.23.58-9
  
   [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm
   MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm
  
   warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY,
   key ID 5072e1f5
   Preparing...
   ### [100%]
 1:MySQL-server
   ### [ 33%]
   Installing all prepared tables
   040802 17:21:17  Warning: Asked for 196608 thread stack, but got
   126976040802 17:21:17  /usr/sbin/mysqld: Shutdown Complete
  
  
  
  
  
  
   PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
   To do so, start the server, then issue the following commands:
   /usr/bin/mysqladmin -u root password 'new-password'
   /usr/bin/mysqladmin -u root -h localhost.localdomain password
 'new-
   password'See the manual for more instructions.
  
  
  
   NOTE:  If you are upgrading from a MySQL = 3.22.10 you should run
   the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be
   able to use the new GRANT command!
  
  
  
   Please report any problems with the /usr/bin/mysqlbug script!
  
  
  
   The latest information about MySQL is available on the web at
   http://www.mysql.com
   Support MySQL by buying support/licenses at
 https://order.mysql.com 
  
  
 2:MySQL-client
   ### [ 67%]
 3:MySQL-devel
   ### [100%]
   [EMAIL PROTECTED] Desktop]#
  
  
  
   Does this mean success? Also, what does this line mean? 040802
   17:21:17  Warning: Asked for 196608 thread stack, but got 126976
  
   Thanks for the help
  
   - Original Message -
   From: Japheth Cleaver [EMAIL PROTECTED]
   Date: Monday, 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.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:
[EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-
   0.i386.rpm
MySQL-client-4.0.20-0.i386.rpm
warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature:
   NOKEY,
key ID
5072e1f5
error: Failed dependencies:
 libmysqlclient.so.10 is needed by (installed) perl

Re: Upgrading mySQL 3.23 to 4.0

[Batara Kesuma]

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 assistance

It seems like your MySQL server is not running. Try:
# /etc/init.d/mysql start

And check what does the error log say. On my Fedora it is in:
/var/lib/mysql/hostname.err


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading MySQL

[Carlos Sunden]

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
 


-
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.

Thinking About Upgrading MySQL, PHP, and phpmyAdmin

[[EMAIL PROTECTED]]

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 upgrading over the old?

Thank you.

Stephen Tiano


mail2web - Check your email from the web at
http://mail2web.com/ .



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Thinking About Upgrading MySQL, PHP, and phpmyAdmin

[Yves Goergen]

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 . But I recently upgraded to 4.0 series (on Win2k and a Linux
testbox) and had no problems with it. So changing this to 4.0.17 (latest
stable 4.0 release) should be OK. Also, upgrade should be documented there,
I don't know how this is done on MacOS. On Linux, you'd need to stop the
daemon, copy in the new program, run an update script and re-start it again.

And I personally don't use phpMyAdmin any more, but from 2.5 on, there were
all new features and all new (and old) bugs... Here, upgrading is just as
simple as deleting the old directory and replacing it by what you can
download from www.phpmyadmin.net . PMA is MySQL 4.0 ready.

-- 
Yves Goergen
[EMAIL PROTECTED]
Please don't CC me (causes double mails)


On Saturday, January 03, 2004 2:19 PM CET, [EMAIL PROTECTED] wrote:
 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 upgrading over the old?

 Thank you.

 Stephen Tiano

 
 mail2web - Check your email from the web at
 http://mail2web.com/ .


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading MySQL on RedHat 9

[Lenz Grimmer]

-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 (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 up
 my whole installation.
 
 My planned steps are to:
 
 1. mysqldump everything to a backup file
 2. stop the service
 3. uninstall all the current rpm's
 4. install the fresh rpm's
 5. startup
 6. \. the file from step 1
 
 Anything I need to lookout for?

If you want to keep apps that shipped with the distro but are linked
against the 3.23 libmysqlclient, you may want to install
MySQL-shared-compat to satisfy the RPM library dependencies.

 That should work, but after you install the new RPM files, use

 chkconfig --list mysql

 to make sure that the server is set to start on runlevels 2 through 5.
 If it's not, use:

 chkconfig --levels 2345 mysql on

 Otherwise, the server won't start automatically at system boot time.

 This problem has been seen on RH 8 and RH 9. I understand it's been
 fixed now, but I'm not sure if the fix is in the current release or
 the next one.

It will be fixed for 4.0.14:

http://bugs.mysql.com/bug.php?id=272

Bye,
LenZ
- -- 
 Lenz Grimmer [EMAIL PROTECTED]
 Senior Production Engineer
 MySQL GmbH, http://www.mysql.de/
 Hamburg, Germany

 For technical support contracts, visit https://order.mysql.com/?ref=mlgr
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE/BIQsSVDhKrJykfIRAsaIAJ0RkCCcoWOTJ1gHCkZ+MSvvt3vxBACfeW7X
P7xkEZ1GfESz7bwMpF4+5/E=
=aHHD
-END PGP SIGNATURE-

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Upgrading MySQL on RedHat 9

[Andrew Pierce]

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 up
my whole installation.

My planned steps are to:

1. mysqldump everything to a backup file
2. stop the service
3. uninstall all the current rpm's
4. install the fresh rpm's
5. startup
6. \. the file from step 1

Anything I need to lookout for?

Thanks.
Andrew



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Upgrading MySQL on RedHat 9

[Paul DuBois]

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 it when I try something like this and screw up
my whole installation.
My planned steps are to:

1. mysqldump everything to a backup file
2. stop the service
3. uninstall all the current rpm's
4. install the fresh rpm's
5. startup
6. \. the file from step 1
Anything I need to lookout for?
That should work, but after you install the new RPM files, use

chkconfig --list mysql

to make sure that the server is set to start on runlevels 2 through 5.
If it's not, use:
chkconfig --levels 2345 mysql on

Otherwise, the server won't start automatically at system boot time.

This problem has been seen on RH 8 and RH 9. I understand it's been
fixed now, but I'm not sure if the fix is in the current release or
the next one.
Thanks.
Andrew


--
Paul DuBois, Senior Technical Writer
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
Are you MySQL certified?  http://www.mysql.com/certification/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

upgrading mysql

[[EMAIL PROTECTED]]

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. 
Do I leave my current version of mysql alone and then rpm on my linux box the upgrade 
(new version)? Can someone help point me in the right direction? Thanks

Mike

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: upgrading mysql

[Tab Alleman]

[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
generically speaking, upgrading to 3.23.56 was easy:  I downloaded the
installation files to my server and unzipped them.  Stopped the MySQL
service AND mysqladmin (you will have errors if you don't do this!).
Then ran the setup.exe, restarted the service, checked mysql admin and
saw that the version had been updated, and smiled.  I would imagine if
you follow the corresponding linux-steps, you should have no problems.

Good luck,
Tab

mysql


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: upgrading mysql

[Jennifer Goodie]

On a linux box you do not have to stop everything like on Windows.  We
always leave our current version running, install the upgrade in a new
location with a new data dir (a snapshot of the live one).  We run the new
install on a different port than the live install so we can test it and what
not before switching over.  We always leave our installs in a directory that
gives the version info like mysql-3.23.55-pc-linux-i686 and then symlink a
directory named mysql to the version that should be live.  So when we decide
it is time to go live with the new install we change the conf to point to
the correct data dir and to be on the right port, stop mysqld, change the
symlink and then restart with the new version.  This allows for easy
rollbacks just in case.

We have had really poor luck with building from source on 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:[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 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
generically speaking, upgrading to 3.23.56 was easy:  I downloaded the
installation files to my server and unzipped them.  Stopped the MySQL
service AND mysqladmin (you will have errors if you don't do this!).
Then ran the setup.exe, restarted the service, checked mysql admin and
saw that the version had been updated, and smiled.  I would imagine if
you follow the corresponding linux-steps, you should have no problems.

Good luck,
Tab

mysql


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: upgrading mysql

[[EMAIL PROTECTED]]

Thank you for your reply.  OK, I understand that.  So what are the steps to install 
the file.  Isn't there an RPM or something.  Do I take the 4.0 binary and place it an 
any folder on my box?  Then go to that directory and type a lynix command to unpack 
and install the files?  Then, go to the config file (not sure which one), maybe the 
one in my database and point it to the new mqsql program?
I relly appreciate your help.

Thanks,
Mike

The following message was sent by Jennifer Goodie [EMAIL PROTECTED] on Fri, 21 Mar 
2003 14:36:43 -0800.

 On a linux box you do not have to stop everything like on Windows.  We
 always leave our current version running, install the upgrade in a new
 location with a new data dir (a snapshot of the live one).  We run the 
 new
 install on a different port than the live install so we can test it and 
 what
 not before switching over.  We always leave our installs in a directory 
 that
 gives the version info like mysql-3.23.55-pc-linux-i686 and then symlink 
 a
 directory named mysql to the version that should be live.  So when we decide
 it is time to go live with the new install we change the conf to point 
 to
 the correct data dir and to be on the right port, stop mysqld, change the
 symlink and then restart with the new version.  This allows for easy
 rollbacks just in case.
 
 We have had really poor luck with building from source on 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:[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 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
 generically speaking, upgrading to 3.23.56 was easy:  I downloaded the
 installation files to my server and unzipped them.  Stopped the MySQL
 service AND mysqladmin (you will have errors if you don't do this!).
 Then ran the setup.exe, restarted the service, checked mysql admin and
 saw that the version had been updated, and smiled.  I would imagine if
 you follow the corresponding linux-steps, you should have no problems.
 
 Good luck,
 Tab
 
 mysql
 

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: upgrading mysql

[Jeff Shapiro]

These links may help:
2.5.2 Upgrading From Version 3.23 to Version 4.0
http://www.mysql.com/doc/en/Upgrading-from-3.23.html
2.1.1 Installing MySQL on Linux
http://www.mysql.com/doc/en/Linux-RPM.html
2.6.1.1 Linux Notes for Binary Distributions
http://www.mysql.com/doc/en/Binary_notes-Linux.html
2.2 General Installation Issues
http://www.mysql.com/doc/en/General_Installation_Issues.html
At 16:59 -0500 3/21/03, [EMAIL PROTECTED] wrote:
Thank you for your reply.  OK, I understand that.  So what are the 
steps to install the file.  Isn't there an RPM or something.  Do I 
take the 4.0 binary and place it an any folder on my box?  Then go 
to that directory and type a lynix command to unpack and install the 
files?  Then, go to the config file (not sure which one), maybe the 
one in my database and point it to the new mqsql program?
I relly appreciate your help.

Thanks,
Mike
The following message was sent by Jennifer Goodie 
[EMAIL PROTECTED] on Fri, 21 Mar 2003 14:36:43 -0800.

 On a linux box you do not have to stop everything like on Windows.  We
 always leave our current version running, install the upgrade in a new
 location with a new data dir (a snapshot of the live one).  We run the
 new
 install on a different port than the live install so we can test it and
 what
 not before switching over.  We always leave our installs in a directory
 that
 gives the version info like mysql-3.23.55-pc-linux-i686 and then symlink
 a
 directory named mysql to the version that should be live.  So when we decide
 it is time to go live with the new install we change the conf to point
 to
 the correct data dir and to be on the right port, stop mysqld, change the
 symlink and then restart with the new version.  This allows for easy
 rollbacks just in case.
 We have had really poor luck with building from source on 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:[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 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
 generically speaking, upgrading to 3.23.56 was easy:  I downloaded the
 installation files to my server and unzipped them.  Stopped the MySQL
 service AND mysqladmin (you will have errors if you don't do this!).
 Then ran the setup.exe, restarted the service, checked mysql admin and
 saw that the version had been updated, and smiled.  I would imagine if
 you follow the corresponding linux-steps, you should have no problems.
 Good luck,
 Tab
 mysql

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
--

Jeff Shapiro, Colorado Springs, CO, USA

At work I *have* to use a Windows machine, at home I *get* to use a Mac.

-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Upgrading MySQL/Solaris 2.7

[John P]

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 but not for 2.7.

Or does this exploit not affect Solaris?

Thanks
John


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Upgrading MySQL/Solaris 2.7

[Lenz Grimmer]

-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 platform
 or should I wait for the binaries to be updated? There is a .54 release
 for 2.8 and 2.9 but not for 2.7.

 Or does this exploit not affect Solaris?

Unfortunately it does affect all platforms. Sadly, our Solaris 2.7 build
host has died (hardware failure) and we are currently unable to provide a
3.23.54 binary for Solaris 2.7 - sorry about that. However, I've already
received a hint from a user who is using our Solaris 2.8 binary on a 2.7
system - you might want to try that first before doing a compile by
yourself.

Bye,
LenZ
- -- 
For technical support contracts, visit https://order.mysql.com/?ref=mlgr
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /  Mr. Lenz Grimmer [EMAIL PROTECTED]
 / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Production Engineer
/_/  /_/\_, /___/\___\_\___/ Hamburg, Germany
   ___/   www.mysql.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE9/4ijSVDhKrJykfIRAsOqAJ46tYXvOiNnT7I8wqiVEYToO9WrTQCeNzPs
AQzcmaregampBpI8ff/B+Rs=
=FVJq
-END PGP SIGNATURE-


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

upgrading mysql on RedHat

[João Borsoi]

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.

First, I tried to upgrade the RPMs and got some dependence errors.
Specially with libmysqlclient.so.10. I guess RedHat RPMs may be compiled
not the same way. Is that correct? So, will I have to update all
packages with dependence problems also, like php? Or it's a better idea
compiling mysql? Any advices for my task?

Thanks a lot again,
Joao.




-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Upgrading mysql with mysql binary vs. compiling

[Greg Macek]

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



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Upgrading MySQL from 3.23.41 to 3.23.53a

[Rick Root]

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?  I tried 
using the RPM facility to install and upgrade the new packages I just 
downloaded but I get conflicts... ie...

[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: failed dependencies:
MySQL-server conflicts with mysql-server-3.23.41-1
libmysqlclient.so.10   is needed by mysql-server-3.23.41-1
libmysqlclient.so.10   is needed by perl-DBD-MySQL-1.2216-4
[root@frodo MySQL]#

So what should I do?  Do I need to actually remove the old MySQL first 
and then install the new one?

 - Rick Root


-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: Upgrading MySQL from 3.23.41 to 3.23.53a

[Black, Kelly W [PCS]]

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 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?  I tried 
using the RPM facility to install and upgrade the new packages I just 
downloaded but I get conflicts... ie...

[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: failed dependencies:
 MySQL-server conflicts with mysql-server-3.23.41-1
 libmysqlclient.so.10   is needed by mysql-server-3.23.41-1
 libmysqlclient.so.10   is needed by perl-DBD-MySQL-1.2216-4
[root@frodo MySQL]#

So what should I do?  Do I need to actually remove the old MySQL first 
and then install the new one?

  - Rick Root


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Upgrading MySQL from 3.23.41 to 3.23.53a

[Lars Andersson]

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: failed dependencies:
MySQL-server conflicts with mysql-server-3.23.41-1
libmysqlclient.so.10   is needed by mysql-server-3.23.41-1
So what should I do?  Do I need to actually remove the old MySQL first and 
then install the new one?

You are trying to replace the redhat installed mysql with MySQL:s rpms. Do 
things in this order and it should work (I don't promise it will work =)

1. do a full mysqldump of all your databases.
2. shutdown and remove mysql with rpm -e your-old-package
3. Install the new mysql, start it and check if your databases are intact. 
Else restore from dumps.

regards
/Lars


-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

upgrading mysql

[aaron]

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 
corrupted because of this? 

Can I just upgrade mysql? Will all databases have to be added again? 

I really just need the main mysql file replaced, but I don't know an easy 
way to do that. The original build directory is long past gone. 

Is upgrading a decent solution for this, or what else might I try? 

Thanks,
Aaron 

-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Upgrading mysql from 3.22 to 3.23

[Campbell McLeay]

Greetings,

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 symlink to point to the new 
distribution, and restart. However, I was wondering what data files had to be moved 
across and how this might be done. At a guess, I would assume everything in the 'data' 
subdirectory of the old distro should be copied across (using e.g., 'cp -pR') but I 
also noticed that there a number of files in the root directory called 
'recoftrans.XXX', where 'XXX' is a 3 digit number. Do these have to be moved as well? 
And is there anything else that has to be copied? 

Any help greatly appreciated.

Cheers,

Campbell  

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php