| Cloud Link Service fails to register when you use an older activation package. |
If you have generated a new activation package but used an older activation package to register the Cloud Link Service, the registration fails and no error message is logged. |
To resolve the issue, perform the following steps:
1. Generate and download the new activation package from NetWitness Platform on the cloud. For more information, see Download the Activation Package.
2. Register the Cloud Link Service using the new activation package. For more information, see Register the Cloud Link Service. |
| Cloud Link Service fails to register when the date and time are not in sync with NTP Server. |
If the date and time on the host containing the Cloud Link Service are not in sync with the NTP server, then invalid certificate exceptions are logged. |
Update the date and time to be in sync with the NTP Server.
Execute the following commands to resolve the issue:
1. To display the default date and time on your system, execute the following command: timedatectl status
2. Execute the following command to turn off the NTP Server: timedatectl set-ntp 0
3. Execute the following command to correct the date and time: timedatectl set-time ‘date time’ Replace the default date and time with current date and time. Example: timedatectl set-time '2020-02-02 16:14:50'
4. Execute the following command to turn on the NTP Server: timedatectl set-ntp 1
5. Register the Cloud Link Service by using the recently downloaded activation package. For more information, see Register the Cloud Link Service. |
| Deletion of the Cloud Link Service sensor failed |
If you have removed the Cloud Link Service sensor when the Cloud Link Service is offline, the logs show the Cloud Link Service sensor is deleted, however the Cloud Link service is not deleted and is back online. |
Ensure that you uninstall the Cloud Link Service on the NetWitness Platform soon after you remove it from the NetWitness Cloud Portal UI to delete the Cloud Link Service completely. For more information, see Uninstall the Cloud Link Service. |
| Unable to update the Cloud Link Service due to RPM file download failure. |
During network outage, the RPM file download fails because there is no access to the RPM file URL. |
Check your network connection and try again. If the problem persists, try after some time. |
| Unable to update the Cloud Link Service. |
One of the services might be down or offline. |
Ensure that all the services are up and running. For more details, check the following services log:
- Check the orchestration log on the Admin server: /var/log/netwitness/orchestration-server/orchestration-server.log
- Check the chef-solo.log on the Cloud Link servers: /var/log/netwitness/config-management/chef-solo.log |
| Unable to update the Cloud Link Service due to RPM checksum validation failure. |
The checksum validation of the RPM file fails because of the following reasons:
- The RPM file downloaded is corrupted.
- The RPM file downloaded is incomplete or incorrect. |
Check your network connection and try again. If the problem persists, try after some time. |
| Unable to update the Cloud Link Sensor due to a Timeout. |
If the sensor fails to update within a predefined 60-minute timeframe, an email notification will be sent to the administrators regarding the sensor update timeout failure. The timeout could occur due to network connectivity issues. |
If encountering an update timeout failure, try the following steps:
1. Wait for 30 minutes and then retry the sensor update.
2. Check the following services log:
- Orchestration log on the admin server: /var/log/netwitness/orchestration-server/orchestration-server.log
- Chef-solo.log on the Cloud Link Servers:
/var/log/netwitness/config-management/chef-solo.log
- Cloud Link service logs on the Cloud Link Servers: /var/log/netwitness/cloud-link-server/cloud-link-server.log
For more information, refer to the Orchestration section in the Troubleshooting Installation and Upgrade Issues topic of the NetWitness Upgrade Guide for 12.4.2 version. |
| Unable to update the Cloud Link Sensor due to Canceled operation. |
If the sensor fails to communicate for more than 24 hours after the sensor update is initiated, the system will automatically cancel the sensor update process and an email notification will be sent to the administrator. |
To address the issue, check if the Cloud Link Server is offline. Then try restarting the Cloud Link Server service from the Services page using the following steps:
1. Log in to the NetWitness Platform.
2. Go to  (Admin) > Services.
3. In the Services list, select the Cloud Link Server service.
4. Click  > Start.
5. Additionally, ensure that the internet connection on the Cloud Link Sensor is functioning properly by checking the firewall and network settings. |