Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- key_buffer_size=268435456
- read_buffer_size=1048576
- max_used_connections=0
- max_threads=500
- 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 = 1291909 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
- /usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7ff57f2c5793]
- /usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7ff57f1b2b44]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7ff57e9b08d0]
- /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7ff57d3a6147]
- /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7ff57d3a7528]
- /usr/sbin/mysqld(+0x52aa65)[0x7ff57f30ba65]
- /usr/sbin/mysqld(+0x52c2e1)[0x7ff57f30d2e1]
- /usr/sbin/mysqld(+0x5f93c2)[0x7ff57f3da3c2]
- /usr/sbin/mysqld(+0x5ef5e7)[0x7ff57f3d05e7]
- /usr/sbin/mysqld(+0x52d5d3)[0x7ff57f30e5d3]
- /usr/sbin/mysqld(+0x51e4ac)[0x7ff57f2ff4ac]
- /usr/sbin/mysqld(+0x522cb3)[0x7ff57f303cb3]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7ff57e9a90a4]
- /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff57d4599cd]
- 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.
- 160622 09:31:52 mysqld_safe Number of processes running now: 0
- 160622 09:31:52 mysqld_safe mysqld restarted
- 160622 9:31:52 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
- 160622 9:31:52 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 16129 ...
- 160622 9:31:52 [Note] Plugin 'FEDERATED' is disabled.
- 160622 9:31:52 InnoDB: The InnoDB memory heap is disabled
- 160622 9:31:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 160622 9:31:52 InnoDB: Compressed tables use zlib 1.2.8
- 160622 9:31:52 InnoDB: Using Linux native AIO
- 160622 9:31:52 InnoDB: Initializing buffer pool, size = 128.0M
- 160622 9:31:52 InnoDB: Completed initialization of buffer pool
- 160622 9:31:52 InnoDB: highest supported file format is Barracuda.
- InnoDB: The log sequence number in ibdata files does not match
- InnoDB: the log sequence number in the ib_logfiles!
- 160622 9:31:52 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...
- 160622 9:31:52 InnoDB: Waiting for the background threads to start
- 160622 9:31:53 InnoDB: 5.5.46 started; log sequence number 1515417572
- 160622 9:31:53 InnoDB: !!! innodb_force_recovery is set to 1 !!!
- 160622 9:31:53 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
- 160622 9:31:53 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 160622 9:31:53 [Note] Server socket created on IP: '0.0.0.0'.
- 160622 9:31:53 [Warning] 'user' entry '[email protected]' ignored in --skip-name-resolve mode.
- 160622 9:31:53 [Warning] 'proxies_priv' entry '@ [email protected]' ignored in --skip-name-resolve mode.
- 160622 9:31:53 [Note] Event Scheduler: Loaded 0 events
- 160622 9:31:53 [Note] /usr/sbin/mysqld: ready for connections.
- Version: '5.5.46-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
- 160622 9:31:53 InnoDB: Assertion failure in thread 140470035228416 in file trx0purge.c line 840
- InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
- 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:31:53 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=268435456
- read_buffer_size=1048576
- max_used_connections=0
- max_threads=500
- 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 = 1291909 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
- /usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7fc1e1d02793]
- /usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7fc1e1befb44]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fc1e13ed8d0]
- /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fc1dfde3147]
- /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fc1dfde4528]
- /usr/sbin/mysqld(+0x52aa65)[0x7fc1e1d48a65]
- /usr/sbin/mysqld(+0x52c2e1)[0x7fc1e1d4a2e1]
- /usr/sbin/mysqld(+0x5f93c2)[0x7fc1e1e173c2]
- /usr/sbin/mysqld(+0x5ef5e7)[0x7fc1e1e0d5e7]
- /usr/sbin/mysqld(+0x52d5d3)[0x7fc1e1d4b5d3]
- /usr/sbin/mysqld(+0x51e4ac)[0x7fc1e1d3c4ac]
- /usr/sbin/mysqld(+0x522cb3)[0x7fc1e1d40cb3]
- /lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fc1e13e60a4]
- /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc1dfe969cd]
- 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.
- 160622 09:31:53 mysqld_safe Number of processes running now: 0
- 160622 09:31:53 mysqld_safe mysqld restarted
- 160622 9:31:53 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
- 160622 9:31:53 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 16187 ...
Advertisement
Add Comment
Please, Sign In to add comment