DescriptionSystem does not start after a power outage or a reboot.
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 shutdown, the database tables can become corrupt
and need to be manually repaired.
ScopeVersion: 7.1.0.306 and Earlier
Solution1. Shutdown the management process:
shutdownCampusMgr -kill
2. Backup 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 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 Note: How to reboot Control and Application servers via CLI