Bug #68024 hangs in mysql_real_query
Submitted: 4 Jan 2013 2:12 Modified: 7 Feb 2013 16:23
Reporter: alexander qiao Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: C API (client library) Severity:S3 (Non-critical)
Version:mysql-5.0.22 OS:Linux (SuSe Version2.6)
Assigned to: CPU Architecture:Any
Tags: deadlock, hangs, mysql_real_query, vio_read

[4 Jan 2013 2:12] alexander qiao 
Description:
My progress has normal runned one month, Suddendly hangged in mysql_query at 2013/01/01. I attached the progress with gdb, then see the stack in flowing.
#0 0x00002aae2925b710 in __read_nocancel () from /lib64/libc.so.6
#1 0x00002aae289b6f68 in vio_read () from /usr/lib64/libmysqlclient.so.15
#2 0x00002aae289b6fc3 in vio_read_buff() from /usr/lib64/libmysqlclient.so.15
#3 0x00002aae289b7a35 in my_real_read() from /usr/lib64/libmysqlclient.so.15
#4 0x00002aae289b7d19 in my_net_read () from /usr/lib64/libmysqlclient.so.15
#5 0x00002aae289b2282 in net_safe_read() from /usr/lib64/libmysqlclient.so.15
#6 0x00002aae289b4599 in cli_read_query_result ()from /usr/lib64/libmysqlclient.so.15
#7 0x00002aae289b1e7e in mysql_real_query () from /usr/lib64/libmysqlclient.so.15
The sql statment that mysql_query execued at that moment is that "'update role set mission='2|184|101|17' where id=103560' ".
  Then, I Observed the mysql-server on the other different linux server. and It is Ok. The mysql-client on the other different linux server also is ok.

How to repeat:
can't repeat
[4 Jan 2013 2:25] MySQL Verification Team 
Same problem as in http://bugs.mysql.com/bug.php?id=57622

Do you connect via tcp/ip or socket?

I'd recommend using a modern version of the client libraries, 
at least I encourage you to try 5.0.96 and 5.5.29 versions and see if things are any better.
[4 Jan 2013 2:39] alexander qiao 
okey, I'll try version 5.0.96, and thanks a lot.
[8 Feb 2013 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".