071129 07:54:14 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 071129 7:54:15 InnoDB: Setting file ./ibdata1 size to 1024 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000 071129 7:54:20 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 400 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 300 400 071129 7:54:23 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 400 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 300 400 071129 7:54:26 InnoDB: Log file ./ib_logfile2 did not exist: new to be created InnoDB: Setting log file ./ib_logfile2 size to 400 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 200 300 400 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 071129 7:54:29 InnoDB: Started; log sequence number 0 0 071129 7:54:29 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071130 12:01:01 InnoDB: Error: cannot allocate 999424 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071130 12:02:01 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=134217728 read_buffer_size=2093056 max_used_connections=47 max_connections=100 threads_connected=14 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1154671 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071130 12:02:02 mysqld restarted 071130 12:02:02 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... 071130 12:02:02 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 11 3953468642. InnoDB: Doing recovery: scanned up to log sequence number 11 3958711296 InnoDB: Doing recovery: scanned up to log sequence number 11 3963954176 InnoDB: Doing recovery: scanned up to log sequence number 11 3969197056 InnoDB: Doing recovery: scanned up to log sequence number 11 3974439936 InnoDB: Doing recovery: scanned up to log sequence number 11 3979682816 InnoDB: Doing recovery: scanned up to log sequence number 11 3984925696 InnoDB: Doing recovery: scanned up to log sequence number 11 3990168576 InnoDB: Doing recovery: scanned up to log sequence number 11 3995411456 InnoDB: Doing recovery: scanned up to log sequence number 11 4000654336 InnoDB: Doing recovery: scanned up to log sequence number 11 4005897216 InnoDB: Doing recovery: scanned up to log sequence number 11 4011140096 InnoDB: Doing recovery: scanned up to log sequence number 11 4016382976 InnoDB: Doing recovery: scanned up to log sequence number 11 4021625856 InnoDB: Doing recovery: scanned up to log sequence number 11 4026868736 InnoDB: Doing recovery: scanned up to log sequence number 11 4032111616 InnoDB: Doing recovery: scanned up to log sequence number 11 4037354496 InnoDB: Doing recovery: scanned up to log sequence number 11 4042597376 InnoDB: Doing recovery: scanned up to log sequence number 11 4047840256 InnoDB: Doing recovery: scanned up to log sequence number 11 4053083136 InnoDB: Doing recovery: scanned up to log sequence number 11 4058326016 InnoDB: Doing recovery: scanned up to log sequence number 11 4063568896 InnoDB: Doing recovery: scanned up to log sequence number 11 4068811776 InnoDB: Doing recovery: scanned up to log sequence number 11 4074054656 InnoDB: Doing recovery: scanned up to log sequence number 11 4079297536 InnoDB: Doing recovery: scanned up to log sequence number 11 4084540416 InnoDB: Doing recovery: scanned up to log sequence number 11 4089783296 InnoDB: Doing recovery: scanned up to log sequence number 11 4095026176 InnoDB: Doing recovery: scanned up to log sequence number 11 4100269056 InnoDB: Doing recovery: scanned up to log sequence number 11 4105511936 InnoDB: Doing recovery: scanned up to log sequence number 11 4110754816 InnoDB: Doing recovery: scanned up to log sequence number 11 4115997696 InnoDB: Doing recovery: scanned up to log sequence number 11 4121240576 InnoDB: Doing recovery: scanned up to log sequence number 11 4126483456 InnoDB: Doing recovery: scanned up to log sequence number 11 4131726336 InnoDB: Doing recovery: scanned up to log sequence number 11 4136969216 InnoDB: Doing recovery: scanned up to log sequence number 11 4142212096 InnoDB: Doing recovery: scanned up to log sequence number 11 4147454976 InnoDB: Doing recovery: scanned up to log sequence number 11 4152697856 InnoDB: Doing recovery: scanned up to log sequence number 11 4157940736 InnoDB: Doing recovery: scanned up to log sequence number 11 4163183616 InnoDB: Doing recovery: scanned up to log sequence number 11 4168426496 InnoDB: Doing recovery: scanned up to log sequence number 11 4173669376 InnoDB: Doing recovery: scanned up to log sequence number 11 4178912256 InnoDB: Doing recovery: scanned up to log sequence number 11 4184155136 InnoDB: Doing recovery: scanned up to log sequence number 11 4189398016 InnoDB: Doing recovery: scanned up to log sequence number 11 4194640896 InnoDB: Doing recovery: scanned up to log sequence number 11 4199883776 InnoDB: Doing recovery: scanned up to log sequence number 11 4205126656 InnoDB: Doing recovery: scanned up to log sequence number 11 4210369536 InnoDB: Doing recovery: scanned up to log sequence number 11 4215612416 InnoDB: Doing recovery: scanned up to log sequence number 11 4220855296 InnoDB: Doing recovery: scanned up to log sequence number 11 4226098176 InnoDB: Doing recovery: scanned up to log sequence number 11 4231341056 InnoDB: Doing recovery: scanned up to log sequence number 11 4236583936 InnoDB: Doing recovery: scanned up to log sequence number 11 4241826816 InnoDB: Doing recovery: scanned up to log sequence number 11 4247069696 InnoDB: Doing recovery: scanned up to log sequence number 11 4252312576 InnoDB: Doing recovery: scanned up to log sequence number 11 4257555456 InnoDB: Doing recovery: scanned up to log sequence number 11 4262798336 InnoDB: Doing recovery: scanned up to log sequence number 11 4268041216 InnoDB: Doing recovery: scanned up to log sequence number 11 4273284096 InnoDB: Doing recovery: scanned up to log sequence number 11 4278526976 InnoDB: Doing recovery: scanned up to log sequence number 11 4283769856 InnoDB: Doing recovery: scanned up to log sequence number 11 4289012736 InnoDB: Doing recovery: scanned up to log sequence number 11 4294255616 InnoDB: Doing recovery: scanned up to log sequence number 12 4531200 InnoDB: Doing recovery: scanned up to log sequence number 12 9774080 InnoDB: Doing recovery: scanned up to log sequence number 12 15016960 InnoDB: Doing recovery: scanned up to log sequence number 12 20259840 InnoDB: Doing recovery: scanned up to log sequence number 12 25502720 InnoDB: Doing recovery: scanned up to log sequence number 12 30745600 InnoDB: Doing recovery: scanned up to log sequence number 12 35988480 InnoDB: Doing recovery: scanned up to log sequence number 12 41231360 InnoDB: Doing recovery: scanned up to log sequence number 12 46474240 InnoDB: Doing recovery: scanned up to log sequence number 12 51717120 InnoDB: Doing recovery: scanned up to log sequence number 12 56960000 InnoDB: Doing recovery: scanned up to log sequence number 12 62202880 InnoDB: Doing recovery: scanned up to log sequence number 12 67445760 InnoDB: Doing recovery: scanned up to log sequence number 12 72688640 InnoDB: Doing recovery: scanned up to log sequence number 12 77931520 InnoDB: Doing recovery: scanned up to log sequence number 12 83174400 InnoDB: Doing recovery: scanned up to log sequence number 12 88417280 InnoDB: Doing recovery: scanned up to log sequence number 12 93660160 InnoDB: Doing recovery: scanned up to log sequence number 12 98903040 InnoDB: Doing recovery: scanned up to log sequence number 12 104145920 InnoDB: Doing recovery: scanned up to log sequence number 12 109388800 InnoDB: Doing recovery: scanned up to log sequence number 12 114631680 InnoDB: Doing recovery: scanned up to log sequence number 12 119874560 InnoDB: Doing recovery: scanned up to log sequence number 12 125117440 InnoDB: Doing recovery: scanned up to log sequence number 12 130360320 InnoDB: Doing recovery: scanned up to log sequence number 12 135603200 InnoDB: Doing recovery: scanned up to log sequence number 12 140846080 InnoDB: Doing recovery: scanned up to log sequence number 12 146088960 InnoDB: Doing recovery: scanned up to log sequence number 12 151331840 InnoDB: Doing recovery: scanned up to log sequence number 12 156574720 InnoDB: Doing recovery: scanned up to log sequence number 12 161817600 InnoDB: Doing recovery: scanned up to log sequence number 12 167060480 InnoDB: Doing recovery: scanned up to log sequence number 12 172303360 InnoDB: Doing recovery: scanned up to log sequence number 12 177546240 InnoDB: Doing recovery: scanned up to log sequence number 12 182789120 InnoDB: Doing recovery: scanned up to log sequence number 12 188032000 InnoDB: Doing recovery: scanned up to log sequence number 12 193274880 InnoDB: Doing recovery: scanned up to log sequence number 12 198517760 InnoDB: Doing recovery: scanned up to log sequence number 12 203760640 InnoDB: Doing recovery: scanned up to log sequence number 12 209003520 InnoDB: Doing recovery: scanned up to log sequence number 12 214246400 InnoDB: Doing recovery: scanned up to log sequence number 12 219489280 InnoDB: Doing recovery: scanned up to log sequence number 12 224732160 InnoDB: Doing recovery: scanned up to log sequence number 12 229975040 InnoDB: Doing recovery: scanned up to log sequence number 12 235217920 InnoDB: Doing recovery: scanned up to log sequence number 12 240460800 InnoDB: Doing recovery: scanned up to log sequence number 12 245703680 InnoDB: Doing recovery: scanned up to log sequence number 12 250946560 InnoDB: Doing recovery: scanned up to log sequence number 12 256189440 InnoDB: Doing recovery: scanned up to log sequence number 12 261432320 InnoDB: Doing recovery: scanned up to log sequence number 12 266675200 InnoDB: Doing recovery: scanned up to log sequence number 12 271918080 InnoDB: Doing recovery: scanned up to log sequence number 12 277160960 InnoDB: Doing recovery: scanned up to log sequence number 12 282403840 InnoDB: Doing recovery: scanned up to log sequence number 12 287646720 InnoDB: Doing recovery: scanned up to log sequence number 12 292889600 InnoDB: Doing recovery: scanned up to log sequence number 12 298132480 InnoDB: Doing recovery: scanned up to log sequence number 12 303375360 InnoDB: Doing recovery: scanned up to log sequence number 12 308618240 InnoDB: Doing recovery: scanned up to log sequence number 12 313861120 InnoDB: Doing recovery: scanned up to log sequence number 12 319104000 InnoDB: Doing recovery: scanned up to log sequence number 12 324346880 InnoDB: Doing recovery: scanned up to log sequence number 12 329589760 InnoDB: Doing recovery: scanned up to log sequence number 12 334832640 InnoDB: Doing recovery: scanned up to log sequence number 12 340075520 InnoDB: Doing recovery: scanned up to log sequence number 12 345318400 InnoDB: Doing recovery: scanned up to log sequence number 12 350561280 InnoDB: Doing recovery: scanned up to log sequence number 12 355804160 InnoDB: Doing recovery: scanned up to log sequence number 12 361047040 InnoDB: Doing recovery: scanned up to log sequence number 12 366289920 InnoDB: Doing recovery: scanned up to log sequence number 12 371532800 InnoDB: Doing recovery: scanned up to log sequence number 12 376775680 InnoDB: Doing recovery: scanned up to log sequence number 12 382018560 InnoDB: Doing recovery: scanned up to log sequence number 12 387261440 InnoDB: Doing recovery: scanned up to log sequence number 12 392504320 InnoDB: Doing recovery: scanned up to log sequence number 12 397747200 InnoDB: Doing recovery: scanned up to log sequence number 12 402990080 InnoDB: Doing recovery: scanned up to log sequence number 12 408232960 InnoDB: Doing recovery: scanned up to log sequence number 12 413475840 InnoDB: Doing recovery: scanned up to log sequence number 12 418718720 InnoDB: Doing recovery: scanned up to log sequence number 12 423961600 InnoDB: Doing recovery: scanned up to log sequence number 12 429204480 InnoDB: Doing recovery: scanned up to log sequence number 12 434447360 InnoDB: Doing recovery: scanned up to log sequence number 12 439690240 InnoDB: Doing recovery: scanned up to log sequence number 12 444933120 InnoDB: Doing recovery: scanned up to log sequence number 12 450176000 InnoDB: Doing recovery: scanned up to log sequence number 12 455418880 InnoDB: Doing recovery: scanned up to log sequence number 12 460661760 InnoDB: Doing recovery: scanned up to log sequence number 12 465904640 InnoDB: Doing recovery: scanned up to log sequence number 12 471147520 InnoDB: Doing recovery: scanned up to log sequence number 12 476390400 071130 12:04:39 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 12 481633280 InnoDB: Doing recovery: scanned up to log sequence number 12 486876160 InnoDB: Doing recovery: scanned up to log sequence number 12 492119040 InnoDB: Doing recovery: scanned up to log sequence number 12 497361920 InnoDB: Doing recovery: scanned up to log sequence number 12 502604800 InnoDB: Doing recovery: scanned up to log sequence number 12 507847680 InnoDB: Doing recovery: scanned up to log sequence number 12 513090560 InnoDB: Doing recovery: scanned up to log sequence number 12 518333440 InnoDB: Doing recovery: scanned up to log sequence number 12 523576320 InnoDB: Doing recovery: scanned up to log sequence number 12 528819200 InnoDB: Doing recovery: scanned up to log sequence number 12 534062080 InnoDB: Doing recovery: scanned up to log sequence number 12 539304960 InnoDB: Doing recovery: scanned up to log sequence number 12 544547840 InnoDB: Doing recovery: scanned up to log sequence number 12 549520232 InnoDB: 4 transaction(s) which must be rolled back or cleaned up InnoDB: in total 109 row operations to undo InnoDB: Trx id counter is 0 145490688 071130 12:08:04 InnoDB: Starting an apply batch of log records to the database... 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 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 071130 12:09:43 InnoDB: Started; log sequence number 12 549520232 InnoDB: Starting in background the rollback of uncommitted transactions 071130 12:09:43 InnoDB: Rolling back trx with id 0 145490389, 12 rows to undo InnoDB: Rolling back of trx id 0 145490389 completed 071130 12:09:43 InnoDB: Rolling back trx with id 0 145490383, 60 rows to undo InnoDB: Rolling back of trx id 0 145490383 completed 071130 12:09:43 InnoDB: Rolling back trx with id 0 145490378, 36 rows to undo InnoDB: Rolling back of trx id 0 145490378 completed 071130 12:09:43 InnoDB: Rolling back trx with id 0 145490373, 1 rows to undo InnoDB: Rolling back of trx id 0 145490373 completed 071130 12:09:43 InnoDB: Rollback of non-prepared transactions completed 071130 12:09:43 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071130 12:09:46 [ERROR] /usr/sbin/mysqld: Table './mysql/proc' is marked as crashed and should be repaired 071130 12:09:46 [Warning] Checking table: './mysql/proc' 071130 12:09:46 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071130 12:09:46 [Warning] Checking table: './tlbbdb/t_global' 071201 8:28:21 InnoDB: Error: cannot allocate 1064960 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071201 8:29:21 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=134217728 read_buffer_size=2093056 max_used_connections=47 max_connections=100 threads_connected=10 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1154671 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071201 08:29:22 mysqld restarted 071201 8:29:22 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... 071201 8:29:22 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 23 716383450. InnoDB: Doing recovery: scanned up to log sequence number 23 721626112 InnoDB: Doing recovery: scanned up to log sequence number 23 726868992 InnoDB: Doing recovery: scanned up to log sequence number 23 732111872 InnoDB: Doing recovery: scanned up to log sequence number 23 737354752 InnoDB: Doing recovery: scanned up to log sequence number 23 742597632 InnoDB: Doing recovery: scanned up to log sequence number 23 747840512 InnoDB: Doing recovery: scanned up to log sequence number 23 753083392 InnoDB: Doing recovery: scanned up to log sequence number 23 758326272 InnoDB: Doing recovery: scanned up to log sequence number 23 763569152 InnoDB: Doing recovery: scanned up to log sequence number 23 768812032 InnoDB: Doing recovery: scanned up to log sequence number 23 774054912 InnoDB: Doing recovery: scanned up to log sequence number 23 779297792 InnoDB: Doing recovery: scanned up to log sequence number 23 784540672 InnoDB: Doing recovery: scanned up to log sequence number 23 789783552 InnoDB: Doing recovery: scanned up to log sequence number 23 795026432 InnoDB: Doing recovery: scanned up to log sequence number 23 800269312 InnoDB: Doing recovery: scanned up to log sequence number 23 805512192 InnoDB: Doing recovery: scanned up to log sequence number 23 810755072 InnoDB: Doing recovery: scanned up to log sequence number 23 815997952 InnoDB: Doing recovery: scanned up to log sequence number 23 821240832 InnoDB: Doing recovery: scanned up to log sequence number 23 826483712 InnoDB: Doing recovery: scanned up to log sequence number 23 831726592 InnoDB: Doing recovery: scanned up to log sequence number 23 836969472 InnoDB: Doing recovery: scanned up to log sequence number 23 842212352 InnoDB: Doing recovery: scanned up to log sequence number 23 847455232 InnoDB: Doing recovery: scanned up to log sequence number 23 852698112 InnoDB: Doing recovery: scanned up to log sequence number 23 857940992 InnoDB: Doing recovery: scanned up to log sequence number 23 863183872 InnoDB: Doing recovery: scanned up to log sequence number 23 868426752 InnoDB: Doing recovery: scanned up to log sequence number 23 873669632 InnoDB: Doing recovery: scanned up to log sequence number 23 878912512 InnoDB: Doing recovery: scanned up to log sequence number 23 884155392 InnoDB: Doing recovery: scanned up to log sequence number 23 889398272 InnoDB: Doing recovery: scanned up to log sequence number 23 894641152 InnoDB: Doing recovery: scanned up to log sequence number 23 899884032 InnoDB: Doing recovery: scanned up to log sequence number 23 905126912 InnoDB: Doing recovery: scanned up to log sequence number 23 910369792 InnoDB: Doing recovery: scanned up to log sequence number 23 915612672 InnoDB: Doing recovery: scanned up to log sequence number 23 920855552 InnoDB: Doing recovery: scanned up to log sequence number 23 926098432 InnoDB: Doing recovery: scanned up to log sequence number 23 931341312 InnoDB: Doing recovery: scanned up to log sequence number 23 936584192 InnoDB: Doing recovery: scanned up to log sequence number 23 941827072 InnoDB: Doing recovery: scanned up to log sequence number 23 947069952 InnoDB: Doing recovery: scanned up to log sequence number 23 952312832 InnoDB: Doing recovery: scanned up to log sequence number 23 957555712 InnoDB: Doing recovery: scanned up to log sequence number 23 962798592 InnoDB: Doing recovery: scanned up to log sequence number 23 968041472 InnoDB: Doing recovery: scanned up to log sequence number 23 973284352 InnoDB: Doing recovery: scanned up to log sequence number 23 978527232 InnoDB: Doing recovery: scanned up to log sequence number 23 983770112 InnoDB: Doing recovery: scanned up to log sequence number 23 989012992 InnoDB: Doing recovery: scanned up to log sequence number 23 994255872 InnoDB: Doing recovery: scanned up to log sequence number 23 999498752 InnoDB: Doing recovery: scanned up to log sequence number 23 1004741632 InnoDB: Doing recovery: scanned up to log sequence number 23 1009984512 InnoDB: Doing recovery: scanned up to log sequence number 23 1015227392 InnoDB: Doing recovery: scanned up to log sequence number 23 1020470272 InnoDB: Doing recovery: scanned up to log sequence number 23 1025713152 InnoDB: Doing recovery: scanned up to log sequence number 23 1030956032 InnoDB: Doing recovery: scanned up to log sequence number 23 1036198912 InnoDB: Doing recovery: scanned up to log sequence number 23 1041441792 InnoDB: Doing recovery: scanned up to log sequence number 23 1046684672 InnoDB: Doing recovery: scanned up to log sequence number 23 1051927552 InnoDB: Doing recovery: scanned up to log sequence number 23 1057170432 InnoDB: Doing recovery: scanned up to log sequence number 23 1062413312 InnoDB: Doing recovery: scanned up to log sequence number 23 1067656192 InnoDB: Doing recovery: scanned up to log sequence number 23 1072899072 InnoDB: Doing recovery: scanned up to log sequence number 23 1078141952 InnoDB: Doing recovery: scanned up to log sequence number 23 1083384832 InnoDB: Doing recovery: scanned up to log sequence number 23 1088627712 InnoDB: Doing recovery: scanned up to log sequence number 23 1093870592 InnoDB: Doing recovery: scanned up to log sequence number 23 1099113472 InnoDB: Doing recovery: scanned up to log sequence number 23 1104356352 InnoDB: Doing recovery: scanned up to log sequence number 23 1109599232 InnoDB: Doing recovery: scanned up to log sequence number 23 1114842112 InnoDB: Doing recovery: scanned up to log sequence number 23 1120084992 InnoDB: Doing recovery: scanned up to log sequence number 23 1125327872 InnoDB: Doing recovery: scanned up to log sequence number 23 1130570752 InnoDB: Doing recovery: scanned up to log sequence number 23 1135813632 InnoDB: Doing recovery: scanned up to log sequence number 23 1141056512 InnoDB: Doing recovery: scanned up to log sequence number 23 1146299392 InnoDB: Doing recovery: scanned up to log sequence number 23 1151542272 InnoDB: Doing recovery: scanned up to log sequence number 23 1156785152 InnoDB: Doing recovery: scanned up to log sequence number 23 1162028032 InnoDB: Doing recovery: scanned up to log sequence number 23 1167270912 InnoDB: Doing recovery: scanned up to log sequence number 23 1172513792 InnoDB: Doing recovery: scanned up to log sequence number 23 1177756672 InnoDB: Doing recovery: scanned up to log sequence number 23 1182999552 InnoDB: Doing recovery: scanned up to log sequence number 23 1188242432 InnoDB: Doing recovery: scanned up to log sequence number 23 1193485312 InnoDB: Doing recovery: scanned up to log sequence number 23 1198728192 InnoDB: Doing recovery: scanned up to log sequence number 23 1203971072 InnoDB: Doing recovery: scanned up to log sequence number 23 1209213952 InnoDB: Doing recovery: scanned up to log sequence number 23 1214456832 InnoDB: Doing recovery: scanned up to log sequence number 23 1219699712 InnoDB: Doing recovery: scanned up to log sequence number 23 1224942592 InnoDB: Doing recovery: scanned up to log sequence number 23 1230185472 InnoDB: Doing recovery: scanned up to log sequence number 23 1235428352 InnoDB: Doing recovery: scanned up to log sequence number 23 1240671232 InnoDB: Doing recovery: scanned up to log sequence number 23 1245914112 InnoDB: Doing recovery: scanned up to log sequence number 23 1251156992 InnoDB: Doing recovery: scanned up to log sequence number 23 1256399872 InnoDB: Doing recovery: scanned up to log sequence number 23 1261642752 InnoDB: Doing recovery: scanned up to log sequence number 23 1266885632 InnoDB: Doing recovery: scanned up to log sequence number 23 1272128512 InnoDB: Doing recovery: scanned up to log sequence number 23 1277371392 InnoDB: Doing recovery: scanned up to log sequence number 23 1282614272 InnoDB: Doing recovery: scanned up to log sequence number 23 1287857152 InnoDB: Doing recovery: scanned up to log sequence number 23 1293100032 InnoDB: Doing recovery: scanned up to log sequence number 23 1298342912 InnoDB: Doing recovery: scanned up to log sequence number 23 1303585792 InnoDB: Doing recovery: scanned up to log sequence number 23 1308828672 InnoDB: Doing recovery: scanned up to log sequence number 23 1314071552 InnoDB: Doing recovery: scanned up to log sequence number 23 1319314432 InnoDB: Doing recovery: scanned up to log sequence number 23 1324557312 InnoDB: Doing recovery: scanned up to log sequence number 23 1329800192 InnoDB: Doing recovery: scanned up to log sequence number 23 1335043072 InnoDB: Doing recovery: scanned up to log sequence number 23 1340285952 InnoDB: Doing recovery: scanned up to log sequence number 23 1345528832 InnoDB: Doing recovery: scanned up to log sequence number 23 1350771712 InnoDB: Doing recovery: scanned up to log sequence number 23 1356014592 InnoDB: Doing recovery: scanned up to log sequence number 23 1361257472 InnoDB: Doing recovery: scanned up to log sequence number 23 1366500352 InnoDB: Doing recovery: scanned up to log sequence number 23 1371743232 InnoDB: Doing recovery: scanned up to log sequence number 23 1376986112 InnoDB: Doing recovery: scanned up to log sequence number 23 1382228992 InnoDB: Doing recovery: scanned up to log sequence number 23 1387471872 InnoDB: Doing recovery: scanned up to log sequence number 23 1392714752 InnoDB: Doing recovery: scanned up to log sequence number 23 1397957632 InnoDB: Doing recovery: scanned up to log sequence number 23 1403200512 InnoDB: Doing recovery: scanned up to log sequence number 23 1408443392 InnoDB: Doing recovery: scanned up to log sequence number 23 1413686272 InnoDB: Doing recovery: scanned up to log sequence number 23 1418929152 InnoDB: Doing recovery: scanned up to log sequence number 23 1424172032 InnoDB: Doing recovery: scanned up to log sequence number 23 1429414912 InnoDB: Doing recovery: scanned up to log sequence number 23 1434657792 InnoDB: Doing recovery: scanned up to log sequence number 23 1439900672 InnoDB: Doing recovery: scanned up to log sequence number 23 1445143552 InnoDB: Doing recovery: scanned up to log sequence number 23 1450386432 InnoDB: Doing recovery: scanned up to log sequence number 23 1455629312 InnoDB: Doing recovery: scanned up to log sequence number 23 1460872192 InnoDB: Doing recovery: scanned up to log sequence number 23 1466115072 InnoDB: Doing recovery: scanned up to log sequence number 23 1471357952 InnoDB: Doing recovery: scanned up to log sequence number 23 1476600832 InnoDB: Doing recovery: scanned up to log sequence number 23 1481843712 InnoDB: Doing recovery: scanned up to log sequence number 23 1487086592 InnoDB: Doing recovery: scanned up to log sequence number 23 1492329472 InnoDB: Doing recovery: scanned up to log sequence number 23 1497572352 InnoDB: Doing recovery: scanned up to log sequence number 23 1502815232 InnoDB: Doing recovery: scanned up to log sequence number 23 1508058112 InnoDB: Doing recovery: scanned up to log sequence number 23 1513300992 InnoDB: Doing recovery: scanned up to log sequence number 23 1518543872 InnoDB: Doing recovery: scanned up to log sequence number 23 1523786752 InnoDB: Doing recovery: scanned up to log sequence number 23 1529029632 InnoDB: Doing recovery: scanned up to log sequence number 23 1534272512 InnoDB: Doing recovery: scanned up to log sequence number 23 1539515392 071201 8:31:58 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 23 1544758272 InnoDB: Doing recovery: scanned up to log sequence number 23 1550001152 InnoDB: Doing recovery: scanned up to log sequence number 23 1555244032 InnoDB: Doing recovery: scanned up to log sequence number 23 1560486912 InnoDB: Doing recovery: scanned up to log sequence number 23 1565729792 InnoDB: Doing recovery: scanned up to log sequence number 23 1570972672 InnoDB: Doing recovery: scanned up to log sequence number 23 1576215552 InnoDB: Doing recovery: scanned up to log sequence number 23 1581458432 InnoDB: Doing recovery: scanned up to log sequence number 23 1586701312 InnoDB: Doing recovery: scanned up to log sequence number 23 1591944192 InnoDB: Doing recovery: scanned up to log sequence number 23 1597187072 InnoDB: Doing recovery: scanned up to log sequence number 23 1602429952 InnoDB: Doing recovery: scanned up to log sequence number 23 1607672832 InnoDB: Doing recovery: scanned up to log sequence number 23 1608080477 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 290945024 071201 8:35:26 InnoDB: Starting an apply batch of log records to the database... 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 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 071201 8:36:55 InnoDB: Started; log sequence number 23 1608080477 InnoDB: Starting in background the rollback of uncommitted transactions 071201 8:36:55 InnoDB: Rolling back trx with id 0 290942327, 1 rows to undo InnoDB: Rolling back of trx id 0 290942327 completed 071201 8:36:55 InnoDB: Rollback of non-prepared transactions completed 071201 8:36:55 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071201 8:37:05 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071201 8:37:05 [Warning] Checking table: './tlbbdb/t_global' 071202 3:00:05 InnoDB: Error: cannot allocate 1064960 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029406 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071202 3:01:05 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=134217728 read_buffer_size=2093056 max_used_connections=47 max_connections=100 threads_connected=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1154671 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071202 03:01:05 mysqld restarted 071202 3:01:06 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... 071202 3:01:06 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 34 1317969943. InnoDB: Doing recovery: scanned up to log sequence number 34 1323212800 InnoDB: Doing recovery: scanned up to log sequence number 34 1328455680 InnoDB: Doing recovery: scanned up to log sequence number 34 1333698560 InnoDB: Doing recovery: scanned up to log sequence number 34 1338941440 InnoDB: Doing recovery: scanned up to log sequence number 34 1344184320 InnoDB: Doing recovery: scanned up to log sequence number 34 1349427200 InnoDB: Doing recovery: scanned up to log sequence number 34 1354670080 InnoDB: Doing recovery: scanned up to log sequence number 34 1359912960 InnoDB: Doing recovery: scanned up to log sequence number 34 1365155840 InnoDB: Doing recovery: scanned up to log sequence number 34 1370398720 InnoDB: Doing recovery: scanned up to log sequence number 34 1375641600 InnoDB: Doing recovery: scanned up to log sequence number 34 1380884480 InnoDB: Doing recovery: scanned up to log sequence number 34 1386127360 InnoDB: Doing recovery: scanned up to log sequence number 34 1391370240 InnoDB: Doing recovery: scanned up to log sequence number 34 1396613120 InnoDB: Doing recovery: scanned up to log sequence number 34 1401856000 InnoDB: Doing recovery: scanned up to log sequence number 34 1407098880 InnoDB: Doing recovery: scanned up to log sequence number 34 1412341760 InnoDB: Doing recovery: scanned up to log sequence number 34 1417584640 InnoDB: Doing recovery: scanned up to log sequence number 34 1422827520 InnoDB: Doing recovery: scanned up to log sequence number 34 1428070400 InnoDB: Doing recovery: scanned up to log sequence number 34 1433313280 InnoDB: Doing recovery: scanned up to log sequence number 34 1438556160 InnoDB: Doing recovery: scanned up to log sequence number 34 1443799040 InnoDB: Doing recovery: scanned up to log sequence number 34 1449041920 InnoDB: Doing recovery: scanned up to log sequence number 34 1454284800 InnoDB: Doing recovery: scanned up to log sequence number 34 1459527680 InnoDB: Doing recovery: scanned up to log sequence number 34 1464770560 InnoDB: Doing recovery: scanned up to log sequence number 34 1470013440 InnoDB: Doing recovery: scanned up to log sequence number 34 1475256320 InnoDB: Doing recovery: scanned up to log sequence number 34 1480499200 InnoDB: Doing recovery: scanned up to log sequence number 34 1485742080 InnoDB: Doing recovery: scanned up to log sequence number 34 1490984960 InnoDB: Doing recovery: scanned up to log sequence number 34 1496227840 InnoDB: Doing recovery: scanned up to log sequence number 34 1501470720 InnoDB: Doing recovery: scanned up to log sequence number 34 1506713600 InnoDB: Doing recovery: scanned up to log sequence number 34 1511956480 InnoDB: Doing recovery: scanned up to log sequence number 34 1517199360 InnoDB: Doing recovery: scanned up to log sequence number 34 1522442240 InnoDB: Doing recovery: scanned up to log sequence number 34 1527685120 InnoDB: Doing recovery: scanned up to log sequence number 34 1532928000 InnoDB: Doing recovery: scanned up to log sequence number 34 1538170880 InnoDB: Doing recovery: scanned up to log sequence number 34 1543413760 InnoDB: Doing recovery: scanned up to log sequence number 34 1548656640 InnoDB: Doing recovery: scanned up to log sequence number 34 1553899520 InnoDB: Doing recovery: scanned up to log sequence number 34 1559142400 InnoDB: Doing recovery: scanned up to log sequence number 34 1564385280 InnoDB: Doing recovery: scanned up to log sequence number 34 1569628160 InnoDB: Doing recovery: scanned up to log sequence number 34 1574871040 InnoDB: Doing recovery: scanned up to log sequence number 34 1580113920 InnoDB: Doing recovery: scanned up to log sequence number 34 1585356800 InnoDB: Doing recovery: scanned up to log sequence number 34 1590599680 InnoDB: Doing recovery: scanned up to log sequence number 34 1595842560 InnoDB: Doing recovery: scanned up to log sequence number 34 1601085440 InnoDB: Doing recovery: scanned up to log sequence number 34 1606328320 InnoDB: Doing recovery: scanned up to log sequence number 34 1611571200 InnoDB: Doing recovery: scanned up to log sequence number 34 1616814080 InnoDB: Doing recovery: scanned up to log sequence number 34 1622056960 InnoDB: Doing recovery: scanned up to log sequence number 34 1627299840 InnoDB: Doing recovery: scanned up to log sequence number 34 1632542720 InnoDB: Doing recovery: scanned up to log sequence number 34 1637785600 InnoDB: Doing recovery: scanned up to log sequence number 34 1643028480 InnoDB: Doing recovery: scanned up to log sequence number 34 1648271360 InnoDB: Doing recovery: scanned up to log sequence number 34 1653514240 InnoDB: Doing recovery: scanned up to log sequence number 34 1658757120 InnoDB: Doing recovery: scanned up to log sequence number 34 1664000000 InnoDB: Doing recovery: scanned up to log sequence number 34 1669242880 InnoDB: Doing recovery: scanned up to log sequence number 34 1674485760 InnoDB: Doing recovery: scanned up to log sequence number 34 1679728640 InnoDB: Doing recovery: scanned up to log sequence number 34 1684971520 InnoDB: Doing recovery: scanned up to log sequence number 34 1690214400 InnoDB: Doing recovery: scanned up to log sequence number 34 1695457280 InnoDB: Doing recovery: scanned up to log sequence number 34 1700700160 InnoDB: Doing recovery: scanned up to log sequence number 34 1705943040 InnoDB: Doing recovery: scanned up to log sequence number 34 1711185920 InnoDB: Doing recovery: scanned up to log sequence number 34 1716428800 InnoDB: Doing recovery: scanned up to log sequence number 34 1721671680 InnoDB: Doing recovery: scanned up to log sequence number 34 1726914560 InnoDB: Doing recovery: scanned up to log sequence number 34 1732157440 InnoDB: Doing recovery: scanned up to log sequence number 34 1737400320 InnoDB: Doing recovery: scanned up to log sequence number 34 1742643200 InnoDB: Doing recovery: scanned up to log sequence number 34 1747886080 InnoDB: Doing recovery: scanned up to log sequence number 34 1753128960 InnoDB: Doing recovery: scanned up to log sequence number 34 1758371840 InnoDB: Doing recovery: scanned up to log sequence number 34 1763614720 InnoDB: Doing recovery: scanned up to log sequence number 34 1768857600 InnoDB: Doing recovery: scanned up to log sequence number 34 1774100480 InnoDB: Doing recovery: scanned up to log sequence number 34 1779343360 InnoDB: Doing recovery: scanned up to log sequence number 34 1784586240 InnoDB: Doing recovery: scanned up to log sequence number 34 1789829120 InnoDB: Doing recovery: scanned up to log sequence number 34 1795072000 InnoDB: Doing recovery: scanned up to log sequence number 34 1800314880 InnoDB: Doing recovery: scanned up to log sequence number 34 1805557760 InnoDB: Doing recovery: scanned up to log sequence number 34 1810800640 InnoDB: Doing recovery: scanned up to log sequence number 34 1816043520 InnoDB: Doing recovery: scanned up to log sequence number 34 1821286400 InnoDB: Doing recovery: scanned up to log sequence number 34 1826529280 InnoDB: Doing recovery: scanned up to log sequence number 34 1831772160 InnoDB: Doing recovery: scanned up to log sequence number 34 1837015040 InnoDB: Doing recovery: scanned up to log sequence number 34 1842257920 InnoDB: Doing recovery: scanned up to log sequence number 34 1847500800 InnoDB: Doing recovery: scanned up to log sequence number 34 1852743680 InnoDB: Doing recovery: scanned up to log sequence number 34 1857986560 InnoDB: Doing recovery: scanned up to log sequence number 34 1863229440 InnoDB: Doing recovery: scanned up to log sequence number 34 1868472320 InnoDB: Doing recovery: scanned up to log sequence number 34 1873715200 InnoDB: Doing recovery: scanned up to log sequence number 34 1878958080 InnoDB: Doing recovery: scanned up to log sequence number 34 1884200960 InnoDB: Doing recovery: scanned up to log sequence number 34 1889443840 InnoDB: Doing recovery: scanned up to log sequence number 34 1894686720 InnoDB: Doing recovery: scanned up to log sequence number 34 1899929600 InnoDB: Doing recovery: scanned up to log sequence number 34 1905172480 InnoDB: Doing recovery: scanned up to log sequence number 34 1910415360 InnoDB: Doing recovery: scanned up to log sequence number 34 1915658240 InnoDB: Doing recovery: scanned up to log sequence number 34 1920901120 InnoDB: Doing recovery: scanned up to log sequence number 34 1926144000 InnoDB: Doing recovery: scanned up to log sequence number 34 1931386880 InnoDB: Doing recovery: scanned up to log sequence number 34 1936629760 InnoDB: Doing recovery: scanned up to log sequence number 34 1941872640 InnoDB: Doing recovery: scanned up to log sequence number 34 1947115520 InnoDB: Doing recovery: scanned up to log sequence number 34 1952358400 InnoDB: Doing recovery: scanned up to log sequence number 34 1957601280 InnoDB: Doing recovery: scanned up to log sequence number 34 1962844160 InnoDB: Doing recovery: scanned up to log sequence number 34 1968087040 InnoDB: Doing recovery: scanned up to log sequence number 34 1973329920 InnoDB: Doing recovery: scanned up to log sequence number 34 1978572800 InnoDB: Doing recovery: scanned up to log sequence number 34 1983815680 InnoDB: Doing recovery: scanned up to log sequence number 34 1989058560 InnoDB: Doing recovery: scanned up to log sequence number 34 1994301440 InnoDB: Doing recovery: scanned up to log sequence number 34 1999544320 InnoDB: Doing recovery: scanned up to log sequence number 34 2004787200 InnoDB: Doing recovery: scanned up to log sequence number 34 2010030080 InnoDB: Doing recovery: scanned up to log sequence number 34 2015272960 InnoDB: Doing recovery: scanned up to log sequence number 34 2020515840 InnoDB: Doing recovery: scanned up to log sequence number 34 2025758720 InnoDB: Doing recovery: scanned up to log sequence number 34 2031001600 InnoDB: Doing recovery: scanned up to log sequence number 34 2036244480 InnoDB: Doing recovery: scanned up to log sequence number 34 2041487360 InnoDB: Doing recovery: scanned up to log sequence number 34 2046730240 InnoDB: Doing recovery: scanned up to log sequence number 34 2051973120 InnoDB: Doing recovery: scanned up to log sequence number 34 2057216000 InnoDB: Doing recovery: scanned up to log sequence number 34 2062458880 InnoDB: Doing recovery: scanned up to log sequence number 34 2067701760 InnoDB: Doing recovery: scanned up to log sequence number 34 2072944640 InnoDB: Doing recovery: scanned up to log sequence number 34 2078187520 InnoDB: Doing recovery: scanned up to log sequence number 34 2083430400 InnoDB: Doing recovery: scanned up to log sequence number 34 2088673280 InnoDB: Doing recovery: scanned up to log sequence number 34 2093916160 InnoDB: Doing recovery: scanned up to log sequence number 34 2099159040 InnoDB: Doing recovery: scanned up to log sequence number 34 2104401920 InnoDB: Doing recovery: scanned up to log sequence number 34 2109644800 InnoDB: Doing recovery: scanned up to log sequence number 34 2114887680 InnoDB: Doing recovery: scanned up to log sequence number 34 2120130560 InnoDB: Doing recovery: scanned up to log sequence number 34 2125373440 InnoDB: Doing recovery: scanned up to log sequence number 34 2130616320 InnoDB: Doing recovery: scanned up to log sequence number 34 2135859200 071202 3:03:42 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 34 2141102080 InnoDB: Doing recovery: scanned up to log sequence number 34 2146344960 InnoDB: Doing recovery: scanned up to log sequence number 34 2151587840 InnoDB: Doing recovery: scanned up to log sequence number 34 2156830720 InnoDB: Doing recovery: scanned up to log sequence number 34 2162073600 InnoDB: Doing recovery: scanned up to log sequence number 34 2167316480 InnoDB: Doing recovery: scanned up to log sequence number 34 2172559360 InnoDB: Doing recovery: scanned up to log sequence number 34 2177802240 InnoDB: Doing recovery: scanned up to log sequence number 34 2183045120 InnoDB: Doing recovery: scanned up to log sequence number 34 2188288000 InnoDB: Doing recovery: scanned up to log sequence number 34 2193530880 InnoDB: Doing recovery: scanned up to log sequence number 34 2198773760 InnoDB: Doing recovery: scanned up to log sequence number 34 2204016640 InnoDB: Doing recovery: scanned up to log sequence number 34 2209259520 InnoDB: Doing recovery: scanned up to log sequence number 34 2210185515 071202 3:07:29 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071202 3:07:29 InnoDB: Starting an apply batch of log records to the database... 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 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 071202 3:09:00 InnoDB: Started; log sequence number 34 2210185515 071202 3:09:00 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071202 3:09:02 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071202 3:09:02 [Warning] Checking table: './tlbbdb/t_global' 071203 2:45:15 InnoDB: Error: cannot allocate 1064960 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071203 2:46:15 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=2093056 max_used_connections=47 max_connections=100 threads_connected=45 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 474736 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071203 02:46:15 mysqld restarted 071203 2:46:16 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... 071203 2:46:16 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 47 187931076. InnoDB: Doing recovery: scanned up to log sequence number 47 193173504 InnoDB: Doing recovery: scanned up to log sequence number 47 198416384 InnoDB: Doing recovery: scanned up to log sequence number 47 203659264 InnoDB: Doing recovery: scanned up to log sequence number 47 208902144 InnoDB: Doing recovery: scanned up to log sequence number 47 214145024 InnoDB: Doing recovery: scanned up to log sequence number 47 219387904 InnoDB: Doing recovery: scanned up to log sequence number 47 224630784 InnoDB: Doing recovery: scanned up to log sequence number 47 229873664 InnoDB: Doing recovery: scanned up to log sequence number 47 235116544 InnoDB: Doing recovery: scanned up to log sequence number 47 240359424 InnoDB: Doing recovery: scanned up to log sequence number 47 245602304 InnoDB: Doing recovery: scanned up to log sequence number 47 250845184 InnoDB: Doing recovery: scanned up to log sequence number 47 256088064 InnoDB: Doing recovery: scanned up to log sequence number 47 261330944 InnoDB: Doing recovery: scanned up to log sequence number 47 266573824 InnoDB: Doing recovery: scanned up to log sequence number 47 271816704 InnoDB: Doing recovery: scanned up to log sequence number 47 277059584 InnoDB: Doing recovery: scanned up to log sequence number 47 282302464 InnoDB: Doing recovery: scanned up to log sequence number 47 287545344 InnoDB: Doing recovery: scanned up to log sequence number 47 292788224 InnoDB: Doing recovery: scanned up to log sequence number 47 298031104 InnoDB: Doing recovery: scanned up to log sequence number 47 303273984 InnoDB: Doing recovery: scanned up to log sequence number 47 308516864 InnoDB: Doing recovery: scanned up to log sequence number 47 313759744 InnoDB: Doing recovery: scanned up to log sequence number 47 319002624 InnoDB: Doing recovery: scanned up to log sequence number 47 324245504 InnoDB: Doing recovery: scanned up to log sequence number 47 329488384 InnoDB: Doing recovery: scanned up to log sequence number 47 334731264 InnoDB: Doing recovery: scanned up to log sequence number 47 339974144 InnoDB: Doing recovery: scanned up to log sequence number 47 345217024 InnoDB: Doing recovery: scanned up to log sequence number 47 350459904 InnoDB: Doing recovery: scanned up to log sequence number 47 355702784 InnoDB: Doing recovery: scanned up to log sequence number 47 360945664 InnoDB: Doing recovery: scanned up to log sequence number 47 366188544 InnoDB: Doing recovery: scanned up to log sequence number 47 371431424 InnoDB: Doing recovery: scanned up to log sequence number 47 376674304 InnoDB: Doing recovery: scanned up to log sequence number 47 381917184 InnoDB: Doing recovery: scanned up to log sequence number 47 387160064 InnoDB: Doing recovery: scanned up to log sequence number 47 392402944 InnoDB: Doing recovery: scanned up to log sequence number 47 397645824 InnoDB: Doing recovery: scanned up to log sequence number 47 402888704 InnoDB: Doing recovery: scanned up to log sequence number 47 408131584 InnoDB: Doing recovery: scanned up to log sequence number 47 413374464 InnoDB: Doing recovery: scanned up to log sequence number 47 418617344 InnoDB: Doing recovery: scanned up to log sequence number 47 423860224 InnoDB: Doing recovery: scanned up to log sequence number 47 429103104 InnoDB: Doing recovery: scanned up to log sequence number 47 434345984 InnoDB: Doing recovery: scanned up to log sequence number 47 439588864 InnoDB: Doing recovery: scanned up to log sequence number 47 444831744 InnoDB: Doing recovery: scanned up to log sequence number 47 450074624 InnoDB: Doing recovery: scanned up to log sequence number 47 455317504 InnoDB: Doing recovery: scanned up to log sequence number 47 460560384 InnoDB: Doing recovery: scanned up to log sequence number 47 465803264 InnoDB: Doing recovery: scanned up to log sequence number 47 471046144 InnoDB: Doing recovery: scanned up to log sequence number 47 476289024 InnoDB: Doing recovery: scanned up to log sequence number 47 481531904 InnoDB: Doing recovery: scanned up to log sequence number 47 486774784 InnoDB: Doing recovery: scanned up to log sequence number 47 492017664 InnoDB: Doing recovery: scanned up to log sequence number 47 497260544 InnoDB: Doing recovery: scanned up to log sequence number 47 502503424 InnoDB: Doing recovery: scanned up to log sequence number 47 507746304 InnoDB: Doing recovery: scanned up to log sequence number 47 512989184 InnoDB: Doing recovery: scanned up to log sequence number 47 518232064 InnoDB: Doing recovery: scanned up to log sequence number 47 523474944 InnoDB: Doing recovery: scanned up to log sequence number 47 528717824 InnoDB: Doing recovery: scanned up to log sequence number 47 533960704 InnoDB: Doing recovery: scanned up to log sequence number 47 539203584 InnoDB: Doing recovery: scanned up to log sequence number 47 544446464 InnoDB: Doing recovery: scanned up to log sequence number 47 549689344 InnoDB: Doing recovery: scanned up to log sequence number 47 554932224 InnoDB: Doing recovery: scanned up to log sequence number 47 560175104 InnoDB: Doing recovery: scanned up to log sequence number 47 565417984 InnoDB: Doing recovery: scanned up to log sequence number 47 570660864 InnoDB: Doing recovery: scanned up to log sequence number 47 575903744 InnoDB: Doing recovery: scanned up to log sequence number 47 581146624 InnoDB: Doing recovery: scanned up to log sequence number 47 586389504 InnoDB: Doing recovery: scanned up to log sequence number 47 591632384 InnoDB: Doing recovery: scanned up to log sequence number 47 596875264 InnoDB: Doing recovery: scanned up to log sequence number 47 602118144 InnoDB: Doing recovery: scanned up to log sequence number 47 607361024 InnoDB: Doing recovery: scanned up to log sequence number 47 612603904 InnoDB: Doing recovery: scanned up to log sequence number 47 617846784 InnoDB: Doing recovery: scanned up to log sequence number 47 623089664 InnoDB: Doing recovery: scanned up to log sequence number 47 628332544 InnoDB: Doing recovery: scanned up to log sequence number 47 633575424 InnoDB: Doing recovery: scanned up to log sequence number 47 638818304 InnoDB: Doing recovery: scanned up to log sequence number 47 644061184 InnoDB: Doing recovery: scanned up to log sequence number 47 649304064 InnoDB: Doing recovery: scanned up to log sequence number 47 654546944 InnoDB: Doing recovery: scanned up to log sequence number 47 659789824 InnoDB: Doing recovery: scanned up to log sequence number 47 665032704 InnoDB: Doing recovery: scanned up to log sequence number 47 670275584 InnoDB: Doing recovery: scanned up to log sequence number 47 675518464 InnoDB: Doing recovery: scanned up to log sequence number 47 680761344 InnoDB: Doing recovery: scanned up to log sequence number 47 686004224 InnoDB: Doing recovery: scanned up to log sequence number 47 691247104 InnoDB: Doing recovery: scanned up to log sequence number 47 696489984 InnoDB: Doing recovery: scanned up to log sequence number 47 701732864 InnoDB: Doing recovery: scanned up to log sequence number 47 706975744 InnoDB: Doing recovery: scanned up to log sequence number 47 712218624 InnoDB: Doing recovery: scanned up to log sequence number 47 717461504 InnoDB: Doing recovery: scanned up to log sequence number 47 722704384 InnoDB: Doing recovery: scanned up to log sequence number 47 727947264 InnoDB: Doing recovery: scanned up to log sequence number 47 733190144 InnoDB: Doing recovery: scanned up to log sequence number 47 738433024 InnoDB: Doing recovery: scanned up to log sequence number 47 743675904 InnoDB: Doing recovery: scanned up to log sequence number 47 748918784 InnoDB: Doing recovery: scanned up to log sequence number 47 754161664 InnoDB: Doing recovery: scanned up to log sequence number 47 759404544 InnoDB: Doing recovery: scanned up to log sequence number 47 764647424 InnoDB: Doing recovery: scanned up to log sequence number 47 769890304 InnoDB: Doing recovery: scanned up to log sequence number 47 775133184 InnoDB: Doing recovery: scanned up to log sequence number 47 780376064 InnoDB: Doing recovery: scanned up to log sequence number 47 785618944 InnoDB: Doing recovery: scanned up to log sequence number 47 790861824 InnoDB: Doing recovery: scanned up to log sequence number 47 796104704 InnoDB: Doing recovery: scanned up to log sequence number 47 801347584 InnoDB: Doing recovery: scanned up to log sequence number 47 806590464 InnoDB: Doing recovery: scanned up to log sequence number 47 811833344 InnoDB: Doing recovery: scanned up to log sequence number 47 817076224 InnoDB: Doing recovery: scanned up to log sequence number 47 822319104 InnoDB: Doing recovery: scanned up to log sequence number 47 827561984 InnoDB: Doing recovery: scanned up to log sequence number 47 832804864 InnoDB: Doing recovery: scanned up to log sequence number 47 838047744 InnoDB: Doing recovery: scanned up to log sequence number 47 843290624 InnoDB: Doing recovery: scanned up to log sequence number 47 848533504 InnoDB: Doing recovery: scanned up to log sequence number 47 853776384 InnoDB: Doing recovery: scanned up to log sequence number 47 859019264 InnoDB: Doing recovery: scanned up to log sequence number 47 864262144 InnoDB: Doing recovery: scanned up to log sequence number 47 869505024 InnoDB: Doing recovery: scanned up to log sequence number 47 874747904 InnoDB: Doing recovery: scanned up to log sequence number 47 879990784 InnoDB: Doing recovery: scanned up to log sequence number 47 885233664 InnoDB: Doing recovery: scanned up to log sequence number 47 890476544 InnoDB: Doing recovery: scanned up to log sequence number 47 895719424 InnoDB: Doing recovery: scanned up to log sequence number 47 900962304 InnoDB: Doing recovery: scanned up to log sequence number 47 906205184 InnoDB: Doing recovery: scanned up to log sequence number 47 911448064 InnoDB: Doing recovery: scanned up to log sequence number 47 916690944 InnoDB: Doing recovery: scanned up to log sequence number 47 921933824 InnoDB: Doing recovery: scanned up to log sequence number 47 927176704 InnoDB: Doing recovery: scanned up to log sequence number 47 932419584 InnoDB: Doing recovery: scanned up to log sequence number 47 937662464 InnoDB: Doing recovery: scanned up to log sequence number 47 942905344 InnoDB: Doing recovery: scanned up to log sequence number 47 948148224 InnoDB: Doing recovery: scanned up to log sequence number 47 953391104 InnoDB: Doing recovery: scanned up to log sequence number 47 958633984 InnoDB: Doing recovery: scanned up to log sequence number 47 963876864 InnoDB: Doing recovery: scanned up to log sequence number 47 969119744 InnoDB: Doing recovery: scanned up to log sequence number 47 974362624 InnoDB: Doing recovery: scanned up to log sequence number 47 979605504 InnoDB: Doing recovery: scanned up to log sequence number 47 984848384 InnoDB: Doing recovery: scanned up to log sequence number 47 990091264 InnoDB: Doing recovery: scanned up to log sequence number 47 995334144 InnoDB: Doing recovery: scanned up to log sequence number 47 1000577024 InnoDB: Doing recovery: scanned up to log sequence number 47 1005819904 InnoDB: Doing recovery: scanned up to log sequence number 47 1011062784 071203 2:48:52 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 47 1016305664 InnoDB: Doing recovery: scanned up to log sequence number 47 1021548544 InnoDB: Doing recovery: scanned up to log sequence number 47 1026791424 InnoDB: Doing recovery: scanned up to log sequence number 47 1032034304 InnoDB: Doing recovery: scanned up to log sequence number 47 1037277184 InnoDB: Doing recovery: scanned up to log sequence number 47 1042520064 InnoDB: Doing recovery: scanned up to log sequence number 47 1047762944 InnoDB: Doing recovery: scanned up to log sequence number 47 1053005824 InnoDB: Doing recovery: scanned up to log sequence number 47 1058248704 InnoDB: Doing recovery: scanned up to log sequence number 47 1063491584 InnoDB: Doing recovery: scanned up to log sequence number 47 1068734464 InnoDB: Doing recovery: scanned up to log sequence number 47 1073977344 InnoDB: Doing recovery: scanned up to log sequence number 47 1079220224 InnoDB: Doing recovery: scanned up to log sequence number 47 1083682843 InnoDB: 2 transaction(s) which must be rolled back or cleaned up InnoDB: in total 104 row operations to undo InnoDB: Trx id counter is 0 599686144 071203 2:51:55 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071203 2:51:55 InnoDB: Starting an apply batch of log records to the database... 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 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 071203 2:53:28 InnoDB: Started; log sequence number 47 1083682843 InnoDB: Starting in background the rollback of uncommitted transactions 071203 2:53:28 InnoDB: Rolling back trx with id 0 599684314, 54 rows to undo InnoDB: Rolling back of trx id 0 599684314 completed 071203 2:53:28 InnoDB: Rolling back trx with id 0 599678017, 50 rows to undo InnoDB: Rolling back of trx id 0 599678017 completed 071203 2:53:28 InnoDB: Rollback of non-prepared transactions completed 071203 2:53:28 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071203 2:53:30 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071203 2:53:30 [Warning] Checking table: './tlbbdb/t_global' 071204 11:21:52 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 071204 11:21:53 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 071204 11:22:08 InnoDB: Error: cannot allocate 458752 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071204 11:23:09 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1048576 max_used_connections=47 max_connections=100 threads_connected=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 270336 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071204 11:23:09 mysqld restarted 071204 11:23:09 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... 071204 11:23:09 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 59 2726527338. InnoDB: Doing recovery: scanned up to log sequence number 59 2731769856 InnoDB: Doing recovery: scanned up to log sequence number 59 2737012736 InnoDB: Doing recovery: scanned up to log sequence number 59 2742255616 InnoDB: Doing recovery: scanned up to log sequence number 59 2747498496 InnoDB: Doing recovery: scanned up to log sequence number 59 2752741376 InnoDB: Doing recovery: scanned up to log sequence number 59 2757984256 InnoDB: Doing recovery: scanned up to log sequence number 59 2763227136 InnoDB: Doing recovery: scanned up to log sequence number 59 2768470016 InnoDB: Doing recovery: scanned up to log sequence number 59 2773712896 InnoDB: Doing recovery: scanned up to log sequence number 59 2778955776 InnoDB: Doing recovery: scanned up to log sequence number 59 2784198656 InnoDB: Doing recovery: scanned up to log sequence number 59 2789441536 InnoDB: Doing recovery: scanned up to log sequence number 59 2794684416 InnoDB: Doing recovery: scanned up to log sequence number 59 2799927296 InnoDB: Doing recovery: scanned up to log sequence number 59 2805170176 InnoDB: Doing recovery: scanned up to log sequence number 59 2810413056 InnoDB: Doing recovery: scanned up to log sequence number 59 2815655936 InnoDB: Doing recovery: scanned up to log sequence number 59 2820898816 InnoDB: Doing recovery: scanned up to log sequence number 59 2826141696 InnoDB: Doing recovery: scanned up to log sequence number 59 2831384576 InnoDB: Doing recovery: scanned up to log sequence number 59 2836627456 InnoDB: Doing recovery: scanned up to log sequence number 59 2841870336 InnoDB: Doing recovery: scanned up to log sequence number 59 2847113216 InnoDB: Doing recovery: scanned up to log sequence number 59 2852356096 InnoDB: Doing recovery: scanned up to log sequence number 59 2857598976 InnoDB: Doing recovery: scanned up to log sequence number 59 2862841856 InnoDB: Doing recovery: scanned up to log sequence number 59 2868084736 InnoDB: Doing recovery: scanned up to log sequence number 59 2873327616 InnoDB: Doing recovery: scanned up to log sequence number 59 2878570496 InnoDB: Doing recovery: scanned up to log sequence number 59 2883813376 InnoDB: Doing recovery: scanned up to log sequence number 59 2889056256 InnoDB: Doing recovery: scanned up to log sequence number 59 2894299136 InnoDB: Doing recovery: scanned up to log sequence number 59 2899542016 InnoDB: Doing recovery: scanned up to log sequence number 59 2904784896 InnoDB: Doing recovery: scanned up to log sequence number 59 2910027776 InnoDB: Doing recovery: scanned up to log sequence number 59 2915270656 InnoDB: Doing recovery: scanned up to log sequence number 59 2920513536 InnoDB: Doing recovery: scanned up to log sequence number 59 2925756416 InnoDB: Doing recovery: scanned up to log sequence number 59 2930999296 InnoDB: Doing recovery: scanned up to log sequence number 59 2936242176 InnoDB: Doing recovery: scanned up to log sequence number 59 2941485056 InnoDB: Doing recovery: scanned up to log sequence number 59 2946727936 InnoDB: Doing recovery: scanned up to log sequence number 59 2951970816 InnoDB: Doing recovery: scanned up to log sequence number 59 2957213696 InnoDB: Doing recovery: scanned up to log sequence number 59 2962456576 InnoDB: Doing recovery: scanned up to log sequence number 59 2967699456 InnoDB: Doing recovery: scanned up to log sequence number 59 2972942336 InnoDB: Doing recovery: scanned up to log sequence number 59 2978185216 InnoDB: Doing recovery: scanned up to log sequence number 59 2983428096 InnoDB: Doing recovery: scanned up to log sequence number 59 2988670976 InnoDB: Doing recovery: scanned up to log sequence number 59 2993913856 InnoDB: Doing recovery: scanned up to log sequence number 59 2999156736 InnoDB: Doing recovery: scanned up to log sequence number 59 3004399616 InnoDB: Doing recovery: scanned up to log sequence number 59 3009642496 InnoDB: Doing recovery: scanned up to log sequence number 59 3014885376 InnoDB: Doing recovery: scanned up to log sequence number 59 3020128256 InnoDB: Doing recovery: scanned up to log sequence number 59 3025371136 InnoDB: Doing recovery: scanned up to log sequence number 59 3030614016 InnoDB: Doing recovery: scanned up to log sequence number 59 3035856896 InnoDB: Doing recovery: scanned up to log sequence number 59 3041099776 InnoDB: Doing recovery: scanned up to log sequence number 59 3046342656 InnoDB: Doing recovery: scanned up to log sequence number 59 3051585536 InnoDB: Doing recovery: scanned up to log sequence number 59 3056828416 InnoDB: Doing recovery: scanned up to log sequence number 59 3062071296 InnoDB: Doing recovery: scanned up to log sequence number 59 3067314176 InnoDB: Doing recovery: scanned up to log sequence number 59 3072557056 InnoDB: Doing recovery: scanned up to log sequence number 59 3077799936 InnoDB: Doing recovery: scanned up to log sequence number 59 3083042816 InnoDB: Doing recovery: scanned up to log sequence number 59 3088285696 InnoDB: Doing recovery: scanned up to log sequence number 59 3093528576 InnoDB: Doing recovery: scanned up to log sequence number 59 3098771456 InnoDB: Doing recovery: scanned up to log sequence number 59 3104014336 InnoDB: Doing recovery: scanned up to log sequence number 59 3109257216 InnoDB: Doing recovery: scanned up to log sequence number 59 3114500096 InnoDB: Doing recovery: scanned up to log sequence number 59 3119742976 InnoDB: Doing recovery: scanned up to log sequence number 59 3124985856 InnoDB: Doing recovery: scanned up to log sequence number 59 3130228736 InnoDB: Doing recovery: scanned up to log sequence number 59 3135471616 InnoDB: Doing recovery: scanned up to log sequence number 59 3140714496 InnoDB: Doing recovery: scanned up to log sequence number 59 3145957376 InnoDB: Doing recovery: scanned up to log sequence number 59 3151200256 InnoDB: Doing recovery: scanned up to log sequence number 59 3156443136 InnoDB: Doing recovery: scanned up to log sequence number 59 3161686016 InnoDB: Doing recovery: scanned up to log sequence number 59 3166928896 InnoDB: Doing recovery: scanned up to log sequence number 59 3172171776 InnoDB: Doing recovery: scanned up to log sequence number 59 3177414656 InnoDB: Doing recovery: scanned up to log sequence number 59 3182657536 InnoDB: Doing recovery: scanned up to log sequence number 59 3187900416 InnoDB: Doing recovery: scanned up to log sequence number 59 3193143296 InnoDB: Doing recovery: scanned up to log sequence number 59 3198386176 InnoDB: Doing recovery: scanned up to log sequence number 59 3203629056 InnoDB: Doing recovery: scanned up to log sequence number 59 3208871936 InnoDB: Doing recovery: scanned up to log sequence number 59 3214114816 InnoDB: Doing recovery: scanned up to log sequence number 59 3219357696 InnoDB: Doing recovery: scanned up to log sequence number 59 3224600576 InnoDB: Doing recovery: scanned up to log sequence number 59 3229843456 InnoDB: Doing recovery: scanned up to log sequence number 59 3235086336 InnoDB: Doing recovery: scanned up to log sequence number 59 3240329216 InnoDB: Doing recovery: scanned up to log sequence number 59 3245572096 InnoDB: Doing recovery: scanned up to log sequence number 59 3250814976 InnoDB: Doing recovery: scanned up to log sequence number 59 3256057856 InnoDB: Doing recovery: scanned up to log sequence number 59 3261300736 InnoDB: Doing recovery: scanned up to log sequence number 59 3266543616 InnoDB: Doing recovery: scanned up to log sequence number 59 3271786496 InnoDB: Doing recovery: scanned up to log sequence number 59 3277029376 InnoDB: Doing recovery: scanned up to log sequence number 59 3282272256 InnoDB: Doing recovery: scanned up to log sequence number 59 3287515136 InnoDB: Doing recovery: scanned up to log sequence number 59 3292758016 InnoDB: Doing recovery: scanned up to log sequence number 59 3298000896 InnoDB: Doing recovery: scanned up to log sequence number 59 3303243776 InnoDB: Doing recovery: scanned up to log sequence number 59 3308486656 InnoDB: Doing recovery: scanned up to log sequence number 59 3313729536 InnoDB: Doing recovery: scanned up to log sequence number 59 3318972416 InnoDB: Doing recovery: scanned up to log sequence number 59 3324215296 InnoDB: Doing recovery: scanned up to log sequence number 59 3329458176 InnoDB: Doing recovery: scanned up to log sequence number 59 3334701056 InnoDB: Doing recovery: scanned up to log sequence number 59 3339943936 InnoDB: Doing recovery: scanned up to log sequence number 59 3345186816 InnoDB: Doing recovery: scanned up to log sequence number 59 3350429696 InnoDB: Doing recovery: scanned up to log sequence number 59 3355672576 InnoDB: Doing recovery: scanned up to log sequence number 59 3360915456 InnoDB: Doing recovery: scanned up to log sequence number 59 3366158336 InnoDB: Doing recovery: scanned up to log sequence number 59 3371401216 InnoDB: Doing recovery: scanned up to log sequence number 59 3376644096 InnoDB: Doing recovery: scanned up to log sequence number 59 3381886976 InnoDB: Doing recovery: scanned up to log sequence number 59 3387129856 InnoDB: Doing recovery: scanned up to log sequence number 59 3392372736 InnoDB: Doing recovery: scanned up to log sequence number 59 3397615616 InnoDB: Doing recovery: scanned up to log sequence number 59 3402858496 InnoDB: Doing recovery: scanned up to log sequence number 59 3408101376 InnoDB: Doing recovery: scanned up to log sequence number 59 3413344256 InnoDB: Doing recovery: scanned up to log sequence number 59 3418587136 InnoDB: Doing recovery: scanned up to log sequence number 59 3423830016 InnoDB: Doing recovery: scanned up to log sequence number 59 3429072896 InnoDB: Doing recovery: scanned up to log sequence number 59 3434315776 InnoDB: Doing recovery: scanned up to log sequence number 59 3439558656 InnoDB: Doing recovery: scanned up to log sequence number 59 3444801536 InnoDB: Doing recovery: scanned up to log sequence number 59 3450044416 InnoDB: Doing recovery: scanned up to log sequence number 59 3455287296 InnoDB: Doing recovery: scanned up to log sequence number 59 3460530176 InnoDB: Doing recovery: scanned up to log sequence number 59 3465773056 InnoDB: Doing recovery: scanned up to log sequence number 59 3471015936 InnoDB: Doing recovery: scanned up to log sequence number 59 3476258816 InnoDB: Doing recovery: scanned up to log sequence number 59 3481501696 InnoDB: Doing recovery: scanned up to log sequence number 59 3486744576 InnoDB: Doing recovery: scanned up to log sequence number 59 3491987456 InnoDB: Doing recovery: scanned up to log sequence number 59 3497230336 InnoDB: Doing recovery: scanned up to log sequence number 59 3502473216 InnoDB: Doing recovery: scanned up to log sequence number 59 3507716096 InnoDB: Doing recovery: scanned up to log sequence number 59 3512958976 InnoDB: Doing recovery: scanned up to log sequence number 59 3518201856 InnoDB: Doing recovery: scanned up to log sequence number 59 3523444736 InnoDB: Doing recovery: scanned up to log sequence number 59 3528687616 InnoDB: Doing recovery: scanned up to log sequence number 59 3533930496 InnoDB: Doing recovery: scanned up to log sequence number 59 3539173376 071204 11:25:44 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 59 3544416256 InnoDB: Doing recovery: scanned up to log sequence number 59 3549659136 InnoDB: Doing recovery: scanned up to log sequence number 59 3554902016 InnoDB: Doing recovery: scanned up to log sequence number 59 3560144896 InnoDB: Doing recovery: scanned up to log sequence number 59 3565387776 InnoDB: Doing recovery: scanned up to log sequence number 59 3570630656 InnoDB: Doing recovery: scanned up to log sequence number 59 3575873536 InnoDB: Doing recovery: scanned up to log sequence number 59 3581116416 InnoDB: Doing recovery: scanned up to log sequence number 59 3586359296 InnoDB: Doing recovery: scanned up to log sequence number 59 3591602176 InnoDB: Doing recovery: scanned up to log sequence number 59 3596845056 InnoDB: Doing recovery: scanned up to log sequence number 59 3602087936 InnoDB: Doing recovery: scanned up to log sequence number 59 3607330816 InnoDB: Doing recovery: scanned up to log sequence number 59 3612573696 InnoDB: Doing recovery: scanned up to log sequence number 59 3617402964 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 763197440 071204 11:29:25 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071204 11:29:25 InnoDB: Starting an apply batch of log records to the database... 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 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 071204 11:31:00 InnoDB: Started; log sequence number 59 3617402964 InnoDB: Starting in background the rollback of uncommitted transactions 071204 11:31:00 InnoDB: Rolling back trx with id 0 763191836, 1 rows to undo InnoDB: Rolling back of trx id 0 763191836 completed 071204 11:31:00 InnoDB: Rollback of non-prepared transactions completed 071204 11:31:00 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071204 11:31:05 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071204 11:31:05 [Warning] Checking table: './tlbbdb/t_global' 071205 15:13:29 InnoDB: Error: cannot allocate 786432 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071205 15:14:29 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=48 max_connections=100 threads_connected=13 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071205 15:14:29 mysqld restarted 071205 15:14:30 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... 071205 15:14:30 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 72 1522697178. InnoDB: Doing recovery: scanned up to log sequence number 72 1527939584 InnoDB: Doing recovery: scanned up to log sequence number 72 1533182464 InnoDB: Doing recovery: scanned up to log sequence number 72 1538425344 InnoDB: Doing recovery: scanned up to log sequence number 72 1543668224 InnoDB: Doing recovery: scanned up to log sequence number 72 1548911104 InnoDB: Doing recovery: scanned up to log sequence number 72 1554153984 InnoDB: Doing recovery: scanned up to log sequence number 72 1559396864 InnoDB: Doing recovery: scanned up to log sequence number 72 1564639744 InnoDB: Doing recovery: scanned up to log sequence number 72 1569882624 InnoDB: Doing recovery: scanned up to log sequence number 72 1575125504 InnoDB: Doing recovery: scanned up to log sequence number 72 1580368384 InnoDB: Doing recovery: scanned up to log sequence number 72 1585611264 InnoDB: Doing recovery: scanned up to log sequence number 72 1590854144 InnoDB: Doing recovery: scanned up to log sequence number 72 1596097024 InnoDB: Doing recovery: scanned up to log sequence number 72 1601339904 InnoDB: Doing recovery: scanned up to log sequence number 72 1606582784 InnoDB: Doing recovery: scanned up to log sequence number 72 1611825664 InnoDB: Doing recovery: scanned up to log sequence number 72 1617068544 InnoDB: Doing recovery: scanned up to log sequence number 72 1622311424 InnoDB: Doing recovery: scanned up to log sequence number 72 1627554304 InnoDB: Doing recovery: scanned up to log sequence number 72 1632797184 InnoDB: Doing recovery: scanned up to log sequence number 72 1638040064 InnoDB: Doing recovery: scanned up to log sequence number 72 1643282944 InnoDB: Doing recovery: scanned up to log sequence number 72 1648525824 InnoDB: Doing recovery: scanned up to log sequence number 72 1653768704 InnoDB: Doing recovery: scanned up to log sequence number 72 1659011584 InnoDB: Doing recovery: scanned up to log sequence number 72 1664254464 InnoDB: Doing recovery: scanned up to log sequence number 72 1669497344 InnoDB: Doing recovery: scanned up to log sequence number 72 1674740224 InnoDB: Doing recovery: scanned up to log sequence number 72 1679983104 InnoDB: Doing recovery: scanned up to log sequence number 72 1685225984 InnoDB: Doing recovery: scanned up to log sequence number 72 1690468864 InnoDB: Doing recovery: scanned up to log sequence number 72 1695711744 InnoDB: Doing recovery: scanned up to log sequence number 72 1700954624 InnoDB: Doing recovery: scanned up to log sequence number 72 1706197504 InnoDB: Doing recovery: scanned up to log sequence number 72 1711440384 InnoDB: Doing recovery: scanned up to log sequence number 72 1716683264 InnoDB: Doing recovery: scanned up to log sequence number 72 1721926144 InnoDB: Doing recovery: scanned up to log sequence number 72 1727169024 InnoDB: Doing recovery: scanned up to log sequence number 72 1732411904 InnoDB: Doing recovery: scanned up to log sequence number 72 1737654784 InnoDB: Doing recovery: scanned up to log sequence number 72 1742897664 InnoDB: Doing recovery: scanned up to log sequence number 72 1748140544 InnoDB: Doing recovery: scanned up to log sequence number 72 1753383424 InnoDB: Doing recovery: scanned up to log sequence number 72 1758626304 InnoDB: Doing recovery: scanned up to log sequence number 72 1763869184 InnoDB: Doing recovery: scanned up to log sequence number 72 1769112064 InnoDB: Doing recovery: scanned up to log sequence number 72 1774354944 InnoDB: Doing recovery: scanned up to log sequence number 72 1779597824 InnoDB: Doing recovery: scanned up to log sequence number 72 1784840704 InnoDB: Doing recovery: scanned up to log sequence number 72 1790083584 InnoDB: Doing recovery: scanned up to log sequence number 72 1795326464 InnoDB: Doing recovery: scanned up to log sequence number 72 1800569344 InnoDB: Doing recovery: scanned up to log sequence number 72 1805812224 InnoDB: Doing recovery: scanned up to log sequence number 72 1811055104 InnoDB: Doing recovery: scanned up to log sequence number 72 1816297984 InnoDB: Doing recovery: scanned up to log sequence number 72 1821540864 InnoDB: Doing recovery: scanned up to log sequence number 72 1826783744 InnoDB: Doing recovery: scanned up to log sequence number 72 1832026624 InnoDB: Doing recovery: scanned up to log sequence number 72 1837269504 InnoDB: Doing recovery: scanned up to log sequence number 72 1842512384 InnoDB: Doing recovery: scanned up to log sequence number 72 1847755264 InnoDB: Doing recovery: scanned up to log sequence number 72 1852998144 InnoDB: Doing recovery: scanned up to log sequence number 72 1858241024 InnoDB: Doing recovery: scanned up to log sequence number 72 1863483904 InnoDB: Doing recovery: scanned up to log sequence number 72 1868726784 InnoDB: Doing recovery: scanned up to log sequence number 72 1873969664 InnoDB: Doing recovery: scanned up to log sequence number 72 1879212544 InnoDB: Doing recovery: scanned up to log sequence number 72 1884455424 InnoDB: Doing recovery: scanned up to log sequence number 72 1889698304 InnoDB: Doing recovery: scanned up to log sequence number 72 1894941184 InnoDB: Doing recovery: scanned up to log sequence number 72 1900184064 InnoDB: Doing recovery: scanned up to log sequence number 72 1905426944 InnoDB: Doing recovery: scanned up to log sequence number 72 1910669824 InnoDB: Doing recovery: scanned up to log sequence number 72 1915912704 InnoDB: Doing recovery: scanned up to log sequence number 72 1921155584 InnoDB: Doing recovery: scanned up to log sequence number 72 1926398464 InnoDB: Doing recovery: scanned up to log sequence number 72 1931641344 InnoDB: Doing recovery: scanned up to log sequence number 72 1936884224 InnoDB: Doing recovery: scanned up to log sequence number 72 1942127104 InnoDB: Doing recovery: scanned up to log sequence number 72 1947369984 InnoDB: Doing recovery: scanned up to log sequence number 72 1952612864 InnoDB: Doing recovery: scanned up to log sequence number 72 1957855744 InnoDB: Doing recovery: scanned up to log sequence number 72 1963098624 InnoDB: Doing recovery: scanned up to log sequence number 72 1968341504 InnoDB: Doing recovery: scanned up to log sequence number 72 1973584384 InnoDB: Doing recovery: scanned up to log sequence number 72 1978827264 InnoDB: Doing recovery: scanned up to log sequence number 72 1984070144 InnoDB: Doing recovery: scanned up to log sequence number 72 1989313024 InnoDB: Doing recovery: scanned up to log sequence number 72 1994555904 InnoDB: Doing recovery: scanned up to log sequence number 72 1999798784 InnoDB: Doing recovery: scanned up to log sequence number 72 2005041664 InnoDB: Doing recovery: scanned up to log sequence number 72 2010284544 InnoDB: Doing recovery: scanned up to log sequence number 72 2015527424 InnoDB: Doing recovery: scanned up to log sequence number 72 2020770304 InnoDB: Doing recovery: scanned up to log sequence number 72 2026013184 InnoDB: Doing recovery: scanned up to log sequence number 72 2031256064 InnoDB: Doing recovery: scanned up to log sequence number 72 2036498944 InnoDB: Doing recovery: scanned up to log sequence number 72 2041741824 InnoDB: Doing recovery: scanned up to log sequence number 72 2046984704 InnoDB: Doing recovery: scanned up to log sequence number 72 2052227584 InnoDB: Doing recovery: scanned up to log sequence number 72 2057470464 InnoDB: Doing recovery: scanned up to log sequence number 72 2062713344 InnoDB: Doing recovery: scanned up to log sequence number 72 2067956224 InnoDB: Doing recovery: scanned up to log sequence number 72 2073199104 InnoDB: Doing recovery: scanned up to log sequence number 72 2078441984 InnoDB: Doing recovery: scanned up to log sequence number 72 2083684864 InnoDB: Doing recovery: scanned up to log sequence number 72 2088927744 InnoDB: Doing recovery: scanned up to log sequence number 72 2094170624 InnoDB: Doing recovery: scanned up to log sequence number 72 2099413504 InnoDB: Doing recovery: scanned up to log sequence number 72 2104656384 InnoDB: Doing recovery: scanned up to log sequence number 72 2109899264 InnoDB: Doing recovery: scanned up to log sequence number 72 2115142144 InnoDB: Doing recovery: scanned up to log sequence number 72 2120385024 InnoDB: Doing recovery: scanned up to log sequence number 72 2125627904 InnoDB: Doing recovery: scanned up to log sequence number 72 2130870784 InnoDB: Doing recovery: scanned up to log sequence number 72 2136113664 InnoDB: Doing recovery: scanned up to log sequence number 72 2141356544 InnoDB: Doing recovery: scanned up to log sequence number 72 2146599424 InnoDB: Doing recovery: scanned up to log sequence number 72 2151842304 InnoDB: Doing recovery: scanned up to log sequence number 72 2157085184 InnoDB: Doing recovery: scanned up to log sequence number 72 2162328064 InnoDB: Doing recovery: scanned up to log sequence number 72 2167570944 InnoDB: Doing recovery: scanned up to log sequence number 72 2172813824 InnoDB: Doing recovery: scanned up to log sequence number 72 2178056704 InnoDB: Doing recovery: scanned up to log sequence number 72 2183299584 InnoDB: Doing recovery: scanned up to log sequence number 72 2188542464 InnoDB: Doing recovery: scanned up to log sequence number 72 2193785344 InnoDB: Doing recovery: scanned up to log sequence number 72 2199028224 InnoDB: Doing recovery: scanned up to log sequence number 72 2204271104 InnoDB: Doing recovery: scanned up to log sequence number 72 2209513984 InnoDB: Doing recovery: scanned up to log sequence number 72 2214756864 InnoDB: Doing recovery: scanned up to log sequence number 72 2219999744 InnoDB: Doing recovery: scanned up to log sequence number 72 2225242624 InnoDB: Doing recovery: scanned up to log sequence number 72 2230485504 InnoDB: Doing recovery: scanned up to log sequence number 72 2235728384 InnoDB: Doing recovery: scanned up to log sequence number 72 2240971264 InnoDB: Doing recovery: scanned up to log sequence number 72 2246214144 InnoDB: Doing recovery: scanned up to log sequence number 72 2251457024 InnoDB: Doing recovery: scanned up to log sequence number 72 2256699904 InnoDB: Doing recovery: scanned up to log sequence number 72 2261942784 InnoDB: Doing recovery: scanned up to log sequence number 72 2267185664 InnoDB: Doing recovery: scanned up to log sequence number 72 2272428544 InnoDB: Doing recovery: scanned up to log sequence number 72 2277671424 InnoDB: Doing recovery: scanned up to log sequence number 72 2282914304 InnoDB: Doing recovery: scanned up to log sequence number 72 2288157184 InnoDB: Doing recovery: scanned up to log sequence number 72 2293400064 InnoDB: Doing recovery: scanned up to log sequence number 72 2298642944 InnoDB: Doing recovery: scanned up to log sequence number 72 2303885824 InnoDB: Doing recovery: scanned up to log sequence number 72 2309128704 InnoDB: Doing recovery: scanned up to log sequence number 72 2314371584 InnoDB: Doing recovery: scanned up to log sequence number 72 2319614464 InnoDB: Doing recovery: scanned up to log sequence number 72 2324857344 InnoDB: Doing recovery: scanned up to log sequence number 72 2330100224 InnoDB: Doing recovery: scanned up to log sequence number 72 2335343104 InnoDB: Doing recovery: scanned up to log sequence number 72 2340585984 071205 15:17:07 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 72 2345828864 InnoDB: Doing recovery: scanned up to log sequence number 72 2351071744 InnoDB: Doing recovery: scanned up to log sequence number 72 2356314624 InnoDB: Doing recovery: scanned up to log sequence number 72 2361557504 InnoDB: Doing recovery: scanned up to log sequence number 72 2366800384 InnoDB: Doing recovery: scanned up to log sequence number 72 2372043264 InnoDB: Doing recovery: scanned up to log sequence number 72 2377286144 InnoDB: Doing recovery: scanned up to log sequence number 72 2382529024 InnoDB: Doing recovery: scanned up to log sequence number 72 2387771904 InnoDB: Doing recovery: scanned up to log sequence number 72 2393014784 InnoDB: Doing recovery: scanned up to log sequence number 72 2398257664 InnoDB: Doing recovery: scanned up to log sequence number 72 2403500544 InnoDB: Doing recovery: scanned up to log sequence number 72 2408743424 InnoDB: Doing recovery: scanned up to log sequence number 72 2413986304 InnoDB: Doing recovery: scanned up to log sequence number 72 2418823224 InnoDB: 2 transaction(s) which must be rolled back or cleaned up InnoDB: in total 121 row operations to undo InnoDB: Trx id counter is 0 928349184 071205 15:20:45 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071205 15:20:45 InnoDB: Starting an apply batch of log records to the database... 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 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: Starting in background the rollback of uncommitted transactions 071205 15:22:31 InnoDB: Rolling back trx with id 0 928346358, 37 rows to undo 071205 15:22:31 InnoDB: Started; log sequence number 72 2418823224 InnoDB: Rolling back of trx id 0 928346358 completed 071205 15:22:31 InnoDB: Rolling back trx with id 0 928345265, 84 rows to undo 071205 15:22:31 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) InnoDB: Rolling back of trx id 0 928345265 completed 071205 15:22:31 InnoDB: Rollback of non-prepared transactions completed 071205 15:22:39 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071205 15:22:39 [Warning] Checking table: './tlbbdb/t_global' 071206 20:04:59 InnoDB: Error: cannot allocate 704512 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071206 20:05:59 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=47 max_connections=100 threads_connected=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071206 20:05:59 mysqld restarted 071206 20:06:00 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... 071206 20:06:00 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 85 1242638467. InnoDB: Doing recovery: scanned up to log sequence number 85 1247881216 InnoDB: Doing recovery: scanned up to log sequence number 85 1253124096 InnoDB: Doing recovery: scanned up to log sequence number 85 1258366976 InnoDB: Doing recovery: scanned up to log sequence number 85 1263609856 InnoDB: Doing recovery: scanned up to log sequence number 85 1268852736 InnoDB: Doing recovery: scanned up to log sequence number 85 1274095616 InnoDB: Doing recovery: scanned up to log sequence number 85 1279338496 InnoDB: Doing recovery: scanned up to log sequence number 85 1284581376 InnoDB: Doing recovery: scanned up to log sequence number 85 1289824256 InnoDB: Doing recovery: scanned up to log sequence number 85 1295067136 InnoDB: Doing recovery: scanned up to log sequence number 85 1300310016 InnoDB: Doing recovery: scanned up to log sequence number 85 1305552896 InnoDB: Doing recovery: scanned up to log sequence number 85 1310795776 InnoDB: Doing recovery: scanned up to log sequence number 85 1316038656 InnoDB: Doing recovery: scanned up to log sequence number 85 1321281536 InnoDB: Doing recovery: scanned up to log sequence number 85 1326524416 InnoDB: Doing recovery: scanned up to log sequence number 85 1331767296 InnoDB: Doing recovery: scanned up to log sequence number 85 1337010176 InnoDB: Doing recovery: scanned up to log sequence number 85 1342253056 InnoDB: Doing recovery: scanned up to log sequence number 85 1347495936 InnoDB: Doing recovery: scanned up to log sequence number 85 1352738816 InnoDB: Doing recovery: scanned up to log sequence number 85 1357981696 InnoDB: Doing recovery: scanned up to log sequence number 85 1363224576 InnoDB: Doing recovery: scanned up to log sequence number 85 1368467456 InnoDB: Doing recovery: scanned up to log sequence number 85 1373710336 InnoDB: Doing recovery: scanned up to log sequence number 85 1378953216 InnoDB: Doing recovery: scanned up to log sequence number 85 1384196096 InnoDB: Doing recovery: scanned up to log sequence number 85 1389438976 InnoDB: Doing recovery: scanned up to log sequence number 85 1394681856 InnoDB: Doing recovery: scanned up to log sequence number 85 1399924736 InnoDB: Doing recovery: scanned up to log sequence number 85 1405167616 InnoDB: Doing recovery: scanned up to log sequence number 85 1410410496 InnoDB: Doing recovery: scanned up to log sequence number 85 1415653376 InnoDB: Doing recovery: scanned up to log sequence number 85 1420896256 InnoDB: Doing recovery: scanned up to log sequence number 85 1426139136 InnoDB: Doing recovery: scanned up to log sequence number 85 1431382016 InnoDB: Doing recovery: scanned up to log sequence number 85 1436624896 InnoDB: Doing recovery: scanned up to log sequence number 85 1441867776 InnoDB: Doing recovery: scanned up to log sequence number 85 1447110656 InnoDB: Doing recovery: scanned up to log sequence number 85 1452353536 InnoDB: Doing recovery: scanned up to log sequence number 85 1457596416 InnoDB: Doing recovery: scanned up to log sequence number 85 1462839296 InnoDB: Doing recovery: scanned up to log sequence number 85 1468082176 InnoDB: Doing recovery: scanned up to log sequence number 85 1473325056 InnoDB: Doing recovery: scanned up to log sequence number 85 1478567936 InnoDB: Doing recovery: scanned up to log sequence number 85 1483810816 InnoDB: Doing recovery: scanned up to log sequence number 85 1489053696 InnoDB: Doing recovery: scanned up to log sequence number 85 1494296576 InnoDB: Doing recovery: scanned up to log sequence number 85 1499539456 InnoDB: Doing recovery: scanned up to log sequence number 85 1504782336 InnoDB: Doing recovery: scanned up to log sequence number 85 1510025216 InnoDB: Doing recovery: scanned up to log sequence number 85 1515268096 InnoDB: Doing recovery: scanned up to log sequence number 85 1520510976 InnoDB: Doing recovery: scanned up to log sequence number 85 1525753856 InnoDB: Doing recovery: scanned up to log sequence number 85 1530996736 InnoDB: Doing recovery: scanned up to log sequence number 85 1536239616 InnoDB: Doing recovery: scanned up to log sequence number 85 1541482496 InnoDB: Doing recovery: scanned up to log sequence number 85 1546725376 InnoDB: Doing recovery: scanned up to log sequence number 85 1551968256 InnoDB: Doing recovery: scanned up to log sequence number 85 1557211136 InnoDB: Doing recovery: scanned up to log sequence number 85 1562454016 InnoDB: Doing recovery: scanned up to log sequence number 85 1567696896 InnoDB: Doing recovery: scanned up to log sequence number 85 1572939776 InnoDB: Doing recovery: scanned up to log sequence number 85 1578182656 InnoDB: Doing recovery: scanned up to log sequence number 85 1583425536 InnoDB: Doing recovery: scanned up to log sequence number 85 1588668416 InnoDB: Doing recovery: scanned up to log sequence number 85 1593911296 InnoDB: Doing recovery: scanned up to log sequence number 85 1599154176 InnoDB: Doing recovery: scanned up to log sequence number 85 1604397056 InnoDB: Doing recovery: scanned up to log sequence number 85 1609639936 InnoDB: Doing recovery: scanned up to log sequence number 85 1614882816 InnoDB: Doing recovery: scanned up to log sequence number 85 1620125696 InnoDB: Doing recovery: scanned up to log sequence number 85 1625368576 InnoDB: Doing recovery: scanned up to log sequence number 85 1630611456 InnoDB: Doing recovery: scanned up to log sequence number 85 1635854336 InnoDB: Doing recovery: scanned up to log sequence number 85 1641097216 InnoDB: Doing recovery: scanned up to log sequence number 85 1646340096 InnoDB: Doing recovery: scanned up to log sequence number 85 1651582976 InnoDB: Doing recovery: scanned up to log sequence number 85 1656825856 InnoDB: Doing recovery: scanned up to log sequence number 85 1662068736 InnoDB: Doing recovery: scanned up to log sequence number 85 1667311616 InnoDB: Doing recovery: scanned up to log sequence number 85 1672554496 InnoDB: Doing recovery: scanned up to log sequence number 85 1677797376 InnoDB: Doing recovery: scanned up to log sequence number 85 1683040256 InnoDB: Doing recovery: scanned up to log sequence number 85 1688283136 InnoDB: Doing recovery: scanned up to log sequence number 85 1693526016 InnoDB: Doing recovery: scanned up to log sequence number 85 1698768896 InnoDB: Doing recovery: scanned up to log sequence number 85 1704011776 InnoDB: Doing recovery: scanned up to log sequence number 85 1709254656 InnoDB: Doing recovery: scanned up to log sequence number 85 1714497536 InnoDB: Doing recovery: scanned up to log sequence number 85 1719740416 InnoDB: Doing recovery: scanned up to log sequence number 85 1724983296 InnoDB: Doing recovery: scanned up to log sequence number 85 1730226176 InnoDB: Doing recovery: scanned up to log sequence number 85 1735469056 InnoDB: Doing recovery: scanned up to log sequence number 85 1740711936 InnoDB: Doing recovery: scanned up to log sequence number 85 1745954816 InnoDB: Doing recovery: scanned up to log sequence number 85 1751197696 InnoDB: Doing recovery: scanned up to log sequence number 85 1756440576 InnoDB: Doing recovery: scanned up to log sequence number 85 1761683456 InnoDB: Doing recovery: scanned up to log sequence number 85 1766926336 InnoDB: Doing recovery: scanned up to log sequence number 85 1772169216 InnoDB: Doing recovery: scanned up to log sequence number 85 1777412096 InnoDB: Doing recovery: scanned up to log sequence number 85 1782654976 InnoDB: Doing recovery: scanned up to log sequence number 85 1787897856 InnoDB: Doing recovery: scanned up to log sequence number 85 1793140736 InnoDB: Doing recovery: scanned up to log sequence number 85 1798383616 InnoDB: Doing recovery: scanned up to log sequence number 85 1803626496 InnoDB: Doing recovery: scanned up to log sequence number 85 1808869376 InnoDB: Doing recovery: scanned up to log sequence number 85 1814112256 InnoDB: Doing recovery: scanned up to log sequence number 85 1819355136 InnoDB: Doing recovery: scanned up to log sequence number 85 1824598016 InnoDB: Doing recovery: scanned up to log sequence number 85 1829840896 InnoDB: Doing recovery: scanned up to log sequence number 85 1835083776 InnoDB: Doing recovery: scanned up to log sequence number 85 1840326656 InnoDB: Doing recovery: scanned up to log sequence number 85 1845569536 InnoDB: Doing recovery: scanned up to log sequence number 85 1850812416 InnoDB: Doing recovery: scanned up to log sequence number 85 1856055296 InnoDB: Doing recovery: scanned up to log sequence number 85 1861298176 InnoDB: Doing recovery: scanned up to log sequence number 85 1866541056 InnoDB: Doing recovery: scanned up to log sequence number 85 1871783936 InnoDB: Doing recovery: scanned up to log sequence number 85 1877026816 InnoDB: Doing recovery: scanned up to log sequence number 85 1882269696 InnoDB: Doing recovery: scanned up to log sequence number 85 1887512576 InnoDB: Doing recovery: scanned up to log sequence number 85 1892755456 InnoDB: Doing recovery: scanned up to log sequence number 85 1897998336 InnoDB: Doing recovery: scanned up to log sequence number 85 1903241216 InnoDB: Doing recovery: scanned up to log sequence number 85 1908484096 InnoDB: Doing recovery: scanned up to log sequence number 85 1913726976 InnoDB: Doing recovery: scanned up to log sequence number 85 1918969856 InnoDB: Doing recovery: scanned up to log sequence number 85 1924212736 InnoDB: Doing recovery: scanned up to log sequence number 85 1929455616 InnoDB: Doing recovery: scanned up to log sequence number 85 1934698496 InnoDB: Doing recovery: scanned up to log sequence number 85 1939941376 InnoDB: Doing recovery: scanned up to log sequence number 85 1945184256 InnoDB: Doing recovery: scanned up to log sequence number 85 1950427136 InnoDB: Doing recovery: scanned up to log sequence number 85 1955670016 InnoDB: Doing recovery: scanned up to log sequence number 85 1960912896 InnoDB: Doing recovery: scanned up to log sequence number 85 1966155776 InnoDB: Doing recovery: scanned up to log sequence number 85 1971398656 InnoDB: Doing recovery: scanned up to log sequence number 85 1976641536 InnoDB: Doing recovery: scanned up to log sequence number 85 1981884416 InnoDB: Doing recovery: scanned up to log sequence number 85 1987127296 InnoDB: Doing recovery: scanned up to log sequence number 85 1992370176 InnoDB: Doing recovery: scanned up to log sequence number 85 1997613056 InnoDB: Doing recovery: scanned up to log sequence number 85 2002855936 InnoDB: Doing recovery: scanned up to log sequence number 85 2008098816 InnoDB: Doing recovery: scanned up to log sequence number 85 2013341696 InnoDB: Doing recovery: scanned up to log sequence number 85 2018584576 InnoDB: Doing recovery: scanned up to log sequence number 85 2023827456 InnoDB: Doing recovery: scanned up to log sequence number 85 2029070336 InnoDB: Doing recovery: scanned up to log sequence number 85 2034313216 InnoDB: Doing recovery: scanned up to log sequence number 85 2039556096 InnoDB: Doing recovery: scanned up to log sequence number 85 2044798976 InnoDB: Doing recovery: scanned up to log sequence number 85 2050041856 InnoDB: Doing recovery: scanned up to log sequence number 85 2055284736 InnoDB: Doing recovery: scanned up to log sequence number 85 2060527616 071206 20:08:37 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 85 2065770496 InnoDB: Doing recovery: scanned up to log sequence number 85 2071013376 InnoDB: Doing recovery: scanned up to log sequence number 85 2076256256 InnoDB: Doing recovery: scanned up to log sequence number 85 2081499136 InnoDB: Doing recovery: scanned up to log sequence number 85 2086742016 InnoDB: Doing recovery: scanned up to log sequence number 85 2091984896 InnoDB: Doing recovery: scanned up to log sequence number 85 2097227776 InnoDB: Doing recovery: scanned up to log sequence number 85 2102470656 InnoDB: Doing recovery: scanned up to log sequence number 85 2107713536 InnoDB: Doing recovery: scanned up to log sequence number 85 2112956416 InnoDB: Doing recovery: scanned up to log sequence number 85 2118199296 InnoDB: Doing recovery: scanned up to log sequence number 85 2123442176 InnoDB: Doing recovery: scanned up to log sequence number 85 2128685056 InnoDB: Doing recovery: scanned up to log sequence number 85 2133927936 InnoDB: Doing recovery: scanned up to log sequence number 85 2133987632 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 1095370496 071206 20:12:48 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071206 20:12:48 InnoDB: Starting an apply batch of log records to the database... 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 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: Starting in background the rollback of uncommitted transactions 071206 20:14:34 InnoDB: Rolling back trx with id 0 1095369130, 1 rows to undo 071206 20:14:34 InnoDB: Started; log sequence number 85 2133987632 InnoDB: Rolling back of trx id 0 1095369130 completed 071206 20:14:34 InnoDB: Rollback of non-prepared transactions completed 071206 20:14:34 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071206 20:14:38 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071206 20:14:38 [Warning] Checking table: './tlbbdb/t_global' 071207 23:15:19 InnoDB: Error: cannot allocate 1064960 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071207 23:16:19 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=48 max_connections=100 threads_connected=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071207 23:16:19 mysqld restarted 071207 23:16:20 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... 071207 23:16:20 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 98 1507004715. InnoDB: Doing recovery: scanned up to log sequence number 98 1512247296 InnoDB: Doing recovery: scanned up to log sequence number 98 1517490176 InnoDB: Doing recovery: scanned up to log sequence number 98 1522733056 InnoDB: Doing recovery: scanned up to log sequence number 98 1527975936 InnoDB: Doing recovery: scanned up to log sequence number 98 1533218816 InnoDB: Doing recovery: scanned up to log sequence number 98 1538461696 InnoDB: Doing recovery: scanned up to log sequence number 98 1543704576 InnoDB: Doing recovery: scanned up to log sequence number 98 1548947456 InnoDB: Doing recovery: scanned up to log sequence number 98 1554190336 InnoDB: Doing recovery: scanned up to log sequence number 98 1559433216 InnoDB: Doing recovery: scanned up to log sequence number 98 1564676096 InnoDB: Doing recovery: scanned up to log sequence number 98 1569918976 InnoDB: Doing recovery: scanned up to log sequence number 98 1575161856 InnoDB: Doing recovery: scanned up to log sequence number 98 1580404736 InnoDB: Doing recovery: scanned up to log sequence number 98 1585647616 InnoDB: Doing recovery: scanned up to log sequence number 98 1590890496 InnoDB: Doing recovery: scanned up to log sequence number 98 1596133376 InnoDB: Doing recovery: scanned up to log sequence number 98 1601376256 InnoDB: Doing recovery: scanned up to log sequence number 98 1606619136 InnoDB: Doing recovery: scanned up to log sequence number 98 1611862016 InnoDB: Doing recovery: scanned up to log sequence number 98 1617104896 InnoDB: Doing recovery: scanned up to log sequence number 98 1622347776 InnoDB: Doing recovery: scanned up to log sequence number 98 1627590656 InnoDB: Doing recovery: scanned up to log sequence number 98 1632833536 InnoDB: Doing recovery: scanned up to log sequence number 98 1638076416 InnoDB: Doing recovery: scanned up to log sequence number 98 1643319296 InnoDB: Doing recovery: scanned up to log sequence number 98 1648562176 InnoDB: Doing recovery: scanned up to log sequence number 98 1653805056 InnoDB: Doing recovery: scanned up to log sequence number 98 1659047936 InnoDB: Doing recovery: scanned up to log sequence number 98 1664290816 InnoDB: Doing recovery: scanned up to log sequence number 98 1669533696 InnoDB: Doing recovery: scanned up to log sequence number 98 1674776576 InnoDB: Doing recovery: scanned up to log sequence number 98 1680019456 InnoDB: Doing recovery: scanned up to log sequence number 98 1685262336 InnoDB: Doing recovery: scanned up to log sequence number 98 1690505216 InnoDB: Doing recovery: scanned up to log sequence number 98 1695748096 InnoDB: Doing recovery: scanned up to log sequence number 98 1700990976 InnoDB: Doing recovery: scanned up to log sequence number 98 1706233856 InnoDB: Doing recovery: scanned up to log sequence number 98 1711476736 InnoDB: Doing recovery: scanned up to log sequence number 98 1716719616 InnoDB: Doing recovery: scanned up to log sequence number 98 1721962496 InnoDB: Doing recovery: scanned up to log sequence number 98 1727205376 InnoDB: Doing recovery: scanned up to log sequence number 98 1732448256 InnoDB: Doing recovery: scanned up to log sequence number 98 1737691136 InnoDB: Doing recovery: scanned up to log sequence number 98 1742934016 InnoDB: Doing recovery: scanned up to log sequence number 98 1748176896 InnoDB: Doing recovery: scanned up to log sequence number 98 1753419776 InnoDB: Doing recovery: scanned up to log sequence number 98 1758662656 InnoDB: Doing recovery: scanned up to log sequence number 98 1763905536 InnoDB: Doing recovery: scanned up to log sequence number 98 1769148416 InnoDB: Doing recovery: scanned up to log sequence number 98 1774391296 InnoDB: Doing recovery: scanned up to log sequence number 98 1779634176 InnoDB: Doing recovery: scanned up to log sequence number 98 1784877056 InnoDB: Doing recovery: scanned up to log sequence number 98 1790119936 InnoDB: Doing recovery: scanned up to log sequence number 98 1795362816 InnoDB: Doing recovery: scanned up to log sequence number 98 1800605696 InnoDB: Doing recovery: scanned up to log sequence number 98 1805848576 InnoDB: Doing recovery: scanned up to log sequence number 98 1811091456 InnoDB: Doing recovery: scanned up to log sequence number 98 1816334336 InnoDB: Doing recovery: scanned up to log sequence number 98 1821577216 InnoDB: Doing recovery: scanned up to log sequence number 98 1826820096 InnoDB: Doing recovery: scanned up to log sequence number 98 1832062976 InnoDB: Doing recovery: scanned up to log sequence number 98 1837305856 InnoDB: Doing recovery: scanned up to log sequence number 98 1842548736 InnoDB: Doing recovery: scanned up to log sequence number 98 1847791616 InnoDB: Doing recovery: scanned up to log sequence number 98 1853034496 InnoDB: Doing recovery: scanned up to log sequence number 98 1858277376 InnoDB: Doing recovery: scanned up to log sequence number 98 1863520256 InnoDB: Doing recovery: scanned up to log sequence number 98 1868763136 InnoDB: Doing recovery: scanned up to log sequence number 98 1874006016 InnoDB: Doing recovery: scanned up to log sequence number 98 1879248896 InnoDB: Doing recovery: scanned up to log sequence number 98 1884491776 InnoDB: Doing recovery: scanned up to log sequence number 98 1889734656 InnoDB: Doing recovery: scanned up to log sequence number 98 1894977536 InnoDB: Doing recovery: scanned up to log sequence number 98 1900220416 InnoDB: Doing recovery: scanned up to log sequence number 98 1905463296 InnoDB: Doing recovery: scanned up to log sequence number 98 1910706176 InnoDB: Doing recovery: scanned up to log sequence number 98 1915949056 InnoDB: Doing recovery: scanned up to log sequence number 98 1921191936 InnoDB: Doing recovery: scanned up to log sequence number 98 1926434816 InnoDB: Doing recovery: scanned up to log sequence number 98 1931677696 InnoDB: Doing recovery: scanned up to log sequence number 98 1936920576 InnoDB: Doing recovery: scanned up to log sequence number 98 1942163456 InnoDB: Doing recovery: scanned up to log sequence number 98 1947406336 InnoDB: Doing recovery: scanned up to log sequence number 98 1952649216 InnoDB: Doing recovery: scanned up to log sequence number 98 1957892096 InnoDB: Doing recovery: scanned up to log sequence number 98 1963134976 InnoDB: Doing recovery: scanned up to log sequence number 98 1968377856 InnoDB: Doing recovery: scanned up to log sequence number 98 1973620736 InnoDB: Doing recovery: scanned up to log sequence number 98 1978863616 InnoDB: Doing recovery: scanned up to log sequence number 98 1984106496 InnoDB: Doing recovery: scanned up to log sequence number 98 1989349376 InnoDB: Doing recovery: scanned up to log sequence number 98 1994592256 InnoDB: Doing recovery: scanned up to log sequence number 98 1999835136 InnoDB: Doing recovery: scanned up to log sequence number 98 2005078016 InnoDB: Doing recovery: scanned up to log sequence number 98 2010320896 InnoDB: Doing recovery: scanned up to log sequence number 98 2015563776 InnoDB: Doing recovery: scanned up to log sequence number 98 2020806656 InnoDB: Doing recovery: scanned up to log sequence number 98 2026049536 InnoDB: Doing recovery: scanned up to log sequence number 98 2031292416 InnoDB: Doing recovery: scanned up to log sequence number 98 2036535296 InnoDB: Doing recovery: scanned up to log sequence number 98 2041778176 InnoDB: Doing recovery: scanned up to log sequence number 98 2047021056 InnoDB: Doing recovery: scanned up to log sequence number 98 2052263936 InnoDB: Doing recovery: scanned up to log sequence number 98 2057506816 InnoDB: Doing recovery: scanned up to log sequence number 98 2062749696 InnoDB: Doing recovery: scanned up to log sequence number 98 2067992576 InnoDB: Doing recovery: scanned up to log sequence number 98 2073235456 InnoDB: Doing recovery: scanned up to log sequence number 98 2078478336 InnoDB: Doing recovery: scanned up to log sequence number 98 2083721216 InnoDB: Doing recovery: scanned up to log sequence number 98 2088964096 InnoDB: Doing recovery: scanned up to log sequence number 98 2094206976 InnoDB: Doing recovery: scanned up to log sequence number 98 2099449856 InnoDB: Doing recovery: scanned up to log sequence number 98 2104692736 InnoDB: Doing recovery: scanned up to log sequence number 98 2109935616 InnoDB: Doing recovery: scanned up to log sequence number 98 2115178496 InnoDB: Doing recovery: scanned up to log sequence number 98 2120421376 InnoDB: Doing recovery: scanned up to log sequence number 98 2125664256 InnoDB: Doing recovery: scanned up to log sequence number 98 2130907136 InnoDB: Doing recovery: scanned up to log sequence number 98 2136150016 InnoDB: Doing recovery: scanned up to log sequence number 98 2141392896 InnoDB: Doing recovery: scanned up to log sequence number 98 2146635776 InnoDB: Doing recovery: scanned up to log sequence number 98 2151878656 InnoDB: Doing recovery: scanned up to log sequence number 98 2157121536 InnoDB: Doing recovery: scanned up to log sequence number 98 2162364416 InnoDB: Doing recovery: scanned up to log sequence number 98 2167607296 InnoDB: Doing recovery: scanned up to log sequence number 98 2172850176 InnoDB: Doing recovery: scanned up to log sequence number 98 2178093056 InnoDB: Doing recovery: scanned up to log sequence number 98 2183335936 InnoDB: Doing recovery: scanned up to log sequence number 98 2188578816 InnoDB: Doing recovery: scanned up to log sequence number 98 2193821696 InnoDB: Doing recovery: scanned up to log sequence number 98 2199064576 InnoDB: Doing recovery: scanned up to log sequence number 98 2204307456 InnoDB: Doing recovery: scanned up to log sequence number 98 2209550336 InnoDB: Doing recovery: scanned up to log sequence number 98 2214793216 InnoDB: Doing recovery: scanned up to log sequence number 98 2220036096 InnoDB: Doing recovery: scanned up to log sequence number 98 2225278976 InnoDB: Doing recovery: scanned up to log sequence number 98 2230521856 InnoDB: Doing recovery: scanned up to log sequence number 98 2235764736 InnoDB: Doing recovery: scanned up to log sequence number 98 2241007616 InnoDB: Doing recovery: scanned up to log sequence number 98 2246250496 InnoDB: Doing recovery: scanned up to log sequence number 98 2251493376 InnoDB: Doing recovery: scanned up to log sequence number 98 2256736256 InnoDB: Doing recovery: scanned up to log sequence number 98 2261979136 InnoDB: Doing recovery: scanned up to log sequence number 98 2267222016 InnoDB: Doing recovery: scanned up to log sequence number 98 2272464896 InnoDB: Doing recovery: scanned up to log sequence number 98 2277707776 InnoDB: Doing recovery: scanned up to log sequence number 98 2282950656 InnoDB: Doing recovery: scanned up to log sequence number 98 2288193536 InnoDB: Doing recovery: scanned up to log sequence number 98 2293436416 InnoDB: Doing recovery: scanned up to log sequence number 98 2298679296 InnoDB: Doing recovery: scanned up to log sequence number 98 2303922176 InnoDB: Doing recovery: scanned up to log sequence number 98 2309165056 InnoDB: Doing recovery: scanned up to log sequence number 98 2314407936 InnoDB: Doing recovery: scanned up to log sequence number 98 2319650816 071207 23:18:55 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 98 2324893696 InnoDB: Doing recovery: scanned up to log sequence number 98 2330136576 InnoDB: Doing recovery: scanned up to log sequence number 98 2335379456 InnoDB: Doing recovery: scanned up to log sequence number 98 2340622336 InnoDB: Doing recovery: scanned up to log sequence number 98 2345865216 InnoDB: Doing recovery: scanned up to log sequence number 98 2351108096 InnoDB: Doing recovery: scanned up to log sequence number 98 2356350976 InnoDB: Doing recovery: scanned up to log sequence number 98 2361593856 InnoDB: Doing recovery: scanned up to log sequence number 98 2366836736 InnoDB: Doing recovery: scanned up to log sequence number 98 2372079616 InnoDB: Doing recovery: scanned up to log sequence number 98 2377322496 InnoDB: Doing recovery: scanned up to log sequence number 98 2382565376 InnoDB: Doing recovery: scanned up to log sequence number 98 2387808256 InnoDB: Doing recovery: scanned up to log sequence number 98 2393051136 InnoDB: Doing recovery: scanned up to log sequence number 98 2398294016 InnoDB: Doing recovery: scanned up to log sequence number 98 2398525782 InnoDB: 4 transaction(s) which must be rolled back or cleaned up InnoDB: in total 44 row operations to undo InnoDB: Trx id counter is 0 1264786432 071207 23:22:41 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071207 23:22:41 InnoDB: Starting an apply batch of log records to the database... 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 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: Starting in background the rollback of uncommitted transactions 071207 23:24:29 InnoDB: Rolling back trx with id 0 1264786127, 1 rows to undo 071207 23:24:29 InnoDB: Started; log sequence number 98 2398525782 InnoDB: Rolling back of trx id 0 1264786127 completed 071207 23:24:29 InnoDB: Rolling back trx with id 0 1264786056, 8 rows to undo InnoDB: Rolling back of trx id 0 1264786056 completed 071207 23:24:29 InnoDB: Rolling back trx with id 0 1264785204, 14 rows to undo InnoDB: Rolling back of trx id 0 1264785204 completed 071207 23:24:29 InnoDB: Rolling back trx with id 0 1264784385, 21 rows to undo InnoDB: Rolling back of trx id 0 1264784385 completed 071207 23:24:29 InnoDB: Rollback of non-prepared transactions completed 071207 23:24:29 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071207 23:24:42 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071207 23:24:42 [Warning] Checking table: './tlbbdb/t_global' 071209 0:03:39 InnoDB: Error: cannot allocate 1064960 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071209 0:04:39 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=47 max_connections=100 threads_connected=20 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071209 00:04:39 mysqld restarted 071209 0:04:39 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... 071209 0:04:39 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 111 2988268006. InnoDB: Doing recovery: scanned up to log sequence number 111 2993510400 InnoDB: Doing recovery: scanned up to log sequence number 111 2998753280 InnoDB: Doing recovery: scanned up to log sequence number 111 3003996160 InnoDB: Doing recovery: scanned up to log sequence number 111 3009239040 InnoDB: Doing recovery: scanned up to log sequence number 111 3014481920 InnoDB: Doing recovery: scanned up to log sequence number 111 3019724800 InnoDB: Doing recovery: scanned up to log sequence number 111 3024967680 InnoDB: Doing recovery: scanned up to log sequence number 111 3030210560 InnoDB: Doing recovery: scanned up to log sequence number 111 3035453440 InnoDB: Doing recovery: scanned up to log sequence number 111 3040696320 InnoDB: Doing recovery: scanned up to log sequence number 111 3045939200 InnoDB: Doing recovery: scanned up to log sequence number 111 3051182080 InnoDB: Doing recovery: scanned up to log sequence number 111 3056424960 InnoDB: Doing recovery: scanned up to log sequence number 111 3061667840 InnoDB: Doing recovery: scanned up to log sequence number 111 3066910720 InnoDB: Doing recovery: scanned up to log sequence number 111 3072153600 InnoDB: Doing recovery: scanned up to log sequence number 111 3077396480 InnoDB: Doing recovery: scanned up to log sequence number 111 3082639360 InnoDB: Doing recovery: scanned up to log sequence number 111 3087882240 InnoDB: Doing recovery: scanned up to log sequence number 111 3093125120 InnoDB: Doing recovery: scanned up to log sequence number 111 3098368000 InnoDB: Doing recovery: scanned up to log sequence number 111 3103610880 InnoDB: Doing recovery: scanned up to log sequence number 111 3108853760 InnoDB: Doing recovery: scanned up to log sequence number 111 3114096640 InnoDB: Doing recovery: scanned up to log sequence number 111 3119339520 InnoDB: Doing recovery: scanned up to log sequence number 111 3124582400 InnoDB: Doing recovery: scanned up to log sequence number 111 3129825280 InnoDB: Doing recovery: scanned up to log sequence number 111 3135068160 InnoDB: Doing recovery: scanned up to log sequence number 111 3140311040 InnoDB: Doing recovery: scanned up to log sequence number 111 3145553920 InnoDB: Doing recovery: scanned up to log sequence number 111 3150796800 InnoDB: Doing recovery: scanned up to log sequence number 111 3156039680 InnoDB: Doing recovery: scanned up to log sequence number 111 3161282560 InnoDB: Doing recovery: scanned up to log sequence number 111 3166525440 InnoDB: Doing recovery: scanned up to log sequence number 111 3171768320 InnoDB: Doing recovery: scanned up to log sequence number 111 3177011200 InnoDB: Doing recovery: scanned up to log sequence number 111 3182254080 InnoDB: Doing recovery: scanned up to log sequence number 111 3187496960 InnoDB: Doing recovery: scanned up to log sequence number 111 3192739840 InnoDB: Doing recovery: scanned up to log sequence number 111 3197982720 InnoDB: Doing recovery: scanned up to log sequence number 111 3203225600 InnoDB: Doing recovery: scanned up to log sequence number 111 3208468480 InnoDB: Doing recovery: scanned up to log sequence number 111 3213711360 InnoDB: Doing recovery: scanned up to log sequence number 111 3218954240 InnoDB: Doing recovery: scanned up to log sequence number 111 3224197120 InnoDB: Doing recovery: scanned up to log sequence number 111 3229440000 InnoDB: Doing recovery: scanned up to log sequence number 111 3234682880 InnoDB: Doing recovery: scanned up to log sequence number 111 3239925760 InnoDB: Doing recovery: scanned up to log sequence number 111 3245168640 InnoDB: Doing recovery: scanned up to log sequence number 111 3250411520 InnoDB: Doing recovery: scanned up to log sequence number 111 3255654400 InnoDB: Doing recovery: scanned up to log sequence number 111 3260897280 InnoDB: Doing recovery: scanned up to log sequence number 111 3266140160 InnoDB: Doing recovery: scanned up to log sequence number 111 3271383040 InnoDB: Doing recovery: scanned up to log sequence number 111 3276625920 InnoDB: Doing recovery: scanned up to log sequence number 111 3281868800 InnoDB: Doing recovery: scanned up to log sequence number 111 3287111680 InnoDB: Doing recovery: scanned up to log sequence number 111 3292354560 InnoDB: Doing recovery: scanned up to log sequence number 111 3297597440 InnoDB: Doing recovery: scanned up to log sequence number 111 3302840320 InnoDB: Doing recovery: scanned up to log sequence number 111 3308083200 InnoDB: Doing recovery: scanned up to log sequence number 111 3313326080 InnoDB: Doing recovery: scanned up to log sequence number 111 3318568960 InnoDB: Doing recovery: scanned up to log sequence number 111 3323811840 InnoDB: Doing recovery: scanned up to log sequence number 111 3329054720 InnoDB: Doing recovery: scanned up to log sequence number 111 3334297600 InnoDB: Doing recovery: scanned up to log sequence number 111 3339540480 InnoDB: Doing recovery: scanned up to log sequence number 111 3344783360 InnoDB: Doing recovery: scanned up to log sequence number 111 3350026240 InnoDB: Doing recovery: scanned up to log sequence number 111 3355269120 InnoDB: Doing recovery: scanned up to log sequence number 111 3360512000 InnoDB: Doing recovery: scanned up to log sequence number 111 3365754880 InnoDB: Doing recovery: scanned up to log sequence number 111 3370997760 InnoDB: Doing recovery: scanned up to log sequence number 111 3376240640 InnoDB: Doing recovery: scanned up to log sequence number 111 3381483520 InnoDB: Doing recovery: scanned up to log sequence number 111 3386726400 InnoDB: Doing recovery: scanned up to log sequence number 111 3391969280 InnoDB: Doing recovery: scanned up to log sequence number 111 3397212160 InnoDB: Doing recovery: scanned up to log sequence number 111 3402455040 InnoDB: Doing recovery: scanned up to log sequence number 111 3407697920 InnoDB: Doing recovery: scanned up to log sequence number 111 3412940800 InnoDB: Doing recovery: scanned up to log sequence number 111 3418183680 InnoDB: Doing recovery: scanned up to log sequence number 111 3423426560 InnoDB: Doing recovery: scanned up to log sequence number 111 3428669440 InnoDB: Doing recovery: scanned up to log sequence number 111 3433912320 InnoDB: Doing recovery: scanned up to log sequence number 111 3439155200 InnoDB: Doing recovery: scanned up to log sequence number 111 3444398080 InnoDB: Doing recovery: scanned up to log sequence number 111 3449640960 InnoDB: Doing recovery: scanned up to log sequence number 111 3454883840 InnoDB: Doing recovery: scanned up to log sequence number 111 3460126720 InnoDB: Doing recovery: scanned up to log sequence number 111 3465369600 InnoDB: Doing recovery: scanned up to log sequence number 111 3470612480 InnoDB: Doing recovery: scanned up to log sequence number 111 3475855360 InnoDB: Doing recovery: scanned up to log sequence number 111 3481098240 InnoDB: Doing recovery: scanned up to log sequence number 111 3486341120 InnoDB: Doing recovery: scanned up to log sequence number 111 3491584000 InnoDB: Doing recovery: scanned up to log sequence number 111 3496826880 InnoDB: Doing recovery: scanned up to log sequence number 111 3502069760 InnoDB: Doing recovery: scanned up to log sequence number 111 3507312640 InnoDB: Doing recovery: scanned up to log sequence number 111 3512555520 InnoDB: Doing recovery: scanned up to log sequence number 111 3517798400 InnoDB: Doing recovery: scanned up to log sequence number 111 3523041280 InnoDB: Doing recovery: scanned up to log sequence number 111 3528284160 InnoDB: Doing recovery: scanned up to log sequence number 111 3533527040 InnoDB: Doing recovery: scanned up to log sequence number 111 3538769920 InnoDB: Doing recovery: scanned up to log sequence number 111 3544012800 InnoDB: Doing recovery: scanned up to log sequence number 111 3549255680 InnoDB: Doing recovery: scanned up to log sequence number 111 3554498560 InnoDB: Doing recovery: scanned up to log sequence number 111 3559741440 InnoDB: Doing recovery: scanned up to log sequence number 111 3564984320 InnoDB: Doing recovery: scanned up to log sequence number 111 3570227200 InnoDB: Doing recovery: scanned up to log sequence number 111 3575470080 InnoDB: Doing recovery: scanned up to log sequence number 111 3580712960 InnoDB: Doing recovery: scanned up to log sequence number 111 3585955840 InnoDB: Doing recovery: scanned up to log sequence number 111 3591198720 InnoDB: Doing recovery: scanned up to log sequence number 111 3596441600 InnoDB: Doing recovery: scanned up to log sequence number 111 3601684480 InnoDB: Doing recovery: scanned up to log sequence number 111 3606927360 InnoDB: Doing recovery: scanned up to log sequence number 111 3612170240 InnoDB: Doing recovery: scanned up to log sequence number 111 3617413120 InnoDB: Doing recovery: scanned up to log sequence number 111 3622656000 InnoDB: Doing recovery: scanned up to log sequence number 111 3627898880 InnoDB: Doing recovery: scanned up to log sequence number 111 3633141760 InnoDB: Doing recovery: scanned up to log sequence number 111 3638384640 InnoDB: Doing recovery: scanned up to log sequence number 111 3643627520 InnoDB: Doing recovery: scanned up to log sequence number 111 3648870400 InnoDB: Doing recovery: scanned up to log sequence number 111 3654113280 InnoDB: Doing recovery: scanned up to log sequence number 111 3659356160 InnoDB: Doing recovery: scanned up to log sequence number 111 3664599040 InnoDB: Doing recovery: scanned up to log sequence number 111 3669841920 InnoDB: Doing recovery: scanned up to log sequence number 111 3675084800 InnoDB: Doing recovery: scanned up to log sequence number 111 3680327680 InnoDB: Doing recovery: scanned up to log sequence number 111 3685570560 InnoDB: Doing recovery: scanned up to log sequence number 111 3690813440 InnoDB: Doing recovery: scanned up to log sequence number 111 3696056320 InnoDB: Doing recovery: scanned up to log sequence number 111 3701299200 InnoDB: Doing recovery: scanned up to log sequence number 111 3706542080 InnoDB: Doing recovery: scanned up to log sequence number 111 3711784960 InnoDB: Doing recovery: scanned up to log sequence number 111 3717027840 InnoDB: Doing recovery: scanned up to log sequence number 111 3722270720 InnoDB: Doing recovery: scanned up to log sequence number 111 3727513600 InnoDB: Doing recovery: scanned up to log sequence number 111 3732756480 InnoDB: Doing recovery: scanned up to log sequence number 111 3737999360 InnoDB: Doing recovery: scanned up to log sequence number 111 3743242240 InnoDB: Doing recovery: scanned up to log sequence number 111 3748485120 InnoDB: Doing recovery: scanned up to log sequence number 111 3753728000 InnoDB: Doing recovery: scanned up to log sequence number 111 3758970880 InnoDB: Doing recovery: scanned up to log sequence number 111 3764213760 InnoDB: Doing recovery: scanned up to log sequence number 111 3769456640 InnoDB: Doing recovery: scanned up to log sequence number 111 3774699520 InnoDB: Doing recovery: scanned up to log sequence number 111 3779942400 InnoDB: Doing recovery: scanned up to log sequence number 111 3785185280 InnoDB: Doing recovery: scanned up to log sequence number 111 3790428160 InnoDB: Doing recovery: scanned up to log sequence number 111 3795671040 InnoDB: Doing recovery: scanned up to log sequence number 111 3800913920 InnoDB: Doing recovery: scanned up to log sequence number 111 3806156800 071209 0:07:16 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 111 3811399680 InnoDB: Doing recovery: scanned up to log sequence number 111 3816642560 InnoDB: Doing recovery: scanned up to log sequence number 111 3821885440 InnoDB: Doing recovery: scanned up to log sequence number 111 3827128320 InnoDB: Doing recovery: scanned up to log sequence number 111 3832371200 InnoDB: Doing recovery: scanned up to log sequence number 111 3837614080 InnoDB: Doing recovery: scanned up to log sequence number 111 3842856960 InnoDB: Doing recovery: scanned up to log sequence number 111 3848099840 InnoDB: Doing recovery: scanned up to log sequence number 111 3853342720 InnoDB: Doing recovery: scanned up to log sequence number 111 3858585600 InnoDB: Doing recovery: scanned up to log sequence number 111 3863828480 InnoDB: Doing recovery: scanned up to log sequence number 111 3869071360 InnoDB: Doing recovery: scanned up to log sequence number 111 3874314240 InnoDB: Doing recovery: scanned up to log sequence number 111 3879258055 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 1437394176 071209 0:11:12 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071209 0:11:12 InnoDB: Starting an apply batch of log records to the database... 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 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: Starting in background the rollback of uncommitted transactions 071209 0:12:55 InnoDB: Rolling back trx with id 0 1437393805, 1 rows to undo 071209 0:12:55 InnoDB: Started; log sequence number 111 3879258055 InnoDB: Rolling back of trx id 0 1437393805 completed 071209 0:12:55 InnoDB: Rollback of non-prepared transactions completed 071209 0:12:55 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071209 0:13:10 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071209 0:13:10 [Warning] Checking table: './tlbbdb/t_global' 071210 2:16:02 InnoDB: Error: cannot allocate 720896 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071210 2:17:01 InnoDB: Error: cannot allocate 704512 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071210 2:18:01 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=47 max_connections=100 threads_connected=13 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071210 02:18:02 mysqld restarted 071210 2:18:02 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... 071210 2:18:02 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 125 513526637. InnoDB: Doing recovery: scanned up to log sequence number 125 518769152 InnoDB: Doing recovery: scanned up to log sequence number 125 524012032 InnoDB: Doing recovery: scanned up to log sequence number 125 529254912 InnoDB: Doing recovery: scanned up to log sequence number 125 534497792 InnoDB: Doing recovery: scanned up to log sequence number 125 539740672 InnoDB: Doing recovery: scanned up to log sequence number 125 544983552 InnoDB: Doing recovery: scanned up to log sequence number 125 550226432 InnoDB: Doing recovery: scanned up to log sequence number 125 555469312 InnoDB: Doing recovery: scanned up to log sequence number 125 560712192 InnoDB: Doing recovery: scanned up to log sequence number 125 565955072 InnoDB: Doing recovery: scanned up to log sequence number 125 571197952 InnoDB: Doing recovery: scanned up to log sequence number 125 576440832 InnoDB: Doing recovery: scanned up to log sequence number 125 581683712 InnoDB: Doing recovery: scanned up to log sequence number 125 586926592 InnoDB: Doing recovery: scanned up to log sequence number 125 592169472 InnoDB: Doing recovery: scanned up to log sequence number 125 597412352 InnoDB: Doing recovery: scanned up to log sequence number 125 602655232 InnoDB: Doing recovery: scanned up to log sequence number 125 607898112 InnoDB: Doing recovery: scanned up to log sequence number 125 613140992 InnoDB: Doing recovery: scanned up to log sequence number 125 618383872 InnoDB: Doing recovery: scanned up to log sequence number 125 623626752 InnoDB: Doing recovery: scanned up to log sequence number 125 628869632 InnoDB: Doing recovery: scanned up to log sequence number 125 634112512 InnoDB: Doing recovery: scanned up to log sequence number 125 639355392 InnoDB: Doing recovery: scanned up to log sequence number 125 644598272 InnoDB: Doing recovery: scanned up to log sequence number 125 649841152 InnoDB: Doing recovery: scanned up to log sequence number 125 655084032 InnoDB: Doing recovery: scanned up to log sequence number 125 660326912 InnoDB: Doing recovery: scanned up to log sequence number 125 665569792 InnoDB: Doing recovery: scanned up to log sequence number 125 670812672 InnoDB: Doing recovery: scanned up to log sequence number 125 676055552 InnoDB: Doing recovery: scanned up to log sequence number 125 681298432 InnoDB: Doing recovery: scanned up to log sequence number 125 686541312 InnoDB: Doing recovery: scanned up to log sequence number 125 691784192 InnoDB: Doing recovery: scanned up to log sequence number 125 697027072 InnoDB: Doing recovery: scanned up to log sequence number 125 702269952 InnoDB: Doing recovery: scanned up to log sequence number 125 707512832 InnoDB: Doing recovery: scanned up to log sequence number 125 712755712 InnoDB: Doing recovery: scanned up to log sequence number 125 717998592 InnoDB: Doing recovery: scanned up to log sequence number 125 723241472 InnoDB: Doing recovery: scanned up to log sequence number 125 728484352 InnoDB: Doing recovery: scanned up to log sequence number 125 733727232 InnoDB: Doing recovery: scanned up to log sequence number 125 738970112 InnoDB: Doing recovery: scanned up to log sequence number 125 744212992 InnoDB: Doing recovery: scanned up to log sequence number 125 749455872 InnoDB: Doing recovery: scanned up to log sequence number 125 754698752 InnoDB: Doing recovery: scanned up to log sequence number 125 759941632 InnoDB: Doing recovery: scanned up to log sequence number 125 765184512 InnoDB: Doing recovery: scanned up to log sequence number 125 770427392 InnoDB: Doing recovery: scanned up to log sequence number 125 775670272 InnoDB: Doing recovery: scanned up to log sequence number 125 780913152 InnoDB: Doing recovery: scanned up to log sequence number 125 786156032 InnoDB: Doing recovery: scanned up to log sequence number 125 791398912 InnoDB: Doing recovery: scanned up to log sequence number 125 796641792 InnoDB: Doing recovery: scanned up to log sequence number 125 801884672 InnoDB: Doing recovery: scanned up to log sequence number 125 807127552 InnoDB: Doing recovery: scanned up to log sequence number 125 812370432 InnoDB: Doing recovery: scanned up to log sequence number 125 817613312 InnoDB: Doing recovery: scanned up to log sequence number 125 822856192 InnoDB: Doing recovery: scanned up to log sequence number 125 828099072 InnoDB: Doing recovery: scanned up to log sequence number 125 833341952 InnoDB: Doing recovery: scanned up to log sequence number 125 838584832 InnoDB: Doing recovery: scanned up to log sequence number 125 843827712 InnoDB: Doing recovery: scanned up to log sequence number 125 849070592 InnoDB: Doing recovery: scanned up to log sequence number 125 854313472 InnoDB: Doing recovery: scanned up to log sequence number 125 859556352 InnoDB: Doing recovery: scanned up to log sequence number 125 864799232 InnoDB: Doing recovery: scanned up to log sequence number 125 870042112 InnoDB: Doing recovery: scanned up to log sequence number 125 875284992 InnoDB: Doing recovery: scanned up to log sequence number 125 880527872 InnoDB: Doing recovery: scanned up to log sequence number 125 885770752 InnoDB: Doing recovery: scanned up to log sequence number 125 891013632 InnoDB: Doing recovery: scanned up to log sequence number 125 896256512 InnoDB: Doing recovery: scanned up to log sequence number 125 901499392 InnoDB: Doing recovery: scanned up to log sequence number 125 906742272 InnoDB: Doing recovery: scanned up to log sequence number 125 911985152 InnoDB: Doing recovery: scanned up to log sequence number 125 917228032 InnoDB: Doing recovery: scanned up to log sequence number 125 922470912 InnoDB: Doing recovery: scanned up to log sequence number 125 927713792 InnoDB: Doing recovery: scanned up to log sequence number 125 932956672 InnoDB: Doing recovery: scanned up to log sequence number 125 938199552 InnoDB: Doing recovery: scanned up to log sequence number 125 943442432 InnoDB: Doing recovery: scanned up to log sequence number 125 948685312 InnoDB: Doing recovery: scanned up to log sequence number 125 953928192 InnoDB: Doing recovery: scanned up to log sequence number 125 959171072 InnoDB: Doing recovery: scanned up to log sequence number 125 964413952 InnoDB: Doing recovery: scanned up to log sequence number 125 969656832 InnoDB: Doing recovery: scanned up to log sequence number 125 974899712 InnoDB: Doing recovery: scanned up to log sequence number 125 980142592 InnoDB: Doing recovery: scanned up to log sequence number 125 985385472 InnoDB: Doing recovery: scanned up to log sequence number 125 990628352 InnoDB: Doing recovery: scanned up to log sequence number 125 995871232 InnoDB: Doing recovery: scanned up to log sequence number 125 1001114112 InnoDB: Doing recovery: scanned up to log sequence number 125 1006356992 InnoDB: Doing recovery: scanned up to log sequence number 125 1011599872 InnoDB: Doing recovery: scanned up to log sequence number 125 1016842752 InnoDB: Doing recovery: scanned up to log sequence number 125 1022085632 InnoDB: Doing recovery: scanned up to log sequence number 125 1027328512 InnoDB: Doing recovery: scanned up to log sequence number 125 1032571392 InnoDB: Doing recovery: scanned up to log sequence number 125 1037814272 InnoDB: Doing recovery: scanned up to log sequence number 125 1043057152 InnoDB: Doing recovery: scanned up to log sequence number 125 1048300032 InnoDB: Doing recovery: scanned up to log sequence number 125 1053542912 InnoDB: Doing recovery: scanned up to log sequence number 125 1058785792 InnoDB: Doing recovery: scanned up to log sequence number 125 1064028672 InnoDB: Doing recovery: scanned up to log sequence number 125 1069271552 InnoDB: Doing recovery: scanned up to log sequence number 125 1074514432 InnoDB: Doing recovery: scanned up to log sequence number 125 1079757312 InnoDB: Doing recovery: scanned up to log sequence number 125 1085000192 InnoDB: Doing recovery: scanned up to log sequence number 125 1090243072 InnoDB: Doing recovery: scanned up to log sequence number 125 1095485952 InnoDB: Doing recovery: scanned up to log sequence number 125 1100728832 InnoDB: Doing recovery: scanned up to log sequence number 125 1105971712 InnoDB: Doing recovery: scanned up to log sequence number 125 1111214592 InnoDB: Doing recovery: scanned up to log sequence number 125 1116457472 InnoDB: Doing recovery: scanned up to log sequence number 125 1121700352 InnoDB: Doing recovery: scanned up to log sequence number 125 1126943232 InnoDB: Doing recovery: scanned up to log sequence number 125 1132186112 InnoDB: Doing recovery: scanned up to log sequence number 125 1137428992 InnoDB: Doing recovery: scanned up to log sequence number 125 1142671872 InnoDB: Doing recovery: scanned up to log sequence number 125 1147914752 InnoDB: Doing recovery: scanned up to log sequence number 125 1153157632 InnoDB: Doing recovery: scanned up to log sequence number 125 1158400512 InnoDB: Doing recovery: scanned up to log sequence number 125 1163643392 InnoDB: Doing recovery: scanned up to log sequence number 125 1168886272 InnoDB: Doing recovery: scanned up to log sequence number 125 1174129152 InnoDB: Doing recovery: scanned up to log sequence number 125 1179372032 InnoDB: Doing recovery: scanned up to log sequence number 125 1184614912 InnoDB: Doing recovery: scanned up to log sequence number 125 1189857792 InnoDB: Doing recovery: scanned up to log sequence number 125 1195100672 InnoDB: Doing recovery: scanned up to log sequence number 125 1200343552 InnoDB: Doing recovery: scanned up to log sequence number 125 1205586432 InnoDB: Doing recovery: scanned up to log sequence number 125 1210829312 InnoDB: Doing recovery: scanned up to log sequence number 125 1216072192 InnoDB: Doing recovery: scanned up to log sequence number 125 1221315072 InnoDB: Doing recovery: scanned up to log sequence number 125 1226557952 InnoDB: Doing recovery: scanned up to log sequence number 125 1231800832 InnoDB: Doing recovery: scanned up to log sequence number 125 1237043712 InnoDB: Doing recovery: scanned up to log sequence number 125 1242286592 InnoDB: Doing recovery: scanned up to log sequence number 125 1247529472 InnoDB: Doing recovery: scanned up to log sequence number 125 1252772352 InnoDB: Doing recovery: scanned up to log sequence number 125 1258015232 InnoDB: Doing recovery: scanned up to log sequence number 125 1263258112 InnoDB: Doing recovery: scanned up to log sequence number 125 1268500992 InnoDB: Doing recovery: scanned up to log sequence number 125 1273743872 InnoDB: Doing recovery: scanned up to log sequence number 125 1278986752 InnoDB: Doing recovery: scanned up to log sequence number 125 1284229632 InnoDB: Doing recovery: scanned up to log sequence number 125 1289472512 InnoDB: Doing recovery: scanned up to log sequence number 125 1294715392 InnoDB: Doing recovery: scanned up to log sequence number 125 1299958272 InnoDB: Doing recovery: scanned up to log sequence number 125 1305201152 InnoDB: Doing recovery: scanned up to log sequence number 125 1310444032 InnoDB: Doing recovery: scanned up to log sequence number 125 1315686912 InnoDB: Doing recovery: scanned up to log sequence number 125 1320929792 InnoDB: Doing recovery: scanned up to log sequence number 125 1326172672 InnoDB: Doing recovery: scanned up to log sequence number 125 1331415552 InnoDB: Doing recovery: scanned up to log sequence number 125 1336658432 InnoDB: Doing recovery: scanned up to log sequence number 125 1341901312 071210 2:20:40 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 125 1347144192 InnoDB: Doing recovery: scanned up to log sequence number 125 1352387072 InnoDB: Doing recovery: scanned up to log sequence number 125 1357629952 InnoDB: Doing recovery: scanned up to log sequence number 125 1362872832 InnoDB: Doing recovery: scanned up to log sequence number 125 1368115712 InnoDB: Doing recovery: scanned up to log sequence number 125 1373358592 InnoDB: Doing recovery: scanned up to log sequence number 125 1378601472 InnoDB: Doing recovery: scanned up to log sequence number 125 1383844352 InnoDB: Doing recovery: scanned up to log sequence number 125 1389087232 InnoDB: Doing recovery: scanned up to log sequence number 125 1394330112 InnoDB: Doing recovery: scanned up to log sequence number 125 1399572992 InnoDB: Doing recovery: scanned up to log sequence number 125 1404815872 InnoDB: Doing recovery: scanned up to log sequence number 125 1406834564 InnoDB: 3 transaction(s) which must be rolled back or cleaned up InnoDB: in total 59 row operations to undo InnoDB: Trx id counter is 0 1609858304 071210 2:23:55 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071210 2:23:55 InnoDB: Starting an apply batch of log records to the database... 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 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 071210 2:25:27 InnoDB: Started; log sequence number 125 1406834564 InnoDB: Starting in background the rollback of uncommitted transactions 071210 2:25:27 InnoDB: Rolling back trx with id 0 1609857865, 1 rows to undo InnoDB: Rolling back of trx id 0 1609857865 completed 071210 2:25:27 InnoDB: Rolling back trx with id 0 1609857787, 3 rows to undo InnoDB: Rolling back of trx id 0 1609857787 completed 071210 2:25:27 InnoDB: Rolling back trx with id 0 1609857782, 55 rows to undo InnoDB: Rolling back of trx id 0 1609857782 completed 071210 2:25:27 InnoDB: Rollback of non-prepared transactions completed 071210 2:25:27 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071210 2:25:28 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071210 2:25:28 [Warning] Checking table: './tlbbdb/t_global' 071211 13:36:44 InnoDB: Error: cannot allocate 966656 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071211 13:37:44 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=47 max_connections=100 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071211 13:37:44 mysqld restarted 071211 13:37:44 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... 071211 13:37:45 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 138 1054407669. InnoDB: Doing recovery: scanned up to log sequence number 138 1059650048 InnoDB: Doing recovery: scanned up to log sequence number 138 1064892928 InnoDB: Doing recovery: scanned up to log sequence number 138 1070135808 InnoDB: Doing recovery: scanned up to log sequence number 138 1075378688 InnoDB: Doing recovery: scanned up to log sequence number 138 1080621568 InnoDB: Doing recovery: scanned up to log sequence number 138 1085864448 InnoDB: Doing recovery: scanned up to log sequence number 138 1091107328 InnoDB: Doing recovery: scanned up to log sequence number 138 1096350208 InnoDB: Doing recovery: scanned up to log sequence number 138 1101593088 InnoDB: Doing recovery: scanned up to log sequence number 138 1106835968 InnoDB: Doing recovery: scanned up to log sequence number 138 1112078848 InnoDB: Doing recovery: scanned up to log sequence number 138 1117321728 InnoDB: Doing recovery: scanned up to log sequence number 138 1122564608 InnoDB: Doing recovery: scanned up to log sequence number 138 1127807488 InnoDB: Doing recovery: scanned up to log sequence number 138 1133050368 InnoDB: Doing recovery: scanned up to log sequence number 138 1138293248 InnoDB: Doing recovery: scanned up to log sequence number 138 1143536128 InnoDB: Doing recovery: scanned up to log sequence number 138 1148779008 InnoDB: Doing recovery: scanned up to log sequence number 138 1154021888 InnoDB: Doing recovery: scanned up to log sequence number 138 1159264768 InnoDB: Doing recovery: scanned up to log sequence number 138 1164507648 InnoDB: Doing recovery: scanned up to log sequence number 138 1169750528 InnoDB: Doing recovery: scanned up to log sequence number 138 1174993408 InnoDB: Doing recovery: scanned up to log sequence number 138 1180236288 InnoDB: Doing recovery: scanned up to log sequence number 138 1185479168 InnoDB: Doing recovery: scanned up to log sequence number 138 1190722048 InnoDB: Doing recovery: scanned up to log sequence number 138 1195964928 InnoDB: Doing recovery: scanned up to log sequence number 138 1201207808 InnoDB: Doing recovery: scanned up to log sequence number 138 1206450688 InnoDB: Doing recovery: scanned up to log sequence number 138 1211693568 InnoDB: Doing recovery: scanned up to log sequence number 138 1216936448 InnoDB: Doing recovery: scanned up to log sequence number 138 1222179328 InnoDB: Doing recovery: scanned up to log sequence number 138 1227422208 InnoDB: Doing recovery: scanned up to log sequence number 138 1232665088 InnoDB: Doing recovery: scanned up to log sequence number 138 1237907968 InnoDB: Doing recovery: scanned up to log sequence number 138 1243150848 InnoDB: Doing recovery: scanned up to log sequence number 138 1248393728 InnoDB: Doing recovery: scanned up to log sequence number 138 1253636608 InnoDB: Doing recovery: scanned up to log sequence number 138 1258879488 InnoDB: Doing recovery: scanned up to log sequence number 138 1264122368 InnoDB: Doing recovery: scanned up to log sequence number 138 1269365248 InnoDB: Doing recovery: scanned up to log sequence number 138 1274608128 InnoDB: Doing recovery: scanned up to log sequence number 138 1279851008 InnoDB: Doing recovery: scanned up to log sequence number 138 1285093888 InnoDB: Doing recovery: scanned up to log sequence number 138 1290336768 InnoDB: Doing recovery: scanned up to log sequence number 138 1295579648 InnoDB: Doing recovery: scanned up to log sequence number 138 1300822528 InnoDB: Doing recovery: scanned up to log sequence number 138 1306065408 InnoDB: Doing recovery: scanned up to log sequence number 138 1311308288 InnoDB: Doing recovery: scanned up to log sequence number 138 1316551168 InnoDB: Doing recovery: scanned up to log sequence number 138 1321794048 InnoDB: Doing recovery: scanned up to log sequence number 138 1327036928 InnoDB: Doing recovery: scanned up to log sequence number 138 1332279808 InnoDB: Doing recovery: scanned up to log sequence number 138 1337522688 InnoDB: Doing recovery: scanned up to log sequence number 138 1342765568 InnoDB: Doing recovery: scanned up to log sequence number 138 1348008448 InnoDB: Doing recovery: scanned up to log sequence number 138 1353251328 InnoDB: Doing recovery: scanned up to log sequence number 138 1358494208 InnoDB: Doing recovery: scanned up to log sequence number 138 1363737088 InnoDB: Doing recovery: scanned up to log sequence number 138 1368979968 InnoDB: Doing recovery: scanned up to log sequence number 138 1374222848 InnoDB: Doing recovery: scanned up to log sequence number 138 1379465728 InnoDB: Doing recovery: scanned up to log sequence number 138 1384708608 InnoDB: Doing recovery: scanned up to log sequence number 138 1389951488 InnoDB: Doing recovery: scanned up to log sequence number 138 1395194368 InnoDB: Doing recovery: scanned up to log sequence number 138 1400437248 InnoDB: Doing recovery: scanned up to log sequence number 138 1405680128 InnoDB: Doing recovery: scanned up to log sequence number 138 1410923008 InnoDB: Doing recovery: scanned up to log sequence number 138 1416165888 InnoDB: Doing recovery: scanned up to log sequence number 138 1421408768 InnoDB: Doing recovery: scanned up to log sequence number 138 1426651648 InnoDB: Doing recovery: scanned up to log sequence number 138 1431894528 InnoDB: Doing recovery: scanned up to log sequence number 138 1437137408 InnoDB: Doing recovery: scanned up to log sequence number 138 1442380288 InnoDB: Doing recovery: scanned up to log sequence number 138 1447623168 InnoDB: Doing recovery: scanned up to log sequence number 138 1452866048 InnoDB: Doing recovery: scanned up to log sequence number 138 1458108928 InnoDB: Doing recovery: scanned up to log sequence number 138 1463351808 InnoDB: Doing recovery: scanned up to log sequence number 138 1468594688 InnoDB: Doing recovery: scanned up to log sequence number 138 1473837568 InnoDB: Doing recovery: scanned up to log sequence number 138 1479080448 InnoDB: Doing recovery: scanned up to log sequence number 138 1484323328 InnoDB: Doing recovery: scanned up to log sequence number 138 1489566208 InnoDB: Doing recovery: scanned up to log sequence number 138 1494809088 InnoDB: Doing recovery: scanned up to log sequence number 138 1500051968 InnoDB: Doing recovery: scanned up to log sequence number 138 1505294848 InnoDB: Doing recovery: scanned up to log sequence number 138 1510537728 InnoDB: Doing recovery: scanned up to log sequence number 138 1515780608 InnoDB: Doing recovery: scanned up to log sequence number 138 1521023488 InnoDB: Doing recovery: scanned up to log sequence number 138 1526266368 InnoDB: Doing recovery: scanned up to log sequence number 138 1531509248 InnoDB: Doing recovery: scanned up to log sequence number 138 1536752128 InnoDB: Doing recovery: scanned up to log sequence number 138 1541995008 InnoDB: Doing recovery: scanned up to log sequence number 138 1547237888 InnoDB: Doing recovery: scanned up to log sequence number 138 1552480768 InnoDB: Doing recovery: scanned up to log sequence number 138 1557723648 InnoDB: Doing recovery: scanned up to log sequence number 138 1562966528 InnoDB: Doing recovery: scanned up to log sequence number 138 1568209408 InnoDB: Doing recovery: scanned up to log sequence number 138 1573452288 InnoDB: Doing recovery: scanned up to log sequence number 138 1578695168 InnoDB: Doing recovery: scanned up to log sequence number 138 1583938048 InnoDB: Doing recovery: scanned up to log sequence number 138 1589180928 InnoDB: Doing recovery: scanned up to log sequence number 138 1594423808 InnoDB: Doing recovery: scanned up to log sequence number 138 1599666688 InnoDB: Doing recovery: scanned up to log sequence number 138 1604909568 InnoDB: Doing recovery: scanned up to log sequence number 138 1610152448 InnoDB: Doing recovery: scanned up to log sequence number 138 1615395328 InnoDB: Doing recovery: scanned up to log sequence number 138 1620638208 InnoDB: Doing recovery: scanned up to log sequence number 138 1625881088 InnoDB: Doing recovery: scanned up to log sequence number 138 1631123968 InnoDB: Doing recovery: scanned up to log sequence number 138 1636366848 InnoDB: Doing recovery: scanned up to log sequence number 138 1641609728 InnoDB: Doing recovery: scanned up to log sequence number 138 1646852608 InnoDB: Doing recovery: scanned up to log sequence number 138 1652095488 InnoDB: Doing recovery: scanned up to log sequence number 138 1657338368 InnoDB: Doing recovery: scanned up to log sequence number 138 1662581248 InnoDB: Doing recovery: scanned up to log sequence number 138 1667824128 InnoDB: Doing recovery: scanned up to log sequence number 138 1673067008 InnoDB: Doing recovery: scanned up to log sequence number 138 1678309888 InnoDB: Doing recovery: scanned up to log sequence number 138 1683552768 InnoDB: Doing recovery: scanned up to log sequence number 138 1688795648 InnoDB: Doing recovery: scanned up to log sequence number 138 1694038528 InnoDB: Doing recovery: scanned up to log sequence number 138 1699281408 InnoDB: Doing recovery: scanned up to log sequence number 138 1704524288 InnoDB: Doing recovery: scanned up to log sequence number 138 1709767168 InnoDB: Doing recovery: scanned up to log sequence number 138 1715010048 InnoDB: Doing recovery: scanned up to log sequence number 138 1720252928 InnoDB: Doing recovery: scanned up to log sequence number 138 1725495808 InnoDB: Doing recovery: scanned up to log sequence number 138 1730738688 InnoDB: Doing recovery: scanned up to log sequence number 138 1735981568 InnoDB: Doing recovery: scanned up to log sequence number 138 1741224448 InnoDB: Doing recovery: scanned up to log sequence number 138 1746467328 InnoDB: Doing recovery: scanned up to log sequence number 138 1751710208 InnoDB: Doing recovery: scanned up to log sequence number 138 1756953088 InnoDB: Doing recovery: scanned up to log sequence number 138 1762195968 InnoDB: Doing recovery: scanned up to log sequence number 138 1767438848 InnoDB: Doing recovery: scanned up to log sequence number 138 1772681728 InnoDB: Doing recovery: scanned up to log sequence number 138 1777924608 InnoDB: Doing recovery: scanned up to log sequence number 138 1783167488 InnoDB: Doing recovery: scanned up to log sequence number 138 1788410368 InnoDB: Doing recovery: scanned up to log sequence number 138 1793653248 InnoDB: Doing recovery: scanned up to log sequence number 138 1798896128 InnoDB: Doing recovery: scanned up to log sequence number 138 1804139008 InnoDB: Doing recovery: scanned up to log sequence number 138 1809381888 InnoDB: Doing recovery: scanned up to log sequence number 138 1814624768 InnoDB: Doing recovery: scanned up to log sequence number 138 1819867648 InnoDB: Doing recovery: scanned up to log sequence number 138 1825110528 InnoDB: Doing recovery: scanned up to log sequence number 138 1830353408 InnoDB: Doing recovery: scanned up to log sequence number 138 1835596288 InnoDB: Doing recovery: scanned up to log sequence number 138 1840839168 InnoDB: Doing recovery: scanned up to log sequence number 138 1846082048 InnoDB: Doing recovery: scanned up to log sequence number 138 1851324928 InnoDB: Doing recovery: scanned up to log sequence number 138 1856567808 InnoDB: Doing recovery: scanned up to log sequence number 138 1861810688 InnoDB: Doing recovery: scanned up to log sequence number 138 1867053568 InnoDB: Doing recovery: scanned up to log sequence number 138 1872296448 071211 13:40:20 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 138 1877539328 InnoDB: Doing recovery: scanned up to log sequence number 138 1882782208 InnoDB: Doing recovery: scanned up to log sequence number 138 1888025088 InnoDB: Doing recovery: scanned up to log sequence number 138 1893267968 InnoDB: Doing recovery: scanned up to log sequence number 138 1898510848 InnoDB: Doing recovery: scanned up to log sequence number 138 1903753728 InnoDB: Doing recovery: scanned up to log sequence number 138 1908996608 InnoDB: Doing recovery: scanned up to log sequence number 138 1914239488 InnoDB: Doing recovery: scanned up to log sequence number 138 1919482368 InnoDB: Doing recovery: scanned up to log sequence number 138 1924725248 InnoDB: Doing recovery: scanned up to log sequence number 138 1929968128 InnoDB: Doing recovery: scanned up to log sequence number 138 1935211008 InnoDB: Doing recovery: scanned up to log sequence number 138 1940453888 InnoDB: Doing recovery: scanned up to log sequence number 138 1945696768 InnoDB: Doing recovery: scanned up to log sequence number 138 1950939648 InnoDB: Doing recovery: scanned up to log sequence number 138 1955706044 InnoDB: 4 transaction(s) which must be rolled back or cleaned up InnoDB: in total 47 row operations to undo InnoDB: Trx id counter is 0 1781846016 071211 13:44:22 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071211 13:44:22 InnoDB: Starting an apply batch of log records to the database... 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 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: Starting in background the rollback of uncommitted transactions 071211 13:46:13 InnoDB: Rolling back trx with id 0 1781845543, 30 rows to undo 071211 13:46:13 InnoDB: Started; log sequence number 138 1955706044 InnoDB: Rolling back of trx id 0 1781845543 completed 071211 13:46:13 InnoDB: Rolling back trx with id 0 1781845040, 13 rows to undo InnoDB: Rolling back of trx id 0 1781845040 completed 071211 13:46:13 InnoDB: Rolling back trx with id 0 1781844282, 3 rows to undo InnoDB: Rolling back of trx id 0 1781844282 completed 071211 13:46:13 InnoDB: Rolling back trx with id 0 1781844258, 1 rows to undo InnoDB: Rolling back of trx id 0 1781844258 completed 071211 13:46:13 InnoDB: Rollback of non-prepared transactions completed 071211 13:46:13 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071211 13:46:22 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071211 13:46:22 [Warning] Checking table: './tlbbdb/t_global' 071212 20:09:47 InnoDB: Error: cannot allocate 1064960 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071212 20:10:47 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=47 max_connections=100 threads_connected=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071212 20:10:47 mysqld restarted 071212 20:10:48 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... 071212 20:10:48 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 151 2202225135. InnoDB: Doing recovery: scanned up to log sequence number 151 2207467520 InnoDB: Doing recovery: scanned up to log sequence number 151 2212710400 InnoDB: Doing recovery: scanned up to log sequence number 151 2217953280 InnoDB: Doing recovery: scanned up to log sequence number 151 2223196160 InnoDB: Doing recovery: scanned up to log sequence number 151 2228439040 InnoDB: Doing recovery: scanned up to log sequence number 151 2233681920 InnoDB: Doing recovery: scanned up to log sequence number 151 2238924800 InnoDB: Doing recovery: scanned up to log sequence number 151 2244167680 InnoDB: Doing recovery: scanned up to log sequence number 151 2249410560 InnoDB: Doing recovery: scanned up to log sequence number 151 2254653440 InnoDB: Doing recovery: scanned up to log sequence number 151 2259896320 InnoDB: Doing recovery: scanned up to log sequence number 151 2265139200 InnoDB: Doing recovery: scanned up to log sequence number 151 2270382080 InnoDB: Doing recovery: scanned up to log sequence number 151 2275624960 InnoDB: Doing recovery: scanned up to log sequence number 151 2280867840 InnoDB: Doing recovery: scanned up to log sequence number 151 2286110720 InnoDB: Doing recovery: scanned up to log sequence number 151 2291353600 InnoDB: Doing recovery: scanned up to log sequence number 151 2296596480 InnoDB: Doing recovery: scanned up to log sequence number 151 2301839360 InnoDB: Doing recovery: scanned up to log sequence number 151 2307082240 InnoDB: Doing recovery: scanned up to log sequence number 151 2312325120 InnoDB: Doing recovery: scanned up to log sequence number 151 2317568000 InnoDB: Doing recovery: scanned up to log sequence number 151 2322810880 InnoDB: Doing recovery: scanned up to log sequence number 151 2328053760 InnoDB: Doing recovery: scanned up to log sequence number 151 2333296640 InnoDB: Doing recovery: scanned up to log sequence number 151 2338539520 InnoDB: Doing recovery: scanned up to log sequence number 151 2343782400 InnoDB: Doing recovery: scanned up to log sequence number 151 2349025280 InnoDB: Doing recovery: scanned up to log sequence number 151 2354268160 InnoDB: Doing recovery: scanned up to log sequence number 151 2359511040 InnoDB: Doing recovery: scanned up to log sequence number 151 2364753920 InnoDB: Doing recovery: scanned up to log sequence number 151 2369996800 InnoDB: Doing recovery: scanned up to log sequence number 151 2375239680 InnoDB: Doing recovery: scanned up to log sequence number 151 2380482560 InnoDB: Doing recovery: scanned up to log sequence number 151 2385725440 InnoDB: Doing recovery: scanned up to log sequence number 151 2390968320 InnoDB: Doing recovery: scanned up to log sequence number 151 2396211200 InnoDB: Doing recovery: scanned up to log sequence number 151 2401454080 InnoDB: Doing recovery: scanned up to log sequence number 151 2406696960 InnoDB: Doing recovery: scanned up to log sequence number 151 2411939840 InnoDB: Doing recovery: scanned up to log sequence number 151 2417182720 InnoDB: Doing recovery: scanned up to log sequence number 151 2422425600 InnoDB: Doing recovery: scanned up to log sequence number 151 2427668480 InnoDB: Doing recovery: scanned up to log sequence number 151 2432911360 InnoDB: Doing recovery: scanned up to log sequence number 151 2438154240 InnoDB: Doing recovery: scanned up to log sequence number 151 2443397120 InnoDB: Doing recovery: scanned up to log sequence number 151 2448640000 InnoDB: Doing recovery: scanned up to log sequence number 151 2453882880 InnoDB: Doing recovery: scanned up to log sequence number 151 2459125760 InnoDB: Doing recovery: scanned up to log sequence number 151 2464368640 InnoDB: Doing recovery: scanned up to log sequence number 151 2469611520 InnoDB: Doing recovery: scanned up to log sequence number 151 2474854400 InnoDB: Doing recovery: scanned up to log sequence number 151 2480097280 InnoDB: Doing recovery: scanned up to log sequence number 151 2485340160 InnoDB: Doing recovery: scanned up to log sequence number 151 2490583040 InnoDB: Doing recovery: scanned up to log sequence number 151 2495825920 InnoDB: Doing recovery: scanned up to log sequence number 151 2501068800 InnoDB: Doing recovery: scanned up to log sequence number 151 2506311680 InnoDB: Doing recovery: scanned up to log sequence number 151 2511554560 InnoDB: Doing recovery: scanned up to log sequence number 151 2516797440 InnoDB: Doing recovery: scanned up to log sequence number 151 2522040320 InnoDB: Doing recovery: scanned up to log sequence number 151 2527283200 InnoDB: Doing recovery: scanned up to log sequence number 151 2532526080 InnoDB: Doing recovery: scanned up to log sequence number 151 2537768960 InnoDB: Doing recovery: scanned up to log sequence number 151 2543011840 InnoDB: Doing recovery: scanned up to log sequence number 151 2548254720 InnoDB: Doing recovery: scanned up to log sequence number 151 2553497600 InnoDB: Doing recovery: scanned up to log sequence number 151 2558740480 InnoDB: Doing recovery: scanned up to log sequence number 151 2563983360 InnoDB: Doing recovery: scanned up to log sequence number 151 2569226240 InnoDB: Doing recovery: scanned up to log sequence number 151 2574469120 InnoDB: Doing recovery: scanned up to log sequence number 151 2579712000 InnoDB: Doing recovery: scanned up to log sequence number 151 2584954880 InnoDB: Doing recovery: scanned up to log sequence number 151 2590197760 InnoDB: Doing recovery: scanned up to log sequence number 151 2595440640 InnoDB: Doing recovery: scanned up to log sequence number 151 2600683520 InnoDB: Doing recovery: scanned up to log sequence number 151 2605926400 InnoDB: Doing recovery: scanned up to log sequence number 151 2611169280 InnoDB: Doing recovery: scanned up to log sequence number 151 2616412160 InnoDB: Doing recovery: scanned up to log sequence number 151 2621655040 InnoDB: Doing recovery: scanned up to log sequence number 151 2626897920 InnoDB: Doing recovery: scanned up to log sequence number 151 2632140800 InnoDB: Doing recovery: scanned up to log sequence number 151 2637383680 InnoDB: Doing recovery: scanned up to log sequence number 151 2642626560 InnoDB: Doing recovery: scanned up to log sequence number 151 2647869440 InnoDB: Doing recovery: scanned up to log sequence number 151 2653112320 InnoDB: Doing recovery: scanned up to log sequence number 151 2658355200 InnoDB: Doing recovery: scanned up to log sequence number 151 2663598080 InnoDB: Doing recovery: scanned up to log sequence number 151 2668840960 InnoDB: Doing recovery: scanned up to log sequence number 151 2674083840 InnoDB: Doing recovery: scanned up to log sequence number 151 2679326720 InnoDB: Doing recovery: scanned up to log sequence number 151 2684569600 InnoDB: Doing recovery: scanned up to log sequence number 151 2689812480 InnoDB: Doing recovery: scanned up to log sequence number 151 2695055360 InnoDB: Doing recovery: scanned up to log sequence number 151 2700298240 InnoDB: Doing recovery: scanned up to log sequence number 151 2705541120 InnoDB: Doing recovery: scanned up to log sequence number 151 2710784000 InnoDB: Doing recovery: scanned up to log sequence number 151 2716026880 InnoDB: Doing recovery: scanned up to log sequence number 151 2721269760 InnoDB: Doing recovery: scanned up to log sequence number 151 2726512640 InnoDB: Doing recovery: scanned up to log sequence number 151 2731755520 InnoDB: Doing recovery: scanned up to log sequence number 151 2736998400 InnoDB: Doing recovery: scanned up to log sequence number 151 2742241280 InnoDB: Doing recovery: scanned up to log sequence number 151 2747484160 InnoDB: Doing recovery: scanned up to log sequence number 151 2752727040 InnoDB: Doing recovery: scanned up to log sequence number 151 2757969920 InnoDB: Doing recovery: scanned up to log sequence number 151 2763212800 InnoDB: Doing recovery: scanned up to log sequence number 151 2768455680 InnoDB: Doing recovery: scanned up to log sequence number 151 2773698560 InnoDB: Doing recovery: scanned up to log sequence number 151 2778941440 InnoDB: Doing recovery: scanned up to log sequence number 151 2784184320 InnoDB: Doing recovery: scanned up to log sequence number 151 2789427200 InnoDB: Doing recovery: scanned up to log sequence number 151 2794670080 InnoDB: Doing recovery: scanned up to log sequence number 151 2799912960 InnoDB: Doing recovery: scanned up to log sequence number 151 2805155840 InnoDB: Doing recovery: scanned up to log sequence number 151 2810398720 InnoDB: Doing recovery: scanned up to log sequence number 151 2815641600 InnoDB: Doing recovery: scanned up to log sequence number 151 2820884480 InnoDB: Doing recovery: scanned up to log sequence number 151 2826127360 InnoDB: Doing recovery: scanned up to log sequence number 151 2831370240 InnoDB: Doing recovery: scanned up to log sequence number 151 2836613120 InnoDB: Doing recovery: scanned up to log sequence number 151 2841856000 InnoDB: Doing recovery: scanned up to log sequence number 151 2847098880 InnoDB: Doing recovery: scanned up to log sequence number 151 2852341760 InnoDB: Doing recovery: scanned up to log sequence number 151 2857584640 InnoDB: Doing recovery: scanned up to log sequence number 151 2862827520 InnoDB: Doing recovery: scanned up to log sequence number 151 2868070400 InnoDB: Doing recovery: scanned up to log sequence number 151 2873313280 InnoDB: Doing recovery: scanned up to log sequence number 151 2878556160 InnoDB: Doing recovery: scanned up to log sequence number 151 2883799040 InnoDB: Doing recovery: scanned up to log sequence number 151 2889041920 InnoDB: Doing recovery: scanned up to log sequence number 151 2894284800 InnoDB: Doing recovery: scanned up to log sequence number 151 2899527680 InnoDB: Doing recovery: scanned up to log sequence number 151 2904770560 InnoDB: Doing recovery: scanned up to log sequence number 151 2910013440 InnoDB: Doing recovery: scanned up to log sequence number 151 2915256320 InnoDB: Doing recovery: scanned up to log sequence number 151 2920499200 InnoDB: Doing recovery: scanned up to log sequence number 151 2925742080 InnoDB: Doing recovery: scanned up to log sequence number 151 2930984960 InnoDB: Doing recovery: scanned up to log sequence number 151 2936227840 InnoDB: Doing recovery: scanned up to log sequence number 151 2941470720 InnoDB: Doing recovery: scanned up to log sequence number 151 2946713600 InnoDB: Doing recovery: scanned up to log sequence number 151 2951956480 InnoDB: Doing recovery: scanned up to log sequence number 151 2957199360 InnoDB: Doing recovery: scanned up to log sequence number 151 2962442240 InnoDB: Doing recovery: scanned up to log sequence number 151 2967685120 InnoDB: Doing recovery: scanned up to log sequence number 151 2972928000 InnoDB: Doing recovery: scanned up to log sequence number 151 2978170880 InnoDB: Doing recovery: scanned up to log sequence number 151 2983413760 InnoDB: Doing recovery: scanned up to log sequence number 151 2988656640 InnoDB: Doing recovery: scanned up to log sequence number 151 2993899520 InnoDB: Doing recovery: scanned up to log sequence number 151 2999142400 InnoDB: Doing recovery: scanned up to log sequence number 151 3004385280 InnoDB: Doing recovery: scanned up to log sequence number 151 3009628160 InnoDB: Doing recovery: scanned up to log sequence number 151 3014871040 071212 20:13:23 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 151 3020113920 InnoDB: Doing recovery: scanned up to log sequence number 151 3025356800 InnoDB: Doing recovery: scanned up to log sequence number 151 3030599680 InnoDB: Doing recovery: scanned up to log sequence number 151 3035842560 InnoDB: Doing recovery: scanned up to log sequence number 151 3041085440 InnoDB: Doing recovery: scanned up to log sequence number 151 3046328320 InnoDB: Doing recovery: scanned up to log sequence number 151 3051571200 InnoDB: Doing recovery: scanned up to log sequence number 151 3056814080 InnoDB: Doing recovery: scanned up to log sequence number 151 3062056960 InnoDB: Doing recovery: scanned up to log sequence number 151 3067299840 InnoDB: Doing recovery: scanned up to log sequence number 151 3072542720 InnoDB: Doing recovery: scanned up to log sequence number 151 3077785600 InnoDB: Doing recovery: scanned up to log sequence number 151 3083028480 InnoDB: Doing recovery: scanned up to log sequence number 151 3088271360 InnoDB: Doing recovery: scanned up to log sequence number 151 3093514240 InnoDB: Doing recovery: scanned up to log sequence number 151 3096522970 InnoDB: 3 transaction(s) which must be rolled back or cleaned up InnoDB: in total 21 row operations to undo InnoDB: Trx id counter is 0 1955850240 071212 20:17:23 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071212 20:17:23 InnoDB: Starting an apply batch of log records to the database... 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 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 071212 20:19:12 InnoDB: Started; log sequence number 151 3096522970 InnoDB: Starting in background the rollback of uncommitted transactions 071212 20:19:12 InnoDB: Rolling back trx with id 0 1955849392, 19 rows to undo InnoDB: Rolling back of trx id 0 1955849392 completed 071212 20:19:12 InnoDB: Rolling back trx with id 0 1955848866, 1 rows to undo InnoDB: Rolling back of trx id 0 1955848866 completed 071212 20:19:12 InnoDB: Rolling back trx with id 0 1955846722, 1 rows to undo InnoDB: Rolling back of trx id 0 1955846722 completed 071212 20:19:12 InnoDB: Rollback of non-prepared transactions completed 071212 20:19:12 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071212 20:19:17 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071212 20:19:17 [Warning] Checking table: './tlbbdb/t_global' 071214 6:58:12 InnoDB: Error: cannot allocate 983040 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071214 6:59:12 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=47 max_connections=100 threads_connected=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071214 06:59:12 mysqld restarted 071214 6:59:13 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... 071214 6:59:13 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 165 457001680. InnoDB: Doing recovery: scanned up to log sequence number 165 462244352 InnoDB: Doing recovery: scanned up to log sequence number 165 467487232 InnoDB: Doing recovery: scanned up to log sequence number 165 472730112 InnoDB: Doing recovery: scanned up to log sequence number 165 477972992 InnoDB: Doing recovery: scanned up to log sequence number 165 483215872 InnoDB: Doing recovery: scanned up to log sequence number 165 488458752 InnoDB: Doing recovery: scanned up to log sequence number 165 493701632 InnoDB: Doing recovery: scanned up to log sequence number 165 498944512 InnoDB: Doing recovery: scanned up to log sequence number 165 504187392 InnoDB: Doing recovery: scanned up to log sequence number 165 509430272 InnoDB: Doing recovery: scanned up to log sequence number 165 514673152 InnoDB: Doing recovery: scanned up to log sequence number 165 519916032 InnoDB: Doing recovery: scanned up to log sequence number 165 525158912 InnoDB: Doing recovery: scanned up to log sequence number 165 530401792 InnoDB: Doing recovery: scanned up to log sequence number 165 535644672 InnoDB: Doing recovery: scanned up to log sequence number 165 540887552 InnoDB: Doing recovery: scanned up to log sequence number 165 546130432 InnoDB: Doing recovery: scanned up to log sequence number 165 551373312 InnoDB: Doing recovery: scanned up to log sequence number 165 556616192 InnoDB: Doing recovery: scanned up to log sequence number 165 561859072 InnoDB: Doing recovery: scanned up to log sequence number 165 567101952 InnoDB: Doing recovery: scanned up to log sequence number 165 572344832 InnoDB: Doing recovery: scanned up to log sequence number 165 577587712 InnoDB: Doing recovery: scanned up to log sequence number 165 582830592 InnoDB: Doing recovery: scanned up to log sequence number 165 588073472 InnoDB: Doing recovery: scanned up to log sequence number 165 593316352 InnoDB: Doing recovery: scanned up to log sequence number 165 598559232 InnoDB: Doing recovery: scanned up to log sequence number 165 603802112 InnoDB: Doing recovery: scanned up to log sequence number 165 609044992 InnoDB: Doing recovery: scanned up to log sequence number 165 614287872 InnoDB: Doing recovery: scanned up to log sequence number 165 619530752 InnoDB: Doing recovery: scanned up to log sequence number 165 624773632 InnoDB: Doing recovery: scanned up to log sequence number 165 630016512 InnoDB: Doing recovery: scanned up to log sequence number 165 635259392 InnoDB: Doing recovery: scanned up to log sequence number 165 640502272 InnoDB: Doing recovery: scanned up to log sequence number 165 645745152 InnoDB: Doing recovery: scanned up to log sequence number 165 650988032 InnoDB: Doing recovery: scanned up to log sequence number 165 656230912 InnoDB: Doing recovery: scanned up to log sequence number 165 661473792 InnoDB: Doing recovery: scanned up to log sequence number 165 666716672 InnoDB: Doing recovery: scanned up to log sequence number 165 671959552 InnoDB: Doing recovery: scanned up to log sequence number 165 677202432 InnoDB: Doing recovery: scanned up to log sequence number 165 682445312 InnoDB: Doing recovery: scanned up to log sequence number 165 687688192 InnoDB: Doing recovery: scanned up to log sequence number 165 692931072 InnoDB: Doing recovery: scanned up to log sequence number 165 698173952 InnoDB: Doing recovery: scanned up to log sequence number 165 703416832 InnoDB: Doing recovery: scanned up to log sequence number 165 708659712 InnoDB: Doing recovery: scanned up to log sequence number 165 713902592 InnoDB: Doing recovery: scanned up to log sequence number 165 719145472 InnoDB: Doing recovery: scanned up to log sequence number 165 724388352 InnoDB: Doing recovery: scanned up to log sequence number 165 729631232 InnoDB: Doing recovery: scanned up to log sequence number 165 734874112 InnoDB: Doing recovery: scanned up to log sequence number 165 740116992 InnoDB: Doing recovery: scanned up to log sequence number 165 745359872 InnoDB: Doing recovery: scanned up to log sequence number 165 750602752 InnoDB: Doing recovery: scanned up to log sequence number 165 755845632 InnoDB: Doing recovery: scanned up to log sequence number 165 761088512 InnoDB: Doing recovery: scanned up to log sequence number 165 766331392 InnoDB: Doing recovery: scanned up to log sequence number 165 771574272 InnoDB: Doing recovery: scanned up to log sequence number 165 776817152 InnoDB: Doing recovery: scanned up to log sequence number 165 782060032 InnoDB: Doing recovery: scanned up to log sequence number 165 787302912 InnoDB: Doing recovery: scanned up to log sequence number 165 792545792 InnoDB: Doing recovery: scanned up to log sequence number 165 797788672 InnoDB: Doing recovery: scanned up to log sequence number 165 803031552 InnoDB: Doing recovery: scanned up to log sequence number 165 808274432 InnoDB: Doing recovery: scanned up to log sequence number 165 813517312 InnoDB: Doing recovery: scanned up to log sequence number 165 818760192 InnoDB: Doing recovery: scanned up to log sequence number 165 824003072 InnoDB: Doing recovery: scanned up to log sequence number 165 829245952 InnoDB: Doing recovery: scanned up to log sequence number 165 834488832 InnoDB: Doing recovery: scanned up to log sequence number 165 839731712 InnoDB: Doing recovery: scanned up to log sequence number 165 844974592 InnoDB: Doing recovery: scanned up to log sequence number 165 850217472 InnoDB: Doing recovery: scanned up to log sequence number 165 855460352 InnoDB: Doing recovery: scanned up to log sequence number 165 860703232 InnoDB: Doing recovery: scanned up to log sequence number 165 865946112 InnoDB: Doing recovery: scanned up to log sequence number 165 871188992 InnoDB: Doing recovery: scanned up to log sequence number 165 876431872 InnoDB: Doing recovery: scanned up to log sequence number 165 881674752 InnoDB: Doing recovery: scanned up to log sequence number 165 886917632 InnoDB: Doing recovery: scanned up to log sequence number 165 892160512 InnoDB: Doing recovery: scanned up to log sequence number 165 897403392 InnoDB: Doing recovery: scanned up to log sequence number 165 902646272 InnoDB: Doing recovery: scanned up to log sequence number 165 907889152 InnoDB: Doing recovery: scanned up to log sequence number 165 913132032 InnoDB: Doing recovery: scanned up to log sequence number 165 918374912 InnoDB: Doing recovery: scanned up to log sequence number 165 923617792 InnoDB: Doing recovery: scanned up to log sequence number 165 928860672 InnoDB: Doing recovery: scanned up to log sequence number 165 934103552 InnoDB: Doing recovery: scanned up to log sequence number 165 939346432 InnoDB: Doing recovery: scanned up to log sequence number 165 944589312 InnoDB: Doing recovery: scanned up to log sequence number 165 949832192 InnoDB: Doing recovery: scanned up to log sequence number 165 955075072 InnoDB: Doing recovery: scanned up to log sequence number 165 960317952 InnoDB: Doing recovery: scanned up to log sequence number 165 965560832 InnoDB: Doing recovery: scanned up to log sequence number 165 970803712 InnoDB: Doing recovery: scanned up to log sequence number 165 976046592 InnoDB: Doing recovery: scanned up to log sequence number 165 981289472 InnoDB: Doing recovery: scanned up to log sequence number 165 986532352 InnoDB: Doing recovery: scanned up to log sequence number 165 991775232 InnoDB: Doing recovery: scanned up to log sequence number 165 997018112 InnoDB: Doing recovery: scanned up to log sequence number 165 1002260992 InnoDB: Doing recovery: scanned up to log sequence number 165 1007503872 InnoDB: Doing recovery: scanned up to log sequence number 165 1012746752 InnoDB: Doing recovery: scanned up to log sequence number 165 1017989632 InnoDB: Doing recovery: scanned up to log sequence number 165 1023232512 InnoDB: Doing recovery: scanned up to log sequence number 165 1028475392 InnoDB: Doing recovery: scanned up to log sequence number 165 1033718272 InnoDB: Doing recovery: scanned up to log sequence number 165 1038961152 InnoDB: Doing recovery: scanned up to log sequence number 165 1044204032 InnoDB: Doing recovery: scanned up to log sequence number 165 1049446912 InnoDB: Doing recovery: scanned up to log sequence number 165 1054689792 InnoDB: Doing recovery: scanned up to log sequence number 165 1059932672 InnoDB: Doing recovery: scanned up to log sequence number 165 1065175552 InnoDB: Doing recovery: scanned up to log sequence number 165 1070418432 InnoDB: Doing recovery: scanned up to log sequence number 165 1075661312 InnoDB: Doing recovery: scanned up to log sequence number 165 1080904192 InnoDB: Doing recovery: scanned up to log sequence number 165 1086147072 InnoDB: Doing recovery: scanned up to log sequence number 165 1091389952 InnoDB: Doing recovery: scanned up to log sequence number 165 1096632832 InnoDB: Doing recovery: scanned up to log sequence number 165 1101875712 InnoDB: Doing recovery: scanned up to log sequence number 165 1107118592 InnoDB: Doing recovery: scanned up to log sequence number 165 1112361472 InnoDB: Doing recovery: scanned up to log sequence number 165 1117604352 InnoDB: Doing recovery: scanned up to log sequence number 165 1122847232 InnoDB: Doing recovery: scanned up to log sequence number 165 1128090112 InnoDB: Doing recovery: scanned up to log sequence number 165 1133332992 InnoDB: Doing recovery: scanned up to log sequence number 165 1138575872 InnoDB: Doing recovery: scanned up to log sequence number 165 1143818752 InnoDB: Doing recovery: scanned up to log sequence number 165 1149061632 InnoDB: Doing recovery: scanned up to log sequence number 165 1154304512 InnoDB: Doing recovery: scanned up to log sequence number 165 1159547392 InnoDB: Doing recovery: scanned up to log sequence number 165 1164790272 InnoDB: Doing recovery: scanned up to log sequence number 165 1170033152 InnoDB: Doing recovery: scanned up to log sequence number 165 1175276032 InnoDB: Doing recovery: scanned up to log sequence number 165 1180518912 InnoDB: Doing recovery: scanned up to log sequence number 165 1185761792 InnoDB: Doing recovery: scanned up to log sequence number 165 1191004672 InnoDB: Doing recovery: scanned up to log sequence number 165 1196247552 InnoDB: Doing recovery: scanned up to log sequence number 165 1201490432 InnoDB: Doing recovery: scanned up to log sequence number 165 1206733312 InnoDB: Doing recovery: scanned up to log sequence number 165 1211976192 InnoDB: Doing recovery: scanned up to log sequence number 165 1217219072 InnoDB: Doing recovery: scanned up to log sequence number 165 1222461952 InnoDB: Doing recovery: scanned up to log sequence number 165 1227704832 InnoDB: Doing recovery: scanned up to log sequence number 165 1232947712 InnoDB: Doing recovery: scanned up to log sequence number 165 1238190592 InnoDB: Doing recovery: scanned up to log sequence number 165 1243433472 InnoDB: Doing recovery: scanned up to log sequence number 165 1248676352 InnoDB: Doing recovery: scanned up to log sequence number 165 1253919232 InnoDB: Doing recovery: scanned up to log sequence number 165 1259162112 InnoDB: Doing recovery: scanned up to log sequence number 165 1264404992 InnoDB: Doing recovery: scanned up to log sequence number 165 1269647872 071214 7:01:47 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 165 1274890752 InnoDB: Doing recovery: scanned up to log sequence number 165 1280133632 InnoDB: Doing recovery: scanned up to log sequence number 165 1285376512 InnoDB: Doing recovery: scanned up to log sequence number 165 1290619392 InnoDB: Doing recovery: scanned up to log sequence number 165 1295862272 InnoDB: Doing recovery: scanned up to log sequence number 165 1301105152 InnoDB: Doing recovery: scanned up to log sequence number 165 1306348032 InnoDB: Doing recovery: scanned up to log sequence number 165 1311590912 InnoDB: Doing recovery: scanned up to log sequence number 165 1316833792 InnoDB: Doing recovery: scanned up to log sequence number 165 1322076672 InnoDB: Doing recovery: scanned up to log sequence number 165 1327319552 InnoDB: Doing recovery: scanned up to log sequence number 165 1332562432 InnoDB: Doing recovery: scanned up to log sequence number 165 1337805312 InnoDB: Doing recovery: scanned up to log sequence number 165 1343048192 InnoDB: Doing recovery: scanned up to log sequence number 165 1347985992 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 2131196672 071214 7:04:43 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071214 7:04:43 InnoDB: Starting an apply batch of log records to the database... 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 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: Starting in background the rollback of uncommitted transactions 071214 7:06:19 InnoDB: Rolling back trx with id 0 2131196243, 1 rows to undo 071214 7:06:19 InnoDB: Started; log sequence number 165 1347985992 InnoDB: Rolling back of trx id 0 2131196243 completed 071214 7:06:19 InnoDB: Rollback of non-prepared transactions completed 071214 7:06:19 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071214 7:06:25 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071214 7:06:25 [Warning] Checking table: './tlbbdb/t_global' 071215 13:12:41 InnoDB: Error: cannot allocate 884736 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071215 13:13:41 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=46 max_connections=100 threads_connected=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071215 13:13:41 mysqld restarted 071215 13:13:42 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... 071215 13:13:42 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 178 1432850013. InnoDB: Doing recovery: scanned up to log sequence number 178 1438092800 InnoDB: Doing recovery: scanned up to log sequence number 178 1443335680 InnoDB: Doing recovery: scanned up to log sequence number 178 1448578560 InnoDB: Doing recovery: scanned up to log sequence number 178 1453821440 InnoDB: Doing recovery: scanned up to log sequence number 178 1459064320 InnoDB: Doing recovery: scanned up to log sequence number 178 1464307200 InnoDB: Doing recovery: scanned up to log sequence number 178 1469550080 InnoDB: Doing recovery: scanned up to log sequence number 178 1474792960 InnoDB: Doing recovery: scanned up to log sequence number 178 1480035840 InnoDB: Doing recovery: scanned up to log sequence number 178 1485278720 InnoDB: Doing recovery: scanned up to log sequence number 178 1490521600 InnoDB: Doing recovery: scanned up to log sequence number 178 1495764480 InnoDB: Doing recovery: scanned up to log sequence number 178 1501007360 InnoDB: Doing recovery: scanned up to log sequence number 178 1506250240 InnoDB: Doing recovery: scanned up to log sequence number 178 1511493120 InnoDB: Doing recovery: scanned up to log sequence number 178 1516736000 InnoDB: Doing recovery: scanned up to log sequence number 178 1521978880 InnoDB: Doing recovery: scanned up to log sequence number 178 1527221760 InnoDB: Doing recovery: scanned up to log sequence number 178 1532464640 InnoDB: Doing recovery: scanned up to log sequence number 178 1537707520 InnoDB: Doing recovery: scanned up to log sequence number 178 1542950400 InnoDB: Doing recovery: scanned up to log sequence number 178 1548193280 InnoDB: Doing recovery: scanned up to log sequence number 178 1553436160 InnoDB: Doing recovery: scanned up to log sequence number 178 1558679040 InnoDB: Doing recovery: scanned up to log sequence number 178 1563921920 InnoDB: Doing recovery: scanned up to log sequence number 178 1569164800 InnoDB: Doing recovery: scanned up to log sequence number 178 1574407680 InnoDB: Doing recovery: scanned up to log sequence number 178 1579650560 InnoDB: Doing recovery: scanned up to log sequence number 178 1584893440 InnoDB: Doing recovery: scanned up to log sequence number 178 1590136320 InnoDB: Doing recovery: scanned up to log sequence number 178 1595379200 InnoDB: Doing recovery: scanned up to log sequence number 178 1600622080 InnoDB: Doing recovery: scanned up to log sequence number 178 1605864960 InnoDB: Doing recovery: scanned up to log sequence number 178 1611107840 InnoDB: Doing recovery: scanned up to log sequence number 178 1616350720 InnoDB: Doing recovery: scanned up to log sequence number 178 1621593600 InnoDB: Doing recovery: scanned up to log sequence number 178 1626836480 InnoDB: Doing recovery: scanned up to log sequence number 178 1632079360 InnoDB: Doing recovery: scanned up to log sequence number 178 1637322240 InnoDB: Doing recovery: scanned up to log sequence number 178 1642565120 InnoDB: Doing recovery: scanned up to log sequence number 178 1647808000 InnoDB: Doing recovery: scanned up to log sequence number 178 1653050880 InnoDB: Doing recovery: scanned up to log sequence number 178 1658293760 InnoDB: Doing recovery: scanned up to log sequence number 178 1663536640 InnoDB: Doing recovery: scanned up to log sequence number 178 1668779520 InnoDB: Doing recovery: scanned up to log sequence number 178 1674022400 InnoDB: Doing recovery: scanned up to log sequence number 178 1679265280 InnoDB: Doing recovery: scanned up to log sequence number 178 1684508160 InnoDB: Doing recovery: scanned up to log sequence number 178 1689751040 InnoDB: Doing recovery: scanned up to log sequence number 178 1694993920 InnoDB: Doing recovery: scanned up to log sequence number 178 1700236800 InnoDB: Doing recovery: scanned up to log sequence number 178 1705479680 InnoDB: Doing recovery: scanned up to log sequence number 178 1710722560 InnoDB: Doing recovery: scanned up to log sequence number 178 1715965440 InnoDB: Doing recovery: scanned up to log sequence number 178 1721208320 InnoDB: Doing recovery: scanned up to log sequence number 178 1726451200 InnoDB: Doing recovery: scanned up to log sequence number 178 1731694080 InnoDB: Doing recovery: scanned up to log sequence number 178 1736936960 InnoDB: Doing recovery: scanned up to log sequence number 178 1742179840 InnoDB: Doing recovery: scanned up to log sequence number 178 1747422720 InnoDB: Doing recovery: scanned up to log sequence number 178 1752665600 InnoDB: Doing recovery: scanned up to log sequence number 178 1757908480 InnoDB: Doing recovery: scanned up to log sequence number 178 1763151360 InnoDB: Doing recovery: scanned up to log sequence number 178 1768394240 InnoDB: Doing recovery: scanned up to log sequence number 178 1773637120 InnoDB: Doing recovery: scanned up to log sequence number 178 1778880000 InnoDB: Doing recovery: scanned up to log sequence number 178 1784122880 InnoDB: Doing recovery: scanned up to log sequence number 178 1789365760 InnoDB: Doing recovery: scanned up to log sequence number 178 1794608640 InnoDB: Doing recovery: scanned up to log sequence number 178 1799851520 InnoDB: Doing recovery: scanned up to log sequence number 178 1805094400 InnoDB: Doing recovery: scanned up to log sequence number 178 1810337280 InnoDB: Doing recovery: scanned up to log sequence number 178 1815580160 InnoDB: Doing recovery: scanned up to log sequence number 178 1820823040 InnoDB: Doing recovery: scanned up to log sequence number 178 1826065920 InnoDB: Doing recovery: scanned up to log sequence number 178 1831308800 InnoDB: Doing recovery: scanned up to log sequence number 178 1836551680 InnoDB: Doing recovery: scanned up to log sequence number 178 1841794560 InnoDB: Doing recovery: scanned up to log sequence number 178 1847037440 InnoDB: Doing recovery: scanned up to log sequence number 178 1852280320 InnoDB: Doing recovery: scanned up to log sequence number 178 1857523200 InnoDB: Doing recovery: scanned up to log sequence number 178 1862766080 InnoDB: Doing recovery: scanned up to log sequence number 178 1868008960 InnoDB: Doing recovery: scanned up to log sequence number 178 1873251840 InnoDB: Doing recovery: scanned up to log sequence number 178 1878494720 InnoDB: Doing recovery: scanned up to log sequence number 178 1883737600 InnoDB: Doing recovery: scanned up to log sequence number 178 1888980480 InnoDB: Doing recovery: scanned up to log sequence number 178 1894223360 InnoDB: Doing recovery: scanned up to log sequence number 178 1899466240 InnoDB: Doing recovery: scanned up to log sequence number 178 1904709120 InnoDB: Doing recovery: scanned up to log sequence number 178 1909952000 InnoDB: Doing recovery: scanned up to log sequence number 178 1915194880 InnoDB: Doing recovery: scanned up to log sequence number 178 1920437760 InnoDB: Doing recovery: scanned up to log sequence number 178 1925680640 InnoDB: Doing recovery: scanned up to log sequence number 178 1930923520 InnoDB: Doing recovery: scanned up to log sequence number 178 1936166400 InnoDB: Doing recovery: scanned up to log sequence number 178 1941409280 InnoDB: Doing recovery: scanned up to log sequence number 178 1946652160 InnoDB: Doing recovery: scanned up to log sequence number 178 1951895040 InnoDB: Doing recovery: scanned up to log sequence number 178 1957137920 InnoDB: Doing recovery: scanned up to log sequence number 178 1962380800 InnoDB: Doing recovery: scanned up to log sequence number 178 1967623680 InnoDB: Doing recovery: scanned up to log sequence number 178 1972866560 InnoDB: Doing recovery: scanned up to log sequence number 178 1978109440 InnoDB: Doing recovery: scanned up to log sequence number 178 1983352320 InnoDB: Doing recovery: scanned up to log sequence number 178 1988595200 InnoDB: Doing recovery: scanned up to log sequence number 178 1993838080 InnoDB: Doing recovery: scanned up to log sequence number 178 1999080960 InnoDB: Doing recovery: scanned up to log sequence number 178 2004323840 InnoDB: Doing recovery: scanned up to log sequence number 178 2009566720 InnoDB: Doing recovery: scanned up to log sequence number 178 2014809600 InnoDB: Doing recovery: scanned up to log sequence number 178 2020052480 InnoDB: Doing recovery: scanned up to log sequence number 178 2025295360 InnoDB: Doing recovery: scanned up to log sequence number 178 2030538240 InnoDB: Doing recovery: scanned up to log sequence number 178 2035781120 InnoDB: Doing recovery: scanned up to log sequence number 178 2041024000 InnoDB: Doing recovery: scanned up to log sequence number 178 2046266880 InnoDB: Doing recovery: scanned up to log sequence number 178 2051509760 InnoDB: Doing recovery: scanned up to log sequence number 178 2056752640 InnoDB: Doing recovery: scanned up to log sequence number 178 2061995520 InnoDB: Doing recovery: scanned up to log sequence number 178 2067238400 InnoDB: Doing recovery: scanned up to log sequence number 178 2072481280 InnoDB: Doing recovery: scanned up to log sequence number 178 2077724160 InnoDB: Doing recovery: scanned up to log sequence number 178 2082967040 InnoDB: Doing recovery: scanned up to log sequence number 178 2088209920 InnoDB: Doing recovery: scanned up to log sequence number 178 2093452800 InnoDB: Doing recovery: scanned up to log sequence number 178 2098695680 InnoDB: Doing recovery: scanned up to log sequence number 178 2103938560 InnoDB: Doing recovery: scanned up to log sequence number 178 2109181440 InnoDB: Doing recovery: scanned up to log sequence number 178 2114424320 InnoDB: Doing recovery: scanned up to log sequence number 178 2119667200 InnoDB: Doing recovery: scanned up to log sequence number 178 2124910080 InnoDB: Doing recovery: scanned up to log sequence number 178 2130152960 InnoDB: Doing recovery: scanned up to log sequence number 178 2135395840 InnoDB: Doing recovery: scanned up to log sequence number 178 2140638720 InnoDB: Doing recovery: scanned up to log sequence number 178 2145881600 InnoDB: Doing recovery: scanned up to log sequence number 178 2151124480 InnoDB: Doing recovery: scanned up to log sequence number 178 2156367360 InnoDB: Doing recovery: scanned up to log sequence number 178 2161610240 InnoDB: Doing recovery: scanned up to log sequence number 178 2166853120 InnoDB: Doing recovery: scanned up to log sequence number 178 2172096000 InnoDB: Doing recovery: scanned up to log sequence number 178 2177338880 InnoDB: Doing recovery: scanned up to log sequence number 178 2182581760 InnoDB: Doing recovery: scanned up to log sequence number 178 2187824640 InnoDB: Doing recovery: scanned up to log sequence number 178 2193067520 InnoDB: Doing recovery: scanned up to log sequence number 178 2198310400 InnoDB: Doing recovery: scanned up to log sequence number 178 2203553280 InnoDB: Doing recovery: scanned up to log sequence number 178 2208796160 InnoDB: Doing recovery: scanned up to log sequence number 178 2214039040 InnoDB: Doing recovery: scanned up to log sequence number 178 2219281920 InnoDB: Doing recovery: scanned up to log sequence number 178 2224524800 InnoDB: Doing recovery: scanned up to log sequence number 178 2229767680 InnoDB: Doing recovery: scanned up to log sequence number 178 2235010560 InnoDB: Doing recovery: scanned up to log sequence number 178 2240253440 InnoDB: Doing recovery: scanned up to log sequence number 178 2245496320 InnoDB: Doing recovery: scanned up to log sequence number 178 2250739200 071215 13:16:17 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 178 2255982080 InnoDB: Doing recovery: scanned up to log sequence number 178 2261224960 InnoDB: Doing recovery: scanned up to log sequence number 178 2266467840 InnoDB: Doing recovery: scanned up to log sequence number 178 2271710720 InnoDB: Doing recovery: scanned up to log sequence number 178 2276953600 InnoDB: Doing recovery: scanned up to log sequence number 178 2282196480 InnoDB: Doing recovery: scanned up to log sequence number 178 2287439360 InnoDB: Doing recovery: scanned up to log sequence number 178 2292682240 InnoDB: Doing recovery: scanned up to log sequence number 178 2297925120 InnoDB: Doing recovery: scanned up to log sequence number 178 2303168000 InnoDB: Doing recovery: scanned up to log sequence number 178 2308410880 InnoDB: Doing recovery: scanned up to log sequence number 178 2313653760 InnoDB: Doing recovery: scanned up to log sequence number 178 2318896640 InnoDB: Doing recovery: scanned up to log sequence number 178 2323908865 InnoDB: 4 transaction(s) which must be rolled back or cleaned up InnoDB: in total 131 row operations to undo InnoDB: Trx id counter is 0 2301806080 071215 13:20:02 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071215 13:20:02 InnoDB: Starting an apply batch of log records to the database... 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 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 071215 13:21:50 InnoDB: Started; log sequence number 178 2323908865 InnoDB: Starting in background the rollback of uncommitted transactions 071215 13:21:50 InnoDB: Rolling back trx with id 0 2301805568, 17 rows to undo InnoDB: Rolling back of trx id 0 2301805568 completed 071215 13:21:50 InnoDB: Rolling back trx with id 0 2301805564, 80 rows to undo 071215 13:21:50 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) InnoDB: Rolling back of trx id 0 2301805564 completed 071215 13:21:50 InnoDB: Rolling back trx with id 0 2301805430, 33 rows to undo InnoDB: Rolling back of trx id 0 2301805430 completed 071215 13:21:50 InnoDB: Rolling back trx with id 0 2301805396, 1 rows to undo InnoDB: Rolling back of trx id 0 2301805396 completed 071215 13:21:50 InnoDB: Rollback of non-prepared transactions completed 071215 13:21:50 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071215 13:21:50 [Warning] Checking table: './tlbbdb/t_global' 071216 15:45:30 InnoDB: Error: cannot allocate 606208 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 2319029454 bytes. Operating system errno: 12 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process InnoDB: memory space is limited to 2 GB or 4 GB. InnoDB: We keep retrying the allocation for 60 seconds... 071216 15:46:30 InnoDB: We now intentionally generate a seg fault so that InnoDB: on Linux we get a stack trace. 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=67108864 read_buffer_size=1044480 max_used_connections=46 max_connections=100 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0x2adb3f2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x8379b72 0x8379bac 0x837e62c 0x834e70c 0x8295f95 0xaa3371 0xa0dffe 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 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. Number of processes running now: 0 071216 15:46:31 mysqld restarted 071216 15:46:31 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... 071216 15:46:31 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 192 1223556267. InnoDB: Doing recovery: scanned up to log sequence number 192 1228798976 InnoDB: Doing recovery: scanned up to log sequence number 192 1234041856 InnoDB: Doing recovery: scanned up to log sequence number 192 1239284736 InnoDB: Doing recovery: scanned up to log sequence number 192 1244527616 InnoDB: Doing recovery: scanned up to log sequence number 192 1249770496 InnoDB: Doing recovery: scanned up to log sequence number 192 1255013376 InnoDB: Doing recovery: scanned up to log sequence number 192 1260256256 InnoDB: Doing recovery: scanned up to log sequence number 192 1265499136 InnoDB: Doing recovery: scanned up to log sequence number 192 1270742016 InnoDB: Doing recovery: scanned up to log sequence number 192 1275984896 InnoDB: Doing recovery: scanned up to log sequence number 192 1281227776 InnoDB: Doing recovery: scanned up to log sequence number 192 1286470656 InnoDB: Doing recovery: scanned up to log sequence number 192 1291713536 InnoDB: Doing recovery: scanned up to log sequence number 192 1296956416 InnoDB: Doing recovery: scanned up to log sequence number 192 1302199296 InnoDB: Doing recovery: scanned up to log sequence number 192 1307442176 InnoDB: Doing recovery: scanned up to log sequence number 192 1312685056 InnoDB: Doing recovery: scanned up to log sequence number 192 1317927936 InnoDB: Doing recovery: scanned up to log sequence number 192 1323170816 InnoDB: Doing recovery: scanned up to log sequence number 192 1328413696 InnoDB: Doing recovery: scanned up to log sequence number 192 1333656576 InnoDB: Doing recovery: scanned up to log sequence number 192 1338899456 InnoDB: Doing recovery: scanned up to log sequence number 192 1344142336 InnoDB: Doing recovery: scanned up to log sequence number 192 1349385216 InnoDB: Doing recovery: scanned up to log sequence number 192 1354628096 InnoDB: Doing recovery: scanned up to log sequence number 192 1359870976 InnoDB: Doing recovery: scanned up to log sequence number 192 1365113856 InnoDB: Doing recovery: scanned up to log sequence number 192 1370356736 InnoDB: Doing recovery: scanned up to log sequence number 192 1375599616 InnoDB: Doing recovery: scanned up to log sequence number 192 1380842496 InnoDB: Doing recovery: scanned up to log sequence number 192 1386085376 InnoDB: Doing recovery: scanned up to log sequence number 192 1391328256 InnoDB: Doing recovery: scanned up to log sequence number 192 1396571136 InnoDB: Doing recovery: scanned up to log sequence number 192 1401814016 InnoDB: Doing recovery: scanned up to log sequence number 192 1407056896 InnoDB: Doing recovery: scanned up to log sequence number 192 1412299776 InnoDB: Doing recovery: scanned up to log sequence number 192 1417542656 InnoDB: Doing recovery: scanned up to log sequence number 192 1422785536 InnoDB: Doing recovery: scanned up to log sequence number 192 1428028416 InnoDB: Doing recovery: scanned up to log sequence number 192 1433271296 InnoDB: Doing recovery: scanned up to log sequence number 192 1438514176 InnoDB: Doing recovery: scanned up to log sequence number 192 1443757056 InnoDB: Doing recovery: scanned up to log sequence number 192 1448999936 InnoDB: Doing recovery: scanned up to log sequence number 192 1454242816 InnoDB: Doing recovery: scanned up to log sequence number 192 1459485696 InnoDB: Doing recovery: scanned up to log sequence number 192 1464728576 InnoDB: Doing recovery: scanned up to log sequence number 192 1469971456 InnoDB: Doing recovery: scanned up to log sequence number 192 1475214336 InnoDB: Doing recovery: scanned up to log sequence number 192 1480457216 InnoDB: Doing recovery: scanned up to log sequence number 192 1485700096 InnoDB: Doing recovery: scanned up to log sequence number 192 1490942976 InnoDB: Doing recovery: scanned up to log sequence number 192 1496185856 InnoDB: Doing recovery: scanned up to log sequence number 192 1501428736 InnoDB: Doing recovery: scanned up to log sequence number 192 1506671616 InnoDB: Doing recovery: scanned up to log sequence number 192 1511914496 InnoDB: Doing recovery: scanned up to log sequence number 192 1517157376 InnoDB: Doing recovery: scanned up to log sequence number 192 1522400256 InnoDB: Doing recovery: scanned up to log sequence number 192 1527643136 InnoDB: Doing recovery: scanned up to log sequence number 192 1532886016 InnoDB: Doing recovery: scanned up to log sequence number 192 1538128896 InnoDB: Doing recovery: scanned up to log sequence number 192 1543371776 InnoDB: Doing recovery: scanned up to log sequence number 192 1548614656 InnoDB: Doing recovery: scanned up to log sequence number 192 1553857536 InnoDB: Doing recovery: scanned up to log sequence number 192 1559100416 InnoDB: Doing recovery: scanned up to log sequence number 192 1564343296 InnoDB: Doing recovery: scanned up to log sequence number 192 1569586176 InnoDB: Doing recovery: scanned up to log sequence number 192 1574829056 InnoDB: Doing recovery: scanned up to log sequence number 192 1580071936 InnoDB: Doing recovery: scanned up to log sequence number 192 1585314816 InnoDB: Doing recovery: scanned up to log sequence number 192 1590557696 InnoDB: Doing recovery: scanned up to log sequence number 192 1595800576 InnoDB: Doing recovery: scanned up to log sequence number 192 1601043456 InnoDB: Doing recovery: scanned up to log sequence number 192 1606286336 InnoDB: Doing recovery: scanned up to log sequence number 192 1611529216 InnoDB: Doing recovery: scanned up to log sequence number 192 1616772096 InnoDB: Doing recovery: scanned up to log sequence number 192 1622014976 InnoDB: Doing recovery: scanned up to log sequence number 192 1627257856 InnoDB: Doing recovery: scanned up to log sequence number 192 1632500736 InnoDB: Doing recovery: scanned up to log sequence number 192 1637743616 InnoDB: Doing recovery: scanned up to log sequence number 192 1642986496 InnoDB: Doing recovery: scanned up to log sequence number 192 1648229376 InnoDB: Doing recovery: scanned up to log sequence number 192 1653472256 InnoDB: Doing recovery: scanned up to log sequence number 192 1658715136 InnoDB: Doing recovery: scanned up to log sequence number 192 1663958016 InnoDB: Doing recovery: scanned up to log sequence number 192 1669200896 InnoDB: Doing recovery: scanned up to log sequence number 192 1674443776 InnoDB: Doing recovery: scanned up to log sequence number 192 1679686656 InnoDB: Doing recovery: scanned up to log sequence number 192 1684929536 InnoDB: Doing recovery: scanned up to log sequence number 192 1690172416 InnoDB: Doing recovery: scanned up to log sequence number 192 1695415296 InnoDB: Doing recovery: scanned up to log sequence number 192 1700658176 InnoDB: Doing recovery: scanned up to log sequence number 192 1705901056 InnoDB: Doing recovery: scanned up to log sequence number 192 1711143936 InnoDB: Doing recovery: scanned up to log sequence number 192 1716386816 InnoDB: Doing recovery: scanned up to log sequence number 192 1721629696 InnoDB: Doing recovery: scanned up to log sequence number 192 1726872576 InnoDB: Doing recovery: scanned up to log sequence number 192 1732115456 InnoDB: Doing recovery: scanned up to log sequence number 192 1737358336 InnoDB: Doing recovery: scanned up to log sequence number 192 1742601216 InnoDB: Doing recovery: scanned up to log sequence number 192 1747844096 InnoDB: Doing recovery: scanned up to log sequence number 192 1753086976 InnoDB: Doing recovery: scanned up to log sequence number 192 1758329856 InnoDB: Doing recovery: scanned up to log sequence number 192 1763572736 InnoDB: Doing recovery: scanned up to log sequence number 192 1768815616 InnoDB: Doing recovery: scanned up to log sequence number 192 1774058496 InnoDB: Doing recovery: scanned up to log sequence number 192 1779301376 InnoDB: Doing recovery: scanned up to log sequence number 192 1784544256 InnoDB: Doing recovery: scanned up to log sequence number 192 1789787136 InnoDB: Doing recovery: scanned up to log sequence number 192 1795030016 InnoDB: Doing recovery: scanned up to log sequence number 192 1800272896 InnoDB: Doing recovery: scanned up to log sequence number 192 1805515776 InnoDB: Doing recovery: scanned up to log sequence number 192 1810758656 InnoDB: Doing recovery: scanned up to log sequence number 192 1816001536 InnoDB: Doing recovery: scanned up to log sequence number 192 1821244416 InnoDB: Doing recovery: scanned up to log sequence number 192 1826487296 InnoDB: Doing recovery: scanned up to log sequence number 192 1831730176 InnoDB: Doing recovery: scanned up to log sequence number 192 1836973056 InnoDB: Doing recovery: scanned up to log sequence number 192 1842215936 InnoDB: Doing recovery: scanned up to log sequence number 192 1847458816 InnoDB: Doing recovery: scanned up to log sequence number 192 1852701696 InnoDB: Doing recovery: scanned up to log sequence number 192 1857944576 InnoDB: Doing recovery: scanned up to log sequence number 192 1863187456 InnoDB: Doing recovery: scanned up to log sequence number 192 1868430336 InnoDB: Doing recovery: scanned up to log sequence number 192 1873673216 InnoDB: Doing recovery: scanned up to log sequence number 192 1878916096 InnoDB: Doing recovery: scanned up to log sequence number 192 1884158976 InnoDB: Doing recovery: scanned up to log sequence number 192 1889401856 InnoDB: Doing recovery: scanned up to log sequence number 192 1894644736 InnoDB: Doing recovery: scanned up to log sequence number 192 1899887616 InnoDB: Doing recovery: scanned up to log sequence number 192 1905130496 InnoDB: Doing recovery: scanned up to log sequence number 192 1910373376 InnoDB: Doing recovery: scanned up to log sequence number 192 1915616256 InnoDB: Doing recovery: scanned up to log sequence number 192 1920859136 InnoDB: Doing recovery: scanned up to log sequence number 192 1926102016 InnoDB: Doing recovery: scanned up to log sequence number 192 1931344896 InnoDB: Doing recovery: scanned up to log sequence number 192 1936587776 InnoDB: Doing recovery: scanned up to log sequence number 192 1941830656 InnoDB: Doing recovery: scanned up to log sequence number 192 1947073536 InnoDB: Doing recovery: scanned up to log sequence number 192 1952316416 InnoDB: Doing recovery: scanned up to log sequence number 192 1957559296 InnoDB: Doing recovery: scanned up to log sequence number 192 1962802176 InnoDB: Doing recovery: scanned up to log sequence number 192 1968045056 InnoDB: Doing recovery: scanned up to log sequence number 192 1973287936 InnoDB: Doing recovery: scanned up to log sequence number 192 1978530816 InnoDB: Doing recovery: scanned up to log sequence number 192 1983773696 InnoDB: Doing recovery: scanned up to log sequence number 192 1989016576 InnoDB: Doing recovery: scanned up to log sequence number 192 1994259456 InnoDB: Doing recovery: scanned up to log sequence number 192 1999502336 InnoDB: Doing recovery: scanned up to log sequence number 192 2004745216 InnoDB: Doing recovery: scanned up to log sequence number 192 2009988096 InnoDB: Doing recovery: scanned up to log sequence number 192 2015230976 InnoDB: Doing recovery: scanned up to log sequence number 192 2020473856 InnoDB: Doing recovery: scanned up to log sequence number 192 2025716736 InnoDB: Doing recovery: scanned up to log sequence number 192 2030959616 InnoDB: Doing recovery: scanned up to log sequence number 192 2036202496 InnoDB: Doing recovery: scanned up to log sequence number 192 2041445376 071216 15:49:07 InnoDB: Starting an apply batch of log records to the database... 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 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: Doing recovery: scanned up to log sequence number 192 2046688256 InnoDB: Doing recovery: scanned up to log sequence number 192 2051931136 InnoDB: Doing recovery: scanned up to log sequence number 192 2057174016 InnoDB: Doing recovery: scanned up to log sequence number 192 2062416896 InnoDB: Doing recovery: scanned up to log sequence number 192 2067659776 InnoDB: Doing recovery: scanned up to log sequence number 192 2072902656 InnoDB: Doing recovery: scanned up to log sequence number 192 2078145536 InnoDB: Doing recovery: scanned up to log sequence number 192 2083388416 InnoDB: Doing recovery: scanned up to log sequence number 192 2088631296 InnoDB: Doing recovery: scanned up to log sequence number 192 2093874176 InnoDB: Doing recovery: scanned up to log sequence number 192 2099117056 InnoDB: Doing recovery: scanned up to log sequence number 192 2104359936 InnoDB: Doing recovery: scanned up to log sequence number 192 2109602816 InnoDB: Doing recovery: scanned up to log sequence number 192 2114845696 InnoDB: Doing recovery: scanned up to log sequence number 192 2120088576 InnoDB: Doing recovery: scanned up to log sequence number 192 2122204195 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 27 row operations to undo InnoDB: Trx id counter is 0 2481063680 071216 15:53:03 InnoDB: Error: table 'tmp/#sql1317_484_0' InnoDB: in InnoDB data dictionary has tablespace id 29, InnoDB: but tablespace with that id or name does not exist. Have InnoDB: you deleted or moved .ibd files? InnoDB: This may also be a table created with CREATE TEMPORARY TABLE InnoDB: whose .ibd and .frm files MySQL automatically removed, but the InnoDB: table still exists in the InnoDB internal data dictionary. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting.html InnoDB: for how to resolve the issue. 071216 15:53:03 InnoDB: Starting an apply batch of log records to the database... 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 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: Starting in background the rollback of uncommitted transactions 071216 15:54:54 InnoDB: Rolling back trx with id 0 2481062555, 27 rows to undo 071216 15:54:54 InnoDB: Started; log sequence number 192 2122204195 InnoDB: Rolling back of trx id 0 2481062555 completed 071216 15:54:54 InnoDB: Rollback of non-prepared transactions completed 071216 15:54:54 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/home/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 071216 15:55:06 [ERROR] /usr/sbin/mysqld: Table './tlbbdb/t_global' is marked as crashed and should be repaired 071216 15:55:06 [Warning] Checking table: './tlbbdb/t_global'