Erreur mysql suite reboot


#1

Salut !

Mon installation de gladys fonctionnait bien, et tellement bien depuis quelques jour que j’ai eu l’idée de faire un backup avec win32 imager pour ne pas perdre tout ce que j’avais fais. Chose que j’avais déjà réalisé sans souci.

Sauf que là, impossible de redémarrer gladys. Je parcours les logs et j’ai l’impression que c’est grave docteur…

les logs gladys :

/home/pi/.pm2/logs/gladys-error-0.log last 15 lines:
    0|gladys   | Error: connect ECONNREFUSED 127.0.0.1:3306
    0|gladys   |     at afterwards (/home/pi/gladys/node_modules/sails-mysql/lib/connections/spawn.js:72:13)
    0|gladys   |     at /home/pi/gladys/node_modules/sails-mysql/lib/connections/spawn.js:40:7
    0|gladys   |     at Handshake.onConnect [as _callback] (/home/pi/gladys/node_modules/mysql/lib/Pool.js:54:9)
    0|gladys   |     at Handshake.Sequence.end (/home/pi/gladys/node_modules/mysql/lib/protocol/sequences/Sequence.js:96:24)
    0|gladys   |     at Protocol.handleNetworkError (/home/pi/gladys/node_modules/mysql/lib/protocol/Protocol.js:364:14)
    0|gladys   |     at PoolConnection.Connection._handleNetworkError (/home/pi/gladys/node_modules/mysql/lib/Connection.js:421:18)
    0|gladys   |     at emitOne (events.js:116:13)
    0|gladys   |     at Socket.emit (events.js:211:7)
    0|gladys   |     at emitErrorNT (internal/streams/destroy.js:64:8)
    0|gladys   |     at _combinedTickCallback (internal/process/next_tick.js:138:11)
    0|gladys   |     at process._tickDomainCallback (internal/process/next_tick.js:218:9)

les logs mysql :

pi@gladys:~ $ systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: signal) since Tue 2019-01-29 20:47:33 UTC; 4s ago
  Process: 28266 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
  Process: 28177 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
  Process: 28173 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 28165 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 28266 (code=killed, signal=ABRT)
   Status: "InnoDB: Fatal: Ending processing because of a corrupt database page."
   CGroup: /system.slice/mariadb.service

Jan 29 20:47:33 gladys systemd[1]: Failed to start MariaDB database server.
Jan 29 20:47:33 gladys systemd[1]: mariadb.service: Unit entered failed state.
Jan 29 20:47:33 gladys systemd[1]: mariadb.service: Failed with result 'signal'.

et pour finir le contenu du fichier /var/log/mysql/error.log

InnoDB: End of page dump
2019-01-29 20:50:05 768a9000 InnoDB: uncompressed page, stored checksum in field1 4294967295, calculated checksums for field1: crc32 2794410118, innodb 1239623680, none 3735928559, stored checksum in field2 4294967295, calculated checksums for field2: crc32 2794410118, innodb 391864832, none 3735928559, page LSN 4294967295 4294967295, low 4 bytes of LSN at page end 4294967295, page number (if stored to page already) 4294967295, space id (if created with >= MySQL-4.1.1 and stored already) 4294967295
InnoDB: page type 65535 meaning PAGE TYPE CORRUPTED
2019-01-29 20:50:05 1988792320 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-01-29 20:50:05 1988792320 [ERROR] InnoDB: Ending processing because of a corrupt database page.
2019-01-29 20:50:05 768a9000  InnoDB: Assertion failure in thread 1988792320 in file ha_innodb.cc line 21990
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.
190129 20:50:05 [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.1.23-MariaDB-9+deb9u1
key_buffer_size=16777216
read_buffer_size=131072
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 = 351335 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 0x30000
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.

Si quelqu’un pouvait me dire que j’ai raté un truc et que ca ne vient pas de ma SD j’en serait ravie :smiley:
Merci d’avance pour votre aide.


#2

Il semblerait qu’un fichier de ta DB soit dans un mauvais état. Est-ce lié à la SD ou simple erreur système, difficile à dire dans l’immédiat sachant que “ça peut arriver” (corruption de table MySQL).

As-tu tenté de suivre la procédure présentée ici ? (fais-toi peut-être un backup de tes fichiers DB avant… par sécu…)


#3

Pas mieux. C’est la deuxième fois que j’ai ce souci. Je pense que ça vient de la carte SD. Je vais repartir d’une sauvegarde.
Merci en tout cas.