Skip to main content
NetApp Knowledge Base

Data Sense Linux host loses connectivity after reboot

  1. Last updated
  2. Save as PDF
Views:
222
Visibility:
Public
Votes:
0
Category:
netapp_console
Specialty:
netapp_console_platform
Last Updated:

Applies to

  • Cloud Data Sense (BlueXP classification)
  • BlueXP

Issue

Data Sense Linux host was rebooted after patching and was then no longer accessible from the BlueXP connector.

Cause

The Data Sense Linux host server was rebooted, but was set for a DHCP IP address instead of a static IP.
 

From  OCCM.LOG we see

{"log":"2023-09-29 22:16:38,055 UTC ERROR [Working Environment           ] [KTqOMWxD] [             ] [John Doe  ] (oncloud-akka.actor.default-dispatcher-39) [DataSenseOperations:545] Failed getting compliance status. java.lang.IllegalStateException: Cloud Compliance service is currently not available, please try again later\n","stream":"stdout","time":"2023-09-29T22:16:38.055634179Z"}

The  DEBUG-DATASENSE.LOG shows

<<<< Response <<<<
{"state":"NGINX_OFFLINE","deploy_location":"OnPrem","deployment_in_progress":false,"cloud_compliance_deploy_state":"NGINX_OFFLINE","resources_deploy_state":"DEPLOYED_SUCCESSFULLY","deploy_date":"2023-08-18T17:04:28.497076+00:00","cloud_compliance_private_ip":"10.0.0.0","error_type":null,"id":"ONPREM-DEPLOYMENT","cloud_compliance_instance_id":null,"error_message":"Connection refused to 10.0.0.0:443","deploy_version":null,"error_data":null}

Additionally, the connector showed as 'Inactive' when accessing the On-Prem BlueXP

2009771275.jpg

  • The Customer stated the Data Sense host was previously at IP 10.0.0.0 but then changed to some other IP address after it was rebooted due to the Linux server being set for DHCP
  • Attempting to reset the Linux server back to its original IP address did not resolve the connector state or the Data Sense accessibility

Solution

  1. Run the uninstall command (uninstall.sh) on the connector, which will remove the connector from BlueXP
  2. Run the connector software installation again, which will reestablish the active status for the connector in BlueXP
  3. From BlueXP, run the Data Sense installation script and verify the application operation

Partner Notes

None
 

Additional Information

Internal Notes

If the connector is Active in BlueXP, then use this process:

  1. If the Linux host is reachable by its defined address (i.e. 10.0.0.0) and port 443 has been verified to be open, then log in to the CLI of the connector and run

connector~> sudo docker exec cloudmanager_compliance redis-cli set on-prem.cloud_compliance_private_ip "10.0.0.0”

  1. Restart the connector

connector~>  sudo systemctl restart occm

  1. After the connector restarts, try accessing the Data Sense host from the BlueXP interface again

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.