title: MAMP PRO crashes; MySQL will not start on reboot
body: <p>Today at work my computer randomly froze/crashed. On reboot MAMP refuses to start mysql and I can't figure out why. There are definitely no other mysql processes running; I’ve checked several times. So, the <code>killall -9 mysqld</code> is not the solution. I’ve actually completely re-installed MAMP, also.</p>
  
  <p>This is what seems to be the important part of my MySQL log, but I’m not very seasoned in reading these things, so maybe the answer is right in front of me.</p>
  
  <pre><code>140527 15:06:58 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql
  140527 15:06:58 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
  140527 15:06:58 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql/ is case insensitive
  140527 15:06:58 [Note] Plugin 'FEDERATED' is disabled.
  140527 15:06:58 InnoDB: The InnoDB memory heap is disabled
  140527 15:06:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
  140527 15:06:58 InnoDB: Compressed tables use zlib 1.2.3
  140527 15:06:58 InnoDB: Initializing buffer pool, size = 128.0M
  140527 15:06:58 InnoDB: Completed initialization of buffer pool
  140527 15:06:58 InnoDB: highest supported file format is Barracuda.
  InnoDB: Log scan progressed past the checkpoint lsn 791075520
  140527 15:06:58  InnoDB: Database was not shut down normally!
  InnoDB: Starting crash recovery.
  InnoDB: Reading tablespace information from the .ibd files...
  InnoDB: Restoring possible half-written data pages from the doublewrite
  InnoDB: buffer...
  InnoDB: Doing recovery: scanned up to log sequence number 791076717
  InnoDB: Database page corruption on disk or a failed
  InnoDB: file read of page 8402.
  InnoDB: You may have to recover from a backup.
  140527 15:06:58  InnoDB: Page dump in ascii and hex (16384 bytes):
   len 16384; hex ....
  InnoDB: End of page dump
  140527 15:06:58  InnoDB: Page checksum 3802906200, prior-to-4.0.14-form checksum 786607151
  InnoDB: stored checksum 3802906200, prior-to-4.0.14-form stored checksum 1787456768
  InnoDB: Page lsn 0 791046088, low 4 bytes of lsn at page end 790720183
  InnoDB: Page number (if stored to page already) 8402,
  InnoDB: space id (if created with &gt;= MySQL-4.1.1 and stored already) 0
  InnoDB: Page may be an insert undo log page
  InnoDB: Database page corruption on disk or a failed
  InnoDB: file read of page 8402.
  InnoDB: You may have to recover from a backup.
  InnoDB: It is also possible that your operating
  InnoDB: system has corrupted its own file cache
  InnoDB: and rebooting your computer removes the
  InnoDB: error.
  InnoDB: If the corrupt page is an index page
  InnoDB: you can also try to fix the corruption
  InnoDB: by dumping, dropping, and reimporting
  InnoDB: the corrupt table. You can use CHECK
  InnoDB: TABLE to scan your table for corruption.
  InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  InnoDB: about forcing recovery.
  InnoDB: Ending processing because of a corrupt database page.
  140527 15:06:58  InnoDB: Assertion failure in thread 140735261836048 in file buf0buf.c line 3619
  InnoDB: We intentionally generate a memory trap.
  InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
  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: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  InnoDB: about forcing recovery.
  19:06:58 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.
  
  key_buffer_size=16777216
  read_buffer_size=262144
  max_used_connections=0
  max_threads=151
  thread_count=0
  connection_count=0
  It is possible that mysqld could use up to 
  key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134084 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                              0x000000010028081c my_print_stacktrace + 44
  1   mysqld                              0x0000000100021624 handle_fatal_signal + 692
  2   libsystem_platform.dylib            0x00007fff91e625aa _sigtramp + 26
  3   ???                                 0x0000000000000000 0x0 + 0
  4   libsystem_c.dylib                   0x00007fff9355bb1a abort + 125
  5   mysqld                              0x00000001002b30af buf_page_io_complete + 959
  6   mysqld                              0x00000001002b9892 buf_read_page_low + 610
  7   mysqld                              0x00000001002b9fa5 buf_read_page + 85
  8   mysqld                              0x00000001002b4431 buf_page_get_gen + 673
  9   mysqld                              0x000000010034fdd5 trx_undo_lists_init + 373
  10  mysqld                              0x0000000100348e2e trx_rseg_mem_create + 334
  11  mysqld                              0x0000000100348fed trx_rseg_list_and_array_init + 157
  12  mysqld                              0x000000010034a147 trx_sys_init_at_db_start + 215
  13  mysqld                              0x000000010033eafd innobase_start_or_create_for_mysql + 5805
  14  mysqld                              0x00000001003114c1 _ZL13innobase_initPv + 1473
  15  mysqld                              0x0000000100027028 _Z24ha_initialize_handlertonP13st_plugin_int + 104
  16  mysqld                              0x000000010017f0f1 _ZL17plugin_initializeP13st_plugin_int + 97
  17  mysqld                              0x0000000100181810 _Z11plugin_initPiPPci + 3776
  18  mysqld                              0x00000001000ccce5 _Z11mysqld_mainiPPc + 10405
  19  mysqld                              0x0000000100001804 start + 52
  20  ???                                 0x000000000000000a 0x0 + 10
  The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  information that should help you find out what is causing the crash.
  140527 15:06:58 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
  </code></pre>
  
  <p>And when trying to do a db dump I am getting: (EDIT: I got this part of it fixed)</p>
  
  <pre><code>mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) when trying to connect
  </code></pre>