Cannot start MySQL

Report any found bug here. We are grateful for any useful clues.

Moderator: severin

Post Reply
Posts: 1
Joined: Mon 17. Jun 2013, 00:19

Cannot start MySQL

Post by qian » Mon 17. Jun 2013, 00:27


when I try to start up MAMP I get an error message saying that it cannot start MySQL. The error log reads as follows:
130617 02:08:01 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql
130617 2:08:01 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql/ is case insensitive
130617 2:08:01 [Note] Plugin 'FEDERATED' is disabled.
130617 2:08:01 InnoDB: The InnoDB memory heap is disabled
130617 2:08:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130617 2:08:01 InnoDB: Compressed tables use zlib 1.2.3
130617 2:08:01 InnoDB: Initializing buffer pool, size = 128.0M
130617 2:08:01 InnoDB: Completed initialization of buffer pool
130617 2:08:01 InnoDB: highest supported file format is Barracuda.
130617 2:08:01 InnoDB: Waiting for the background threads to start
130617 2:08:02 InnoDB: 1.1.8 started; log sequence number 15450367
130617 2:08:02 [Note] Event Scheduler: Loaded 0 events
130617 2:08:02 [Note] /Applications/MAMP/Library/bin/mysqld: ready for connections.
Version: '5.5.25' socket: '/Applications/MAMP/tmp/mysql/mysql.sock' port: 0 Source distribution
130617 2:08:02 InnoDB: Assertion failure in thread 4503511040 in file dict0dict.c line 2643
InnoDB: Failing assertion: for_table || ref_table
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: ... overy.html
InnoDB: about forcing recovery.
00:08:02 UTC - mysqld got signal 6 ;
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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134066 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
stack_bottom = 0 thread_stack 0x40000
0 mysqld 0x000000010027a4fc my_print_stacktrace + 44
1 mysqld 0x0000000100021134 handle_fatal_signal + 692
2 libsystem_c.dylib 0x00007fff9523494a _sigtramp + 26
3 mysqld 0x00000001002efd87 mtr_memo_push + 23
4 libsystem_c.dylib 0x00007fff9528bdce abort + 143
5 mysqld 0x00000001002baf96 dict_foreign_add_to_cache + 998
6 mysqld 0x00000001002c09c6 dict_load_foreigns + 1414
7 mysqld 0x00000001002c2b5b dict_load_table + 1707
8 mysqld 0x00000001002c2f1b dict_load_table_on_id + 459
9 mysqld 0x00000001003238ed row_purge_step + 381
10 mysqld 0x00000001003027a6 que_thr_step + 534
11 mysqld 0x00000001003029bd que_run_threads + 125
12 mysqld 0x0000000100339d6c trx_purge + 636
13 mysqld 0x000000010032fdec srv_master_do_purge + 44
14 mysqld 0x0000000100330b41 srv_master_thread + 2497
15 libsystem_c.dylib 0x00007fff952467a2 _pthread_start + 327
16 libsystem_c.dylib 0x00007fff952331e1 thread_start + 13
The manual page at contains
information that should help you find out what is causing the crash.
130617 02:08:02 mysqld_safe mysqld restarted
Any thoughts on how to fix this? I already tried killing the mysqld process, didn't help. I previously used regular MAMP and everything was working fine.


Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest