...

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

The Consumer on the Correlator machine is a Tomcat7 webapp called /var/lib/apache-tomcat7/webapps/populate-web

 Apart from the Tomcat Logs located on /var/log, three log files are created in the /var/log/snmptraps/new-dashboard/Populator/ directory: These are allLog.txt, errorLog.txt and warnLog.txt

The configuration files are stored in /var/lib/apache-tomcat7/webapps/populate-web/WEB-INF/classes

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  

If the ESB pages cannot be displayed, then you may need to restart the ActiveMQ broker service on the ESB. Login to the prod-dboard01-esb.geant.net and run as sudo service activemq restart

Check prod-opsdb01.geant.net

...