Discussion :

[Blo0d4x3]

Bonjour,

Suite a une coupure electrique, mon mysql (5.5.62-0+deb8u1 sur une raspbian 8.0) refuse de se relancer. J'ai ceci dans les logs,

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

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
 
90107 12:44:53 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190107 12:44:53 [Note] Plugin 'FEDERATED' is disabled.
190107 12:44:54 InnoDB: The InnoDB memory heap is disabled
190107 12:44:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190107 12:44:54 InnoDB: Compressed tables use zlib 1.2.8
190107 12:44:54 InnoDB: Using Linux native AIO
190107 12:44:54 InnoDB: Initializing buffer pool, size = 128.0M
190107 12:44:54 InnoDB: Completed initialization of buffer pool
190107 12:44:54 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 39013965499
190107 12:44:54  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...
InnoDB: Doing recovery: scanned up to log sequence number 39013974050
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 A768700
190107 12:44:58  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 
InnoDB: Apply batch completed
190107 12:44:59  InnoDB: Waiting for the background threads to start
InnoDB: Starting in background the rollback of uncommitted transactions
190107 12:44:59  InnoDB: Rolling back trx with id A7685DC, 1 rows to undo
190107 12:44:59  InnoDB: Assertion failure in thread 1715467344 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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
11:44:59 UTC - 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.
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.
 
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346093 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 = 0 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.

J'ai tenté de mettre un innodb_force_recovery = 1 dans my.cnf, ca n'a rien changé, et j'ai jamais vu un output comme cela, si ca parle à quelqu'un merci d'avance .

[SQLpro]

Visiblement vous avez des bibliothèques de code qui sont corrompues. MySQL étant le SGBDR le moins fiable de très loin, cela arrive régulièrement…
Donc, il faut tout réinstaller.

A +

[Blo0d4x3]

Je m'en suis sorti, j'ai juste ajouté dans le fichier my.conf ceci: innodb_force_recovery=6