Skip to main content

 

Druva Documentation

Troubleshooting "Error: Could not register Storage Node. Internal Error"

 

This article applies to:

  • Product edition: inSync 5.4 and later.

Problem description

The error "Could not register Storage Node. Internal Error" is displayed while registering a storage node.

Cause

The error is displayed due to a communication error between inSync Master, inSync Server, and the storage node.  The communication error can occur due to several reasons. Perform the checks provided in the resolution to resolve this error.

Resolution

Since there can be several reasons causing this error, perform the following checks and procedures to resolve this error. 

Ping

Check the basic network communication between inSync Master and Node using the ping utility.

  • Open the command prompt with admin rights and run the following command on both the inSync Master and Node Server.
    Ping <IP address or FQDN of the Node>

    Example:     
    ping 192.168.1.1 
    ping inSyncMaster.local

    If the ping fails, check the network connectivity between inSync Master and Node Server.

Telnet

Use telnet command to confirm whether the ports required for inSync are open and accessible on the storage node.

  • Open command prompt with admin rights and run the following command.

    telnet<space><IP address or FQDN of the Node><Space><Port>

    Example:
    telnet 192.168.1.1 6061 
    telnet inSyncMaster.local 6061

Note: For the current port used in your setup, check the sync port under Settings > Network Settings > Backup/Sync Port on the inSync Management Console.

Firewall

Check the local Firewall to confirm if FQDN, IP address, and the Sync port of the Master server are not blocked.

Time difference

Ensure there is no time difference between the inSync Master and Storage Node. Time difference up to 2 minutes may work; however, Druva recommends you to have accurate time on the inSync Master and Node Server.
If the Master and Node are in different time zones, ensure the time set on both is accurate according to their respective time zones. For example - if the time on inSync Master is 12:00 PM EST and that on the Node is in PST time zone,  the time on the Node should be: 9:00 AM PST.

Version mismatch

  • Ensure the Storage Node version matches with that of inSync Master.
  • Storage Node version must not be higher than the inSync Master server.

If these steps do not help, contact Druva support.