[RISOLTO] mariadb tabella che crasha

Discussioni relative a Debian e Linux

[RISOLTO] mariadb tabella che crasha

Messaggioda desperados » 08/06/2018, 7:52

ho una VM con 2 vcpu, 3gb ram, mariadb 10.0.32, debian 8.10, centreon (una specie di nagios)
in /var/log/syslog ho:
Jun 8 08:30:06 cloro mysqld: 180608 8:30:06 [ERROR] mysqld: Table './centreon_storage/logs' is marked as crashed and should be repaired
Jun 8 08:30:06 cloro mysqld: 180608 8:30:06 [Warning] Checking table: './centreon_storage/logs'
Jun 8 08:30:10 cloro mysqld: 2018-06-08 08:30:10 7f13ad17c700 InnoDB: Assertion failure in thread 139722485122816 in file btr0cur.cc line 332
Jun 8 08:30:10 cloro mysqld: InnoDB: Failing assertion: btr_page_get_prev(get_block->frame, mtr) == page_get_page_no(page)
Jun 8 08:30:10 cloro mysqld: InnoDB: We intentionally generate a memory trap.
Jun 8 08:30:10 cloro mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Jun 8 08:30:10 cloro mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Jun 8 08:30:10 cloro mysqld: InnoDB: immediately after the mysqld startup, there may be
Jun 8 08:30:10 cloro mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Jun 8 08:30:10 cloro mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... overy.html
Jun 8 08:30:10 cloro mysqld: InnoDB: about forcing recovery.
Jun 8 08:30:10 cloro mysqld: 180608 8:30:10 [ERROR] mysqld got signal 6 ;
Jun 8 08:30:10 cloro mysqld: This could be because you hit a bug. It is also possible that this binary
Jun 8 08:30:10 cloro mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Jun 8 08:30:10 cloro mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.

ma se faccio myisamchk /var/lib/mysql/centreon_storage/logs.MYI
Checking MyISAM file: /var/lib/mysql/centreon_storage/logs.MYI
Data records: 1072973 Deleted blocks: 0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check data record references index: 3
- check data record references index: 4
- check data record references index: 5
- check data record references index: 6
- check data record references index: 7
- check data record references index: 8
- check data record references index: 9
- check data record references index: 10
- check record links

e se controllo la tabella con phpmyadmin mi dice che è ok

poi, avviando mysqltuner
[!!] Log file /var/lib/mysql/cloro.err is empty


in my.cnf c'è
general_log_file = /var/log/mysql/general.log
general_log = 1
log_error = /var/log/mysql/error.log


ps aux
root 599 0.3 0.2 24988 6268 ? S giu07 4:15 /bin/bash /usr/bin/mysqld_safe
mysql 16954 0.9 5.8 1612936 181808 ? Sl 08:30 0:10 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --skip-log-error --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306
root 16955 0.0 0.0 23720 2392 ? S 08:30 0:00 logger -t mysqld -p daemon.error


infine da dentro il db
+-------------------------------------------+--------------------------------------------------------------------------------------------------------------+
| Variable_name | Value |
+-------------------------------------------+--------------------------------------------------------------------------------------------------------------+
| general_log | OFF |
| general_log_file | cloro.log |
| log_error | |
+-------------------------------------------+--------------------------------------------------------------------------------------------------------------+


quindi, in conclusione, non capisco:
1. sta tabella, è corrotta o no?
2. sti log, sono attivi o no?
3. il file di conf, viene letto o no?

forse c'è stato qualche casino nel passaggio da mysql a mariadb?
grazie
Ultima modifica di desperados il 09/06/2018, 11:28, modificato 1 volta in totale.
- Potrebbe esser peggio. - E come? - Potrebbe piovere!
desperados
Hero Member
Hero Member
 
Messaggi: 776
Iscritto il: 22/02/2008, 8:55

Re: mariadb tabella che crasha

Messaggioda desperados » 09/06/2018, 11:28

ho fatto un truncate delle tabelle
Codice: Seleziona tutto
TRUNCATE `data_bin`;
TRUNCATE `index_data`;
TRUNCATE `metrics`;

e adesso pare a posto
amen
- Potrebbe esser peggio. - E come? - Potrebbe piovere!
desperados
Hero Member
Hero Member
 
Messaggi: 776
Iscritto il: 22/02/2008, 8:55


Torna a Generale

Chi c’è in linea

Visitano il forum: Nessuno e 4 ospiti