Log Files

Targeting Log Files

Columbus:

The Columbus log files are found under /var/log/columbus

If the PostreSQL database fails to initialize, check the content of:
/var/log/columbus/db/master.err

For all other PostreSQL database issues, check the content of:
/var/log/columbus/db/Blitz-0.log

If the Acapella server fails to initialize, check the content of:
/var/log/columbus/acc/acapella.log

For all other Acapella issues, check the content of:
/var/log/columbus/acc/acc.log

If the Web Server is not running, check the content of:
/var/log/columbus/web/columbus.log
/var/log/columbus/nginx/error.log

Tomcat:

The Tomcat log files are found under /var/log/tomcat6

If the Tomcat startup fails or the Columbus web service is not accessible, check the content of:
/var/log/tomcat6/catalina.out

If the Web Service is accessible yet clients receive an error from the CCInterface2 web service, check the content of:
/var/log/tomcat6/CCInterface2.log

Extracting Log Files

Columbus:

A useful sub-section of log files can be easily extracted via a web browser using the following URL:
http:///help/error/all_logs.zip

Alternatively, the full log set can be compressed and bundled into the /tmp directory on the server by issuing:
$ zip –r /tmp/columbus_logs.zip /var/log/columbus

The compressed columbus_logs.zip file can be exported from the Columbus servers /tmp directory using WinSCP

Tomcat:

The full log set can be compressed and bundled into the /tmp directory by issuing:
$ zip –r /tmp/tomcat_logs.zip /var/log/tomcat6

The compressed tomcat_logs.zip file can then be exported from the Columbus servers /tmp directory using WinSCP