2014/1/7
> 2014/01/06 17:07 +0100, Reindl Harald
> what about look in the servers logfiles
> most likely "max_allowed_packet" laughable low
>
> Is this then, too, likly when the server and the client are the same
> machine?
>
> I left this out, that it only then happens when th
2014/01/06 17:07 +0100, Reindl Harald
what about look in the servers logfiles
most likely "max_allowed_packet" laughable low
Is this then, too, likly when the server and the client are the same machine?
I left this out, that it only then happens when the client has been idle, a
Am 06.01.2014 15:36, schrieb h...@tbbs.net:
> Now that I installed 5.6.14 on our Vista machine, when using "mysql" I often
> see that error-message, which under 5.5.8 I never saw. What is going on?
what about look in the servers logfiles
most likely "max_allowed_packet" laughable low
signatu
Now that I installed 5.6.14 on our Vista machine, when using "mysql" I often
see that error-message, which under 5.5.8 I never saw. What is going on?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql
On 11/19/2012 10:27 AM, walter harms wrote:
hi List,
i get occasionally the following error:
ERROR 2013 (HY000): Lost connection to MySQL server at 'sending authentication
information', system error: 32
$ perror 32
OS error code 32: Broken pipe
Just to start.
If you want help
If you did not work directly on mysql server (login
by mysql command), please try this.
Using script (PHP, ...) may lose connection, as my experience.
Best
--- On Mon, 3/5/12, Singer X.J. Wang wrote:
> From: Singer X.J. Wang
> Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL
egards,
> Javad Bakhshi,
>
>
>
> From: "mail...@securitylabs.it"
> To: mysql@lists.mysql.com
> Sent: Thursday, March 1, 2012 11:09 AM
> Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during
> query
>
> Il 01/03/2012 11:03, javad bakhshi ha sc
, 2012 11:09 AM
Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Il 01/03/2012 11:03, javad bakhshi ha scritto:
> Hi,
>
> I am trying to load data into my table from a very large file but after some
> time I get this error:
>
> ERROR 2013 (HY000)
Il 01/03/2012 11:03, javad bakhshi ha scritto:
Hi,
I am trying to load data into my table from a very large file but after some
time I get this error:
ERROR 2013 (HY000): Lost connection to MySQL server during query
My file size is around 4G and I have 220M lines in my file which have to be
Hi,
I am trying to load data into my table from a very large file but after some
time I get this error:
ERROR 2013 (HY000): Lost connection to MySQL server during query
My file size is around 4G and I have 220M lines in my file which have to be
loaded in to my table.
I have 10 of these
Per Jessen wrote:
> It happened agaIn this morning, but slightly different:
>
> [snip]
> thd=0x7fe0140c7e00
> Attempting backtrace. You can use the following information to find
> out where mysqld died. If you see no messages after this, something
> went terribly wrong...
> Cannot determine threa
Per Jessen wrote:
> I have just discovered that my mysql server was restarted this
> morning, which is what gave me the 2013. In the log I found this:
[snip]
It happened agaIn this morning, but slightly different:
[snip]
thd=0x7fe0140c7e00
Attempting backtrace. You can use the following inform
Darryle Steplight wrote:
> Hi Per,
>
> Maybe you need to beef up your CONNECT_TIMEOUT setting in your .my.cnf
> file. Are these queries appearing in your slow query logs?What is your
> LOG_QUERY_TIMES set too?
>
> Here are some other settings you may want to play around wtih
> CONNECT_TIMEOUT
>
ation had choked
> on getting "Error 2013 Lost connection to MySQL server during query".
> The application is running remotely on 32bit using mysql library from
> version 5.0.67.
>
> I've been googling quite a bit, but haven't really found anything of any
> use.
The issues that we saw only came to light under stress. The
application I am referring to ran under a fair bit of load at the best
of times but it was during sustained spikes that the flaws in our
driver made themselves apparent.
Mind you, we weren't using JFS, so I'm not sure how that would have
Michael Dykman wrote:
> Given the new hardware, I'm now suspecting the RAID controller. I have
> seen misconfigured RAIDs or bad RAID drivers take out a server in just
> such a manner. I had a debian server connected to an EMC SAN.. As
> debian isn't supported, we had this open-source driver whi
Given the new hardware, I'm now suspecting the RAID controller. I have
seen misconfigured RAIDs or bad RAID drivers take out a server in just
such a manner. I had a debian server connected to an EMC SAN.. As
debian isn't supported, we had this open-source driver which gave us
no end of problems.
Per Jessen wrote:
> Michael Dykman wrote:
>
>> Have you tried running the offending SQL manually against you new
>> installation? Does it come back clean in the isolated case?
>
> No, not manually, but the job/the SQL is run several times a day,
> maybe 2-3 times per hour.
I've also just run t
Michael Dykman wrote:
> Have you tried running the offending SQL manually against you new
> installation? Does it come back clean in the isolated case?
No, not manually, but the job/the SQL is run several times a day, maybe
2-3 times per hour.
> Is there anything else which runs against this
On Mon, May 25, 2009 at 11:19 AM, Per Jessen wrote:
> Per Jessen wrote:
>
>> Michael Steinfeld wrote:
>>
>>> just a thought: Did you run "mysql_upgrade" after the import?
>>>
>>
>> No, I didn't - I didn't think of it as I really only moved the data
>> across.
>>
>
I suspect that will solve your i
Have you tried running the offending SQL manually against you new
installation? Does it come back clean in the isolated case? Is there
anything else which runs against this database at night? crons?
Could you post the script that you are running to give some context to
the statement which winds
Per Jessen wrote:
> Michael Steinfeld wrote:
>
>> just a thought: Did you run "mysql_upgrade" after the import?
>>
>
> No, I didn't - I didn't think of it as I really only moved the data
> across.
>
Okay, have done a mysqlcheck --check-upgrade - came back all clean. I
don't see a need to run
Michael Steinfeld wrote:
> just a thought: Did you run "mysql_upgrade" after the import?
>
No, I didn't - I didn't think of it as I really only moved the data
across.
best regards
Per Jessen, Zürich
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscrib
just a thought: Did you run "mysql_upgrade" after the import?
On Mon, May 25, 2009 at 10:19 AM, Per Jessen wrote:
> Michael Dykman wrote:
>
>> It might be helpful if you could tell us how you affected your data
>> migration
>
> Sorry, I'm not familiar with reporting problems in/on mysql.
>
> The
Michael Dykman wrote:
It might be helpful if you could tell us how you affected your data
migration
Sorry, I'm not familiar with reporting problems in/on mysql.
The data migration was done with a full database dump (mysqldump) from
the 32bit system, then a reload on the new 64bit system. I
Per Jessen wrote:
> This weekend we completed migrating a large(ish) mysql server from
> 5.0.26 on 32bit to 5.0.51a on 64bit. Everything went relatively
> smoothly, until this morning when I noticed an application had choked
> on getting "Error 2013 Lost connection to MySQL se
This weekend we completed migrating a large(ish) mysql server from
5.0.26 on 32bit to 5.0.51a on 64bit. Everything went relatively
smoothly, until this morning when I noticed an application had choked
on getting "Error 2013 Lost connection to MySQL server during query".
The application
On Tue, Jan 13, 2009 at 6:06 PM, Dan wrote:
> On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner
> wrote:
>
>> This sounds like you need to raise max_allowed_packet for mysqldump
>> (and possibly mysqld) - these are separate settings for both the
>> client and the server. You can do this via the
On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner
wrote:
> This sounds like you need to raise max_allowed_packet for mysqldump
> (and possibly mysqld) - these are separate settings for both the
> client and the server. You can do this via the my.cnf (or ~/.my.cnf)
> or specify it as an option on
This sounds like you need to raise max_allowed_packet for mysqldump
(and possibly mysqld) - these are separate settings for both the
client and the server. You can do this via the my.cnf (or ~/.my.cnf)
or specify it as an option on the command line "mysqldump --opt ...
--max_allowed_packet=1G dbna
I'm also having a similar issue with some tables I've been trying to dump
(total data set is around 3TB). I'm dumping directly from one host to
another (mysqldump -hSOURCE DATABASE | mysql -hLOCALHOST DATABASE) using
mysql 4.1.22. One system is Solaris 10 SPARC, while the other is Solaris 10
x64
t;
>> Hi all. I have a 30GB innodb-only database in mysql-5.0.54. I have
>> always done nightly backups with:
>>
>> mysqldump --opt db_name > db_name.sql -p
>>
>> Recently this started failing with:
>> Error 2013: Lost connection to MySQL server
&g
n, Jan 12, 2009 at 9:07 AM, Daniel Kasak wrote:
> Hi all. I have a 30GB innodb-only database in mysql-5.0.54. I have
> always done nightly backups with:
>
> mysqldump --opt db_name > db_name.sql -p
>
> Recently this started failing with:
> Error 2013: Lost connection to My
Hi all. I have a 30GB innodb-only database in mysql-5.0.54. I have
always done nightly backups with:
mysqldump --opt db_name > db_name.sql -p
Recently this started failing with:
Error 2013: Lost connection to MySQL server
I have checked all tables for corruption - nothing found. Also as far
Rajesh Mehrotra wrote:
Hi,
We copied over a test copy of a multi-GB database to a new Sun V440 box
running Solaris 10 (64-bit) with a 64-bit MySQL install. When trying to
connect to the database, we consistently get Error 2013.
Any pointers?
Check the server's error log and see if th
Hi,
We copied over a test copy of a multi-GB database to a new Sun V440 box
running Solaris 10 (64-bit) with a 64-bit MySQL install. When trying to
connect to the database, we consistently get Error 2013.
Any pointers?
TIA.
Sincerely,
Raj Mehrotra
hccs
[EMAIL PROTECTED] <mailto:[EM
[EMAIL PROTECTED] schrieb:
> I am running the 64 bit version of mysql server 5.1.18, and on the
> client side I am running python with the mysqldb module. While
> running a very large insert query I get the following error :
>
> 2013, 'Lost connection to MySQL server durin
I am running the 64 bit version of mysql server 5.1.18, and on the
client side I am running python with the mysqldb module. While
running a very large insert query I get the following error :
2013, 'Lost connection to MySQL server during query'
I have --log-warnings set to 3, bu
stopped. Here is error I got this time for stop slave:
> stop slave;
ERROR 2013 (HY000): Lost connection to MySQL server during query
([EMAIL PROTECTED]) (none)> /usr/local/mysql/bin/mysqld_safe: line
1: 401 Illegal instruction nohup /usr/local/mysql/libexec/
mysqld --defaults-extra-fil
4.1.22 source installation on a 1.66 Intel Core Duo
Mac Mini running OS X Server 10.4.8. It is a slave replicating to a
master over ssl. Replication works fine, however I get this error
always if I execute the STOP SLAVE statement
([EMAIL PROTECTED]) (none)> stop slave;
ERROR 2013 (HY
I have MySQL 4.1.22 source installation on a 1.66 Intel Core Duo Mac
Mini running OS X Server 10.4.8. It is a slave replicating to a
master over ssl. Replication works fine, however I get this error
always if I execute the STOP SLAVE statement
([EMAIL PROTECTED]) (none)> stop slave;
ER
Hello
That version is quite old and is an alpha version. I think you can download a
release for production use.
Gu Lei
- Original Message -
From: "murthy gandikota" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 08, 2006 9:04 PM
Subject: ERROR 2013 (HY000): Lost con
Hi,
I am getting this error. Can anyone please help?
mysql> create table sfgbackup.advEmail select * from sfg.advEmail;
ERROR 2013 (HY000): Lost connection to MySQL server during query
Bye
[EMAIL PROTECTED] mgandikota]$ mysql -V
mysql Ver 14.7 Distrib 5.0.2-alpha, for pc-linux (i686)
Tha
ED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, March 27, 2006 3:46 PM
Subject: ERROR 2013 (HY000): Lost connection to MySQL server during query
Hello,
again, I'm having problems with InnoDB tables. A certain table cannot be
dropped. If I'm issueing the drop table statement, the connection is
lo
Hello,
again, I'm having problems with InnoDB tables. A certain table cannot be
dropped. If I'm issueing the drop table statement, the connection is
lost and I get the following in the logfile:
060327 14:38:11 InnoDB: error: space object of table db15670/mw_pagelinks,
InnoDB: space id 12 did
Gleb Paharenko wrote:
Hello.
Can you connect using the mysql command line client program?
"leegold" <[EMAIL PROTECTED]> wrote:
ssh connecting with a mysql client gui I get: ERROR 2013 Lost
connection to MySQL server during query
I'm using mysqlyog and tryin
Hello.
Have a look here:
http://dev.mysql.com/doc/mysql/en/gone-away.html
christophe charron <[EMAIL PROTECTED]> wrote:
> Hi,
> i've got the same kind of problem but not in a dump, in a restore. I
> tried to restore it in a MyIsam type table but i have the same error.
> Could other se
Hi,
i've got the same kind of problem but not in a dump, in a restore. I
tried to restore it in a MyIsam type table but i have the same error.
Could other server variables interfer in this ? For example, i see
that my long_query_time is set to '10' ...
--
Christophe Charron
PROLOGIQ
7 bis Rue
Hello everyone!
I just wanted to give everyone an update. I'm still getting this error
when I try to back up this database table. I don't get it at the same
row each time - today was at row 1,618, yesterday it was at row 24,566.
Just a reminder of my symptoms:
1. mysqldump is the only thing rep
> Have a look here:
> http://dev.mysql.com/doc/mysql/en/gone-away.html
Gleb,
Thanks for the response. The only one that seems to apply is this one:
> You may also see the MySQL server has gone away error if
> MySQL is started with the --skip-networking option.
I do start mySQL without networki
> I believe it's the size of the row, not the size of a
> single field, that matters. Is it possible you have a
> row which exceeds max_allowed_packet size?
No. There is one blob fields (always less than 50MB) and like 10 other fields,
all integers.
smime.p7s
Description: S/MIME cryptographic
Hassan Schroeder wrote:
> Does the size of the contents of that field exceed your defined
> max_allowed_packet size?
>
Gustafson, Tim wrote:
No, max_allowed_packet is 100 megabytes, and the maximum data field in
the database is 50MB right now, and most are well below 10MB.
Tim Gustafson
MEI Te
one table is very
>large - it accounts for the other 20GB of the dataset.
>
>When backing up this table, I get this error message every night:
>
>/usr/local/bin/mysqldump: Error 2013: Lost connection to MySQL server
>during query when dumping table `DocumentVariants` at row: 134
Gustafson, Tim wrote:
No, max_allowed_packet is 100 megabytes, and the maximum data field
> in the database is 50MB right now, and most are well below 10MB.
mmm. OK, not having any more bright ideas :-) I would try dumping
it using an explicit `--where=` claus to guarantee fixed ordering,
and s
: Hassan Schroeder [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005 9:51 AM
To: mysql@lists.mysql.com
Subject: Re: mysqldump: Error 2013
Gustafson, Tim wrote:
> When backing up this table, I get this error message every night:
>
> /usr/local/bin/mysqldump: Error 2013: Lost conn
Gustafson, Tim wrote:
When backing up this table, I get this error message every night:
/usr/local/bin/mysqldump: Error 2013: Lost connection to MySQL server
during query when dumping table `DocumentVariants` at row: 13456
The table actually has 94,916 rows in it. There are no entries in the
0001 Office
(516) 908-4185 Fax
http://www.meitech.com/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005 9:35 AM
To: Gustafson, Tim
Cc: mysql@lists.mysql.com
Subject: Re: mysqldump: Error 2013
"Gustafson, Tim" <[EMAIL PROTECTED]>
is error message every night:
>
> /usr/local/bin/mysqldump: Error 2013: Lost connection to MySQL server
> during query when dumping table `DocumentVariants` at row: 13456
>
> The table actually has 94,916 rows in it. There are no entries in the
> mySQL server log and nothing in /
across more than a hundred tables. However, one table is very
large - it accounts for the other 20GB of the dataset.
When backing up this table, I get this error message every night:
/usr/local/bin/mysqldump: Error 2013: Lost connection to MySQL server
during query when dumping table
Daniel Kasak wrote:
Michael Gale wrote:
Hello,
Earlier today I tried to make some table alterations on a mysql server
(4.0.24) and kept on receiving this error:
ERROR 2013: Lost connection to MySQL server during query
I would login to the server, either through the socket or using the
IP. Then
Michael Gale wrote:
> Hello,
>
> Earlier today I tried to make some table alterations on a mysql server
> (4.0.24) and kept on receiving this error:
>
> ERROR 2013: Lost connection to MySQL server during query
>
> I would login to the server, either through the socket
Hello,
Earlier today I tried to make some table alterations on a mysql server
(4.0.24) and kept on receiving this error:
ERROR 2013: Lost connection to MySQL server during query
I would login to the server, either through the socket or using the IP.
Then connect to a database and try the
hi,
we are running a forum with about 600 to 700 people online at the same time
plus a
shop and other database relying services.
because this was to much for our single mysql server we are running a
master-slave
setup now, both of version 4.0.23. now we get occasional 2013 errors from our
fo
ysql> LOAD DATA CONCURRENT LOCAL INFILE
'../data/mysql/initial_20050318_102517/page_path.tab4'
-> REPLACE INTO TABLE page_path
-> FIELDS TERMINATED BY '^' OPTIONALLY ENCLOSED BY '"' LINES
TERMINATED BY '\n'
-> (PAGE_PATH_ID,NAME,DATE
Hello.
Can you connect using the mysql command line client program?
"leegold" <[EMAIL PROTECTED]> wrote:
> ssh connecting with a mysql client gui I get: ERROR 2013 Lost
> connection to MySQL server during query
>
> I'm using mysqlyog and trying
ssh connecting with a mysql client gui I get: ERROR 2013 Lost
connection to MySQL server during query
I'm using mysqlyog and trying connect via the ssh tunnel. I can connect
with out the ssh w/mysqljog OK. It's a very nice client and would like
to get this working. I have googled it b
Hello - Since recently switching from MyISAM to InnoDB tables in 4.1 on RH
Linux I receive this error when attempting to dump some tables.
mysqldump: Error 2013: Lost connection to MySQL server during query when
dumping table `campaigns` at row: 14721
Any idea what could be causing this
Vance Pattishall http://www.friendster.com
> -Original Message-
> From: Emmett Bishop [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 13, 2004 8:25 AM
> To: [EMAIL PROTECTED]
> Subject: Error 2013
>
> Howdy all,
>
> I got this error while running a rou
Howdy all,
I got this error while running a routine mysqldump
last night: Error 2013: Lost connection to MySQL
server during query when dumping table `contact_log`
at row: 41245
I didn't find any good information on this error at
mysql. Is there a page there that lists all error
codes? I
> I am running Debian sarge with MySQL 4.0.20. My problem is I can
> connect from localhost, but when I try to connect from other host this
> error comes up:
> ERROR 2013: Lost connection to MySQL server during query
Sorry I found the answer. I have ALL:ALL in hosts.deny
--
M
Hi,
I am running Debian sarge with MySQL 4.0.20. My problem is I can connect
from localhost, but when I try to connect from other host this error
comes up:
ERROR 2013: Lost connection to MySQL server during query
I tried from many clients, included MySQL 4.0 and MySQL 3.23, but they
all got same
Ok, it seems I fixed my problem before anybody was available to help me.
The error was due to bad code -- the program was trying to send multiple
queries through the same connection. Even though it was compiled as
"thread safe", you still have to find some way to prevent concurrent
queries on
Hello all,
I'm getting the error message "2013 : Lost connection to MySQL server
during query" during inserts on a lightly-loaded mysql server. I also
noticed the following error in the error log...
Version: '4.0.20-standard-log' socket: '/tmp/mysql.sock' port: 3306
040603 16:25:48 Aborted c
Mauricio Pellegrini <[EMAIL PROTECTED]> wrote:
> I'm using MySql 4.0.18 on Linux (SuSE 8.2)
> and I'm getting this error
>
> ERROR 2013: Lost connection to MySQL server during query
>
> a few seconds after launching
> the following command
>
-
From: Mauricio Pellegrini [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 26, 2004 5:03 PM
To: [EMAIL PROTECTED]
Subject: ERROR 2013
Hi,
I'm using MySql 4.0.18 on Linux (SuSE 8.2)
and I'm getting this error
ERROR 2013: Lost connection to MySQL server during query
Hi,
I'm using MySql 4.0.18 on Linux (SuSE 8.2)
and I'm getting this error
ERROR 2013: Lost connection to MySQL server during query
a few seconds after launching
the following command
LOAD DATA LOCAL INFILE '/root/hc.txt' into table af_afiliados ;
soon
I think this is the problem (cited from mysqld.log)
Some pointers may be invalid and cause the dump to abort...
followed by my query to create the tmp table
But I am not sure how to fix it.
ginger
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:ht
Hi,
The max packet site is 1048576. But I don't think it is a problem cuz I
have successfully outputted the result of this query before. I checked
mysqld.log. This is the tail I think might related to the problem:
Number of processes running now: 0
040406 22:22:01 mysqld restarted
Cannot initi
f some large query to a temporary
> table and then query from there. But all my trials ended up 'ERROR 2013 at
> line 7: Lost connection to MySQL server during query' before creating the
> temporary table. The version of MySQL is 3.23.54, for redhat-linux-gnu
> (i386). Does an
Hello, MySQL gurus,
I have been trying to output the result of some large query to a temporary
table and then query from there. But all my trials ended up 'ERROR 2013 at
line 7: Lost connection to MySQL server during query' before creating the
temporary table. The version of MySQL
"Bungarz, Kai" <[EMAIL PROTECTED]> wrote:
> When i'm using mysql client, version 12.21 - Distrib: 4.0.15 / windows,
> for queries or loading data, i always get an error 2013 ("lost
> connection...")=20
> after 30 seconds and the connection breaks down.
Hi!
When i'm using mysql client, version 12.21 - Distrib: 4.0.15 / windows,
for queries or loading data, i always get an error 2013 ("lost
connection...")
after 30 seconds and the connection breaks down.
This doesn't happen, when i use the older version 11.16 , Distrib: 4.0.0
"Bungarz, Kai" <[EMAIL PROTECTED]> wrote:
> Hi!
> I get error 2013: "Lost connection to mysql server during query", while
> loading
> data into a table using "load data infile..".
> This happens only, when "load data" needs much
Hi!
I get error 2013: "Lost connection to mysql server during query", while
loading
data into a table using "load data infile..".
This happens only, when "load data" needs much time and files are rather
big.
Is there any "time_out" parameter
Hi!
There was a bad bug in the Windows version of the 4.0.15 mysql client. All
queries lasting more than 30 seconds time out with Error 2013 in the client.
Since the changelog entry in the release note of 4.0.16 Oct 22th did not
highlight this bug enough, I am sending this email to mailing lists
Alexander K?ppe <[EMAIL PROTECTED]> wrote:
> Hi,
> I have trouble to connect from a remote host to the mysql-server.
> On localhost works all right.
> But when I want to establish a connection with
>
> mysql --host=server --user=com75778 --database=com75778 --pass
> E
Hi,
I have trouble to connect from a remote host to the mysql-server.
On localhost works all right.
But when I want to establish a connection with
mysql --host=server --user=com75778 --database=com75778 --pass
Enter password:
ERROR 2013: Lost connection to MySQL server during query
from another
Check the connection timeout parameter. Increase it if it's low and try..
>>> "W. Bauer" <[EMAIL PROTECTED]> 10/16/2003 6:20:44 PM >>>
Dear all
When I run a query on a table with about 22 Mio records and three columns of
type bigint, I get a Error 2013
Dear all
When I run a query on a table with about 22 Mio records and three columns of
type bigint, I get a Error 2013 Lost connection to MySQL server during
query. If I use limit x it works fine as long x<70.
Is there anything I can do to circumvent this error?
Thanks, W. Bauer
--
NEU
Dear all
When I use
Insert into table tabl1 (col1)
select ...
to insert about 2 mio. rows into tabl1 I get the error message 2013
connection lost.
When I just run the query, pipe the output into a text file, and use the
load data local infile into table tbl1, it works. How can I chang
gt;
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 09, 2003 11:50 AM
Subject: HELP PLEASE the weirdest error 2013 / connection ?
>
> Hi,
>
> this is the weirdest error I have ever encountered.
>
> We get an error 2013 lost connection when we try to connect via mysql to
>
Hi,
this is the weirdest error I have ever encountered.
We get an error 2013 lost connection when we try to connect via mysql to
another machine having mysql on it as well. The weird part is that when
we change the IP address of the connecting machine to another service
provider it works
Pete,
INSERT ... SELECT ... does not replicate properly with AUTO_INCREMENTs.
Regards,
Heikki
- Original Message -
From: "Pete Harlan" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 02, 200
On Wed, Jul 02, 2003 at 12:55:38AM +0300, Heikki Tuuri wrote:
...
> 4.0.13 has better diagnostics. Please upgrade to it if you are not using
> MySQL replication.
Is there something wrong with 4.0.13's replication, or does it not
replicate properly with 4.0.12?
--Pete
--
MySQL General Mailing Li
Miguel,
best to upgrade to 4.0.13 because it has better diagnostics.
Regards,
Heikki
- Original Message -
From: "Miguel Perez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, July 02, 2003 1:03 AM
Subject: Re: ERROR 2
CTED]>,<[EMAIL PROTECTED]>
Subject: Re: ERROR 2013:Lost connection to MySQL server
Date: Wed, 2 Jul 2003 00:55:38 +0300
Miguel,
the failing assertion is in dict_load_table():
ut_a(DB_SUCCESS == dict_load_foreigns(table->name));
Are you sure you do not have foreign keys wh
<[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, July 02, 2003 12:47 AM
Subject: Re: ERROR 2013:Lost connection to MySQL server
> I am running the 4.0.12 version
> For those tables I don't have FOREIGN KEYS here is the table desc.
>
>
r(10) NOT NULL default '',
FDFECSURT datetime NOT NULL default '-00-00 00:00:00',
FNPEDSALDO decimal(12,2) NOT NULL default '0.00',
FCFOLIOPARAM int(11) NOT NULL default '0',
FDFECIMPFACTURA datetime NOT NULL default '-00-00 00:00:00'
On Tue, Jul 01, 2003 at 04:09:26PM -0500, Miguel Perez wrote:
> The OS I'm using is Red Hat 7.3, and the mysql version is 4.0
>
> The wierd thing is that I could access those tables but just after I
> rebooted my PC
> I couldn't access the 2 tables.
> The log files has the following:
>
> "030701
ailing.database.mysql
Sent: Wednesday, July 02, 2003 12:11 AM
Subject: Re: ERROR 2013:Lost connection to MySQL server
> The OS I'm using is Red Hat 7.3, and the mysql version is 4.0
>
> The wierd thing is that I could access those tables but just after I
> rebooted my PC
> I couldn&
1 - 100 of 150 matches
Mail list logo
