"Service Unreachable" When Accessing Device Performance in Topology Due to netops-da-graphql authentication failure

Products

• Network Observability

Issue/Introduction

 

• Users encounter a "'Service Unreachable' when trying to access device Performance in Topology" message.

   

• The netops-da-graphql service on the Data Aggregator (DA) is in a failed state and continuously attempts to auto-restart (Result: exit-code).

   

• The netops-da-graphql.log file contains Spring Application run failures, specifically: Error creating bean with name 'queryResolver' and Error creating bean with name 'DASecurityDAO': Invocation of init method failed.

   

• The netops-da-graphql.log file also shows severe database connection errors: java.sql.SQLInvalidAuthorizationSpecException: [Vertica][VJDBC] (2248) FATAL: Authentication failed for username "dauser"

 

Environment

DX NetOps Performance Management: All versions.

Cause

The netops-da-graphql service fails to start because it cannot authenticate with the Vertica database (Data Repository). This occurs when the database password defined in the application.properties file is either incorrect or improperly encrypted.

Resolution

To resolve this issue, you must regenerate the encrypted password string and apply it to the configuration file.

1. Navigate to the GraphQL scripts directory on the Data Aggregator: /opt/IMDataAggregator/netqos-da-graphql/scripts.

2. Execute the encrypt.sh script to encrypt the correct Vertica database password. Note: You must enclose the password in single quotes if a $ is included in the password.

   Example command: ./encrypt.sh '<Your_Vertica_Password>'

3. Copy the encoded string returned by the script.

4. Open the application properties file, typically located at /opt/IMDataAggregator/netops-da-graphql/config/application.properties.

5. Update the value of the password parameter with your newly generated string:

   spring.da.datasource.password=<new_encoded_string>

6. Start the netops-da-graphql service.

7. Verify that performance data now loads successfully within the Topology view.