Commvault Live Sync Server Failing Readiness Check

Hi ​@Ivanav ,

The error "Internal error occurred -5" usually points to a certificate-related issue with your StandBy Failover client. This could be due to either the lack of an active certificate or the presence of an invalid one.

To resolve this, you may need to regenerate a new certificate for the 'masi_StandBy_LiveSync' client. You can do this from the CommCell Console by navigating to the Home tab, then clicking Control Panel > Certificate Administration -> Select client 'masi_StandBy_LiveSync' -> Renew Certificate. You may also create temporary certificates following the below documentation

Renewing a Revoked Certificate in a Typical CommCell Environment
Manually Applying Certificate on a Migrated Client
 

Additionally, verify if there are any network rules configured between your StandBy Failover client and the relevant MA. Check Cvfwd log on masi_StandBy_LiveSync for any connection errors with the MA.

Thank You,
Dheeraj Shetty

Hi ​@Ivanav ,

Internal Error Code 5 indicates a certificate expiry on the client. Since this is a new setup, please confirm if there was a change in the client name or whether any cleanup of the old Live Sync clients was done before the hardware refresh.

If not, kindly proceed with the following Plan of Action :

1. DE configure and delete the old Standby Live Sync client listed under "Client Computers," including both the client name and the corresponding pseudo client with the _node suffix.

2. Reinstall the Failover and HA package on the standby machine, and confirm readiness by running the "Check Readiness" operation.

3. Verify network connectivity: Ensure that ports 8405 and 8408 are open between the Active CommServe and the Standby CommServe Failover Client.

Thanks, @Dheeraj Shetty and ​@Pradeep for reply, 

I checked the licenses, and I think that might be the issue. Every time I try to renew the license for ‘masi_StandBy_LiveSync,’ it creates another license that shows a ‘revoked’ status, please see the screenshot below. I’m curious if this relates to ​@Pradeep response. I didn’t remove the old Standby_LiveSync server before installing the new one. My plan was to install the new server, confirm it’s working, and then remove the old one. However, it sounds like I need to remove the old server first and then reinstall it on masi again. Is that correct?

hi ​@Ivanav 

We need to clean the stale entries first and then proceed with new install.

Even after reinstalling the Failover on a new server and deleting the old LiveSync Standby server (as suggested), I was still getting a read failure with the same error.

Solution:
Because the issue was in connection between the new server and a MediaAgent. Here's what I did to fix it:

1. Went to the MediaAgent that the new server was trying to connect to.

2. Opened the hosts file located at:
   C:\Windows\System32\drivers\etc\hosts

3. Added the IP address and hostname of the new server to the file.

4. Saved the file.

5. Rechecked readiness — and it started working!

Thanks to everyone for the quick responses!