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
[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
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
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
> 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
id is 257 to server version: 4.0.14-log
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> use sqlreg3;
Database changed
mysql> LOAD DATA LOCAL INFILE
'C:\\ProjetosD6\\MySQLBackup\\binario\\cfgimpressao.dat' INT
O TABLE cfgimpressao
INFILE 'C:\\ProjetosD6\\MySQLBackup\\binario\\cfgimpressao.dat'
INT
O TABLE cfgimpressao;
ERROR 2013: Lost connection to MySQL server during query
mysql>
The Files of table are in FTP the names is:
cfgimpressao.dat.zip - The zipped Data of File ( saved with the
OUTFILE command, pl
Now, it's working fine !
Thanks a lot
Nivaldo
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, March 04, 2003 12:12 AM
Subject: Re: Error 2013 - Lost connection to MySQL server during quer
Suporte schrieb:
Hi
I installed MySQL on a server running RedHat 8.0 and it's working fine. But
when I try to connect to MySQL from a remote station, using MySQL Control
Center, or even using the command-line "mysql", I get the message:
"Error 2013 - Lost connection to
Hi
I installed MySQL on a server running RedHat 8.0 and it's working fine. But
when I try to connect to MySQL from a remote station, using MySQL Control
Center, or even using the command-line "mysql", I get the message:
"Error 2013 - Lost connection to MySQL server durin
Like several other people I noticed on the web, I am receiving an error
message "Error 2013: Lost connection to mysql server during query",
however I can not find the results of you corrections? Can you please
point me to the place where I can find a fix for this error?
T
Hi,
I have MySQL version 3.23.41 and when I connect from localhost, it's OK.
Hovewer, when I connect via IP (f.e. mysql -h IP, or from other computer in
Internet), then MySQL resut error ERROR 2013: Lost connection to MySQL
server during query.
This is a part of variable from MySQL on t
Davide,
Monday, October 28, 2002, 9:56:46 AM, you wrote:
DP> Thanks for your help, we have installed MySQL 2.23.53a on Red Hat 8.0.
DP> The problem seems to be the version of RedHat. We have now installed the
DP> same version of MySql on RedHat 7.3 and it seems to work fine. Can you
DP> give me a
Thanks for your help, we have installed MySQL 2.23.53a on Red Hat 8.0.
The problem seems to be the version of RedHat. We have now installed the
same version of MySql on RedHat 7.3 and it seems to work fine. Can you
give me a confirmation of this problem?
Thanks
Davide
On Fri, 2002-10-25 at 15
Davide,
Friday, October 25, 2002, 11:57:23 AM, you wrote:
DP> I'm new to MySQL. I am trying to set replication in MySQL but i get the
DP> error in the subject.
DP> Can you help me please?
Can you be more detailed?
What OS? What versions of MySQL servers? What did you done before you got
this er
Hy All,
I'm new to MySQL. I am trying to set replication in MySQL but i get the
error in the subject.
Can you help me please?
Thanks to all
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
Hi all,
I found another solution of a problem with buggy glibc.
Try to start mysqld with --skip-name-resolve
It's work for me fine, but hosts part in security must be only IP addresses,
not names.
Dishko Georgiev
SysAdmin Terasyst Ltd.
---
://www.sqlyog.com/
- Original Message -
From: "Animesh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 19, 2002 2:23 AM
Subject: ERROR 2013: Lost connection to MySQL server during query
> Hi All,,
>
> I am getting this error and mysqld is dy
imesh@;deeproot.co.in]
> Sent: Friday, October 18, 2002 4:53 PM
> To: [EMAIL PROTECTED]
> Subject: ERROR 2013: Lost connection to MySQL server during query
>
>
> Hi All,,
>
> I am getting this error and mysqld is dying out while tring to access a
> particular table
Thanks for the reply.
-rw-rw 1 mysql mysql 12766 Oct 10 12:16 bob-bin.072
-rw-rw 1 mysql mysql 506213 Oct 15 09:11 bob-bin.073
-rw-rw 1 mysql mysql 40391597 Oct 17 12:52 bob-bin.074
-rw-rw 1 mysql mysql 98 Oct 17 12:53 bob-bin.075
-rw-rw 1 mysq
AIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, October 18, 2002 6:37 PM
Subject: Re: ERROR 2013: Lost connection to MySQL server during query
> Hi,
>
> I know there is more than one reason that this error can occur, but I have
> not seen a good guide to debuging.
> It mig
Hi,
I know there is more than one reason that this error can occur, but I have
not seen a good guide to debuging.
It might help, if you are using DBI to do a trace to a log file. I have
this happen every once in a while, but can't track it down because it is
one query out of hundreds and I can'
e '-h hostname' flag it would boot me, they only way i could
get in was with out the '-h'.
Animesh wrote:
Hi All,,
I am getting this error and mysqld is dying out while tring to access
a particular table in a particular databae while others don't fail..
ERROR 2013: Lost con
Hi All,,
I am getting this error and mysqld is dying out while tring to access a
particular table in a particular databae while others don't fail..
ERROR 2013: Lost connection to MySQL server during query
Plz Help as early as possible.
Regards,
Animesh
[EMAIL PROTECTED]
DeepRoot Linu
Tim,
Tuesday, February 19, 2002, 9:57:07 PM, you wrote:
TW> Hopefully someone out there can help me as I haven't been able to find any
TW> documentation on this that applies.
TW> I am running MySQL version 3.22.32 on a FreeBSD v4.4 machine. I am getting
TW> "Error 20
Hopefully someone out there can help me as I haven't been able to find any
documentation on this that applies.
I am running MySQL version 3.22.32 on a FreeBSD v4.4 machine. I am getting
"Error 2013: Lost connection to MySQL server during query" when I run the
following query:
Dear all
I have a problem when I specified my host in order to connect to my
mysql server :
mysql -h p204
ERROR 2013: Lost connection to MySQL server during query
I have just installed the server and set a pass for the root user.
In hope of your help
Guillaume
ew minutes.
Any ideas why it would be taking so long? This is on a RH 6.0 system.
Thank you!
Kurt Hansen
[EMAIL PROTECTED]
> > Subject: ERROR 2013: Lost connection to MySQL server during query
> >
> >
> > Hello,
> >
> > I'm getting the error message above when
: Kurt Hansen <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 8:59 AM
Subject: RE: ERROR 2013: Lost connection to MySQL server during query
> I had a similar problem recently. Try checking the /etc/hosts file to see
if
> the hosts/IPs are matching the cur
2013: Lost connection to MySQL server during query
Hello,
I'm getting the error message above whenever I try to connect from a remote
host to a MySQL server. I issue the following command:
mysql --host=host_name -u user_name -ppass_word
and get the ERROR 2013 back as a response.
We hav
Hello,
I'm getting the error message above whenever I try to connect from a remote
host to a MySQL server. I issue the following command:
mysql --host=host_name -u user_name -ppass_word
and get the ERROR 2013 back as a response.
We have two servers, both running MySQL. I get the same message
I could not find a reference in the manual to this error message. What
could be happening? It is the first problem I have with the database since
installation two years ago- well almost three.
Thanks,
---
Claudia M. Castaneda
Phone 301 286 3397
54 matches
Mail list logo
