Troubleshooting Tip: FortiNAC Manager node unable to recover from 'Failed' state
| Description | This article describes how to recover the FortiNAC Manager node when it shows 'Failed' state in GUI dashboard and output.processManager generates event: 'ERROR yams.CampusManager - CM Exception java.io.EOFException: null'. |
| Scope | FortiNAC-F. |
| Solution | The following events in output.processManager show that the /bsc/campusMgr/.keystore file is corrupted and will prevent the GUI and management processes from starting:
2026-01-20 15:39:36.254 +0300 [main] INFO yams.CampusManager - **** naclab1.forti.lab Start Time Tue Jan 20 15:39:36 TRT 2026 *****
To solve the problem, do the following:
In the FortiNAC CLI, configure the following:
execute restore backup local 'Hostname' 'Year-Month-Day'.
Example:
fortinac # execute restore backup local naclab1 2026-02-17 A reboot is required to complete the backup restoration. Do you wish to reboot now? (y/N) y
Before doing the reset, take a Database backup. Database files are stored as /bsc/backups/database/FortiNAC_DataBase_BackUp_<yy_mm_dd_hh_mm_ss>_<Hostname>.gz.
Reset FortiNAC from the CLI:
execute factoryreset2 all-settings
The option 'factoryreset2' is chosen since it will wipe data partitions but will keep network settings.
After rebooting FortiNAC, restore the database file that was saved previously. Transfer the database file to /bsc/backups/database/ and restore it from the GUI.
To restore the database from the CLI:
naclab1 # execute restore database local FortiNAC_DataBase_BackUp_<yy_mm_dd_hh_mm_ss>_<Hostname>.gz Restoring FortiNAC_DataBase_BackUp_2026_02_17_11_50_03_naclab1.gz... Restore complete naclab1 #
Documentation: |