mysql 执行查询导致服务器崩溃求解:Some pointers may be invalid and cause the dump to abort

  • 时间:
  • 浏览:2

InnoDB: Last MySQL binlog file position 0 18981718, file name ./mysql-bin.006479

/data/mysql/bin/mysqld(Item_subselect::exec()+0x42) [0x59dc12]

thd: 0xf200ed200

or misconfigured. This error can also be caused by malfunctioning hardware.

Attempting backtrace. You can use the following information to find out

read_buffer_size=2097152

InnoDB: buffer...

max_used_connections=1200

120720  9:25:33 [Note] Crash recovery finished.

terribly wrong...

/data/mysql/bin/mysqld(JOIN::optimize()+0x44e) [0x66e734]

InnoDB: http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html

/data/mysql/bin/mysqld(sub_select(JOIN*, st_join_table*, bool)+0xae) [0x68dcaa]

InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 200 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 200 51 52 53 54 55 56 57 58 59 200 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 200 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

/data/mysql/bin/mysqld(mysql_execute_command(THD*)+0x4b00) [0x610c200]

120720  9:25:27  InnoDB: Database was not shut down normally!

120720 09:25:26 mysqld_safe Number of processes running now: 0

120720  9:25:33 [Note] Starting crash recovery...

Some pointers may be invalid and cause the dump to abort...

InnoDB: in InnoDB data dictionary has tablespace id 4219,

120720  9:25:33 [Note] Event Scheduler: Loaded 0 events

/data/mysql/bin/mysqld(subselect_single_select_engine::exec()+0x26d) [0x59e4c1]

thd->thread_id=209

/data/mysql/bin/mysqld(handle_segfault+0x368) [0x200074c]

InnoDB: for how to resolve the issue.

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61828200 K

/data/mysql/bin/mysqld(do_command(THD*)+0x114) [0x200a296]

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: you deleted or moved .ibd files?

/data/mysql/bin/mysqld [0x616ad8]

InnoDB: This may also be a table created with CREATE TEMPORARY TABLE

/data/mysql/bin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x16c) [0x695220]

and this may fail.

120720 09:25:26 mysqld_safe mysqld restarted

/data/mysql/bin/mysqld [0x68e01c]

/data/mysql/bin/mysqld(SQL_SELECT::test_quick_select(THD*, Bitmap<64u>, unsigned long long, unsigned long long, bool)+0x6aa) [0x724144]

/data/mysql/bin/mysqld(Item::save_in_field_no_warnings(Field*, bool)+0x200) [0x52cc8c]

InnoDB: but tablespace with that id or name does not exist. Have

the problem, but since we have already crashed, something is definitely wrong

or one of the libraries it was linked against is corrupt, improperly built,

InnoDB: table still exists in the InnoDB internal data dictionary.

It is possible that mysqld could use up to

120720  9:25:27  InnoDB: Starting an apply batch of log records to the database...

120720  9:25:33  InnoDB: Started; log sequence number 124 4151885387

max_threads=2000

where mysqld died. If you see no messages after this, something went

InnoDB: Doing recovery: scanned up to log sequence number 124 4151885387

/data/mysql/bin/mysqld [0x68d200f]

thd->killed=NOT_KILLED

Version: '5.1.35-log'  socket: '/tmp/mysql.sock'  port: 32006  MySQL Community Server (GPL)

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

This could be because you hit a bug. It is also possible that this binary

InnoDB: Please refer to

/data/mysql/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x133f) [0x200b5d9]

InnoDB: Apply batch completed

bytes of memory

InnoDB: Thread 1103137088 stopped in file handler/ha_innodb.cc line 4583

/data/mysql/bin/mysqld(Item_singlerow_subselect::val_int()+0xb5) [0x59ed8f]

Hope that's ok; if not, decrease some variables in the equation.

/data/mysql/bin/mysqld(Item::save_in_field(Field*, bool)+0x275) [0x2007fb7]

/data/mysql/bin/mysqld [0x675934]

/lib64/libpthread.so.0 [0x3c8cc0eb10]

InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html

InnoDB: Starting crash recovery.

/data/mysql/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x61706e]

InnoDB: immediately after the mysqld startup, there may be

120720  9:25:33 [Note] Recovering after a crash using mysql-bin

InnoDB: Thread 11670182004 stopped in file os/os0sync.c line 588

Trying to get some variables.

/lib64/libpthread.so.0 [0x3c8cc0673d]

/data/mysql/bin/mysqld(my_print_stacktrace+0x20) [0xa05744]

key_buffer_size=33554432

InnoDB: corruption in the InnoDB tablespace. Please refer to

120720  9:25:33 [Note] /data/mysql/bin/mysqld: ready for connections.

thd->query at 0xff36200 = SELECT DISTINCT g.USER_ID FROM SYS_USER_GROUP g  LEFT JOIN SYS_USER u on g.USER_ID=u.USER_ID  WHERE GROUP_ID = (SELECT GROUP_ID  FROM SYS_GROUP WHERE GROUP_CODE='ZB_JIHUAHUAN_GROUP') AND u.org_id = 2

/data/mysql/bin/mysqld [0x72617c]

/data/mysql/bin/mysqld(JOIN::exec()+0x1990) [0x6881e0]

/data/mysql/bin/mysqld [0x72a4ab]

/lib64/libc.so.6(clone+0x6d) [0x3c8c0d3d1d]

InnoDB: Log scan progressed past the checkpoint lsn 124 4200467491

threads_connected=177

InnoDB: Restoring possible half-written data pages from the doublewrite

stack_bottom = 0x42009c118 thread_stack 0x20000

/data/mysql/bin/mysqld [0x725901]

120720  9:25:25  InnoDB: Assertion failure in thread 11720046464 in file row/row0mysql.c line 1534

InnoDB: about forcing recovery.

InnoDB: We intentionally generate a memory trap.

/data/mysql/bin/mysqld(row_unlock_for_mysql+0x11e) [0x915112]

InnoDB: whose .ibd and .frm files MySQL automatically removed, but the

120720  9:25:27  InnoDB: Error: table 'tmp/#sql3712_1558c_2'

/data/mysql/bin/mysqld(handle_one_connection+0xd20) [0x200564c]

information that should help you find out what is causing the crash.

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

InnoDB: If you get repeated assertion failures or crashes, even

120720  9:25:25 - mysqld got signal 11 ;

/data/mysql/bin/mysqld(ha_innobase::unlock_row()+0x57) [0x835200f]

InnoDB: Thread 11706200976 stopped in file ../../storage/innobase/include/sync0sync.ic line 115

We will try our best to scrape up some info that will hopefully help diagnose