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:
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 using
I am attempting to upgrade using the source from 4.1.13 to 4.1.15 on a
Redhat 7.2 machine and have been experiencing problems using the mysql
client. I keep having to revert back to 4.1.13 as it installs just fine.
# mysql -h localhost -u root
Welcome to the MySQL monitor. Commands end
No InnoDB here, just some old ISAM tables.
Sorry about my stupidity on this one, I have only myself to blame...
I have a bunch of old-school ISAM tables that need to be converted to
MyISAM, is there any way to do this en-masse?
(I.E. not having to go through each DB in the DBMS and
ALTER TABLE
I have a MySQL DBMS running with a mysql DB that apparently is an InnoDB
DB, all other DBs in this DBMS are MyISAM. When I try to upgrade, I get
the following output:
041215 16:41:53 mysqld started
InnoDB: Resetting space id's in the doublewrite buffer
041215 16:41:57 InnoDB: Started; log
Hey folks,
My mysql-fu is minimal to the point of nonexistent, so please forgive any
vagaries that come across:
I've recently compiled 4.1.3 to replace 4.1.0 on a machine here where I
work. The compile and install went fine (as far as I can tell, anyway),
but when I try to start mysqld via the
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
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:
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: problem upgrading from
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 9
On Fri, 9 Jul 2004, Victor Pendleton wrote:
What
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 on Solaris 9
Okay, I changed
?
-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, I changed the datadir to /database/var, same error. The symlink
-
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, I changed the datadir to /database/var, same error. The symlink
is
definitely valid
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
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
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 then pops up this error message:
An error
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
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 error
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
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.
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 it
LU does:
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
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
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
-
From: Lance Uyehara [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, October 18, 2002 7:30 PM
Subject: problem upgrading
I was running mysql 3.23.26 on freebsd 4.6 without a problem. Then I
had
a
runaway high load cpu event and figured I should at least get later
code
writable and it still
doesn't work.
-Lance
Jerry
- Original Message -
From: Lance Uyehara [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, October 18, 2002 7:30 PM
Subject: problem upgrading
I was running mysql 3.23.26 on freebsd 4.6 without a problem. Then I had
a
runaway
I was running mysql 3.23.26 on freebsd 4.6 without a problem. Then I had a
runaway high load cpu event and figured I should at least get later code
before complaining. So I grabbed 3.23.52 (the latest freebsd package).
My databases are in /var/db/mysql.
My root partition is mounted readonly.
Friday, January 18, 2002, 10:36:46 PM, you wrote:
Ieoen I had 3.23.41 installed. It came with Rh7.2. I had some mistakes in initial
Ieoen start up . So I thought i would reinstall it. I downloaded the rpm for
Ieoen 3.23.47. And ran the rpm installation. I am not sure if it did the whole
Ieoen
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. I am not sure if it did the whole
install. Now I have a safe_mysqld and 2 other mysqld process runinng. But I
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
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
31 matches
Mail list logo
