|
05.10.2015, 12:38:43
#39068316
Ссылка:
Ссылка на сообщение:
Ссылка с названием темы:
|
|
|
|
Падает переодически Mysql, затем перезапускается, работает, потом через 5 секунд или через 5 часов опять падает.
Не могу понять в чем причина, соседний сервер с такими же примерно нагрузками нормально работает. Вот лог mysql.err. Вначале пару запросов с предупреждениями, затем строчка "Killed"(выделил красным), потом эта строчка будет после строки [Warning] "Checking table: './e92/answer_archive'":
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 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. 100. 101. 102. 103. 104. 105. 106. 107. 108. 109. 110. 111. 112. 113. 114. 115. 116. 117. 118. 119. 120. 121. 122. 123.
2015-10-05 11:35:44 18416 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Statement: INSERT INTO `answer_archive`
SELECT a.id, a.date, a.id_request, a.answer_type, a.id_answer_type_user, a.price, a.comment, a.comment_manager,
a.id_firms, a.id_answered, a.id_answered_admin, a.date_get_request, a.date_answered,
a.count_chat_message, a.chat_show_to_firm, a.chat_disable_to_user, a.hash_au, a.sms_send,
a.cost, a.cost_is_unlimited, a.cost_is_free, a.purchase_flag
FROM answer a LEFT JOIN request r ON r.id = a.id_request WHERE r.id IN (749050)
2015-10-05 11:35:44 18416 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT INTO `answer_chat_archive`
SELECT ch.id, ch.id_answer, ch.author, ch.date, ch.seen, ch.message
FROM answer_chat ch LEFT JOIN answer a ON a.id = ch.id_answer LEFT JOIN request r ON r.id = a.id_request
WHERE r.id IN (749050)
2015-10-05 11:35:45 18416 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Statement: INSERT INTO `answer_archive`
SELECT a.id, a.date, a.id_request, a.answer_type, a.id_answer_type_user, a.price, a.comment, a.comment_manager,
a.id_firms, a.id_answered, a.id_answered_admin, a.date_get_request, a.date_answered,
a.count_chat_message, a.chat_show_to_firm, a.chat_disable_to_user, a.hash_au, a.sms_send,
a.cost, a.cost_is_unlimited, a.cost_is_free, a.purchase_flag
FROM answer a LEFT JOIN request r ON r.id = a.id_request WHERE r.id IN (749052)
2015-10-05 11:35:45 18416 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT INTO `answer_chat_archive`
SELECT ch.id, ch.id_answer, ch.author, ch.date, ch.seen, ch.message
FROM answer_chat ch LEFT JOIN answer a ON a.id = ch.id_answer LEFT JOIN request r ON r.id = a.id_request
WHERE r.id IN (749052)
Killed
151005 11:40:15 mysqld_safe Number of processes running now: 0
151005 11:40:15 mysqld_safe mysqld restarted
2015-10-05 11:40:16 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2015-10-05 11:40:16 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-10-05 11:40:16 0 [Note] /usr/sbin/mysqld (mysqld 5.6.25-1~dotdeb+7.1-log) starting as process 17321 ...
2015-10-05 11:40:16 17321 [Note] Plugin 'FEDERATED' is disabled.
2015-10-05 11:40:16 7f6f528b4720 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-10-05 11:40:16 17321 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-10-05 11:40:16 17321 [Note] InnoDB: The InnoDB memory heap is disabled
2015-10-05 11:40:16 17321 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-10-05 11:40:16 17321 [Note] InnoDB: Memory barrier is not used
2015-10-05 11:40:16 17321 [Note] InnoDB: Compressed tables use zlib 1.2.7
2015-10-05 11:40:16 17321 [Note] InnoDB: Using Linux native AIO
2015-10-05 11:40:16 17321 [Note] InnoDB: Using CPU crc32 instructions
2015-10-05 11:40:16 17321 [Note] InnoDB: Initializing buffer pool, size = 700.0M
2015-10-05 11:40:16 17321 [Note] InnoDB: Completed initialization of buffer pool
2015-10-05 11:40:16 17321 [Note] InnoDB: Highest supported file format is Barracuda.
2015-10-05 11:40:16 17321 [Note] InnoDB: The log sequence numbers 2063930440861 and 2063930440861 in ibdata files do not match the log sequence number 2064079407398 in the ib_logfiles!
2015-10-05 11:40:16 17321 [Note] InnoDB: Database was not shutdown normally!
2015-10-05 11:40:16 17321 [Note] InnoDB: Starting crash recovery.
2015-10-05 11:40:16 17321 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-10-05 11:40:17 17321 [Note] InnoDB: Restoring possible half-written data pages
2015-10-05 11:40:17 17321 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 1651412, file name mysql-bin.000305
2015-10-05 11:40:20 17321 [Note] InnoDB: 128 rollback segment(s) are active.
2015-10-05 11:40:20 17321 [Note] InnoDB: Waiting for purge to start
2015-10-05 11:40:20 17321 [Note] InnoDB: 5.6.25 started; log sequence number 2064079407398
2015-10-05 11:40:20 17321 [Note] Recovering after a crash using /var/lib/mysql/mysql-bin
2015-10-05 11:40:20 17321 [Note] Starting crash recovery...
2015-10-05 11:40:20 17321 [Note] Crash recovery finished.
2015-10-05 11:40:21 17321 [Note] Server hostname (bind-address): '*'; port: 3306
2015-10-05 11:40:21 17321 [Note] IPv6 is available.
2015-10-05 11:40:21 17321 [Note] - '::' resolves to '::';
2015-10-05 11:40:21 17321 [Note] Server socket created on IP: '::'.
2015-10-05 11:40:21 17321 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2015-10-05 11:40:21 17321 [Warning] Slave SQL: If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0
2015-10-05 11:40:21 17321 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000118' at position 14185943, relay log '/var/lib/mysql/master1-relay-bin.000472' position: 9450212
2015-10-05 11:40:22 17321 [Note] Slave I/O thread: connected to master 'replication_e92@62.76.191.211:3306',replication started in log 'mysql-bin.000118' at position 14185943
2015-10-05 11:40:24 17321 [Note] Event Scheduler: Loaded 0 events
2015-10-05 11:40:24 17321 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.25-1~dotdeb+7.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
2015-10-05 11:40:45 17321 [ERROR] /usr/sbin/mysqld: Table './e92/answer_archive#P#p_580' is marked as crashed and should be repaired
2015-10-05 11:40:46 17321 [ERROR] /usr/sbin/mysqld: Table './e92/answer_archive#P#p_580' is marked as crashed and should be repaired
2015-10-05 11:40:46 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:01 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:15 17321 [Warning] Hostname '62-76-191-211.clodo.ru' does not resolve to '62.76.191.211'.
2015-10-05 11:41:15 17321 [Note] Hostname '62-76-191-211.clodo.ru' has the following IP addresses:
2015-10-05 11:41:15 17321 [Note] - 62.76.182.7
2015-10-05 11:41:15 17321 [Note] - 85.143.166.7
2015-10-05 11:41:15 17321 [Note] - 62.76.181.213
2015-10-05 11:41:15 17321 [Note] - 62.76.182.8
2015-10-05 11:41:15 17321 [Note] - 85.143.166.6
2015-10-05 11:41:15 17321 [Note] - 62.76.181.212
2015-10-05 11:41:17 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:22 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:28 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:33 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:35 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:39 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:42 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:41:52 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:42:02 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:42:10 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:42:18 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:42:46 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:42:54 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:42:58 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:01 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:05 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:07 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:12 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:17 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:22 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:29 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:43:39 17321 [Warning] Checking table: './e92/answer_archive'
2015-10-05 11:44:03 17321 [ERROR] /usr/sbin/mysqld: Table './e92_newsletter/campaigns' is marked as crashed and should be repaired
2015-10-05 11:44:03 17321 [Warning] Checking table: './e92_newsletter/campaigns'
2015-10-05 11:44:23 17321 [Warning] Checking table: './e92/answer_archive'
Killed
151005 11:48:59 mysqld_safe Number of processes running now: 0
151005 11:48:59 mysqld_safe mysqld restarted
2015-10-05 11:49:00 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2015-10-05 11:49:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-10-05 11:49:00 0 [Note] /usr/sbin/mysqld (mysqld 5.6.25-1~dotdeb+7.1-log) starting as process 23834 ...
2015-10-05 11:49:00 23834 [Note] Plugin 'FEDERATED' is disabled.
2015-10-05 11:49:00 7f7b6c2a8720 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-10-05 11:49:00 23834 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-10-05 11:49:00 23834 [Note] InnoDB: The InnoDB memory heap is disabled
2015-10-05 11:49:00 23834 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-10-05 11:49:00 23834 [Note] InnoDB: Memory barrier is not used
2015-10-05 11:49:00 23834 [Note] InnoDB: Compressed tables use zlib 1.2.7
2015-10-05 11:49:00 23834 [Note] InnoDB: Using Linux native AIO
2015-10-05 11:49:00 23834 [Note] InnoDB: Using CPU crc32 instructions
2015-10-05 11:49:00 23834 [Note] InnoDB: Initializing buffer pool, size = 700.0M
2015-10-05 11:49:00 23834 [Note] InnoDB: Completed initialization of buffer pool
2015-10-05 11:49:00 23834 [Note] InnoDB: Highest supported file format is Barracuda.
2015-10-05 11:49:00 23834 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2064081371270
2015-10-05 11:49:00 23834 [Note] InnoDB: Database was not shutdown normally!
2015-10-05 11:49:00 23834 [Note] InnoDB: Starting crash recovery.
2015-10-05 11:49:00 23834 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-10-05 11:49:01 23834 [Note] InnoDB: Restoring possible half-written data pages
2015-10-05 11:49:01 23834 [Note] InnoDB: from the doublewrite buffer...
|
|
|