ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Data Aggregator Service down in CA Performance Management (CAPM)

book

Article ID: 111076

calendar_today

Updated On:

Products

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

Issue/Introduction

The Data Aggregator (DA) stops when there is nothing wrong with it and no manual shutdown of services has occurred.

Cause

Karaf.log shows the DA lost connection to the DR. And that is why the DA shutdown.

ERROR | anager-thread-13 | 2018-08-03 23:31:49,439 | shutdown | tTolerantDBConnectionManagerImpl 179 | ommon.core.services.impl | | The primary data repository host '<DR_HOST_NAME>' is no longer available, and there are no available secondary hosts. Current Host Status: {<DR_HOST_NAME>=DOWN

Environment

DX NetOps CAPM, all releases.

Resolution

Check if the Vertica DB on the Data Repository (DR) is up and running. For example, as the dradmin user on the DR, run:

$ /opt/vertica/bin/admintools -t list_allnodes

This will output something similar to (for a 3-node cluster):

 Node              | Host           | State | Version         | DB

-------------------+----------------+-------+-----------------+--------

 v_drdata_node0001 | XXX.XXX.XXX.1  | UP    | vertica-9.1.1.5 | drdata

 v_drdata_node0002 | XXX.XXX.XXX.2  | UP    | vertica-9.1.1.5 | drdata

 v_drdata_node0003 | XXX.XXX.XXX.3  | UP    | vertica-9.1.1.5 | drdata

If it isn't up and running, then start it as the DA can only function when Vertica is running. Its also possible that network issues may hinder the connection between the various components and make it appear to the DA that the DR is down.

Then restart the DA services.