Re: Problem Upgrading

Thanks for pointing me in that direction. The client from the binary distro works fine. I guess I should just stick with the binaries ;-) Ed Gleb Paharenko wrote: >If you want to debug this issue, have a look here: > http://dev.my

Re: Problem Upgrading

Hello. If you want to debug this issue, have a look here: http://dev.mysql.com/doc/refman/5.0/en/debugging-client.html But if I were you I would check first if mysql client from the official binaries produces the same faults. Ed Kasky wrote: > > I am attempting to upgrade usin

Re: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

Swany, I do indeed have a host.frm file, and the timestamp is from 2000. Unfortunately, I've had to start up 4.1.0 again and leave it up as folks here have to work on the db. Since they won't be working tomorrow, I'll try to remove the host.frm (also perhaps the host.ISD and host.ISM?) file tomor

Re: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

Do you have a hosts.MYD, or a hosts.frm file? If you do, and there is no .MYI file, perhaps the older version is just ignoring the table and not making it available while the newer version errors out. If those files exist, try removing them from the data directory (move them somewhere else) then

RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

> -Original Message- > From: [EMAIL PROTECTED] > To: Victor Pendleton > Cc: '[EMAIL PROTECTED] '; ''[EMAIL PROTECTED] ' ' > Sent: 7/9/04 4:15 PM > Subject: RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9 > > Okay,

RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

irectory? > > -Original Message- > From: [EMAIL PROTECTED] > To: Victor Pendleton > Cc: '[EMAIL PROTECTED] '; ''[EMAIL PROTECTED] ' ' > Sent: 7/9/04 4:15 PM > Subject: RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9 > > Okay,

RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

When you ls to /database/var do you see the mysql/ directory? -Original Message- From: [EMAIL PROTECTED] To: Victor Pendleton Cc: '[EMAIL PROTECTED] '; ''[EMAIL PROTECTED] ' ' Sent: 7/9/04 4:15 PM Subject: RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta

RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

nd see if the MySQL server starts up? > > -Original Message- > From: [EMAIL PROTECTED] > To: Victor Pendleton > Cc: 'John Fink '; '[EMAIL PROTECTED] ' > Sent: 7/9/04 4:08 PM > Subject: RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris

RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

Is the symlink still valid? Can you point the data directory variable to this location and see if the MySQL server starts up? -Original Message- From: [EMAIL PROTECTED] To: Victor Pendleton Cc: 'John Fink '; '[EMAIL PROTECTED] ' Sent: 7/9/04 4:08 PM Subject: RE: pr

RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

On Fri, 9 Jul 2004, Victor Pendleton wrote: > What is the location of your data/mysql directory? > It's actually in /database/var. There's a symlink in /opt/mysql that points it over. Could a symlink be the problem? jf -- MySQL General Mailing List For list archives: http://lists.mysql.com

RE: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9

What is the location of your data/mysql directory? -Original Message- From: John Fink To: [EMAIL PROTECTED] Sent: 7/9/04 3:49 PM Subject: problem upgrading from 4.1.0-alpha to 4.1.3-beta on Solaris 9 Hey folks, My mysql-fu is minimal to the point of nonexistent, so please forgive any va

RE: Problem Upgrading 3.23.54 > 3.23.56

miguel solórzano wrote: > Some program has locked C:\mysql\bin\libmySQL.dll, if you can > delete it. Indeed, my server didn't even want me to delete the file, until I checked the process list and realized what was locking it: winmysqladmin. Duh... I shut that down and everything went smoothly.

RE: Problem Upgrading 3.23.54 > 3.23.56

At 14:04 21/03/2003 -0500, Tab Alleman wrote: > Most probably you are running a server and the setup program > fails to rewrite the file. Before run the setup.exe stop the > current server. Most probably you are correct. :) I stopped the server and ran the set-up again, and this time it got much

RE: Problem Upgrading 3.23.54 > 3.23.56

> Most probably you are running a server and the setup program > fails to rewrite the file. Before run the setup.exe stop the > current server. Most probably you are correct. :) I stopped the server and ran the set-up again, and this time it got much further, but I then encountered a new erro

Re: Problem Upgrading 3.23.54 > 3.23.56

At 13:26 21/03/2003 -0500, Tab Alleman wrote: Hi, Ok now I've got my database completely copied on another server, so now I'm doing a trial run of upgrading the copy-db to 3.23.56. I unzipped the stuff and ran the SETUP.exe and after setting the parameters, the SetUp programs runs a little bit and

re: re: Re: problem upgrading

Hello Lance, Wednesday, October 23, 2002, 4:16:16 PM, you wrote: >>LU> I have /tmp symlinked to /var/tmp, and /var is a writable partition, >>while / >>LU> is readonly. When / is readonly mysqld is not able to run. >> >>LU> I've tracked down the problem to the safe_mysqld script. The problem is

re: Re: problem upgrading

At 03:29 PM 10/23/02 +0300, Egor Egorov wrote: Lance, Wednesday, October 23, 2002, 3:23:10 AM, you wrote: LU> I have /tmp symlinked to /var/tmp, and /var is a writable partition, while / LU> is readonly. When / is readonly mysqld is not able to run. LU> I've tracked down the problem to the saf

re: Re: problem upgrading

Lance, Wednesday, October 23, 2002, 3:23:10 AM, you wrote: LU> I have /tmp symlinked to /var/tmp, and /var is a writable partition, while / LU> is readonly. When / is readonly mysqld is not able to run. LU> I've tracked down the problem to the safe_mysqld script. The problem is it LU> does: LU>

Re: problem upgrading

To recap I am trying to run 3.23.52 on FreeBSD 4.6. I have /tmp symlinked to /var/tmp, and /var is a writable partition, while / is readonly. When / is readonly mysqld is not able to run. I've tracked down the problem to the safe_mysqld script. The problem is it does: USER_OPTION="" if

Re: problem upgrading

> I believe you need to move the socket which defaults to /tmp. If you move > it to /var/run or /var/tmp, you should be good to go. I think you can > either set the location at compile time or in the config files. Thanks for the response! I have /tmp symlinked to /var/tmp, and /var is mounted w

Re: problem upgrading

> > I believe you need to move the socket which defaults to /tmp. If you move > > it to /var/run or /var/tmp, you should be good to go. I think you can > > either set the location at compile time or in the config files. > > Thanks for the response! > I have /tmp symlinked to /var/tmp, and /var i

RE: Problem Upgrading

Islam, Sharif wrote: > I had 3.23.41 installed. It came with Rh7.2. I had some mistakes in initial > start up . So I thought i would reinstall it. I downloaded the rpm for > 3.23.47. And ran the rpm installation. >You got the 3.23.47 RPM from MySQL's site, I presume? That RPM is not an Yes

Re: Problem Upgrading

Islam, Sharif wrote: > I had 3.23.41 installed. It came with Rh7.2. I had some mistakes in initial > start up . So I thought i would reinstall it. I downloaded the rpm for > 3.23.47. And ran the rpm installation. You got the 3.23.47 RPM from MySQL's site, I presume? That RPM is not an upgrade