journal.txt

Feb 06 22:10:32 150-95-x-x systemd[1]: Unit mariadb.service entered failed state.
Feb 06 22:10:32 150-95-x-x systemd[1]: mariadb.service failed.
Feb 06 22:10:38 150-95-x-x systemd[1]: mariadb.service holdoff time over, scheduling restart.
Feb 06 22:10:38 150-95-x-x systemd[1]: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argument.
Feb 06 22:10:38 150-95-x-x systemd[1]: Starting MariaDB database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mariadb.service has begun starting up.
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] /usr/sbin/mysqld (mysqld 10.2.7-MariaDB) starting as process 26882 ...
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Uses event mutexes
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Compressed tables use zlib 1.2.7
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Using Linux native AIO
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Number of pools: 1
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Using SSE2 crc32 instructions
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 8, chunk size = 128M
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Completed initialization of buffer pool
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139890472892160 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [Note] InnoDB: Highest supported file format is Barracuda.
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 6588432105687 is in the future! Current system log sequence number 1619291
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=3] log sequence number 6543570567445 is in the future! Current system log sequence number 1619291
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 6588985564533 is in the future! Current system log sequence number 1619291
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 6589262709854 is in the future! Current system log sequence number 1619291
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=11] log sequence number 6577129432258 is in the future! Current system log sequence number 161929
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=1] log sequence number 6541599581264 is in the future! Current system log sequence number 1619291
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 6589262748086 is in the future! Current system log sequence number 1619291
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=6] log sequence number 6589262743311 is in the future! Current system log sequence number 1619291
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=261343] log sequence number 6588985522837 is in the future! Current system log sequence number 16
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=261702] log sequence number 6540274716094 is in the future! Current system log sequence number 16
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=38360] log sequence number 6589101544843 is in the future! Current system log sequence number 161
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=261477] log sequence number 6588986075674 is in the future! Current system log sequence number 16
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=65535] log sequence number 6587024936644 is in the future! Current system log sequence number 161
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=49153] log sequence number 6541287374081 is in the future! Current system log sequence number 161
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Page [page id: space=0, page number=261730] log sequence number 6540276641066 is in the future! Current system log sequence number 16
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.my
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 2018-02-06 22:10:38 139897971091584 [ERROR] [FATAL] InnoDB: Trying to read page number 1728348160 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offs
Feb 06 22:10:38 150-95-x-x mysqld[26882]: 180206 22:10:38 [ERROR] mysqld got signal 6 ;
Feb 06 22:10:38 150-95-x-x mysqld[26882]: This could be because you hit a bug. It is also possible that this binary
Feb 06 22:10:38 150-95-x-x mysqld[26882]: or one of the libraries it was linked against is corrupt, improperly built,
Feb 06 22:10:38 150-95-x-x mysqld[26882]: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb 06 22:10:38 150-95-x-x mysqld[26882]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Feb 06 22:10:38 150-95-x-x mysqld[26882]: We will try our best to scrape up some info that will hopefully help
Feb 06 22:10:38 150-95-x-x mysqld[26882]: diagnose the problem, but since we have already crashed,
Feb 06 22:10:38 150-95-x-x mysqld[26882]: something is definitely wrong and this may fail.
Feb 06 22:10:38 150-95-x-x mysqld[26882]: Server version: 10.2.7-MariaDB
Feb 06 22:10:38 150-95-x-x mysqld[26882]: key_buffer_size=134217728
Feb 06 22:10:38 150-95-x-x mysqld[26882]: read_buffer_size=131072
Feb 06 22:10:38 150-95-x-x mysqld[26882]: max_used_connections=0
Feb 06 22:10:38 150-95-x-x mysqld[26882]: max_threads=10002
Feb 06 22:10:38 150-95-x-x mysqld[26882]: thread_count=0
Feb 06 22:10:38 150-95-x-x mysqld[26882]: It is possible that mysqld could use up to
Feb 06 22:10:38 150-95-x-x mysqld[26882]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22106460 K  bytes of memory
Feb 06 22:10:38 150-95-x-x mysqld[26882]: Hope that's ok; if not, decrease some variables in the equation.
Feb 06 22:10:38 150-95-x-x mysqld[26882]: Thread pointer: 0x0
Feb 06 22:10:38 150-95-x-x mysqld[26882]: Attempting backtrace. You can use the following information to find out
Feb 06 22:10:38 150-95-x-x mysqld[26882]: where mysqld died. If you see no messages after this, something went
Feb 06 22:10:38 150-95-x-x mysqld[26882]: terribly wrong...
Feb 06 22:10:38 150-95-x-x mysqld[26882]: stack_bottom = 0x0 thread_stack 0x49000
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f3c89a5537e]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x7f3c8949afad]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /lib64/libpthread.so.0(+0xf370)[0x7f3c88a09370]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /lib64/libc.so.6(gsignal+0x37)[0x7f3c86f921d7]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /lib64/libc.so.6(abort+0x148)[0x7f3c86f938c8]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /usr/sbin/mysqld(+0x9c14f3)[0x7f3c897f94f3]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /usr/sbin/mysqld(+0xa806c8)[0x7f3c898b86c8]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: mysys/stacktrace.c:268(my_print_stacktrace)[0x7f3c898c06cf]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: sql/signal_handler.cc:168(handle_fatal_signal)[0x7f3c8986bc5d]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: fil/fil0fil.cc:5125(fil_report_invalid_page_access(unsigned long, unsigned long, char const*, unsigned long, unsigned long, bool))[0x7f3c8983e619]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: buf/buf0buf.cc:4321(buf_page_get_gen(page_id_t const&, page_size_t const&, unsigned long, buf_block_t*, unsigned long, char const*, unsigned int, mtr_t*, dberr_t*))[0x7f3c897f1d59]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: include/mach0data.ic:178(trx_rseg_mem_restore(trx_rseg_t*, mtr_t*))[0x7f3c897d8312]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: trx/trx0rseg.cc:261(trx_rseg_array_init())[0x7f3c897d9fd4]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: trx/trx0trx.cc:1007(trx_lists_init_at_db_start())[0x7f3c897ea0ec]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: trx/trx0sys.cc:515(trx_sys_init_at_db_start())[0x7f3c897df39b]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: srv/srv0start.cc:2243(innobase_start_or_create_for_mysql())[0x7f3c897ab1cc]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /usr/sbin/mysqld(+0x840b11)[0x7f3c89678b11]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: handler/ha_innodb.cc:4432(innobase_init(void*))[0x7f3c8949d254]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: sql/handler.cc:512(ha_initialize_handlerton(st_plugin_int*))[0x7f3c893216f0]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: sql/sql_plugin.cc:1694(plugin_init(int*, char**, int))[0x7f3c89322f22]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: sql/mysqld.cc:5253(init_server_components())[0x7f3c8927eef8]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: sql/mysqld.cc:5845(mysqld_main(int, char**))[0x7f3c892831f9]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f3c86f7eb35]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: /usr/sbin/mysqld(+0x43fb9d)[0x7f3c89277b9d]
Feb 06 22:10:38 150-95-x-x mysqld[26882]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Feb 06 22:10:38 150-95-x-x mysqld[26882]: information that should help you find out what is causing the crash.
Feb 06 22:10:39 150-95-x-x abrt-hook-ccpp[26901]: Process 26882 (mysqld) of user 995 killed by SIGABRT - dumping core