DGC does not start after an upgrade

If you upgraded a multi-node environment, it is possible that the environment doesn't start anymore.

In Collibra Console you see the following error message:

Multi nodes environment cannot mix loopback and public addresses.

To work around this issue, you can choose one of the following procedures:

• via the Console configuration file.
• via the Collibra Console user interface.

Collibra Console configuration file

1. Open an SSH session to the node on which Collibra Console runs.
2. Back up console.db:
   cp /collibra_data/console/console.db \
/collibra_data/console/console.db.bck
   

   Note The path to the file can be different for your environment.

3. Stop Collibra Console.
4. Open the file /collibra_data/console/console.db for editing.
   
5. In the nodeSet section, look up the nodes that have a key hostName with value localhost.
   

   "nodeSet" : [ {
        ...
       "hostName" : "localhost",
       "port" : 8081,
       "name" : "NODE NAME",
       "registered" : true,
       ...
     } ],

6. Replace localhost by the private IP address of that node and repeat this for all nodes in this nodeSet section.
7. Save and close the file.
8. Start Collibra Console.
9. Start the environment.

Collibra Console user interface

1. Open Collibra Console with a user profile that has the SUPER role.
   Collibra Console opens with the Infrastructure page.
   
2. Remove the relevant services from the environment and optionally repository clusters.
   The relevant services are the services that are installed on the nodes which are configured as localhost.
3. Remove the node from Collibra Console.
4. Add the node again in Collibra Console using the private IP address of the node.
   
   Note If you receive the following error, follow the procedure as described on Collibra Community.
   

   Error while trying to set up a new node. Is the node up and address correct? 
   certificateRegistrationFailed Message: 
   javax.ws.rs.ProcessingException: java.net.SocketException: 
   Unexpected end of file from server.

5. Add the services on that node to the environment and or repository cluster.
6. Start the environment.