You may encounter these issues and questions when installing TeamForge Orchestrate
- How do I download TeamForge Orchestrate?
- Follow the download instruction in the Installation walk-through
- Is there a disconnected/offline installation process for TeamForge Orchestrate?
- Yes, follow the instruction in the Installation walk-through.
After step 5, link to the article Installation without internet access
for supplementary instructions on obtaining and installing TeamForge Orchestrate using
the disconnected media package.
- I don't see an option to run TeamForge Orchestrate without SSL.
- SSL is a requirement at this time. You can use a self-signed certificate if you
don't have one signed by a recognized authority.
- If I'm using SSH keys, why do I also need to provide the user's password?
- The user's password is required to successfully sudo to root privileges on the target
host.
- I've installed TeamForge Orchestrate but I don't see an "Orchestrate" tab in my project tool bar.
- Normally all active projects automatically get the Orchestrate tab in the project tool bar. If Orchestrate is not available for your project, you can manually enable Orchestrate for your project.
- Log in to TeamForge as a project (or site) admin.
- Choose the TeamForge project to associate to TeamForge Orchestrate.
- Click Project Admin in the project toolbar.
- Navigate to
- Click Add. Choose TeamForge Orchestrate and click
Configure & Add
- Click Save.
Repeat
for any additional project that you'd like to configure to use TeamForge
Orchestrate.
- How do I get the queue server hostname and credentials? I need it to set up
my adapter.
- Adapters use a message queue server to transmit data to TeamForge
Orchestrate. Adapters must therefore be configured with the queue server
hostname, username, and password.
- When you create a new "Source" in TeamForge Orchestrate, a unique set of
queue server credentials is created for use with your adapters. To find the
queue server hostname and credentials, log into TeamForge as a privileged
Orchestrate user and navigate to: . The Sources Overview page appears.
- Select one of the adapters on the left hand side. The 'Source List' shows up
on the right hand side.
- From the list of sources, click the EDIT button of
the desired source.
- Locate the section named "Adapter Configuration Information".
- Copy the queue server's hostname, username, and password and use them to
configure your adapter.
- Note that the same queue server hostname, username and password may be
shared by multiple sources; however, the source association must be unique
for each source.
- I've set up build/review adapters but I'm not seeing any data in the activity stream.
- Make sure you've configured firewall access properly. The adapters must
be able to send data to the MQ server on the designated port (default 5672).
- I've set up a commit source using a project repository but I don't see any data in the
activity stream.
- Make sure that you've completed all
Post-installation tasks,
especially installation of the Orchestrate-TeamForge commit adapter. The commit adapter
supplies TeamForge commit data from TeamForge project repositories to TeamForge
Orchestrate.
- Installer fails with user permission errors
- The installer assumes that the user installing orchestrate has permission to run commands as any user. If the user has a limited set of permissions, then the installer will fail with the following:
failed: "env PATH=/sbin:$PATH sh -c 'cd /opt/collabnet/rabbitmq && sudo -p '\\''sudo password: '\\'' -u collabnet-rabbitmq /opt/collabnet/rabbitmq/sbin/rabbitmqctl list_users'" on hostname
-
Ensure that the user installing Orchestrate has permission to run commands as the following
set of users:
collabnet-redis, collabnet-nginx, orchestrate, collabnet-rabbitmq, collabnet-mongodb
These users are created by the installer and used to setup the various services.
- I received an error related to zlib while installing on RHEL 6.3.
- The following error is related to a documented bug in RHEL 6.3:
---> Package collabnet-ruby.x86_64 0:1.9.3_p392-18.el6 will be installed
--> Processing Dependency: libz.so.1(ZLIB_1.2.2)(64bit) for package: collabnet-ruby-1.9.3_p392-18.el6.x86_64
--> Finished Dependency Resolution
Error: Package: collabnet-ruby-1.9.3_p392-18.el6.x86_64 (collabnet)
Requires: libz.so.1(ZLIB_1.2.2)(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
- The correct this issue, you must upgrade zlib on your system to a version that also provides
zlib 1.2.2. The zlib 1.2.3.27 package does not bundle 1.2.2, but version 1.2.3-29 does include
1.2.2.
There are many alternative paths for upgrading to 1.2.3-29, this article covers but one way.
- wget http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/zlib-1.2.3-29.el6.x86_64.rpm
sudo rpm -Uvh zlib-1.2.3-29.el6.x86_64.rpm
- Confirm that you have zlib 1.2.2:
- rpm -q --provides lib
- Restart the installation process from the beginning.