characters long.
The error is:
ERROR 2013 (HY000) at line 1763: Lost connection to MySQL server during query
About 40 tables are restored correctly from the dump prior to it
failing at this line.
Based on advice from posts I've found on the internet, I've added the
follow settings to my.cnf
1763: Lost connection to MySQL server during query
About 40 tables are restored correctly from the dump prior to it
failing at this line.
Based on advice from posts I've found on the internet, I've added the
follow settings to my.cnf
net_read_timeout=60
# 16 MB
max_allowed_packet=16777216
I
2014/1/7 h...@tbbs.net
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
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, and
right
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
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
(): Lost connection to MySQL server at 'reading initial
communication packet', system error: 111
I stopped the server and restarted it and everything seems to work OK for
hours but when the load start to increase, the errors begin to appear again.
Today I noticed that after I starte phpMyAdmin
. There are several batch scripts
using the database in addition to a web application using it.
The php scripts running in batch mode began to get:
mysql_connect(): Lost connection to MySQL server at 'reading initial
communication packet', system error: 111
I stopped the server and restarted it and everything
On Saturday 12 October 2013 12:01, nixofortune wrote:
You might want to comment
bind-address= 127.0.0.1
in your my.cnf and restart mysql server.
It does not explain why it works under low load and not under high load.
However, I seem to have found something. When I started
Could be a crash related to innodb data dictionary being out of sync. Could
be a bug.
http://bugs.mysql.com/bug.php?id=55277
On 12 Oct 2013 11:21, Jørn Dahl-Stamnes sq...@dahl-stamnes.net wrote:
On Saturday 12 October 2013 12:01, nixofortune wrote:
You might want to comment
bind-address
On Saturday 12 October 2013 13:07, Andrew Moore wrote:
Could be a crash related to innodb data dictionary being out of sync. Could
be a bug.
Seems like a bug yes. However, we had a strange situation yesterday when we
had several processes in the state copying to tmp table (if i remember the
Am 12.10.2013 17:02, schrieb Jørn Dahl-Stamnes:
On Saturday 12 October 2013 13:07, Andrew Moore wrote:
Could be a crash related to innodb data dictionary being out of sync. Could
be a bug.
Seems like a bug yes. However, we had a strange situation yesterday when we
had several processes
On Saturday 12 October 2013 17:36, Reindl Harald wrote:
so someone did optimize table on a large table
you do yourself not a favour restarting the server in such a moment
7 hours before the server was shut down, we did a alter table to add a primary
key to a table that is read-only from the
Am 12.10.2013 19:45, schrieb Jørn Dahl-Stamnes:
On Saturday 12 October 2013 17:36, Reindl Harald wrote:
so someone did optimize table on a large table
you do yourself not a favour restarting the server in such a moment
7 hours before the server was shut down, we did a alter table to add a
We had a similar issue a bit back - and although it sounds similar - based
on your followups it probably isnt, but will just toss this out there
anyhows. We were experiencing connection timeouts when load would ramp up.
Doing some digging we learned that our firewall between the servers
sounds like a scheduler issue
did you try deadline?
http://en.wikipedia.org/wiki/Deadline_scheduler
on Linux systems pass elevator=deadline as kernel param
Am 12.10.2013 20:58, schrieb Chris McKeever:
We had a similar issue a bit back - and although it sounds similar - based
on your followups
the file works fine, in about 12 sec/77
sec.
I
read online how to export MySQL queries into csv's, and I'm not sure
what
I
am doing wrong. I keep getting the error:
Error Code: 2013. Lost connection to MySQL server during query, where
the
duration/fetch values are 600.547 sec (~10
, and I'm not sure what
I
am doing wrong. I keep getting the error:
Error Code: 2013. Lost connection to MySQL server during query, where the
duration/fetch values are 600.547 sec (~10 minutes).
What is the exact error message?
Which client are you using to do the query?
It's strange that the query
;
The query without exporting the file works fine, in about 12 sec/77 sec.
I
read online how to export MySQL queries into csv's, and I'm not sure what
I
am doing wrong. I keep getting the error:
Error Code: 2013. Lost connection to MySQL server during query, where the
duration/fetch
2012/07/26 06:52 +0530, Dhaval Jaiswal
SELECT * FROM test INTO OUTFILE '/home/test.csv' FIELDS TERMINATED BY ','
ENCLOSED BY '' LINES TERMINATED BY '\n'
as above give your join condition before INTO OUTFILE.
Right: MySQL server writes into some directory where it is, not where MySQL
client
Thanks!
On Thu, Jul 26, 2012 at 12:05 AM, h...@tbbs.net wrote:
2012/07/26 06:52 +0530, Dhaval Jaiswal
SELECT * FROM test INTO OUTFILE '/home/test.csv' FIELDS TERMINATED BY ','
ENCLOSED BY '' LINES TERMINATED BY '\n'
as above give your join condition before INTO OUTFILE.
Right: MySQL
the file works fine, in about 12 sec/77 sec. I
read online how to export MySQL queries into csv's, and I'm not sure what I
am doing wrong. I keep getting the error:
Error Code: 2013. Lost connection to MySQL server during query, where the
duration/fetch values are 600.547 sec (~10 minutes).
I'm
read online how to export MySQL queries into csv's, and I'm not sure what I
am doing wrong. I keep getting the error:
Error Code: 2013. Lost connection to MySQL server during query, where the
duration/fetch values are 600.547 sec (~10 minutes).
I'm wondering:
a) What is going on?
b) How do I
(HY000): Lost connection to MySQL server during query
To: javad bakhshi javadbakh...@yahoo.com
Cc: mysql@lists.mysql.com mysql@lists.mysql.com
Date: Monday, March 5, 2012, 10:40 PM
Checking your firewall settings..
S
On Mon, Mar 5, 2012 at 08:39, javad bakhshi javadbakh...@yahoo.com
wrote
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 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
,
From: mail...@securitylabs.it 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 scritto:
Hi,
I am trying to load
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
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
Hi,
We're busy moving legacy apps from foxpro tables to mysql. User logins
were tracked via a record in a table which the app then locked,
preventing multiple logins for the same user code.
I want to simulate this via a locked column in a mysql table, but
would need the field to be cleared
Check out the GET_LOCK and RELEASE_LOCK virtual lock functions in MySQL.
-Hank
On Wed, Sep 28, 2011 at 9:15 AM, Alex Schaft al...@quicksoftware.co.za wrote:
Hi,
We're busy moving legacy apps from foxpro tables to mysql. User logins were
tracked via a record in a table which the app then
Can you provide more details?
network layout, type of client/app used, connectors,etc,etc?
Thanks
Claudio
2009/9/9 stutiredboy stutired...@gmail.com
hi,all:
we met a problem that:
* Lost connection to MySQL server during query
SHOW TABLE STATUS WHERE ENGINE='MyISAM'
*sometimes it works
which cause lost connection to MySQLserver..
we only ran some sql that create table(s)
i have read this article
http://dev.mysql.com/doc/refman/5.1/en/gone-away.html
and can get rid of the problems this article referred
it seems that our problem is similar to this bug:
http://lists.mysql.com
the application program and mysql server are in the same host
and i have add skip-name-resolv to the my.cnf and
extend the max_allowed_packet from 16M to 32M
our application connected to mysql server from mysql.sock
before the query which cause lost connection to MySQLserver..
we only ran some
hi,all:
we met a problem that:
* Lost connection to MySQL server during query
SHOW TABLE STATUS WHERE ENGINE='MyISAM'
*sometimes it works well, sometimes not
our mysql version is 5.0.84
our system is FreeBSD 6.2
thanks
--
MySQL General Mailing List
For list archives: http://lists.mysql.com
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 thread,
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
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 is running
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 server during query.
I
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.
just a thought: Did you run mysql_upgrade after the import?
On Mon, May 25, 2009 at 10:19 AM, Per Jessen p...@computer.org 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.
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 unsubscribe:
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
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
On Mon, May 25, 2009 at 11:19 AM, Per Jessen p...@computer.org 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 issue.
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
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 the query
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.
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 which
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
an application 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. I've checked the two configurations
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
On Tue, 2009-01-13 at 12:19 +0530, Chandru wrote:
Hi,
Did u try using this command
mysqldump --opt db_name db_name.sql -p 2bkp.err
Not quite. Firstly, I had to alter the normal backup cron job, and that
doesn't happen until late at night.
Secondly, yes I added the redirection to
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
On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner
andrew.b.gar...@gmail.com 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
On Tue, Jan 13, 2009 at 6:06 PM, Dan d...@entropy.homelinux.org wrote:
On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner
andrew.b.gar...@gmail.com wrote:
This sounds like you need to raise max_allowed_packet for mysqldump
(and possibly mysqld) - these are separate settings for both the
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 as
I
at 9:07 AM, Daniel Kasak d...@entropy.homelinux.orgwrote:
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
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 as
I can tell there are no issues with clients using the database. There
have
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
of mysql_error() (in php), i get lost connection to mysql server during
query. Here's an example stack trace:
'Can't connect to name database [Lost connection to MySQL server
during
query]'
Similarly, we're seeing stack traces here as well:
'Can't connect to name database []'
I
We've started seeing mysql errors in the logs, and when i look at the output
of mysql_error() (in php), i get lost connection to mysql server during
query. Here's an example stack trace:
'Can't connect to name database [Lost connection to MySQL server during
query]'
Similarly, we're seeing stack
, and when i look at the output
of mysql_error() (in php), i get lost connection to mysql server during
query. Here's an example stack trace:
'Can't connect to name database [Lost connection to MySQL server during
query]'
Similarly, we're seeing stack traces here as well:
'Can't connect
of connections reaches a high
of around 10 and I haven't had the problem since.
Mike
On Wed, Oct 29, 2008 at 2:47 AM, Waynn Lue [EMAIL PROTECTED] wrote:
We've started seeing mysql errors in the logs, and when i look at the
output
of mysql_error() (in php), i get lost connection to mysql
Only increase max_allowed_packet is ok.
On Tue, Aug 19, 2008 at 5:49 PM, Warren Young [EMAIL PROTECTED] wrote:
Mad Unix wrote:
During the update of the MySQL DB (delete/insert), I keep getting the
following message
Lost connection to MySQL server during query...
By default, the MySQL
Hi all
During the update of the MySQL DB (delete/insert), I keep getting the
following message
Lost connection to MySQL server during query...
Any thoughts about this issue, could it be a network, code or tunning
problem ...
Thanks
Mad Unix wrote:
During the update of the MySQL DB (delete/insert), I keep getting the
following message
Lost connection to MySQL server during query...
By default, the MySQL server drops a connection after 8 hours of
receiving no queries on that connection. This can happen
On Tue, Jan 15, 2008 at 09:27:10PM +0100, MAS! wrote:
Can anyone help me to understand why my site (php 4.4.2 / ubuntu
dapper) loose all connections to mysql server when /etc/cron/hourly
starts? (there are no process to start hourly, the directory is empty)
Is the assumption correct, that
Il giorno 16 gen 2008, alle ore 02:59, Moon's Father ha scritto:
Post your error message here.
(from php)
Error message: mysql_connect(): Lost connection to MySQL server
during query
and I have that for _each_ apache2 thread/php-page opened
MAS!
--
MySQL General Mailing List
For list
.
(from php)
Error message: mysql_connect(): Lost connection to MySQL server
during query
and I have that for _each_ apache2 thread/php-page opened
MAS!
--
I'm a mysql DBA in china.
More about me just visit here:
http://yueliangdao0608.cublog.cn
Enter your mysql shell and enter the command:
set global max_allowed_packet=10M
I have it setted at 32M, but that is not the problem; the data are
not too much ...
and it's strange because _ALL_ clients seems to died/be disconnected
each hour, when the hourly cron runs..
--
MySQL
You should give me an error message here.
On Jan 16, 2008 4:44 PM, MAS! [EMAIL PROTECTED] wrote:
Enter your mysql shell and enter the command:
set global max_allowed_packet=10M
I have it setted at 32M, but that is not the problem; the data are
not too much ...
and it's strange because
Marco,
can you post values of wait_timeout and interactive_timeout variables.
You can get them from SHOW VARIABLES output. If they are set to 3600 (1
hour in secs), set them to something bigger like one week and then you
will see if it helps or not. You can read more about those timeouts also
can you post values of wait_timeout and interactive_timeout
variables. You can get them from SHOW VARIABLES output. If they are
set to 3600 (1 hour in secs), set them to something bigger like one
week and then you will see if it helps or not. You can read more about
MAS! napsal(a):
can you post values of wait_timeout and interactive_timeout
variables. You can get them from SHOW VARIABLES output. If they are
set to 3600 (1 hour in secs), set them to something bigger like one
week and then you will see if it helps or not. You can read more about
Hi,
On Jan 16, 2008 3:36 AM, MAS! [EMAIL PROTECTED] wrote:
Il giorno 16 gen 2008, alle ore 02:59, Moon's Father ha scritto:
Post your error message here.
(from php)
Error message: mysql_connect(): Lost connection to MySQL server
during query
and I have that for _each_ apache2 thread
Can anyone help me to understand why my site (php 4.4.2 / ubuntu
dapper) loose all connections to mysql server when /etc/cron/hourly
starts? (there are no process to start hourly, the directory is empty)
I have heavvy web/apache2 traffic on my site and that is not so nice
for my users..
Post your error message here.
On Jan 16, 2008 4:27 AM, MAS! [EMAIL PROTECTED] wrote:
Can anyone help me to understand why my site (php 4.4.2 / ubuntu
dapper) loose all connections to mysql server when /etc/cron/hourly
starts? (there are no process to start hourly, the directory is empty)
I
Hi All,
I have connect to mysql-server using client. When i run the query it give
message lost connection to mysql. The details is as below.
mysql select user_id, user_name from user_info;
ERROR 2013 (HY000): Lost connection to MySQL server during query.
System configuration is
Pentium 2.6 Ghz
Hi All,
I have connect to mysql-server using client. When i run the query it give
message lost connection to mysql. The details is as below.
mysql select user_id, user_name from user_info;
ERROR 2013 (HY000): Lost connection to MySQL server during query.
System configuration is
Pentium 2.6 Ghz
-server using client. When i run the query it give
message lost connection to mysql. The details is as below.
mysql select user_id, user_name from user_info;
ERROR 2013 (HY000): Lost connection to MySQL server during query.
System configuration is
Pentium 2.6 Ghz
Ram 1 GB
My.cnf
key_buffer
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:[EMAIL
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 there's
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, but I get
[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 during query'
I have --log
On Thu, May 10, 2007 at 05:17:12PM +0100, Jon Ribbens wrote:
I suspect some sort of bug in the MySQLd authentication code.
I've managed to discover using --debug that it's due to MySQLd failing
to handle EINTR from read() in the authentication stage.
I've filed a bug report:
On Thu, May 10, 2007 at 03:37:26AM +0100, Jon Ribbens wrote:
I've just upgraded all the clients and servers to 5.0.41 (which looks
like it just came out); I'll see what happens.
It hasn't solved the problem, but it has changed the error message to:
OperationalError:
(2013, Lost
At 06:03 AM 5/10/2007, you wrote:
reading
authorization packet
If you do a google search:
http://www.google.ca/search?q=lost+mysql+connection+%22reading+authorization+packet%22hl=enstart=90sa=N
you'll find about a hundred web sites encountering the exact same error.
Ironically these
On Thu, May 10, 2007 at 08:58:37AM -0600, mos wrote:
If you do a google search:
http://www.google.ca/search?q=lost+mysql+connection+%22reading+authorization+packet%22hl=enstart=90sa=N
you'll find about a hundred web sites encountering the exact same error.
Indeed, I noticed that ;-)
Maybe
We are using MySQL 5.0.27 on RedHat Enterprise Linux ES release 4,
and the MySQL-python-1.2.1_p2 connector.
We are getting intermittent mysterious errors as follows:
OperationalError:
(2013, 'Lost connection to MySQL server during query')
when attempting to connect to the MySQL server
the
problem.
On 5/9/07, Jon Ribbens [EMAIL PROTECTED] wrote:
We are using MySQL 5.0.27 on RedHat Enterprise Linux ES release 4,
and the MySQL-python-1.2.1_p2 connector.
We are getting intermittent mysterious errors as follows:
OperationalError:
(2013, 'Lost connection to MySQL server during query
On Wed, May 09, 2007 at 09:22:34AM -0400, Michael Dykman wrote:
I realize that's quite unlikely that you have performed a similar
sloppy import but there is likely some edge condition on your server
(wierd permissions in the data directory, corruoted tables, etc.)
but I still recommend that
When we first examined our server logs, we saw the same.. in our case
(again) it was only when we slowed down and examined the timestamps on
the start/stop messages that we realized that the server was
restarting at unexpected intervals. Over the course of our
development, we came across this
We also have random lost connections on simple queries, but we are running
MySQL v5.024a on Windows XP. We've checked the logs and nothing abnormal
has turned up and we're using only MyISAM tables with InnoDb disabled.
The only thing that I could suggest is to look for other copies of
intervals.
The last restart, according to both the content of the log, and the
operating system timestamp on the log file itself, was 6 days ago.
The 'lost connection' message has happened several times today,
however.
(how did you get your binaries? pre-compiled from the archive
or build your
Jon Ribbens a écrit :
We are using MySQL 5.0.27 on RedHat Enterprise Linux ES release 4,
and the MySQL-python-1.2.1_p2 connector.
We are getting intermittent mysterious errors as follows:
OperationalError:
(2013, 'Lost connection to MySQL server during query')
when attempting
but the firewall was keeping state of the connection only
for up to 1 hour when no data was transferred. After the firewall had
flushed the state of the connection and that the webserver were trying
to communicate through it, he was reporting Lost connection to mysql
server during query
It's
2013 (HY000): Lost connection to MySQL server during query
([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted
Also, if I execute mysqladmin shutdown, it restarts also
slmini:/usr/local admin$ mysqladmin -u root -p shutdown
Enter password:
slmini:/usr/local admin$ 061220 14:59:19 mysqld
): Lost connection to MySQL server during query
([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted
Also, if I execute mysqladmin shutdown, it restarts also
slmini:/usr/local admin$ mysqladmin -u root -p shutdown
Enter password:
slmini:/usr/local admin$ 061220 14:59:19 mysqld restarted
was 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-file=/usr
i've done a non-stop insert test for 3 days, using mysql++ to connect to MySQL
server
i only use one connection, if it fails to execute ,it will reconnect
during this test , this exception came out twice
is that because of the server or the client?
1 - 100 of 401 matches
Mail list logo
