Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
5.5.33a-galera
-
None
-
Debian Wheezy
Description
The following DELETE causes mariadb-galera-server to abend with signal 11 (and sometimes signal 6). The server crash logs follow the delete statement. Note that the DELETE statement works if broken into smaller pieces.
DELETE FROM period WHERE process IN ('reconcile','statistics') AND ( |
(item_period < '20130830' AND rec_id IN ('10002607', '300032001')) OR |
(item_period < '20130902' AND rec_id IN ('10002530', '10002598', '10003238', '290032001')) OR |
(item_period < '20130903' AND rec_id IN ('10000343', '10828288', '260032001')) OR |
(item_period < '20130905' AND rec_id IN ('10000854', '10002447', '10002472', '10002550', '10002561', '10003120', '100032001', '10003409', '10004172', '10004555', '10004858', '10004861', '10023903', '10032001', '10085903', '110032001', '110132001', '11579596', '11579769', '120032001', '130032001', '150032001', '160032001', '170032001', '190032001', '190132001', '20032001', '250032001', '320051001', '320080001', '320081001', '320082001', '40032001', '60032001', '70032001', '90032001')) OR |
(item_period < '20130905' AND item_period NOT IN ('20130801', '20130802', '20130805', '20130806', '20130807', '20130808', '20130809', '20130812', '20130813', '20130814', '20130815', '20130816', '20130819', '20130820', '20130821', '20130822', '20130823', '20130826', '20130827') AND |
rec_id IN ('11301288')) OR |
(item_period < '20130906' AND rec_id IN ('10001410')) OR |
(item_period < '20130926' AND rec_id IN ('10000346', '10000347', '10002716', '10003510')) OR |
(item_period < '20130930' AND rec_id IN ('10000374', '10000375', '10001810', '10001811', '10750288', '10836288', '10842288', '10966288', '11140288', '11141288', '11142288', '11144288', '11145288', '11146288', '11147288', '11148288', '11149288', '11150288', '11151288', '11152288', '11153288', '11169288', '11170288', '11231288', '11232288', '11237288', '11238288', '11239288', '11483288', '11484288', '11579609', '11579650', '11579700', '11579701', '11579739', '250032004', '250032005', '70032004', '70032005', '90032002', '90032004')) OR |
(item_period < '20131004' AND rec_id IN ('10001418', '10003519', '11579328')) OR |
(item_period < '20131007' AND rec_id IN ('11172288', '300032002')) OR |
(item_period < '20131008' AND rec_id IN ('10001839', '10002531', '10002600', '10003239', '10105903', '10523172', '10749288', '10784288', '10835288', '10837288', '11049288', '11426288', '11485288', '11486288', '11579302', '11579303', '11579387', '11579389', '11579604', '11579638', '11579740', '11579849', '290032002')) OR |
(item_period < '20131009' AND rec_id IN ('10000344', '10829288', '260032002')) OR |
(item_period < '20131010' AND rec_id IN ('10000855', '10002448', '10002474', '10002549', '10002560', '10003119', '10003408', '10004171', '10004556', '10004859', '10004862', '10022903', '10032002', '10084903', '110032002', '110132002', '11579625', '11579770', '120032002', '130032002', '150032002', '160032002', '170032002', '190032002', '190132002', '20032002', '250032002', '320051002', '320080002', '320081002', '320082002', '40032002', '60032002', '70032002', '90032005')) OR |
(item_period < '20131010' AND item_period NOT IN ('20130801', '20130802', '20130805', '20130806', '20130807', '20130808', '20130809', '20130812', '20130813', '20130814', '20130815', '20130816', '20130819', '20130820', '20130821', '20130822', '20130823', '20130826', '20130827') AND rec_id IN ('11300288')) |
)
|
and the server logs...
mysqld: 131021 21:53:14 [ERROR] mysqld got signal 11 ;
|
mysqld: This could be because you hit a bug. It is also possible that this binary
|
mysqld: or one of the libraries it was linked against is corrupt, improperly built,
|
mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
|
mysqld:
|
mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
|
mysqld:
|
mysqld: We will try our best to scrape up some info that will hopefully help
|
mysqld: diagnose the problem, but since we have already crashed,
|
mysqld: something is definitely wrong and this may fail.
|
mysqld:
|
mysqld: Server version: 5.5.33a-MariaDB-1~wheezy-log
|
mysqld: key_buffer_size=536870912
|
mysqld: read_buffer_size=2097152
|
mysqld: max_used_connections=501
|
mysqld: max_threads=10002
|
mysqld: thread_count=143
|
mysqld: It is possible that mysqld could use up to
|
mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62159406 K bytes of memory
|
mysqld: Hope that's ok; if not, decrease some variables in the equation.
|
mysqld:
|
mysqld: Thread pointer: 0x0x7f0c92b45000
|
mysqld: Attempting backtrace. You can use the following information to find out
|
mysqld: where mysqld died. If you see no messages after this, something went
|
mysqld: terribly wrong...
|
mysqld: stack_bottom = 0x7f27c7cccdb0 thread_stack 0x48000
|
mysqld: ??:0(??)[0x7f8bcd8a3e5b]
|
mysqld: ??:0(??)[0x7f8bcd4d58d2]
|
mysqld: ??:0(??)[0x7f8bccbb3030]
|
mysqld: ??:0(??)[0x7f8bcd5aef34]
|
mysqld: ??:0(??)[0x7f8bcd5b8720]
|
mysqld: ??:0(??)[0x7f8bcd5dfaa8]
|
mysqld: ??:0(??)[0x7f8bcd390e78]
|
mysqld: ??:0(??)[0x7f8bcd3943d7]
|
mysqld: ??:0(??)[0x7f8bcd3947cf]
|
mysqld: ??:0(??)[0x7f8bcd39652a]
|
mysqld: ??:0(??)[0x7f8bcd396c59]
|
mysqld: ??:0(??)[0x7f8bcd44994b]
|
mysqld: ??:0(??)[0x7f8bcd4499f1]
|
mysqld: ??:0(??)[0x7f8bccbaab50]
|
mysqld: ??:0(??)[0x7f8bcb4cea7d]
|
mysqld:
|
mysqld: Trying to get some variables.
|
mysqld: Some pointers may be invalid and cause the dump to abort.
|
mysqld: Query (0x7f00bddb2018): is an invalid pointer
|
mysqld: Connection ID (thread ID): 1044736
|
mysqld: Status: NOT_KILLED
|
mysqld:
|
mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engin
|
mysqld:
|
mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
mysqld: information that should help you find out what is causing the crash.
|