Log files in TeamForge
6.1.1 on CentOS
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 TeamForge ; however, in the interest of completeness they are all documented here.
- Email logs
Both the CollabNet TeamForge 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 TeamForge 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.
- Project Build Library audit log
You can use this screen to view the complete list of actions performed in the Project Build Library.
- Profile audit log
Use this screen to view the complete list of actions performed on a profile.
- User Audit Log
You can use this screen to view the list of actions performed by the user in the TeamForge Lab Management system.
- Host audit log
You can use this screen to view the complete list of actions performed on a host.
- Project audit log
The Project audit log screen shows the complete list of changes applied to a project.
- etl.log
This file contains information from extract-transform-load runs, including data transformation warnings and errors.
