SQLinfo.ru - Все о MySQL Highload++ 2017

Форум пользователей MySQL

Задавайте вопросы, мы ответим

Вы не зашли.

#1 27.06.2017 11:11:35

gettelnet
Участник
Зарегистрирован: 27.06.2017
Сообщений: 2

[ERROR] mysqld got signal 11

Eсть небольшой хостинг. На нем панелька Plesk, кучу сайтов, все при создании своих баз указывают localhost из phpMyAdmin.
Но появилось 2 сайта с ошибками на базу. У первого явно был конект потерян с сокетом и там было написано.

Error:2002 SQLSTATE[HY000] [2002] Can't connect to local
MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

(сделаю небольшое отступление и скажу что многие пишут всякую охинеую про то как это лечить,
кто то говорит что нет места, я естественно это проверил, места валом, кто-то говорит что отключи SElinux (пока и не трогал его т.к. до этого все же работало),
кто-то просто говорит что эта 111 ошибка появлятся в момент когда мускул банально лежит,
опять же, я уже раз 10 его рестартовал и рестартуется он со статусом sucsess!)

У второго был движок DataLife engine. C ошибкой на 52 строку в файле /engine/classes/mysql.php
Cтрока там вот такая:

"$this->display_error(mysqli_connect_error(), '1');"


Ну её точно никто не менял. И бог с ней. Как меня уверяют что сайты оба перестают рабоать
ссылаясь на то что "типо мускул у меня падает". Ну ок. Падает так падает. Тут если опустить мускул то у меня и будет таже самая ошибка
Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111) как мне сказали. НО! Сейчас он поднят. И все сайты не выдают ошибку. Возможно из-за того что я уже 100 раз рестартовал. Логи рестарта ниже.

Логи рестарта MySQL:


170627 13:36:33 [Note] /usr/sbin/mysqld: Normal shutdown

170627 13:36:33 [Note] Event Scheduler: Killing the scheduler thread, thread id 1
170627 13:36:33 [Note] Event Scheduler: Waiting for the scheduler thread to reply
170627 13:36:33 [Note] Event Scheduler: Stopped
170627 13:36:33 [Note] Event Scheduler: Purging the queue. 0 events
170627 13:36:33  InnoDB: Starting shutdown...
170627 13:36:35  InnoDB: Shutdown completed; log sequence number 400574926262
170627 13:36:35 [Note] /usr/sbin/mysqld: Shutdown complete

170627 13:36:35 mysqld_safe mysqld from pid file /var/lib/mysql/super_name.pid ended
170627 13:36:35 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170627 13:36:35 [Note] /usr/sbin/mysqld (mysqld 5.5.53-MariaDB) starting as process 18287 ...
170627 13:36:35 InnoDB: The InnoDB memory heap is disabled
170627 13:36:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170627 13:36:35 InnoDB: Compressed tables use zlib 1.2.3
170627 13:36:35 InnoDB: Using Linux native AIO
170627 13:36:35 InnoDB: Initializing buffer pool, size = 2.0G
170627 13:36:36 InnoDB: Completed initialization of buffer pool
170627 13:36:36 InnoDB: highest supported file format is Barracuda.
170627 13:36:36  InnoDB: Waiting for the background threads to start
170627 13:36:37 Percona XtraDB (<a href="http://www.percona.com">http://www.percona.com</a>) 5.5.52-MariaDB-38.3 started; log sequence number 400574926262
170627 13:36:37 [Note] Plugin 'FEEDBACK' is disabled.
170627 13:36:37 [Note] Server socket created on IP: '0.0.0.0'.
170627 13:36:37 [Note] Event Scheduler: Loaded 0 events
170627 13:36:37 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.53-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
170627 13:36:37 [Note] Event Scheduler: scheduler thread started with id 1

И вот поять же, продолжая про ошибку, и про то что на стэковерфлоу пишут мол где они её встречают.
Говортя именно она может появляться когда с CLI подключаешся под рутом в базу Мускула.
Хорошо, я попробывал, залогинился и этой ошибки просто небыло. Мускул как мускул ждал когда я буду создавать таблички в нем. Я вышел.

Впринципе, у меня даже забикс ни пикнул на мускул.  Вероятнее и было падение но потом всё поднялось. Да и сейчас все поднимается. Но падает с вот таким криком в логах:
[ERROR] mysqld got signal 11


Вообщем подводя итоги что мы имеем:
Система: RHEL 6
МуSQL (MariaDB)

Что уже с стоит: rpm -qa | grep ^Ma


MariaDB-compat-5.5.53-1.el6.x86_64
MariaDB-shared-5.5.53-1.el6.x86_64
MariaDB-devel-5.5.53-1.el6.x86_64
MariaDB-client-5.5.53-1.el6.x86_64
MariaDB-server-5.5.53-1.el6.x86_64
MariaDB-common-5.5.53-1.el6.x86_64
 

Конфиг: my.cnf


[mysqld]
local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
innodb_file_per_table=1

max_allowed_packet=32M
low-priority-updates

tmp_table_size = 128M
max_heap_table_size = 64M
table_cache = 1024

innodb_additional_mem_pool_size = 128M
innodb_buffer_pool_size = 2G
innodb_flush_method = O_DIRECT
innodb_io_capacity = 2000
innodb_flush_log_at_trx_commit = 2
innodb_support_xa = 0
innodb_log_buffer_size = 128M

event_scheduler = 1
query_cache_type = 1
query_cache_size = 134217728
join_buffer_size=1M
query_cache_limit=2M
sort_buffer_size=2M
read_buffer_size=2M
read_rnd_buffer_size=4M
key_buffer = 256M
key_buffer_size=64M

max_connections = 256
thread_cache_size=100

wait_timeout  = 100
interactive_timeout = 100
connect_timeout  = 100

collation-server=utf8_unicode_ci
init-connect='SET NAMES utf8'
character-set-server = utf8

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

Отредактированно gettelnet (27.06.2017 11:15:16)

Неактивен

 

#2 27.06.2017 11:15:29

gettelnet
Участник
Зарегистрирован: 27.06.2017
Сообщений: 2

Re: [ERROR] mysqld got signal 11

Ну и самый длинный кусок лог файла с захватом до signal 11 и чуть-чуть после:

tail -f /var/log/mysqld.log



170627 13:36:59 [Note] Event Scheduler: scheduler thread started with id 1
170627 13:37:01 [ERROR] mysqld: Table './host_190879_task_2017/tNotifications' is marked as crashed and should be repaired
170627 13:37:01 [Warning] Checking table:   './host_190879_task_2017/tNotifications'
170627 13:37:02 [ERROR] mysqld: Table './host_394188_sham/xm96n_session' is marked as crashed and should be repaired
170627 13:37:02 [Warning] Checking table:   './host_394188_sham/xm96n_session'
170627 13:37:06 [ERROR] mysqld: Table './host2_112048_ts/survey_637232' is marked as crashed and should be repaired
170627 13:37:06 [Warning] Checking table:   './host2_112048_ts/survey_637232'
170627 13:37:06 [ERROR] mysqld: Table './host2_112048_ts/survey_637232_timings' is marked as crashed and should be repaired
170627 13:37:06 [Warning] Checking table:   './host2_112048_ts/survey_637232_timings'
170627 13:37:07 [ERROR] mysqld: Table './host_444990_dnrsvoboda/dle_post_extras' is marked as crashed and should be repaired
170627 13:37:07 [Warning] Checking table:   './host_444990_dnrsvoboda/dle_post_extras'
170627 13:37:08 [ERROR] mysqld: Table './host_489351_wordpress/wp_postmeta' is marked as crashed and should be repaired
170627 13:37:08 [Warning] Checking table:   './host_489351_wordpress/wp_postmeta'
170627 13:37:18 [ERROR] mysqld: Table './host_444990_svodok/dle_post_extras' is marked as crashed and should be repaired
170627 13:37:18 [Warning] Checking table:   './host_444990_svodok/dle_post_extras'
170627 13:37:45 [ERROR] mysqld: Table './host_478546_54/m6k92_session' is marked as crashed and should be repaired
170627 13:37:45 [Warning] Checking table:   './host_478546_54/m6k92_session'
170627 13:38:12 [ERROR] mysqld: Table './moodle/mdl_cache_text' is marked as crashed and should be repaired
170627 13:38:12 [Warning] Checking table:   './moodle/mdl_cache_text'
170627 13:38:13 [ERROR] mysqld: Table './moodle/mdl_user' is marked as crashed and should be repaired
170627 13:38:13 [Warning] Checking table:   './moodle/mdl_user'
170627 13:38:18 [ERROR] mysqld: Table './host_444990_dnrs/dle_admin_logs' is marked as crashed and should be repaired
170627 13:38:18 [Warning] Checking table:   './host_444990_dnrs/dle_admin_logs'
170627 13:38:42 [ERROR] 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.

To report this bug, see <a href="http://kb.askmonty.org/en/reporting-bugs">http://kb.askmonty.org/en/reporting-bugs</a>

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.

Server version: 5.5.53-MariaDB
key_buffer_size=67108864
read_buffer_size=2097152
max_used_connections=5
max_threads=258
thread_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1126889 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f9214da5000
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 = 0x7f9205122d60 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xa7833b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6d2b58]
/lib64/libpthread.so.0(+0xf7e0)[0x7f92c0c037e0]
/usr/sbin/mysqld[0x945288]
/usr/sbin/mysqld[0x88bf3e]
/usr/sbin/mysqld[0x8c44f2]
/usr/sbin/mysqld[0x8c6242]
/usr/sbin/mysqld[0x8176b8]
/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x3e)[0x6d687e]
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x6d8)[0x633998]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x7ac)[0x56170c]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x5a5)[0x5623d5]
/usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x44)[0x563044]
/usr/sbin/mysqld[0x598418]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x34ac)[0x5a1b9c]
/usr/sbin/mysqld[0x5a4474]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1bf8)[0x5a6948]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x21b)[0x657f9b]
/usr/sbin/mysqld(handle_one_connection+0x4c)[0x65801c]
/lib64/libpthread.so.0(+0x7aa1)[0x7f92c0bfbaa1]
/lib64/libc.so.6(clone+0x6d)[0x7f92bf514aad]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f9203db9018): is an invalid pointer
Connection ID (thread ID): 714
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off

The manual page at <a href="http://dev.mysql.com/doc/mysql/en/crashing.html">http://dev.mysql.com/doc/mysql/en/crashing.html</a> contains
information that should help you find out what is causing the crash.
170627 13:38:42 mysqld_safe Number of processes running now: 0
170627 13:38:42 mysqld_safe mysqld restarted
170627 13:38:42 [Note] /usr/sbin/mysqld (mysqld 5.5.53-MariaDB) starting as process 18969 ...
170627 13:38:42 InnoDB: The InnoDB memory heap is disabled
170627 13:38:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170627 13:38:42 InnoDB: Compressed tables use zlib 1.2.3
170627 13:38:42 InnoDB: Using Linux native AIO
170627 13:38:42 InnoDB: Initializing buffer pool, size = 2.0G
170627 13:38:42 InnoDB: Completed initialization of buffer pool
170627 13:38:42 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 400576042024
170627 13:38:42  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 400576079559
170627 13:38:48  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 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
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/cache_filters'
InnoDB: in InnoDB data dictionary has tablespace id 45944,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/cache_filters.ibd and id 57790, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/cache_text'
InnoDB: in InnoDB data dictionary has tablespace id 45945,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/cache_text.ibd and id 57793, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/capabilities'
InnoDB: in InnoDB data dictionary has tablespace id 45946,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/capabilities.ibd and id 57889, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/config'
InnoDB: in InnoDB data dictionary has tablespace id 45947,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/config.ibd and id 57706, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/config_log'
InnoDB: in InnoDB data dictionary has tablespace id 45948,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/config_log.ibd and id 57711, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/config_plugins'
InnoDB: in InnoDB data dictionary has tablespace id 45949,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/config_plugins.ibd and id 57708, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/context'
InnoDB: in InnoDB data dictionary has tablespace id 45950,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/context.ibd and id 57886, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/context_temp'
InnoDB: in InnoDB data dictionary has tablespace id 45951,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/context_temp.ibd and id 57887, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/course'
InnoDB: in InnoDB data dictionary has tablespace id 45952,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/course.ibd and id 57720, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/course_categories'
InnoDB: in InnoDB data dictionary has tablespace id 45953,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/course_categories.ibd and id 57722, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Error: table 'host2_112048_distant/course_completion_aggr_methd'
InnoDB: in InnoDB data dictionary has tablespace id 45954,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host2_112048_distant/course_completion_aggr_methd.ibd and id 57726, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.

.... куча строк и самое интересное ....

170627 13:38:49  InnoDB: Error: table 'host_484473_db1/wpkv_wfKnownFileList'
InnoDB: in InnoDB data dictionary has tablespace id 101894,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name ./host_484473_db1/wpkv_wfKnownFileList.ibd and id 101725, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html">http://dev.mysql.com/doc/refman/5.5/en/ &hellip; adict.html</a>
InnoDB: for how to resolve the issue.
170627 13:38:49  InnoDB: Waiting for the background threads to start
170627 13:38:50 Percona XtraDB (<a href="http://www.percona.com">http://www.percona.com</a>) 5.5.52-MariaDB-38.3 started; log sequence number 400576079559
170627 13:38:50 [Note] Plugin 'FEEDBACK' is disabled.
170627 13:38:50 [Note] Server socket created on IP: '0.0.0.0'.
170627 13:38:50 [Note] Event Scheduler: Loaded 0 events
170627 13:38:50 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.53-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
170627 13:38:50 [Note] Event Scheduler: scheduler thread started with id 1
170627 13:38:50 [ERROR] mysqld: Table './host_394188_sham/xm96n_session' is marked as crashed and should be repaired
170627 13:38:50 [Warning] Checking table:   './host_394188_sham/xm96n_session'
170627 13:38:50 [ERROR] mysqld: Table './host_394188_sham/xm96n_k2_items' is marked as crashed and should be repaired
170627 13:38:50 [Warning] Checking table:   './host_394188_sham/xm96n_k2_items'
170627 13:38:50 [ERROR] mysqld: Table './host_148631_rib/znd_banners' is marked as crashed and should be repaired
170627 13:38:50 [Warning] Checking table:   './host_148631_rib/znd_banners'
170627 13:38:51 [ERROR] mysqld: Table './host_444990_dnrs/dle_post_extras' is marked as crashed and should be repaired
170627 13:38:51 [Warning] Checking table:   './host_444990_dnrs/dle_post_extras'
170627 13:38:53 [ERROR] mysqld: Table './host2_112048_ts/survey_637232' is marked as crashed and should be repaired
170627 13:38:53 [Warning] Checking table:   './host2_112048_ts/survey_637232'
170627 13:38:54 [ERROR] mysqld: Table './host_190879_task_2017/tNotifications' is marked as crashed and should be repaired
170627 13:38:54 [Warning] Checking table:   './host_190879_task_2017/tNotifications'
170627 13:38:58 [ERROR] mysqld: Table './host_489351_wordpress/wp_postmeta' is marked as crashed and should be repaired
170627 13:38:58 [Warning] Checking table:   './host_489351_wordpress/wp_postmeta'
170627 13:39:01 [ERROR] mysqld: Table './java_kg_oc/oc_product' is marked as crashed and should be repaired
170627 13:39:01 [Warning] Checking table:   './java_kg_oc/oc_product'
170627 13:39:01 [ERROR] mysqld: Table './host2_112048_ts/survey_637232_timings' is marked as crashed and should be repaired
170627 13:39:01 [Warning] Checking table:   './host2_112048_ts/survey_637232_timings'
170627 13:39:03 [ERROR] mysqld: Table './host_444990_svodok/dle_post_extras' is marked as crashed and should be repaired
170627 13:39:03 [Warning] Checking table:   './host_444990_svodok/dle_post_extras'
170627 13:39:13 [ERROR] mysqld: Table './host_478546_54/m6k92_session' is marked as crashed and should be repaired
170627 13:39:13 [Warning] Checking table:   './host_478546_54/m6k92_session'
170627 13:40:29 [ERROR] mysqld: Table './main/cnb_counter_cache' is marked as crashed and should be repaired
170627 13:40:29 [Warning] Checking table:   './main/cnb_counter_cache'
170627 13:40:29 [ERROR] mysqld: Table './main/cnb_counter' is marked as crashed and should be repaired
170627 13:40:29 [Warning] Checking table:   './main/cnb_counter'
170627 13:41:37 [ERROR] mysqld: Table './moodle/mdl_cache_text' is marked as crashed and should be repaired
170627 13:41:37 [Warning] Checking table:   './moodle/mdl_cache_text'
170627 13:42:18 [ERROR] mysqld: Table './host_353236_prokuror17db/prok_phocagallery_categories' is marked as crashed and should be repaired
170627 13:42:18 [Warning] Checking table:   './host_353236_prokuror17db/prok_phocagallery_categories'
170627 13:42:23 [ERROR] mysqld: Table './host2_367920_oshgui/news' is marked as crashed and should be repaired
170627 13:42:23 [Warning] Checking table:   './host2_367920_oshgui/news'
170627 13:42:23 [ERROR] mysqld: Table './host2_102100_esb/jos_session' is marked as crashed and should be repaired
170627 13:42:23 [Warning] Checking table:   './host2_102100_esb/jos_session'
170627 13:42:24 [ERROR] mysqld: Table './host2_102100_esb/jos_vvisitcounter' is marked as crashed and should be repaired
170627 13:42:24 [Warning] Checking table:   './host2_102100_esb/jos_vvisitcounter'
170627 13:45:37 [ERROR] mysqld: Table './host_444990_dnrsvoboda/dle_login_log' is marked as crashed and should be repaired
170627 13:45:37 [Warning] Checking table:   './host_444990_dnrs/dle_login_log'
170627 13:45:37 [ERROR] mysqld: Table './host_444990_dnrsvoboda/dle_admin_logs' is marked as crashed and should be repaired
170627 13:45:37 [Warning] Checking table:   './host_444990_dnrs/dle_admin_logs'
170627 13:47:36 [ERROR] mysqld: Table './host_484473_db1/wpkv_options' is marked as crashed and should be repaired
170627 13:47:36 [Warning] Checking table:   './host_484473_db1/wpkv_options'
170627 13:47:36 [ERROR] mysqld: Table './host_484473_db1/wpkv_wfConfig' is marked as crashed and should be repaired
170627 13:47:36 [Warning] Checking table:   './host_484473_db1/wpkv_wfConfig'
170627 13:47:36 [ERROR] mysqld: Table './host_484473_db1/wpkv_wfHits' is marked as crashed and should be repaired
170627 13:47:36 [Warning] Checking table:   './host_484473_db1/wpkv_wfHits'
170627 13:48:04 [ERROR] mysqld: Table './host2_112048_ts/survey_468313_timings' is marked as crashed and should be repaired
170627 13:48:04 [Warning] Checking table:   './host2_112048_ts/survey_468313_timings'
170627 13:48:30 [ERROR] mysqld: Table './host_484473_db1/wpkv_wfLogins' is marked as crashed and should be repaired
170627 13:48:30 [Warning] Checking table:   './host_484473_db1/wpkv_wfLogins'
170627 13:49:52 [ERROR] mysqld: Table './moodle/mdl_log' is marked as crashed and should be repaired
170627 13:49:52 [Warning] Checking table:   './moodle/mdl_log'
170627 13:53:07 [ERROR] mysqld: Table './host_470740_amrella/oc_product' is marked as crashed and should be repaired
170627 13:53:07 [Warning] Checking table:   './host_470740_amrella/oc_product'
170627 13:57:59  InnoDB: error clustered record for sec rec not found
InnoDB: index `post_id` of table `host_440969_wordpress_9`.`h4y9N6M_postmeta`
InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 8; hex 00000000000002bb; asc         ;;
 1: len 8; hex 000000000000124c; asc        L;;

InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0
 0: len 8; hex 0000000000001201; asc         ;;
 1: len 6; hex 000045f28398; asc   E   ;;
 2: len 7; hex 99000008140084; asc        ;;
 3: len 8; hex 000000000000002f; asc        /;;
 4: len 30; hex 5f6f656d6265645f74696d655f6537383466373232623165363934326432; asc _oembed_time_e784f722b1e6942d2; (total 45 bytes);
 5: len 10; hex 31343933393637323136; asc 1493967216;;

TRANSACTION 4D43FD91, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 0
MySQL thread id 7925, OS thread handle 0x7fceaa099700, query id 201199 localhost host__wordpres_b Sending data
SELECT post_id, meta_key, meta_value FROM h4y9N6M_postmeta WHERE post_id IN (699) ORDER BY meta_id ASC

InnoDB: Submit a detailed bug report to <a href="http://bugs.mysql.com">http://bugs.mysql.com</a>
170627 13:57:59  InnoDB: error clustered record for sec rec not found
InnoDB: index `post_id` of table `host_440969_wordpress_9`.`h4y9N6M_postmeta`
InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 8; hex 00000000000002bb; asc         ;;
 1: len 8; hex 000000000000124d; asc        M;;

InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0
 0: len 8; hex 0000000000001201; asc         ;;
 1: len 6; hex 000045f28398; asc   E   ;;
 2: len 7; hex 99000008140084; asc        ;;
 3: len 8; hex 000000000000002f; asc        /;;
 4: len 30; hex 5f6f656d6265645f74696d655f6537383466373232623165363934326432; asc _oembed_time_e784f722b1e6942d2; (total 45 bytes);
 5: len 10; hex 31343933393637323136; asc 1493967216;;

TRANSACTION 4D43FD91, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 0
MySQL thread id 7925, OS thread handle 0x7fceaa099700, query id 201199 localhost host__wordpres_b Sending data
SELECT post_id, meta_key, meta_value FROM h4y9N6M_postmeta WHERE post_id IN (699) ORDER BY meta_id ASC

InnoDB: Submit a detailed bug report to <a href="http://bugs.mysql.com">http://bugs.mysql.com</a>
170627 13:57:59  InnoDB: error clustered record for sec rec not found
InnoDB: index `post_id` of table `host_440969_wordpress_9`.`h4y9N6M_postmeta`
InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 8; hex 00000000000002b7; asc         ;;
 1: len 8; hex 0000000000001207; asc         ;;

InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0
 0: len 8; hex 0000000000001201; asc         ;;
 1: len 6; hex 000045f28398; asc   E   ;;
 2: len 7; hex 99000008140084; asc        ;;
 3: len 8; hex 000000000000002f; asc        /;;
 4: len 30; hex 5f6f656d6265645f74696d655f6537383466373232623165363934326432; asc _oembed_time_e784f722b1e6942d2; (total 45 bytes);
 5: len 10; hex 31343933393637323136; asc 1493967216;;

TRANSACTION 4D43FD97, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 0
MySQL thread id 7925, OS thread handle 0x7fceaa099700, query id 201205 localhost host__wordpres_b Sending data
SELECT post_id, meta_key, meta_value FROM h4y9N6M_postmeta WHERE post_id IN (695) ORDER BY meta_id ASC

InnoDB: Submit a detailed bug report to <a href="http://bugs.mysql.com">http://bugs.mysql.com</a>
170627 13:57:59  InnoDB: error clustered record for sec rec not found
InnoDB: index `post_id` of table `host_440969_wordpress_9`.`h4y9N6M_postmeta`
InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
 0: len 8; hex 00000000000002b7; asc         ;;
 1: len 8; hex 0000000000001208; asc         ;;

InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0
 0: len 8; hex 0000000000001201; asc         ;;
 1: len 6; hex 000045f28398; asc   E   ;;
 2: len 7; hex 99000008140084; asc        ;;
 3: len 8; hex 000000000000002f; asc        /;;
 4: len 30; hex 5f6f656d6265645f74696d655f6537383466373232623165363934326432; asc _oembed_time_e784f722b1e6942d2; (total 45 bytes);
 5: len 10; hex 31343933393637323136; asc 1493967216;;

TRANSACTION 4D43FD97, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 0
MySQL thread id 7925, OS thread handle 0x7fceaa099700, query id 201205 localhost host__wordpres_b Sending data
SELECT post_id, meta_key, meta_value FROM h4y9N6M_postmeta WHERE post_id IN (695) ORDER BY meta_id ASC

InnoDB: Submit a detailed bug report to <a href="http://bugs.mysql.com">http://bugs.mysql.com</a>
170627 14:01:12 [ERROR] mysqld: Table './host_477675_loft/wploft_options' is marked as crashed and should be repaired
170627 14:01:12 [Warning] Checking table:   './host_477675_loft/wploft_options'

Отредактированно gettelnet (27.06.2017 11:17:15)

Неактивен

 

Board footer

Работает на PunBB
© Copyright 2002–2008 Rickard Andersson