When trying to access the CA Performance Management web UI to log in, an error is observed. The error will state:
HTTP ERROR: 503
Problem accessing /pc/redirector. Reason:
Powered by Jetty://
When examining the systems log files, we found the following in the DMService.log file:
ERROR | WrapperSimpleAppMain | 2016-01-11 08:54:00,207 | com.ca.im.portal.api.common.services.impl.database.DBGlobalAttributes
| Error refreshing attributes from database
org.springframework.dao.DataAccessResourceFailureException: nested exception is java.net.ConnectException: Connection refused
Also seen in the systems log files, we found the following in the EMService.log file:
ERROR | pool-4-thread-1 | 2016-01-11 12:24:14,373 | com.ca.im.portal.em.ds.DeletedDataSourceRemover
| Delete of data source failed.
org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [DELETE from items WHERE sourceID=3]; SQL state [HY000]; error code ; Table './em/items' is marked as crashed and last (automatic?) repair failed; nested exception is java.sql.SQLException: Table './em/items' is marked as crashed and last (automatic?) repair failed
Those log files are found in these locations, in a system that uses the default /opt installation directory. Change /opt as needed to specify your installation directory is other than the default was chosen.
These errors are indications that the netqosportal and/or em MySql databases that reside on the CA Performance Manager host have become corrupted.
Unfortunately these problems will not be resolved by a simple restart of services. In order to resolve this we'll need to resolve the corruption with MySql commands after shutting down the CA Performance Manager services, leaving the MySql service running.
After shutting down the four CA Performance Manager services, but leaving the MySql service running, the first step is to determine how extensive the problem is. To do so:
Most common is to see the *.MYI named tables as corrupted in the output. Any tables without an OK will require resolution. If that is what we see the following command(s) will need to be run:
Change the path as needed if other than the default /opt install location was used.
When the "mysqlcheck --all-databases" command is run and all tables are returned as OK, the corruption has been resolved. It is now safe to restart the four CA Performance Manager services. After this the web UI and log in should work. If it does not, please open a new support case for further investigation and resolution.