HTTP error 500 - cannot connect to 3308

Document ID : KB000104019
Last Modified Date : 03/07/2018
Show Technical Document Details
Issue:
We get an HTTP error 500 when we try to open the NFA console
The mysql .err file contains errors about :
The log sequence numbers xxx in ibdata files do not match the log sequence number
yyy in the ib_logfiles!
Environment:
NFA 9.3.3
Cause:
The CA Mysql service is starting / stopping continually ;
there is 2 mysqld process running .

mysqld try to do 1 recovery but no success .
in the ../mysql/data/*.err log :
InnoDB: Assertion failure in thread 7580 in file btr0cur.cc line 274
InnoDB: Failing assertion: btr_page_get_next(get_block->frame, mtr) == page_get_page_no(page)
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.
...
InnoDB: The log sequence numbers 65100150405 and 65100150405 in ibdata files do not match the log sequence number 2501369019794 in
2018-06-27 09:15:23 4868 [Note] InnoDB: Database was not shutdown normally!
 
Resolution:
CA Mysql crashed and transaction log corrupted
Need to restore ../CA/NFA/mysql/* from old backup and reboot server
(or reinstall Mysql product and restore the bases if no Mysql backup)