Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 140410 13:48:20 InnoDB: Waiting for the background threads to start
- 140410 13:48:21 InnoDB: 5.5.35 started; log sequence number 75993137603
- 140410 13:48:21 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
- 140410 13:48:21 [Note] - '127.0.0.1' resolves to '127.0.0.1';
- 140410 13:48:21 [Note] Server socket created on IP: '127.0.0.1'.
- 140410 13:48:21 [Note] Event Scheduler: Loaded 0 events
- 140410 13:48:21 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.5.35-0ubuntu0.13.10.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
- InnoDB: Error: tablespace id is 146 in the data dictionary
- InnoDB: but in file ./mafiacraft/permissions.ibd it is 118!
- 140410 13:48:24 InnoDB: Assertion failure in thread 140256187328256 in file fil0fil.c line 768
- 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.
- 17:48:24 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=131072
- max_used_connections=1
- 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 = 346700 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x7f8ff4987040
- 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 = 7f8ff0391e68 thread_stack 0x30000
- /usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7f8ff3975d30]
- /usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7f8ff38607b5]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7f8ff25f2bb0]
- /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f8ff1c49f77]
- /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f8ff1c4d5e8]
- /usr/sbin/mysqld(+0x5dc0c9)[0x7f8ff3a630c9]
- /usr/sbin/mysqld(+0x5dc1a7)[0x7f8ff3a631a7]
- /usr/sbin/mysqld(+0x5e5653)[0x7f8ff3a6c653]
- /usr/sbin/mysqld(+0x5c1239)[0x7f8ff3a48239]
- /usr/sbin/mysqld(+0x5c1bbb)[0x7f8ff3a48bbb]
- /usr/sbin/mysqld(+0x5b280f)[0x7f8ff3a3980f]
- /usr/sbin/mysqld(+0x594c0b)[0x7f8ff3a1bc0b]
- /usr/sbin/mysqld(+0x595dfb)[0x7f8ff3a1cdfb]
- /usr/sbin/mysqld(+0x5cf79d)[0x7f8ff3a5679d]
- /usr/sbin/mysqld(+0x5cfb32)[0x7f8ff3a56b32]
- /usr/sbin/mysqld(+0x549a77)[0x7f8ff39d0a77]
- /usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x2a)[0x7f8ff38642da]
- /usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x557)[0x7f8ff37f2f07]
- /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0xc5c)[0x7f8ff374c40c]
- /usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x541)[0x7f8ff374d961]
- /usr/sbin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTj+0x4e)[0x7f8ff374e22e]
- /usr/sbin/mysqld(_Z18mysqld_list_fieldsP3THDP10TABLE_LISTPKc+0x23)[0x7f8ff37beda3]
- /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x259f)[0x7f8ff378536f]
- /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x176)[0x7f8ff38109c6]
- /usr/sbin/mysqld(handle_one_connection+0x41)[0x7f8ff3810a21]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0x7f6e)[0x7f8ff25eaf6e]
- /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f8ff1d0d9cd]
- Trying to get some variables.
- Some pointers may be invalid and cause the dump to abort.
- Query (7f8fcc004c28): is an invalid pointer
- Connection ID (thread ID): 1
- Status: NOT_KILLED
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement