Background

Every Four Hours (which is configurable) or when a user presses the Refresh Map button a button a message is created on the Dashboard Enterprise Service Bus (ESB) in the prodrepopulate.map.queue

The OpsDB Copier process is a runnable JAR file that takes a MySQL dump of the OpsDB data and stores it in /home/local/GEANT/dante.sanigar/dumps/opsdb.sql this file is tarred up into  /home/local/GEANT/dante.sanigar/dumps.tar.gz

The file is rsynced across the the three instances of the Correlator machines:  test-dboard01-corr.geant.net, uat-dboard01-corr.geant.net and prod-dboard01-corr.geant.net to /tmp/received/dumps.tar.gz 

The process writes to a log file /home/local/GEANT/dante.sanigar/copier.log. Changes to the configuration can be made by editing the  /home/local/GEANT/dante.sanigar/config/application.properties 

When a message appears, the ESB Consumer on the Correlator machine picks up the message and starts to load the data it has obtained from the Operations Database (OpsDB) into the Dashboard Network Map. The file /tmp/received/dumps.tar.gz is untarred to /tmp/received/opsdb.sql and then processed

Check ESB

Check the prodrepopulate.map.queue on http://prod-dboard01-esb.geant.net:8161/admin/browse.jsp?JMSDestination=prodrepopulate.map.queue for messages being processed.

Also check the the consumer is running: http://prod-dboard01-esb.geant.net:8161/admin/queueConsumers.jsp?JMSDestination=prodrepopulate.map.queue 

Check prod-opsdb01.geant.net

First things to check is whether the OpsDB Copier Process is running on prod-opsdb01.geant.net.

...

If the process is not running, it can be started: java -jar opsdbCopier-1.0-SNAPSHOT.jar > copier.log &

Check prod-dboard01-corr.geant.net

Next check that everything is OK on the Correlator box prod-dboard01-corr.geant.net

...