Log files

System administrators can use logs to debug problems and ensure that the application is performing to expectations.

• JBoss logs
  The JBoss application server writes several different logs under the <SOURCEFORGE_INSTALL_DIR>/log directory.
• Oracle logging
  The most important Oracle log is the alert log, which is found in $ORACLE_HOME/admin/$SID/bdump/alert_$SID.log .
• SCM (CVS, Subversion, and Perforce) logs
  Software configuration management (SCM) servers generate several logs from the CollabNet SourceForge Enterprise 5.1-managed integration server in <SOURCEFORGE_INSTALL_DIR>/log. Not all of them are unique to CollabNet SourceForge Enterprise 5.1; however, in the interest of completeness they are all documented here.
• Email logs
  Both the CollabNet SourceForge Enterprise 5.1 email and search backends are managed from a parent daemon known as Phoenix. If the mail backend is not operating properly, the first troubleshooting step is to check the phoenix.log to see if it encountered difficulties starting up.
• Search logs
  Both the CollabNet SourceForge Enterprise 5.1 search and email backends are managed from a parent daemon known as Phoenix. If the search backend is not operating properly, the first troubleshooting step is to check the phoenix.log file to see if it encountered difficulties starting up.