Troubleshooting errors with the "yum install teamforge" command

Existence of .marker files in /opt/collabnet/teamforge/runtime/temp directory or existence of server file in /var/run/cli/ directory can cause the yum install teamforge command to error-out and abort. You must remove these files to proceed with yum install teamforge.

Remove the .marker files

The following error message, if seen during yum install teamforge, remove the .marker files from /opt/collabnet/teamforge/runtime/temp and proceed.

It appears that the previous version of TeamForge has not been shut down properly. Please run '/etc/init.d/collabnet stop all' before installing new packages. If this error persists, please clean the directory '/opt/collabnet/teamforge/runtime/temp' and try again.

Stop TeamForge.
- /etc/init.d/collabnet stop all
Go to /opt/collabnet/teamforge/runtime/temp and look for .marker files.
- cd /opt/collabnet/teamforge/runtime/temp
Remove the .marker files, if they exist.
- rm -rf *.marker
In a distributed setup, run the yum history list teamforge command to get the ID of latest yum install teamforge execution. Do this on all the distributed servers. For example, run yum history list teamforge-scm on the SCM server.
Run the yum history repeat <ID> command.

Remove the "server" files

The following error message, if seen during yum install teamforge, remove the "server" file from /var/run/cli/ and proceed.

It appears that CLI Server has not been shut down properly. Please run 'service teamforge_cli_server stop' before installing new packages. If this error persists, please delete '/var/run/cli/server' and try again.

Stop the CLI add-on.
- service teamforge_cli_server stop
Go to /var/run/cli/ and look for "server" file.
- cd /var/run/cli/
Remove the "server" file, if it exists.
- rm -rf /var/run/cli/server
Run the yum history list teamforge command to get the ID of latest yum install teamforge execution.
Run the yum history repeat <ID> command.