Bug #18328 Lost connection when updating multiple tables
Submitted: 18 Mar 2006 13:43 Modified: 25 May 2006 14:38
Reporter: Wil Wellington Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.15 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[18 Mar 2006 13:43] Wil Wellington
Description:
Mysqld crashes when attempting to perform multiple updates.  I've checked and re-checked the code and can't see any immediate problem.

mysql error log follows...

mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=10485760
read_buffer_size=8200
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 215840 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8b89ce8
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, fp=0x43173344, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8160440
0xffffe420
0x8a5f670
0x838082b
0x820e3f1
0x81cec93
0x81aa078
0x81b00de
0x81b02d3
0x81b00de
0x81b0205
0x81b5b52
0x81c2f79
0x81bf81a
0x81cff2c
0x8179da0
0x817d30b
0x817f3ae
0x817fdbd
0x818075b
0x400479ed
0x401729ca
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8a504f0 = update enp_catalog_group ecg, $$catalog_group_total_ads gta
set ecg.total_ads = gta.total_ads
where  ecg.catalog_grp = gta.catalog_group
thd->thread_id=3
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
060318 14:12:40  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060318 14:12:40  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 326087383.
InnoDB: Doing recovery: scanned up to log sequence number 0 326087383
InnoDB: Last MySQL binlog file position 0 1162, file name /datawarehouse/logs.000100
060318 14:12:40  InnoDB: Started; log sequence number 0 326087383
060318 14:12:40 [Note] Recovering after a crash using /datawarehouse/logs
060318 14:12:40 [Note] Starting crash recovery...
060318 14:12:40 [Note] Crash recovery finished.
060318 14:12:40 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.15-standard-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)

How to repeat:
update enp_catalog_group ecg, 
          $$catalog_group_total_ads gta
set      ecg.total_ads   = gta.total_ads
where  ecg.catalog_grp = gta.catalog_group ;
[18 Mar 2006 15:32] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version of MySQL server, 5.0.15, and if you'll get the same results (crash), send a complete test case, with CREATE TABLE, some data, resolved stack trace etc.
[18 Mar 2006 16:33] Wil Wellington
In response to Valeriy Kravchuk comments, I hqave downloaded and updated to version 5.0.19 and I'm still plagued by the same problem.

mysql errorlog follows.....

mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=10485760
read_buffer_size=8200
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 215840 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8a469a0
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, fp=0x4310e2a4, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8167970
0xffffe420
0x8a58c2c
0x838eadb
0x82175c1
0x81d70b8
0x81b1908
0x81b7b8e
0x81b7d83
0x81b7b8e
0x81b7cb5
0x81bddd2
0x81cb0c4
0x81c789d
0x81d835c
0x81810d3
0x818427b
0x818633e
0x8186d5d
0x8187700
0x400339ed
0x401619ca
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8a4de28 = update enp_catalog_group ecg, $$catalog_group_total_ads gta
set ecg.total_ads = gta.total_ads
where  ecg.catalog_grp = gta.catalog_group
thd->thread_id=1
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
060318 17:00:54  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
060318 17:00:54  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 326090114.
InnoDB: Doing recovery: scanned up to log sequence number 0 326092823
060318 17:00:54  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 1162, file name /datawarehouse/logs.000100
060318 17:00:54  InnoDB: Started; log sequence number 0 326092823
060318 17:00:54 [Note] Recovering after a crash using /datawarehouse/logs
060318 17:00:54 [Note] Starting crash recovery...
060318 17:00:54 [Note] Crash recovery finished.
060318 17:00:55 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.19-standard-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
[25 Apr 2006 14:38] Valeriy Kravchuk
So, please, upload the SHOW CREATE TABLE and SHOW TABLE STATUS results for the tables used in your update:

update enp_catalog_group ecg,
$$catalog_group_total_ads gta
set ecg.total_ads = gta.total_ads
where  ecg.catalog_grp = gta.catalog_group

that is, enp_catalog_group and $$catalog_group_total_ads. Did you create these tables in MySQL 5.0.x or they were created in a previous version of MySQL, 4.x.y?
[25 May 2006 23: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".