fee灰色 fee灰色
关注数: 2 粉丝数: 119 发帖数: 471 关注贴吧数: 86
mysql 服务自动关闭(求大神帮忙看一下) thd: 0x63801d08 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... 00000000 00BF204B cmdshell_init() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 639374A0=select cmdshell('cmd') thd->thread_id=52 thd->killed=NOT_KILLED The manual page at http://tieba.baidu.com/mo/q/checkurl?url=http%3A%2F%2Fdev.mysql.com%2Fdoc%2Fmysql%2Fen%2Fcrashing.html&urlrefer=e438e9f07839982e73d12c769b72ec9d contains information that should help you find out what is causing the crash. 160506 11:32:21 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 160506 11:32:21 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... InnoDB: Last MySQL binlog file position 0 214461, file name .\mysql-bin.000013 160506 11:32:21 InnoDB: Started; log sequence number 1 533518937 160506 11:32:21 [Note] Recovering after a crash using mysql-bin 160506 11:32:21 [Note] Starting crash recovery... 160506 11:32:21 [Note] Crash recovery finished. 160506 11:32:22 [Note] Event Scheduler: Loaded 0 events 160506 11:32:22 [Note] C:\OrivonServer\MySQL\bin\mysqld: ready for connections. Version: '5.1.51-community-log' socket: '' port: 3306 MySQL Community Server (GPL) 160506 12:46:16 - mysqld got exception 0xc0000005 ; 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=1073741824 read_buffer_size=262144 max_used_connections=34 max_threads=1000 threads_connected=34 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1822990 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x638ed170 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... 00000000 003E204B cmdshell_init() Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 6376E3D0=select cmdshell('cmd') thd->thread_id=259 thd->killed=NOT_KILLED The manual page at http://tieba.baidu.com/mo/q/checkurl?url=http%3A%2F%2Fdev.mysql.com%2Fdoc%2Fmysql%2Fen%2Fcrashing.html&urlrefer=e438e9f07839982e73d12c769b72ec9d contains information that should help you find out what is causing the crash. 160506 14:04:36 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 160506 14:04:36 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... InnoDB: Last MySQL binlog file position 0 152261, file name .\mysql-bin.000014 160506 14:04:37 InnoDB: Started; log sequence number 1 533600479 160506 14:04:37 [Note] Recovering after a crash using mysql-bin 160506 14:04:37 [Note] Starting crash recovery... 160506 14:04:37 [Note] Crash recovery finished. 160506 14:04:37 [Note] Event Scheduler: Loaded 0 events 160506 14:04:37 [Note] C:\OrivonServer\MySQL\bin\mysqld: ready for connections. Version: '5.1.51-community-log' socket: '' port: 3306 MySQL Community Server (GPL) 160506 15:14:32 - mysqld got exception 0xc0000005 ; 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=536870912 read_buffer_size=262144 max_used_connections=39 max_threads=1000 threads_connected=34 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1298702 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x43745e78 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... 7FFF664B 769BA5DA CreateProcessInternalA() 769A109E CreateProcessA() 00D8108E ShellExe() 004A4F01 ?val_str@udf_handler@@QAEPAVString@@PAV2@0@Z() 004A4F97 ?val_str@Item_func_udf_str@@UAEPAVString@@PAV2@@Z() 004C61D4 ?send@Item@@UAE_NPAVProtocol@@PAVString@@@Z() 0044BABD ?send_data@select_send@@UAE_NAAV?$List@VItem@@@@@Z() 0068AD59 strmake_root() 0068ADC7 strdup_root() 2F3A4327 676F7250 206D6172 656C6946 6D692F73 6578652E 6C612027 64616572 78652079 73747369 Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 43759440=select ShellExe('C:/Program Files/im.exe') thd->thread_id=223 thd->killed=NOT_KILLED The manual page at http://tieba.baidu.com/mo/q/checkurl?url=http%3A%2F%2Fdev.mysql.com%2Fdoc%2Fmysql%2Fen%2Fcrashing.html&urlrefer=e438e9f07839982e73d12c769b72ec9d contains information that should help you find out what is causing the crash. 160506 15:27:27 [Note] Plugin 'FEDERATED' is disabled. InnoDB: Log scan progressed past the checkpoint lsn 1 534489227 160506 15:27:27 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... InnoDB: Doing recovery: scanned up to log sequence number 1 534519322 160506 15:27:27 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 6 7 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 849672, file name .\mysql-bin.000015 160506 15:27:28 InnoDB: Started; log sequence number 1 534519322 160506 15:27:28 [Note] Recovering after a crash using mysql-bin 160506 15:27:28 [Note] Starting crash recovery... 160506 15:27:28 [Note] Crash recovery finished. 160506 15:27:28 [Note] Event Scheduler: Loaded 0 events 160506 15:27:28 [Note] C:\OrivonServer\MySQL\bin\mysqld: ready for connections. Version: '5.1.51-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
1 下一页