Skip to content

Instantly share code, notes, and snippets.

@emrass
Created June 15, 2014 18:40
Show Gist options
  • Save emrass/985c03348145dd3fcc09 to your computer and use it in GitHub Desktop.
Save emrass/985c03348145dd3fcc09 to your computer and use it in GitHub Desktop.
MySQL error log
Version: '5.6.19' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
18:34:01 UTC - 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=8388608
read_buffer_size=131072
max_used_connections=3
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68238 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fac3a8dee00
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 = 13177ce68 thread_stack 0x40000
0 mysqld 0x000000010bb901aa my_print_stacktrace + 61
1 mysqld 0x000000010b9e81d4 handle_fatal_signal + 725
2 libsystem_platform.dylib 0x00007fff9034b5aa _sigtramp + 26
3 ??? 0x00007fac3a81e488 0x0 + 140377692693640
4 mysqld 0x000000010ba65c1c _Z31substitute_for_best_equal_fieldP4ItemP10COND_EQUALPv + 265
5 mysqld 0x000000010ba65c1c _Z31substitute_for_best_equal_fieldP4ItemP10COND_EQUALPv + 265
6 mysqld 0x000000010badc5e6 _Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_ + 1533
7 mysqld 0x000000010ba72aa8 _Z21mysql_execute_commandP3THD + 7881
8 mysqld 0x000000010ba70177 _Z11mysql_parseP3THDPcjP12Parser_state + 601
9 mysqld 0x000000010ba6e308 _Z16dispatch_command19enum_server_commandP3THDPcj + 2654
10 mysqld 0x000000010ba6fd51 _Z10do_commandP3THD + 370
11 mysqld 0x000000010ba34311 _Z24do_handle_one_connectionP3THD + 280
12 mysqld 0x000000010ba341ec handle_one_connection + 59
13 mysqld 0x000000010bd34b03 pfs_spawn_thread + 311
14 libsystem_pthread.dylib 0x00007fff88efa899 _pthread_body + 138
15 libsystem_pthread.dylib 0x00007fff88efa72a _pthread_struct_init + 0
16 libsystem_pthread.dylib 0x00007fff88efefc9 thread_start + 13
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fac3a81cc10): is an invalid pointer
Connection ID (thread ID): 76
Status: NOT_KILLED
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.
140615 20:34:01 mysqld_safe mysqld restarted
2014-06-15 20:34:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-06-15 20:34:02 1221 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive
2014-06-15 20:34:02 1221 [Note] Plugin 'FEDERATED' is disabled.
2014-06-15 20:34:02 1221 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-15 20:34:02 1221 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-15 20:34:02 1221 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-06-15 20:34:02 1221 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-15 20:34:02 1221 [Note] InnoDB: Using CPU crc32 instructions
2014-06-15 20:34:02 1221 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-06-15 20:34:02 1221 [Note] InnoDB: Completed initialization of buffer pool
2014-06-15 20:34:02 1221 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-15 20:34:02 1221 [Note] InnoDB: Log scan progressed past the checkpoint lsn 19938393
2014-06-15 20:34:02 1221 [Note] InnoDB: Database was not shutdown normally!
2014-06-15 20:34:02 1221 [Note] InnoDB: Starting crash recovery.
2014-06-15 20:34:02 1221 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-06-15 20:34:02 1221 [Note] InnoDB: Restoring possible half-written data pages
2014-06-15 20:34:02 1221 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 19981207
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 22 row operations to undo
InnoDB: Trx id counter is 12544
2014-06-15 20:34:02 1221 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2014-06-15 20:34:02 1221 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2014-06-15 20:34:02 12de05000 InnoDB: Rolling back trx with id 12036, 22 rows to undo
2014-06-15 20:34:02 1221 [Note] InnoDB: Rollback of trx with id 12036 completed
2014-06-15 20:34:02 12de05000 InnoDB: Rollback of non-prepared transactions completed
2014-06-15 20:34:02 1221 [Note] InnoDB: Waiting for purge to start
2014-06-15 20:34:02 1221 [Note] InnoDB: 5.6.19 started; log sequence number 19981207
2014-06-15 20:34:02 1221 [Note] Server hostname (bind-address): '*'; port: 3306
2014-06-15 20:34:02 1221 [Note] IPv6 is available.
2014-06-15 20:34:02 1221 [Note] - '::' resolves to '::';
2014-06-15 20:34:02 1221 [Note] Server socket created on IP: '::'.
2014-06-15 20:34:03 1221 [Note] Event Scheduler: Loaded 0 events
2014-06-15 20:34:03 1221 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.19' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment