Форум Сайтостроение Администрирование серверов

Бьётся база данных

12
Plutishe
На сайте с 06.03.2006
Offline
205
Plutishe
1971

Что можно понять из лога: 


141031 20:02:20 InnoDB: The InnoDB memory heap is disabled

141031 20:02:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins

141031 20:02:20 InnoDB: Compressed tables use zlib 1.2.3

141031 20:02:20 InnoDB: Using Linux native AIO

141031 20:02:20 InnoDB: Initializing buffer pool, size = 1000.0M

141031 20:02:20 InnoDB: Completed initialization of buffer pool

141031 20:02:20 InnoDB: highest supported file format is Barracuda.

141031 20:02:20  InnoDB: Waiting for the background threads to start

141031 20:02:21 InnoDB: 5.5.40 started; log sequence number 653355328

141031 20:02:21 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

141031 20:02:21 [Note]   - '0.0.0.0' resolves to '0.0.0.0';

141031 20:02:21 [Note] Server socket created on IP: '0.0.0.0'.

141031 20:02:21 [Note] Event Scheduler: Loaded 0 events

141031 20:02:21 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.5.40-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi

141101 10:44:34 [Warning] IP address '113.138.250.231' could not be resolved: Name or service not known

141102 10:40:02 [Warning] IP address '222.186.30.45' could not be resolved: Name or service not known

141103 12:36:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

141103 12:36:21 InnoDB: The InnoDB memory heap is disabled

141103 12:36:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins

141103 12:36:21 InnoDB: Compressed tables use zlib 1.2.3

141103 12:36:21 InnoDB: Using Linux native AIO

141103 12:36:21 InnoDB: Initializing buffer pool, size = 1000.0M

141103 12:36:21 InnoDB: Completed initialization of buffer pool

141103 12:36:21 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!

141103 12:36:21  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...

141103 12:36:22  InnoDB: Waiting for the background threads to start

141103 12:36:23 InnoDB: 5.5.40 started; log sequence number 697483646

141103 12:36:23 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

141103 12:36:23 [Note]   - '0.0.0.0' resolves to '0.0.0.0';

141103 12:36:23 [Note] Server socket created on IP: '0.0.0.0'.

141103 12:36:23 [Note] Event Scheduler: Loaded 0 events

141103 12:36:23 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.5.40-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi

141103 12:36:34 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:36:34 [ERROR] Got an error from thread_id=2, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 12:36:34 [ERROR] MySQL thread id 2, OS thread handle 0x7f0aaf152700, query id 51 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('95d589468317ce6dd4c6d118f596144d', 'a:5:{s:12:\"sessionStart\";i:1415007393;s:2:\"ip\";i:1123632478;s:9:\"userAgent\";s:72:\"Mozilla/5.0 (compatible; Google$

141103 12:36:51 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:36:51 [ERROR] Got an error from thread_id=4, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 12:36:51 [ERROR] MySQL thread id 4, OS thread handle 0x7f0aaf152700, query id 119 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('ca7a01b458c2b9b0dec748de97e9ca29', 'a:5:{s:12:\"sessionStart\";i:1415007411;s:2:\"ip\";i:1123632478;s:9:\"userAgent\";s:72:\"Mozilla/5.0 (compatible; Google$

141103 12:37:03 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:37:03 [ERROR] Got an error from thread_id=5, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 12:37:03 [ERROR] MySQL thread id 5, OS thread handle 0x7f0aaf152700, query id 167 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('37d1a0cad5248d55ad58c41dc30d9d4f', 'a:5:{s:12:\"sessionStart\";i:1415007423;s:2:\"ip\";i:1123632478;s:9:\"userAgent\";s:72:\"Mozilla/5.0 (compatible; Google$

141103 12:37:08 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:37:08 [ERROR] Got an error from thread_id=6, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 12:37:08 [ERROR] MySQL thread id 6, OS thread handle 0x7f0aaf152700, query id 239 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('766d021cba6ecaf79ab003c76592aaa7', 'a:5:{s:12:\"sessionStart\";i:1415007428;s:2:\"ip\";i:629968147;s:9:\"userAgent\";s:64:\"Mozilla/5.0 (compatible; YandexB$

141103 12:37:13 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:37:13 [ERROR] Got an error from thread_id=7, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226


---------- Добавлено 03.11.2014 в 16:29 ---------- 

myisamchk -css nastej_db/*.MYI





myisamchk: MyISAM file nastej_db/xf_faq_question.MYI

myisamchk: warning: 1 client is using or hasn't closed the table properly

MyISAM-table 'nastej_db/xf_faq_question.MYI' is usable but should be fixed

myisamchk: MyISAM file nastej_db/xf_search_index.MYI

myisamchk: warning: 1 client is using or hasn't closed the table properly

MyISAM-table 'nastej_db/xf_search_index.MYI' is usable but should be fixed

myisamchk: MyISAM file nastej_db/xf_session_admin.MYI

myisamchk: warning: 1 client is using or hasn't closed the table properly

MyISAM-table 'nastej_db/xf_session_admin.MYI' is usable but should be fixed

myisamchk: MyISAM file nastej_db/xf_session.MYI

myisamchk: warning: Table is marked as crashed

myisamchk: warning: 1 client is using or hasn't closed the table properly

myisamchk: warning: Size of datafile is: 1823044         Should be: 1445772

myisamchk: error: record delete-link-chain corrupted

myisamchk: error: Found 4296 keys of 2738

myisamchk: error: Wrong bytesec: 116-97-114 at linkstart: 1418964

MyISAM-table 'nastej_db/xf_session.MYI' is corrupted

База стабильно в 3-4 дня ломается, объём базы 1.5 гб.

Хостинг за РУБЛИ (http://yousite.ru/h) | VPS/VDS на платформе: XEN c администрированием (http://yousite.ru/v) | Регистрация доменов (http://yousite.ru/d)
Plutishe
На сайте с 06.03.2006
Offline
205
Plutishe
#1

Восстановление помогло.

Как понять причину такого поведения? 

141103 16:03:24 [ERROR] MySQL thread id 5445, OS thread handle 0x7f0aaf00d700, query id 253449 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('16c4d3d093f845730d4d8d89ad1044b4', 'a:5:{s:12:\"sessionStart\";i:1415019804;s:2:\"ip\";i:629968147;s:9:\"userAgent\";s:64:\"Mozilla/5.0 (compatible; YandexB$

141103 16:03:32 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 16:03:32 [ERROR] Got an error from thread_id=5446, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 16:03:32 [ERROR] MySQL thread id 5446, OS thread handle 0x7f0aa86c6700, query id 253491 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('aeb8faae602a24a70c9712589eb84259', 'a:5:{s:12:\"sessionStart\";i:1415019812;s:2:\"ip\";i:629968147;s:9:\"userAgent\";s:64:\"Mozilla/5.0 (compatible; YandexB$

141103 16:03:39 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 16:03:39 [ERROR] Got an error from thread_id=5449, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 16:03:39 [ERROR] MySQL thread id 5449, OS thread handle 0x7f0aaf08f700, query id 253664 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('6868e40b2b5a136657860cc331043183', 'a:5:{s:12:\"sessionStart\";i:1415019819;s:2:\"ip\";i:629968147;s:9:\"userAgent\";s:64:\"Mozilla/5.0 (compatible; YandexB$

141103 16:03:47 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 16:03:47 [ERROR] Got an error from thread_id=5450, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 16:03:47 [ERROR] MySQL thread id 5450, OS thread handle 0x7f0aaf0d0700, query id 253706 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('d306b7e822b4b6d3d5d0386aee41777b', 'a:5:{s:12:\"sessionStart\";i:1415019827;s:2:\"ip\";i:629968147;s:9:\"userAgent\";s:64:\"Mozilla/5.0 (compatible; YandexB$

141103 16:03:52 [Note] /usr/libexec/mysqld: Normal shutdown



141103 16:03:52 [Note] Event Scheduler: Purging the queue. 0 events

141103 16:03:54  InnoDB: Starting shutdown...

141103 16:03:55  InnoDB: Shutdown completed; log sequence number 701870940

141103 16:03:55 [Note] /usr/libexec/mysqld: Shutdown complete



141103 16:03:55 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

141103 16:09:45 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

141103 16:09:45 InnoDB: The InnoDB memory heap is disabled

141103 16:09:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins

141103 16:09:45 InnoDB: Compressed tables use zlib 1.2.3

141103 16:09:45 InnoDB: Using Linux native AIO

141103 16:09:45 InnoDB: Initializing buffer pool, size = 1000.0M

141103 16:09:45 InnoDB: Completed initialization of buffer pool

141103 16:09:45 InnoDB: highest supported file format is Barracuda.

141103 16:09:45  InnoDB: Waiting for the background threads to start

141103 16:09:46 InnoDB: 5.5.40 started; log sequence number 701870940

141103 16:09:46 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

141103 16:09:46 [Note]   - '0.0.0.0' resolves to '0.0.0.0';

141103 16:09:46 [Note] Server socket created on IP: '0.0.0.0'.

141103 16:09:46 [Note] Event Scheduler: Loaded 0 events

141103 16:09:46 [Note] /usr/libexec/mysqld: ready for connections.

Спасибо.

lealhost
На сайте с 07.06.2014
Offline
136
lealhost
#2

Перезагружался ли сервер?

Выключался аварийно? Если да, то это вполне нормальное поведение.

Mik Foxi
На сайте с 02.03.2011
Offline
1076
Mik Foxi
#3

диск и файловая система целые? внезапных рестартов и убийств процесса не случается?

Антибот, антиспам, веб файрвол, защита от накрутки поведенческих: https://antibot.cloud/ + партнерка, до 40$ с продажи.
pupseg
На сайте с 14.05.2010
Offline
347
pupseg
#4

место на диске , на разделе где базы? самописных конкрентных запросов не делали ? какие задачи в кроне ?

tmpdir чисто случайно не смотрит в ramdisk ограниченного размера ?

Качественная помощь в обслуживании серверов. (/ru/forum/661100) Бесплатных консультаций не даю, не помогаю, не обучаю. Минималка от 100$. Как пропатчить KDE-просьба не спрашивать. Есть форумы (http://linux.org.ru) и полезные сайты (http://www.opennet.ru/).
Plutishe
На сайте с 06.03.2006
Offline
205
Plutishe
#5 


Filesystem      Size  Used Avail Use% Mounted on

/dev/simfs       50G   17G   34G  33% /



tmp_table_size=264M

tmpdir=/mysqltmp




reboot   system boot  2.6.32-042stab09 Mon Nov  3 12:36 - 17:26  (04:49)

reboot   system boot  2.6.32-042stab09 Fri Oct 31 18:12 - 17:26 (2+23:13)

reboot   system boot  2.6.32-042stab09 Wed Oct 15 22:32 - 17:26 (18+19:53)


---------- Добавлено 03.11.2014 в 17:29 ----------

Это что же получается, из-за перезагрузки в 12-36.... 

141103 12:36:21 InnoDB: Initializing buffer pool, size = 1000.0M

141103 12:36:21 InnoDB: Completed initialization of buffer pool

141103 12:36:21 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!

141103 12:36:21  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...

141103 12:36:22  InnoDB: Waiting for the background threads to start

141103 12:36:23 InnoDB: 5.5.40 started; log sequence number 697483646

141103 12:36:23 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306

141103 12:36:23 [Note]   - '0.0.0.0' resolves to '0.0.0.0';

141103 12:36:23 [Note] Server socket created on IP: '0.0.0.0'.

141103 12:36:23 [Note] Event Scheduler: Loaded 0 events

141103 12:36:23 [Note] /usr/libexec/mysqld: ready for connections.

Version: '5.5.40-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi

141103 12:36:34 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:36:34 [ERROR] Got an error from thread_id=2, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 12:36:34 [ERROR] MySQL thread id 2, OS thread handle 0x7f0aaf152700, query id 51 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('95d589468317ce6dd4c6d118f596144d', 'a:5:{s:12:\"sessionStart\";i:1415007393;s:2:\"ip\";i:1123632478;s:9:\"userAgent\";s:72:\"Mozilla/5.0 (compatible; Google$

141103 12:36:51 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:36:51 [ERROR] Got an error from thread_id=4, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226

141103 12:36:51 [ERROR] MySQL thread id 4, OS thread handle 0x7f0aaf152700, query id 119 localhost nastej_db update

INSERT INTO `xf_session` (`session_id`, `session_data`, `expiry_date`) VALUES ('ca7a01b458c2b9b0dec748de97e9ca29', 'a:5:{s:12:\"sessionStart\";i:1415007411;s:2:\"ip\";i:1123632478;s:9:\"userAgent\";s:72:\"Mozilla/5.0 (compatible; Google$

141103 12:37:03 [ERROR] /usr/libexec/mysqld: Incorrect key file for table './nastej_db/xf_session.MYI'; try to repair it

141103 12:37:03 [ERROR] Got an error from thread_id=5, /builddir/build/BUILD/mysql-5.5.40/storage/myisam/mi_write.c:226


---------- Добавлено 03.11.2014 в 17:36 ----------

Вот бы выяснить от чего была перезагрузка
infant
На сайте с 15.03.2008
Offline
170
infant
#6

чет у вас часто ребуты. Обычно ребут сам по себе не очень страшен, процессы завершаются перед самим ребутом, если только ребут был не "кнопкой".

Поглядите. хватает ли оперативки на работу всех баз сервера, может в ней затырка.

Если не ошибаюсь, то желательно под гиг баз иметь 2 гига рамы.

Plutishe
На сайте с 06.03.2006
Offline
205
Plutishe
#7 

           total       used       free     shared    buffers     cached

Mem:          4096       2409       1686         39          0       1373

-/+ buffers/cache:       1036       3060
infant
На сайте с 15.03.2008
Offline
170
infant
#8

если кроме базы на 1,2 гига больше баз нет, то норм.

Andreyka
На сайте с 19.02.2005
Offline
822
Andreyka
#9

А почему столько ребутов?

Не стоит плодить сущности без необходимости
T
На сайте с 09.12.2011
Offline
55
tls
#10

Можно добавить myisamchk (только аккуратнее с его ключами) в авторан базы или сервера. В Дебиане было как-то так:

# Uncomment the following lines if you want all tables to be automatically
# checked and repaired during startup. You should add sensible key_buffer
# and sort_buffer values to my.cnf to improve check performance or require
# less disk space.
# Alternatively, you can start mysqld with the "myisam-recover" option. See
# the manual for details.
#
# echo "Checking tables in $DATADIR"
# $MY_BASEDIR_VERSION/bin/myisamchk --silent --force --fast --medium-check $DATADIR/*/*.MYI
# $MY_BASEDIR_VERSION/bin/isamchk --silent --force $DATADIR/*/*.ISM
Plutishe:
Вот бы выяснить от чего была перезагрузка

/var/log/messages

/var/log/dmesg

Но для VPS может быть бесполезно.

12

Авторизуйтесь или зарегистрируйтесь, чтобы оставить комментарий