Logging Troubleshooting - NAVADMC/ADSM GitHub Wiki

The ADSM Workspace holds log files that will assist in troubleshooting errors and can be a useful utility for power users to access the raw output of the CEngine simulation.

Log Files

Most of the relevant log files are located in the 'ADSM Workspace/settings/logs' folder.

iterationX.log

If a simulation is crashing out, data columns aren't populating, or you want to view the raw output of the CEngine to hunt down inconsistencies, these logs are where you will find the raw communication between the CEngine and the Frontend client.

Each iteration has its own log file in plain text format. When on Windows, it is suggested to open with Notepad++ or Wordpad as the general Notepad doesn't handle Linux line breaks properly.

server_error.log

Mostly just useful for developers, this log file holds the error output of the Python Application Server (CherryPy).

In general, this will only hold startup and shutdown information unless the wsgi application is crashing.

server_output.log

Also from CherryPy, not generally useful.

console.log

Located in the 'ADSM Workspace/settings/Viewer/[platform]' folder, this log file is the console (similar to the developer console in Chrome) output of the Viewer application. This is useful for developers to hunt down javascript issues.

debug.log

Located in the 'ADSM Workspace/settings/Viewer/[platform]' folder, this log file is the debug output of the Viewer applications C code. This is useful for developers working on upgrading the Chromium code in the Viewer application.

access.log

Located in the 'ADSM Workspace/settings/nginx/logs' folder, this file is the raw http access logs from the Nginx web server. This can help developers troubleshoot requests that are throwing 4xx or 5xx errors.

error.log

Located in the 'ADSM Workspace/settings/nginx/logs' folder, this file the error log for the Nginx web server. This can help developers troubleshoot when http requests aren't making it to the CherryPy application server.