HTTP 503 error, service unavailable when trying to access CAPC
search cancel

HTTP 503 error, service unavailable when trying to access CAPC

book

Article ID: 8183

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

After installing CAPM 3.2 on Redhat 7.3, you will see an HTTP 503 error, service unavailable when trying to access CAPC.

 

The following error is seems in DMService.log

ERROR | WrapperSimpleAppMain | 2017-09-20 11:00:01,788 | com.ca.im.portal.api.services.datasource.DataSourceService 

| Error: Initializing data source repository: nested exception is java.net.ConnectException: Connection refused 

ERROR | WrapperSimpleAppMain | 2017-09-20 11:00:01,925 | 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 

 

Environment

CAPM 3.2Redhat 7.3

Cause

Services starting out of order

Resolution

To workaround this issue please restart services in the appropriate order

//Stop Services 

  1. systemctl stop caperfcenter_console 
  2. systemctl stop caperfcenter_devicemanager 
  3. systemctl stop caperfcenter_sso 
  4. systemctl stop caperfcenter_eventmanager 
  5. systemctl stop mysql 

 

//Start Services 

  1. systemctl start mysql 
  2. systemctl start caperfcenter_sso 
  3. systemctl start caperfcenter_devicemanager 
    • tail -f DMService.log for the following line: Started ServerConnector@...
  4. Wait until you see Started ServerConnector@...
  5. systemctl start caperfcenter_console 
  6. systemctl start caperfcenter_eventmanager 

Additional Information

Issue could also be seen after a reboot of the system