Troubleshooting › Troubleshooting: Unexpected Data Aggregator Shutdown

Troubleshooting: Unexpected Data Aggregator Shutdown

Symptom:

Data Aggregator shuts down unexpectedly.

Solution:

Data Aggregator shuts down if it loses contact with Data Repository. If contact with Data Repository is lost, an audit message is logged in the Data Aggregator installation directory/apache-karaf-2.3.0/shutdown.log file.

Note: The Data Aggregator installation directory/apache-karaf-2.3.0/shutdown_details.log logs heartbeat messages between Data Aggregator and Data Repository, as well as any Data Aggregator shutdowns for debugging purposes.

To resolve any connectivity or other Data Repository issues, perform the following steps:

1. Verify that the Data Repository process is running. Do the following actions:
   1. Log in to the database server you use for Data Repository as the database administrator user, not as the root user.
   2. Type the following command:

      /opt/vertica/bin/adminTools
      

      The Administration Tools dialog opens.

   3. Select (1) View Database Cluster State.

      The returning window should state: “ALL” for Host and “UP” for State.

2. If Data Repository is not running, attempt to start it by performing the following steps:
   1. Log in to the database server you use for Data Repository.
   2. Type the following commands:

      /opt/vertica/bin/adminTools
      

      The Administration Tools dialog opens.

   3. Select (3) Start Database.
   4. Press the Space bar next to the database name, select OK, and press Enter.

      You are prompted for the database password.

   5. Enter the database password and press Enter.

      The Data Repository database starts.

      Note: If you see an error message stating that you cannot connect because of a username or password error, it is possible that a database password change is why Data Aggregator has disconnected from Data Repository.

   6. Select (E) Exit and press Enter.

      If Data Repository does not start, contact CA Technical Support.

3. If Data Repository is running, you have a network connection problem, such as a network latency issue. Address your network connectivity problem.
4. Once Data Aggregator is running again, set up an automatic recovery of the Data Aggregator process.

   Note: For information on setting up an automatic recovery of the Data Aggregator process, see the Data Aggregator Installation Guide.