Manage the TeamForge Orchestrate server-side components
The scope of this guide is limited to key administrative features like starting/stopping services, log locations, etc. Administration and configuration of dependent services (e.g., nginx, MongoDB, RabbitMQ) is not covered; see respective product documentation. It is assumed that as TeamForge Orchestrate administrator you are familiar with basic Linux administration commands and terminology.
TeamForge Orchestrate installs and starts six background services on the App server. Each service is managed using init scripts, which are installed and started as part of the installation process. Init scripts are all located in /etc/init.d/ on the respective hosts. Once started, each service creates a pid file.
Init script | PID file | Host | Description |
---|---|---|---|
collabnet-mongod | /var/run/collabnet-mongodb/mongodb.pid | DB server | Database service |
collabnet-nginx | /var/run/collabnet-nginx/nginx.pid | App server | Web and application server |
collabnet-rabbitmq-server | /var/run/collabnet-rabbitmq/rabbitmq.pid | MQ server | AMQP message service |
collabnet-redis | /var/run/collabnet-redis/redis.pid | App server | Internal job queue service |
orchestrate-ctf-jobs | /var/run/orchestrate/ctf_job_runner.pid | App server | Background communication with TeamForge |
orchestrate-queue-commit | /var/run/orchestrate/scm_queue.pid | App server | Processes message from commit queue |
orchestrate-queue-build | /var/run/orchestrate/build_queue.pid | App server | Processes message from build queue |
orchestrate-queue-review | /var/run/orchestrate/review_queue.pid | App server | Processes message from review queue |
Example usage:
sudo service orchestrate-queue-commit restart
Example usage:
sudo service orchestrate start
During the installation of TeamForge Orchestrate, if RabbitMQ and MongoDB were installed as part of the installation process then the administrative passwords have been written to disk for reference:
The following log files are relevant to TeamForge Orchestrate services and may be useful for debugging. Log rotation on all log files is enabled by default.