Troubleshooting Tip: System will not start up, GUI shows Processes are Down after a power failure or reboot

[FortiKoala]

Description

This article describes how to resolve an issue where the system does not start after a power outage or a reboot.       

Scope

Version: 7.1.0.306 and Earlier.

Solution

Control processes are not running.  To verify, type:

jps 

If Control processes are down, 'Yams' entries will be missing.

Example:

> jps
2339 Jps
16725 TomcatAdmin
16848 TomcatPortal  
4996 CampusManager

Additionally, /bsc/logs/output.processManager log displays the following output:

Error: mysql database is corrupt.
First backup the database:
/bsc/campusMgr/master_loader/mysql/ydb_dated_backup
Then attempt to repair the database:
mysqlcheck --repair bsc

After a power outage or a hard reboot without being properly shut down, the database tables can become corrupt and need to be manually repaired. 

1. Shut down the management process:

shutdownCampusMgr -kill

2. Back up the database.

/bsc/campusMgr/master_loader/mysql/ydb_dated_backup

3. Repair the database

mysqlcheck --repair bsc

Note: If a table is repaired, run the command again to ensure no further repairs are necessary.

4. Start the management process:
   
   

startupCampusMgr

5. Wait 5 minutes (possibly longer depending upon the size of the database) and verify control processes are started.
   
   

> jps
30450 TomcatAdmin
30179 Yams
30357 TomcatPortal
30070 Yams
7855 Jps
29327 CampusManager

Related articles:

Technical Tip: How to reboot Control and Application servers via CLI