Data Aggregator fails to start after upgrade

Document ID : KB000045445
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

Data Aggregator fails to start correctly

 

Configuration:

  • Data Aggregator upgraded to newer release
  • Problem observed during 2.3.2 to 2.4.1 upgrade
  • Problem possible for any release

 

Symptoms:

There are a few ways to observe this problem.

  • Run "ps -ef | grep -i java"; observe only one java process for Data Aggregator; likely missing the activemq process
  • Run "service activemq status" returns errors; "service dadaemon status" is successful
  • Java processes present in the system for the Data Aggregator are not owned or run by the correct user. IE: install owned by root, runs as non-root user.
  • Data Aggregator fails to synchronize with CAPC 

 

Cause:

  • One of two things must take place on the Data Aggregator host for this problem to be seen. Both revolve around install owner changes being made.

A: Installed Data Aggregator using the root user; post installation Data Aggregator related file ownership was changed to the a new sudo-root configured user for ownership; the /etc/DA.cfg file da.user value was not updated to reflect the new user ownership.

B: Installed Data Aggregator using the root user; post installation the /etc/DA.cfg file da.user value was changed; remaining installed Data Aggregator related file ownership was not updated to reflect the new user ownership.

  • In both of these cases post upgrade we can end up with incorrect user references that will prevent correct Data Aggregator start up.
  • In this case specifically we're addressing cause possibility number one above, where the /etc/DA.cfg file is left with the wrong value. In this case, while all other file ownership was accurate, start up file user references were causing the problem.
  • During the upgrade, when the installation rebuilds the /etc/init.d dadaemon and activemq start up scripts, it uses the user from da.user in the /etc/DA.cfg file. In this situation the da.user value was not the root user like it should have been. Thus all user references in the start up scripts referenced the wrong non-root user.

 

Solution:

  1. Modify the da.user value in the /etc/DA.cfg file to show the correct user that should own the installation.
  2. Edit the dadaemon and activemq scripts in /etc/init.d changing all user references to the correct install owner user.