Console error: Duplicate node uuids detected for nodes

Issue

In Console, the following error message may appear while on the Nodes page:

System configuration error, duplicate node uuids detected for nodes:
<table class="data_grid" style="position:relative;left:
11em;width:40em;margin:.5em;"><tr><td>aspera.example.com</td><td>(10.56.1.87)
</td><td>336678a7-268a-4790-956a-b32aa2cfc8a2</td></tr><tr><td>Aspera1_backup
</td><td>(10.128.37.151)</td><td>336678a7-268a-4790-956a-b32aa2cfc8a2</td></tr>
</table>Duplicate uuids will result in transfer management and reporting errors

This error suggests that a transfer server (Enterprise Server, Connect Server or Point to Point) has been cloned and added to Console as a node, and that the original transfer server also exists as a node. The problem is that cloning a transfer server does not update the clone's UUID, its unique identifier, which would cause issues in the database since the original transfer server is using the same UUID.

In order to fix this issue you will need to update the UUID for the cloned server using the following instructions.

Environment

  • Product: Console
  • Operating System: Linux, Windows, Isilon

Solution

1. Stop the asperacentral service on the machine of your cloned transfer server.

Linux
# service asperacentral stop

Isilon
# isi_for_array -s -q /etc/rc.d/asperacentral stop

On Windows, go to Start > Control Panel. Select All Control Panel items by clicking the arrow next to Control Panel. Go to Administrative Tools, then choose Services. Locate and select Aspera Central from the list and click Stop on the left.

2. On newer versions of the transfer server (3.3.3 and later), remove the following file:

  • Linux: /opt/aspera/etc/conf.d/node_id.conf
  • Windows: C:\Program Files (x86)\Aspera\Enterprise Server\etc\conf.d

For example, you can use the following command:

On Linux
rm /opt/aspera/etc/conf.d/node_id.conf

On Windows
del C:\Program Files (x86)\Aspera\Enterprise Server\etc\conf.d

On older versions of the transfer server (earlier than 3.3.3), remove the following file:

  • Linux: /opt/aspera/etc/asperacentral/preferences.db
  • Windows: C:\Program Files (x86)\Aspera\Enterprise Server\etc\asperacentral/preferences.db
  • Isilon: /usr/local/aspera/etc/asperacentral/preferences.db

3. Start asperacentral.

Linux
# service asperacentral start

Isilon
# isi_for_array -s -q /etc/rc.d/asperacentral start

On Windows, navigate back to Services as in step 1. Locate and select Aspera Central and click Start on the left.

4. Your cloned server's UUID has been updated, and you should now no longer receive an error message.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk