search cancel

Data Aggregator is Not Starting Up

book

Article ID: 255646

calendar_today

Updated On:

Products

DX NetOps

Issue/Introduction

When I try to start the dadaemon service on our DA, it's saying it starts and the status check says "running", but then after a few seconds it gots back to failed, as shown below here.

[[email protected] ~]# service dadaemon status
Redirecting to /bin/systemctl status dadaemon.service
‚óŹ dadaemon.service - Data Aggregator
   Loaded: loaded (/etc/systemd/system/dadaemon.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2022-12-05 11:26:50 EST; 7min ago
  Process: 1454881 ExecStop=/opt/CA/IMDataAggregator/scripts/dadaemon stop sysd (code=exited, status=0/SUCCESS)
  Process: 2384713 ExecStart=/opt/CA/IMDataAggregator/scripts/dadaemon start sysd (code=exited, status=0/SUCCESS)
 Main PID: 2384815 (code=exited, status=1/FAILURE)

Dec 05 11:26:22 tda302 systemd[1]: Starting Data Aggregator...
Dec 05 11:26:22 tda302 dadaemon[2384732]: Starting activemq.
Dec 05 11:26:22 tda302 dadaemon[2384732]: Failed to start service activemq
Dec 05 11:26:22 tda302 dadaemon[2384713]: .lock file found, backing up data & deploy, clearing karaf cache
Dec 05 11:26:22 tda302 dadaemon[2384713]: Starting IM Data Aggregator
Dec 05 11:26:22 tda302 dadaemon[2384713]: CEF:0|Broadcom|DX NetOps Data Aggregator|21.2.10.382|100|STARTING SERVICE|1|suser=daadmin shost=tda302
Dec 05 11:26:22 tda302 systemd[1]: Started Data Aggregator.
Dec 05 11:26:50 tda302 systemd[1]: dadaemon.service: Main process exited, code=exited, status=1/FAILURE
Dec 05 11:26:50 tda302 systemd[1]: dadaemon.service: Failed with result 'exit-code'.

Environment

Release : 21.2

Cause

The vertica database was not running. This is the error from the Data Aggregator karaf.log 

java.sql.SQLNonTransientConnectionException: [Vertica][VJDBC](100176) Failed to connect to host HOST.company.com on port 5433. Reason: Failed to establish a connection to the primary server or any backup address.

Resolution

You need go into admintools on the DR and start the database. 

su dradmin

cd /opt/vertica/bin

./admintools 

select start database