Marcus Bointon wrote:
I installed (as root) the standard rpms over a working 4.1.10a
installation (also from standard rpms) from the mysql site with rpm - U,
and all went ok, except that the server failed to start after the
upgrade. I had a look at it from webmin too and noticed that it was
On 3 Aug 2005, at 13:58, Edward Vermillion wrote:
Is the mysql server running?
I only ask because I have the same problem on an FC1
installation, Starting MySQL..[FAILED], but the server is up
and running fine.
I'm thinking it has something to do with something the startup
script
Hello.
I've just successfully upgraded from 4.1.9 to 4.1.13 (all are
standard rpms for x86) on Fedora 3. Check that you able to start
MySQL with mysqld_safe (for example /usr/bin/mysqld_safe --user=mysql).
See:
http://dev.mysql.com/doc/mysql/en/starting-server.html
Marcus Bointon
resuming all above i can say that to my greatest regret nobody even
expects what the matter is :(
so i'll just try to install a newer version of server hoping the bug
will disappear
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
PS
after mysql reinstallation (upgrade from 4.1.12 to 4.1.13) from source
code with EXACTLY THE SAME ./configure options as before and the SAME
configuration file everything is OK
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
Hello Averyanov,
[EMAIL PROTECTED] wrote:
Hello Nuno,
Tuesday, July 26, 2005, 8:53:33 PM, you wrote:
[EMAIL PROTECTED] wrote:
(...)
When i try to execute the following query
(...)
i get this error:
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Hello Nuno,
Tuesday, July 26, 2005, 8:53:33 PM, you wrote:
[EMAIL PROTECTED] wrote:
(...)
When i try to execute the following query
(...)
i get this error:
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:6
Current database: test
I managed to install
MySQL-client-4.0.25-0.ia64.rpm
MySQL-server-4.0.25-0.ia64.rpm
MySQL-devel-4.0.25-0.ia64.rpm
but MySQL-shared-4.0.25-0.ia64.rpm was still giving me the same error
about missing a glibc library even though glibc 2.3 is installed.
Though the install worked, I now get:
[EMAIL
Hi Anne,
I managed to install
MySQL-client-4.0.25-0.ia64.rpm
MySQL-server-4.0.25-0.ia64.rpm
MySQL-devel-4.0.25-0.ia64.rpm
...
x86_64 != ia64
You have installed the wrong architecture executables. Try downloading the
x86_64 versions instead.
Also have a read of our Opteron (x86_64) HOWTO:
i've got a strange problem with concat() function
i have the following data structure:
CREATE TABLE table1 (
field1 int(11) NOT NULL auto_increment,
PRIMARY KEY (field1)
) ENGINE=MyISAM DEFAULT CHARSET=cp1251 AUTO_INCREMENT=3;
CREATE TABLE table2 (
field2 varchar(255) NOT NULL default ''
[EMAIL PROTECTED] wrote:
i've got a strange problem with concat() function
i have the following data structure:
CREATE TABLE table1 (
field1 int(11) NOT NULL auto_increment,
PRIMARY KEY (field1)
) ENGINE=MyISAM DEFAULT CHARSET=cp1251 AUTO_INCREMENT=3;
CREATE TABLE table2 (
field2
[EMAIL PROTECTED] wrote:
(...)
When i try to execute the following query
(...)
i get this error:
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:6
Current database: test
ERROR 2013 (HY000): Lost connection to MySQL server during query
Hello mysql,
i've got a strange problem with concat() function
i have the following data structure:
CREATE TABLE table1 (
field1 int(11) NOT NULL auto_increment,
PRIMARY KEY (field1)
) ENGINE=MyISAM DEFAULT CHARSET=cp1251 AUTO_INCREMENT=3;
CREATE TABLE table2 (
field2
Hi all,
The moral of the story, is don't run out of disk space, but it's a bit to
late for that now.
A quick scenario One master server, two backups replicating from the
master. Our data and bin logs are on two different partitions, and the
partition holding the bin logs, ran out of disk
Hi all,
I have a MySQL server version 4.1.10a, for pc-linux-gnu (i686)
installed (from official binary RPMs) and running.
My question is if there are problems from updating the server to the
most current version of the 4.1.x series, specially things that fail to
work, or database curruption
Nuno Pereira wrote:
Hi all,
I have a MySQL server version 4.1.10a, for pc-linux-gnu (i686)
installed (from official binary RPMs) and running.
My question is if there are problems from updating the server to the
most current version of the 4.1.x series, specially things that fail to
work
Hi Chris,
I have run into this myself before as well, where the partition housing
the bin log filled up. In our case, there weren't failed queries on the
master; the integrity of data on the master was fine, and the slave was
simply out of date, but not error-full. However, even in that case
Hello.
It is not clear from you message what's the problem. From your
calculations I can see that the length of int field in a flat
file row (BTW please send a piece of your file) is different
in mysqldump programs with different versions? How is the length
of integer fields related to
Hello.
This weird behavior is very similar to described at:
http://bugs.mysql.com/bug.php?id=7361
Nico Alberti [EMAIL PROTECTED] wrote:
Hi everybody.
During the migration of our mysql test server to version 5 I noticed a
problem when I tried to import a table that I dumped from
the version is 4.1.12.
show variables like this,
| character_set_client|
latin1
| character_set_connection|
latin1
| character_set_database |
latin1
|
Hi everybody.
During the migration of our mysql test server to version 5 I noticed a
problem when I tried to import a table that I dumped from our 4.1
production machine.
The table has some fields defined as float(31,30) (they came from an
old Access table converted with DBTools Manager). When I
Hello.
Any possible problems with this approach?
It is good, if it solved your problems.
So it works for me.
I've ended doing this in a different way. I've created a patch which forces=
a=20
file to be read - /etc/mysql/mysql-client.conf (which is the same as .my.cn=
f
, character_set_connection, character_set_results
are session variables. And with SET NAMES you're setting
@@character_xxx variables which are synonym for @@session.character_xxx.
I see.
In what way have you done your upgrade? If you haven't used mysqldump
you could get some problems. Make the dump, and restore
Hello.
I've tested your solution. It doesn't work for users which have SUPER
privilege. This mentioned at:
http://dev.mysql.com/doc/mysql/en/server-system-variables.html
However, it works with with ordinary users which don't have SUPER
privilege. Here are pieces of my my.cnf (the
=latin2
Now all my clients connect with latin2 as default.
Any possible problems with this approach?
--
Arkadiusz MiśkiewiczPLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/ http://ftp.pld-linux.org/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com
Hi,
Still having difficulty with stored functions. I downloaded and installed
MySQL 5.0.7 and
I *still* cannot get stored functions to work.
I used the example for hello from section 19.2.1 of the online documentation
for MySQL and the example code doesnt work for me either.
Below are the
At 11:41 -0700 7/7/05, Nic Stevens wrote:
Hi,
Still having difficulty with stored functions. I downloaded and installed
MySQL 5.0.7 and
I *still* cannot get stored functions to work.
I used the example for hello from section 19.2.1 of the online documentation
for MySQL and the example code
Nic,
At the end of the func, your sproc delimiter // needs to come before
restoration of the semi-colon as delimiter, thus:
DELIMITER //
CREATE FUNCTION hello (s CHAR(20)) RETURNS CHAR(50)
RETURN CONCAT('Hello, ',s,'!');
//
DELIMITER ;
PB
-
Nic Stevens wrote:
Hi,
Still having
Hi,
I have mysql 4.0 db with configuration:
set-variable = default-character-set=latin2
set-variable = character-set=latin2
now I'm trying to migrate to mysql 4.1.12 My current config is:
character-set-server=latin2
collation-server=latin2_general_ci
The problem is
. And with SET NAMES you're setting
@@character_xxx variables which are synonym for @@session.character_xxx.
In what way have you done your upgrade? If you haven't used mysqldump
you could get some problems. Make the dump, and restore it setting
the correct connection variables for mysql program
are going to
have problems with TIMESTAMP types. I was looking for solutions as to put +0
when selecting TIMESTAMP fields. But I can't imagine to change that in
thousands lines of PHP code by hand, I'm sure lots of my customers will have
no idea about how to fix that mistake so I'll have to fix
John Trammell wrote:
#!perl
use strict;
use warnings;
sub foo {
warn wantarray() in foo() is: , wantarray(), \n;
my @r = 3 .. 8;
return @r;
}
my @x = foo() or warn in ... or warn() #1\n;
warn [EMAIL PROTECTED]: @x\n;
my $x = foo() or warn in ... or warn() #2\n;
warn \$x: $x\n;
We have an application that has just upgraded to Debian sarge with mysql
upgrading from 3.23.49 to 4.0.24. As far as I know I have followed all
the procedures for upgrading the database.
Some queries always fail in DBD::mysql (in DBI) although they work OK
with the mysql client.
For example,
Oliver Elphick wrote:
which returns 0 rows, works correctly in mysql. But when it is passed
through this statement in Perl:
my @row = $dbh-selectrow_array($sql) or
failed(__FILE__, __LINE__,
Failed to run the sql statement with error
up window, it saves the project . But it never takes the
backup at scheduled time or any other time.
I can take backups manually by clicking on Execute backup now without any
problems.
I did all the configuration settings mentioned in the Mysql administrator
help. I went in options changed
Oliver Elphick wrote:
We have an application that has just upgraded to Debian sarge with mysql
upgrading from 3.23.49 to 4.0.24. As far as I know I have followed all
the procedures for upgrading the database.
Some queries always fail in DBD::mysql (in DBI) although they work OK
with the mysql
-
From: Michael Stassen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 21, 2005 12:48 PM
To: olly@lfix.co.uk
Cc: debian-user@lists.debian.org; mysql@lists.mysql.com
Subject: Re: Sarge problems with MySQL and DBI / DBD::mysql
Oliver Elphick wrote:
We have an application that has just
on Execute backup now without
any
problems.
I did all the configuration settings mentioned in the Mysql
administrator
help. I went in options changed the password setting to obscured. I
saw a
similar posting for this issue, so I tried the solution mentioned as
creating a new connection
Hello.
It is a fresh, brand new :) bug:
http://bugs.mysql.com/bug.php?id=11297
Elton Hughes wrote:
Hello All,
I am trying to install MySQL 4.1.12 on my Powermac G4. My OS is 10.4.1.
I downloaded the binary distribution from the MySQL website. I
uncompressed it and
Hello All,
I am trying to install MySQL 4.1.12 on my Powermac G4. My OS is
10.4.1. I downloaded the binary distribution from the MySQL website.
I uncompressed it and opened the .dmg installer. I ran the installer.
Where it prompted for the Administrator's password, I gave it. The
http://dev.mysql.com/doc/mysql/en/can-not-connect-to-server.html
Double check that mysqld is running. I usually find out that it's not
when I get that error.
kgt
Elton Hughes wrote:
Hello All,
I am trying to install MySQL 4.1.12 on my Powermac G4. My OS is
10.4.1. I downloaded the
Hello Kristen,
It looks like I am running mysqld.
- ps xa | grep mysqld
21281 p1- S 0:00.08 /bin/sh ./bin/mysqld_safe --datadir=/usr/
local/mysql/
21323 p1- R 0:00.98 /usr/local/mysql/bin/mysqld --defaults-
extra-file=/us
21324 p1- R 7:11.11 /bin/sh ./bin/mysqld_safe
case
throughout a given statement. See Section 9.2.2, Identifier Case
Sensitivity.
( http://dev.mysql.com/doc/mysql/en/windows-vs-unix.html )
Try using lower-case names to avoid facing problems when porting data
from windows to *nix-systems.
Regards,
TomH
--
PROSOFT EDV-Loesungen GmbH Co. KG
Hi,
Anyone experience this problem. I did the following:
C:\perlsrcmysql -f --user=root --password= --port=3307
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 48 to server version: 5.0.6-beta-nt-log
Type 'help;' or '\h' for help. Type '\c' to clear
Hi,
Anyone experience this problem. I did the following:
C:\perlsrcmysql -f --user=root --password= --port=3307
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 48 to server version: 5.0.6-beta-nt-log
Type 'help;' or '\h' for help. Type '\c' to clear the
Hi,
Hello.
Check the character sets with the following statement:
show variables like '%char%';
Here's the output:
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_results utf8
character_set_server latin1
character_set_system utf8
Hello.
If you're sure that data in your dump file is in latin1 character
set, you could perform something like:
mysql --default-character-set=latin1 dump_file
Roberto Jobet [EMAIL PROTECTED] wrote:
Hi,
Hello.
Check the character sets with the following =
Hi,
Thanks for your help.
Usually to export and import dump files I use phpmyadmin, so I'm not very much
familiar with the mysqldump command-line utility :-))
In the command line that you specify below, do I have to indicate the db name ?
Thanks in advance
Regards
Roberto Jobet
Hello.
Hello.
Yes, you should specify all necassary options
(database, login, -p switch for password).
Roberto Jobet [EMAIL PROTECTED] wrote:
Hi,
Thanks for your help.
Usually to export and import dump files I=
use phpmyadmin, so I'm not very much
familiar with the mysqldump
to 5-7 seconds with only a simple 1 table update
occurring.
Does anyone have experience with this and/or can provide some insight?
From: gerald_clark
If your applet is making connections on each page, you might be having
reverse dns problems.
From: Shawn Green
It sounds like you don't
Hi,
Thanks for your reply.
What do you mean by right character set ?
The default character set for ver. 4.1 is latin1, right ? This set should
support all western european languages !
Regarding --default-character-set command in chapter 10 is written that a way to
change settings is to
Hello.
Regarding --default-ch aracter-set command in chapter 10 is written that a
way to change settings is to recompile...
Is there another less painful way to do this ?
You may specify default character sets using options when you start
mysqld. See:
I am running mysql 4.0.18 on Windows 2003 server which also hosts my
apache tomcat server. My applet makes a connection to the mysql database
on the server as well as a socket connection to a service on the same
server. In the lab with only a hub between the client and server, the
application
Celona, Paul - AES [EMAIL PROTECTED] wrote on 06/03/2005 01:03:18
PM:
I am running mysql 4.0.18 on Windows 2003 server which also hosts my
apache tomcat server. My applet makes a connection to the mysql database
on the server as well as a socket connection to a service on the same
server. In
-7 seconds with only a simple 1 table update
occurring.
Does anyone have experience with this and/or can provide some insight?
If your applet is making connections on each page, you might be having
reverse dns
problems.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com
with this and/or can provide some insight?
From: gerald_clark
If your applet is making connections on each page, you might be having
reverse dns problems.
From: Shawn Green
It sounds like you don't have all of your indexes declared on your
production database.
There could also be an issue
Hi,
I'm trying to import a db dump made on ver. 4.0, on a new 4.1 version.
All accented characters (french, spanish) are replaced by a '?'
What it's the right way to import it ?
Thanks in advance
Roberto Jobet
Navighi a 4 MEGA
Hello.
Specify the right character set with --default-character-set command
line option for mysql (if you're using it for reading dump). Chapter 10
of the manual could be helpful. See:
http://dev.mysql.com/doc/mysql/en/charset.html
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
Hi there.
I've been having this problem when retrieving rows from a table
using mysql_fetch_row(). The problem is that sometimes it returns
null when I know that there are more records available. The behaviour
is intermittent too so its really difficult to track down.
I've tried it with MySQL
Hello.
You may debug your client. See:
http://dev.mysql.com/doc/mysql/en/debugging-client.html
Have you been at:
http://dev.mysql.com/doc/mysql/en/gone-away.html
Increase your packet size. See:
http://dev.mysql.com/doc/mysql/en/packet-too-large.html
Bradley Kite [EMAIL
Hi
A client of ours has experienced some rather serious hardware failures
resulting in disk errors and therefore corrupted InnoDB files.
We could not get mysql to restart unless the innodb_force_recovery was set to
5. In this situation we encountered failure when attempting to read from
On May 25, 2005, at 9:34 AM, David Brewster wrote:
A client of ours has experienced some rather serious hardware
failures resulting in disk errors and therefore corrupted InnoDB
files.
We could not get mysql to restart unless the innodb_force_recovery
was set to 5. In this situation we
problems
On May 25, 2005, at 9:34 AM, David Brewster wrote:
A client of ours has experienced some rather serious hardware
failures resulting in disk errors and therefore corrupted InnoDB
files.
We could not get mysql to restart unless the innodb_force_recovery
was set to 5
On May 25, 2005, at 10:06 AM, David Brewster wrote:
Here is the log dump :-
Thanks
David
050525 13:24:10 InnoDB: Started
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.15-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306
050525 13:24:11 InnoDB: Assertion failure in thread
-
From: Ware Adams [mailto:[EMAIL PROTECTED]
Sent: 25 May 2005 17:31
To: David Brewster
Cc: mysql@lists.mysql.com
Subject: Re: Restoring InnoDB databases from backups causing problems
On May 25, 2005, at 10:06 AM, David Brewster wrote:
Here is the log dump :-
Thanks
David
050525 13:24:10
Pete Harlan wrote:
In addition to failing the tests, I deployed the server on Machine 1
for a while and it failed quickly, with a simple insert hanging up and
kill threadID being unable to kill it. (The thread's state was
Killed, but it didn't go away and continued to block other threads
from
Pete Harlan wrote:
Hi,
and then it never comes back, presumably from the auto_increment
test. If I run the auto_increment test alone (i.e., ./mysql-test-run
auto_increment), it fails in this same way. When it's hung, mysqld
isn't using any CPU.
Also.. CPU isn't the only thing you should
On Mon, May 23, 2005 at 11:52:50PM -0700, Kevin Burton wrote:
Pete Harlan wrote:
In addition to failing the tests, I deployed the server on Machine 1
for a while and it failed quickly, with a simple insert hanging up and
kill threadID being unable to kill it. (The thread's state was
Hi,
MySQL is not getting very far through make test on 64-bit Debian,
MySQL 4.1.12. I've tried precompiled and self-compiled, and on two
different machines, both of which have been in use for a long time and
both of which run MySQL 4.0 (and its tests) without a problem.
On one machine:
Hello everyone, I'm just trying to grab one column of information and I
keep getting the exception thrown by this snippet of code in
coonection.cpp
if (lock()) {
if (throw_excptns) {
throw BadQuery(lock failed);
}
else {
as the mysql user and look at the database
with
no problems. My mysql version is 3.23.58 (upgraded from yum), php version
4.3.10, server is Fedora Core 2 kernel 2.6.5-1.358smp. Im pretty new to mysql
so be gentle and easy in any help. Everything was working fine prior to
Friday
of last
the message Unable to load database
indicated by configuration file or something similiar when trying to connect to
any database running on the server when the mysql user is running @localhost.
I can however login at terminal as the mysql user and look at the database with
no problems. My mysql
] wrote:
[-- text/plain, encoding 7bit, charset: ISO-8859-1, 74 lines --]
I'm attempting to configure mysql with InnoDB tables and I'm running
into problems. And am using the following version of mysqld-max, Ver
4.0.18-Max for suse-linux on i686 (Source distribution)
First I uncommented
when trying to connect to
any database running on the server when the mysql user is running @localhost.
I can however login at terminal as the mysql user and look at the database with
no problems. My mysql version is 3.23.58 (upgraded from yum), php version
4.3.10, server is Fedora Core 2 kernel
I'm attempting to configure mysql with InnoDB tables and I'm running
into problems. And am using the following version of mysqld-max, Ver
4.0.18-Max for suse-linux on i686 (Source distribution)
First I uncommented the following lines in /etc/my.cnf:
# Uncomment the following if you are using
Is it possible your data was changed during upgrade? How
have you performed it?
Andr$s Villanueva [EMAIL PROTECTED] wrote:
Hi! thanks for your response.
This are the values of the variables you asked for:
collation_connection: utf8_general_ci
collation_database:
Actually, I did a full backup, uninstalled everything, installed a clean
4.1.11 and restored the backup
The data seems to be fine. The funny thing is that if i change one of
the inners for a left everything works fine! I think it's a bug, and an
ugly one...
Andrés Villanueva
Gleb Paharenko
Hello.
Please, send the output of the following statements:
show variables like '%colla%';
show variables like '%char%';
Andr$s Villanueva [EMAIL PROTECTED] wrote:
Anyone??
Original Message
The tables are now entirely in utf8, and that is also the
Hi! thanks for your response.
This are the values of the variables you asked for:
collation_connection: utf8_general_ci
collation_database: utf8_general_ci
collation_server: utf8_general_ci
character_set_client: utf8
character_set_connection: utf8
character_set_database: utf8
Hi everyone! I'm havng the weirdest problem with mysql.
I had v1.1.07 and everything worked like a charm. But it turns out that
we had the need to move everything to UTF8 (until then, only the columns
in russian where set to utf8, and the rest was latin1).
Once we moved everything to utf8, this
: www.alchemetrics.co.uk
Email: [EMAIL PROTECTED]
-Original Message-
From: Andrés Villanueva [mailto:[EMAIL PROTECTED]
Sent: 03 May 2005 15:33
To: mysql@lists.mysql.com
Subject: Collation problems or messed joins?
Hi everyone! I'm havng the weirdest problem with mysql.
I had v1.1.07
SMARTER DATA , FASTER
Tel: 0118 902 9000 (swithcboard)
Tel: 0118 902 9099 (direct)
Web: www.alchemetrics.co.uk
Email: [EMAIL PROTECTED]
-Original Message-
From: Andrés Villanueva [mailto:[EMAIL PROTECTED]
Sent: 03 May 2005 15:33
To: mysql@lists.mysql.com
Subject: Collation problems or messed
@lists.mysql.com
Subject: Collation problems or messed joins?
Hi everyone! I'm havng the weirdest problem with mysql.
I had v1.1.07 and everything worked like a charm. But it turns out
that
we had the need to move everything to UTF8 (until then, only the
columns
in russian where set to utf8
Hello.
But I've been told that the support for Unicode is not yet good in MySQL. Is
it possible to find whether this is true?
I don't think so, as most bugs related to utf8 are reported about the fifth
version
while utf8 support in fourth seems very stable.
Raul Mauri [EMAIL
I use the MyQSL Query Browser for a library database.
I have come across a problem in MySQL: Using extended characters, as , is not
a problem, as long as they are present in the standard 256 characters of a
font. Things become more difficult when I need other East Europe characters.
Could
MySQL: 4.1.11
OS: Solaris
I have a database that stores Japanese in utf-8. I have NO problems if
the field is defined as VARCHAR, but if the field is defined as TEXT any
data after an extended character (Japanese, special symbols etc.) gets
truncated. Looking at the archives I ran
I have a Pentium III with Fedora Core 3 notebook and I need to install
MySQL 4.1 on it.
There was no mysql installed before so I've downloaded the packages and
did what I usually do to install
the packages. They install great. But when I try to run MySQL I have
problems as it does not run
It only shows this:
050413 23:53:35 mysqld started
050413 23:53:35 mysqld ended
Nothing conclusive.
prasanna a wrote:
Hi
please cat the below error file and see
/var/lib/mysql/presario2700.err
__
Do you Yahoo!?
Yahoo! Mail - Find what you need with new
I have a Pentium III with Fedora Core 3 notebook and I need to install
MySQL 4.1 on it.
There was no mysql installed before so I've downloaded the packages and
did what I usually do to install
the packages. They install great. But when I try to run MySQL I have
problems as it does not run
I don't
have the link handy. Basically you can realx the policy via the targetted
settings.
Good luck
//jjs
-Original Message-
From: C.F. Scheidecker Antunes [mailto:[EMAIL PROTECTED]
Sent: Wed 4/13/2005 10:56 PM
To: mysql@lists.mysql.com
Subject: Problems installing MySQL 4.1 under
Hello all,
I now have disabled my SELinux and so it should work.
However it still does not work.
I have a bunch of errors now on my .err file that I am copying bellow.
I've tried to create the tables again by issuing mysql_install_db and then
tried to run the daemon.
Is there any ideias on how to
I am running MySQL-server-4.1.8-0 without problem on FC3.
This could also be hardware related.
Joey
-Original Message-
From: C.F. Scheidecker Antunes [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 14, 2005 1:24 PM
To: Mysql List
Subject: Still having problems with MySQL 4.1
C.F. Scheidecker Antunes wrote:
Hello all,
I now have disabled my SELinux and so it should work.
However it still does not work.
I have a bunch of errors now on my .err file that I am copying bellow.
I've tried to create the tables again by issuing mysql_install_db and
then
tried to run the
the new server and running mysqlcheck -r -v -A, I
experienced the following problems on about 15% of my tables (seemed
to be quite random, i.e. not only the biggest or most used ones):
Christian, do you have any of that tables ? Can you upload one of them
(preferably, the smallest one) to our
upgrading on dev.mysql.com.
After starting the new server and running mysqlcheck -r -v -A, I
experienced the following problems on about 15% of my tables (seemed
to be quite random, i.e. not only the biggest or most used ones):
Christian, do you have any of that tables ? Can you upload
On Apr 8, 2005, at 12:21 PM, Adam Arrowood wrote:
I just installed the 32-bit SPARC Solaris package
(mysql-standard-4.1.11-sun-solaris2.9-sparc.pkg.gz) in made a symbolic
link to the install directory as /usr/local/mysql . I am having the
following problems:
1) when I start mysql
I know this sounds like a stupid question, but I am a complete novice on
MySQL.
I have a Linux box at work with SuSE 9.0 on it, with the default
installation of MySQL 4.0.1 on it. I did not know what I was doing when I
tried to uninstall MySQL using the rpm -e MySQL command. Anyway, I tried
the new server and running mysqlcheck -r -v -A, I
experienced the following problems on about 15% of my tables (seemed
to be quite random, i.e. not only the biggest or most used ones):
Christian, do you have any of that tables ? Can you upload one of them
(preferably, the smallest one) to our
I just installed the 32-bit SPARC Solaris package
(mysql-standard-4.1.11-sun-solaris2.9-sparc.pkg.gz) in made a symbolic
link to the install directory as /usr/local/mysql . I am having the
following problems:
1) when I start mysql with the included mysql.server script, I get the
following
Hello
I've just run into deep troubles while upgrading from 4.0.24 to 4.1.10a
using precomiled Debian packages on Debian Woody although I read the
comments regarding upgrading on dev.mysql.com.
After starting the new server and running mysqlcheck -r -v -A, I
experienced the following problems
501 - 600 of 2763 matches
Mail list logo
