Skip to main content
ndumaj
Staff
Staff
May 29, 2026

Troubleshooting Tip: Unable to perform FortiNAC upgrade due to '[ERROR] mariadbd: Index for table 'CONNECTIONLOG' is corrupt; try to repair it'

  • May 29, 2026
  • 0 replies
  • 47 views

Description

This article describes the required steps to complete a FortiNAC upgrade when the following error is observed in the /var/log/mysql.log file:

YYYY-MM-DD TT-MM-SS 16 [ERROR] Got error 126 when reading table './bsc/CONNECTIONLOG'
YYYY-MM-DD TT-MM-SS 16 [ERROR] mariadbd: Index for table 'CONNECTIONLOG' is corrupt; try to repair it
YYYY-MM-DD TT-MM-SS 16 [ERROR] InnoDB: We detected index corruption in an InnoDB type table. You have to dump + drop + reimport the table or, in a case of widespread corruption, dump all InnoDB tables and recreate the whole tablespace. If the mariadbd server crashes after the startup or when you dump the tables. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

Scope

FortiNAC-F.

Solution

Verify the error in Grab-snapshot-log/logs/mysqld.log.txt:


YYYY-MM-DD TT-MM-SS 16 [ERROR] Got error 126 when reading table './bsc/CONNECTIONLOG'
YYYY-MM-DD TT-MM-SS 16 [ERROR] mariadbd: Index for table 'CONNECTIONLOG' is corrupt; try to repair it
YYYY-MM-DD TT-MM-SS 16 [ERROR] InnoDB: We detected index corruption in an InnoDB type table. You have to dump + drop + reimport the table or, in a case of widespread corruption, dump all InnoDB tables and recreate the whole tablespace. If the mariadbd server crashes after the startup or when you dump the tables. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.


Note: The affected table (e.g., ./bsc/CONNECTIONLOG) may vary depending on the environment and can include other tables such as./bsc/groupMembership, ./bsc/radpostauth, or similar.

Important: Ensure that a VM backup/snapshot and an external database backup are taken before proceeding.

Use the OPTIMIZE TABLE command to attempt to resolve the issue:

execute service stop nac 
execute db-shell
OPTIMIZE TABLE CONNECTIONLOG;
quit
execute service start nac 


If the OPTIMIZE TABLE operation does not resolve the issue, proceed with the ALTER TABLE option:

execute service stop nac 
execute db-shell 
ALTER TABLE CONNECTIONLOG ENGINE=InnoDB; 
quit 
execute service start nac

    Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
    Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
    Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT