Bonsoir,
alors voilà, j’ai un problème avec mariadb,
Suite à un crash (ou une coupure de cournat pendant la journée, je ne suis pas sur), ma base de donnée est corrompue:
systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Tue 2018-01-16 22:51:42 CET; 28min ago
Process: 1184 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
Jan 16 22:51:42 YunoHost /etc/init.d/mysql[2121]: 0 processes alive and ‘/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping’ resulted in
Jan 16 22:51:42 YunoHost /etc/init.d/mysql[2121]:
Jan 16 22:51:42 YunoHost /etc/init.d/mysql[2121]:
Jan 16 22:51:42 YunoHost mysql[1184]: Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jan 16 22:51:42 YunoHost systemd[1]: mysql.service: control process exited, code=exited status=1
Jan 16 22:51:42 YunoHost systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jan 16 22:51:42 YunoHost systemd[1]: Unit mysql.service entered failed state.
et
tail -n 50 /var/lib/mysql/*.err
180116 23:07:30 [Note] InnoDB: Using Linux native AIO
180116 23:07:30 [Note] InnoDB: Not using CPU crc32 instructions
180116 23:07:30 [Note] InnoDB: Initializing buffer pool, size = 256.0M
180116 23:07:30 [Note] InnoDB: Completed initialization of buffer pool
180116 23:07:30 [Note] InnoDB: Highest supported file format is Barracuda.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 16074240
180116 23:07:31 [Note] InnoDB: 128 rollback segment(s) are active.
180116 23:07:31 [Note] InnoDB: Starting in background the rollback of recovered transactions
2018-01-16 23:07:31 54bff420 InnoDB: Rolling back trx with id 16072969, 1 rows to undo
180116 23:07:31 [Note] InnoDB: Waiting for purge to start
2018-01-16 23:07:31 54bff420 InnoDB: Assertion failure in thread 1421866016 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
180116 23:07:31 [ERROR] mysqld got signal 6 ;
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 https://mariadb.com/kb/en/reporting-bugs
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: 10.0.32-MariaDB-0+deb8u1
key_buffer_size=16384
read_buffer_size=262144
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 50911 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = 0x0 thread_stack 0x20000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
180116 23:07:31 mysqld_safe mysqld from pid file /var/lib/mysql/YunoHost.pid ended
J’essaye de récupérer le coup avec innodb_force_recovery jusqu’à 3, mais cela ne fonctionne pas.
Qu’à cela ne tiennent me dis-je, je vais restaurer ma sauvegarde de cette nuit, il ne s’est pas passé grand chose je ne devrais pas perdre trop de données… sauf que voilà:
mysql -u nextcloud -p nextcloud < /media/PersonnalCloud/tmp/nextcloud-dbbackup_20180116.bak
Enter password:
ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”)
Et là, je ne sais plus quoi faire?
Une âme charitable pour m’aider?
MErci!
Krakinou
… Du coup il faudrait arrêter cette commande avant de tenter de relancer proprement mysql.
)