Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: rt-3.9.7
Fetching contributors…

Cannot retrieve contributors at this time

329 lines (224 sloc) 11.548 kb
RT is an enterprise-grade issue tracking system. It allows organizations
to keep track of what needs to get done, who is working on which tasks,
what's already been done, and when tasks were (or weren't) completed.
RT doesn't cost anything to use, no matter how much you use it; it
is freely available under the terms of Version 2 of the GNU General
Public License.
RT is commercially-supported software. To purchase support, training,
custom development, or professional services, please get in touch with
us at
Jesse Vincent
Best Practical Solutions, LLC
March, 2010
o Perl 5.8.3 or later (
Perl versions prior to 5.8.3 contain bugs that could result
in data corruption. RT won't start on older versions.
o A supported SQL database
Currently supported: Mysql 4.1 or later with InnoDB support.
Postgres 8.1 or later.
Oracle 9iR2 or later.
SQLite 3.0. (Not recommended for production)
o Apache version 1.3.x or 2.x (
with mod_perl -- (
or with FastCGI -- (
or other webserver with FastCGI support
RT's FastCGI handler needs to access RT's configuration file.
o Various and sundry perl modules
A tool included with RT takes care of the installation of
most of these automatically during the install process.
The tool supplied with RT uses Perl's CPAN system
( to install modules. Some operating
systems package all or some of the modules required, and
you may be better off installing the modules that way.
This is a rough guide to installing RT. For more detail, you'll
want to read a more comprehensive installation guide at:
1 Unpack this distribution other than where you want to install RT
To do this cleanly, run the following command:
tar xzvf rt.tar.gz -C /tmp
2 Run the "configure" script.
./configure --help to see the list of options
./configure (with the flags you want)
RT defaults to installing in /opt/rt4 with MySQL as its database. It
tries to guess which of www-data, www, apache or nobody your webserver
will run as, but you can override that behavior. Note that the
default install directory in /opt/rt4 does not work under SELinux's
default configuration.
If you're upgrading RT then it is worth reading the UPGRADING document at
this point. Some extensions you are using may have been integrated into the
core. Use a new, clean directory when you're upgrading to a new major
release (for example from 3.6.x to 3.8.x).
3 Make sure that RT has everything it needs to run.
Check for missing dependencies by running:
make testdeps
4 If the script reports any missing dependencies, install them by hand
or run the following command as a user who has permission to install perl
modules on your system:
make fixdeps
Some modules require user input or environment variables to install correctly,
so it may be necessary to install them manually.
5 Check to make sure everything was installed properly.
make testdeps
It might sometimes be necessary to run "make fixdeps" several times
to install all necessary perl modules.
6 If this is a new installation:
As a user with permission to install RT in your chosen directory, type:
make install
Set up etc/ in your RT installation directory.
You'll need to add any values you need to change from the defaults
in etc/
As a user with permission to read RT's configuration file, type:
make initialize-database
If the make fails, type:
make dropdb
and start over from step 6
7 If you're upgrading from RT 3.0 or newer:
Read through the UPGRADING document included in this distribution. If
you're using MySQL, read through UPGRADING.mysql as well.
It includes special upgrade instructions that will help you get this
new version of RT up and running smoothly.
As a user with permission to install RT in your chosen installation
directory, type:
make upgrade
This will install new binaries, config files and libraries without
overwriting your RT database.
Update etc/ in your RT installation directory.
You'll need to add any new values you need to change from the defaults
in etc/
You may also need to update RT's database. You can do this with
the rt-setup-database tool. Replace root with the name of the dba
user on your database (root is the default for MySQL).
You will be prompted for your previous version of RT (such as 3.6.4)
so that we can calculate which database updates to apply
You should back up your database before running this command.
/opt/rt4/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade
Clear mason cache dir:
rm -fr /opt/rt4/var/mason_data/obj
Stop and start web-server.
8 If you're upgrading from RT 2.0:
Use the RT::Extension::RT2toRT3 module to upgrade to the current RT
release. You can download it from CPAN here:
9 Configure the web server, as described in docs/web_deployment.pod, and
the email gateway, as described below.
NOTE: root's password for the web interface is "password"
(without the quotes). Not changing this is a SECURITY risk!
Once you've set up the web interface, consider setting up automatic
logout for inactive sessions. For more information about how to do that,
run: perldoc /path/to/rt/sbin/rt-clean-sessions
10 Set up automated recurring tasks (cronjobs):
To generate email digest messages, you must arrange for the provided
utility to be run once daily, and once weekly. You may also want to
arrange for the rt-email-dashboards utility to be run hourly.
For example, if your task scheduler is cron, you can configure it as
crontab -e # as the RT administrator (probably root)
# insert the following lines:
0 0 * * * /opt/rt4/sbin/rt-email-digest -m daily
0 0 * * 0 /opt/rt4/sbin/rt-email-digest -m weekly
0 * * * * /opt/rt4/sbin/rt-email-dashboards
11 Set up users, groups, queues, scrips and access control.
Until you do this, RT will not be able to send or receive email,
nor will it be more than marginally functional. This is not an
optional step.
To let email flow to your RT server, you need to add a few lines of
configuration to your mail server's "aliases" file. These lines "pipe"
incoming email messages from your mail server to RT.
Add the following lines to /etc/aliases (or your local equivalent) on your mail server:
rt: "|/opt/rt4/bin/rt-mailgate --queue general --action correspond --url"
rt-comment: "|/opt/rt4/bin/rt-mailgate --queue general --action comment --url"
You'll need to add similar lines for each queue you want to be able
to send email to. To find out more about how to configure RT's email
gateway, type:
perldoc /opt/rt4/bin/rt-mailgate
If RT is mission-critical for you or if you use it heavily, we recommend that
you purchase a commercial support contract. Details on support contracts
are available at or by writing to
If you're interested in having RT extended or customized or would like more
information about commercial support options, please send email to
<> to discuss rates and availability.
For current information about RT, check out the RT website at
You'll find screenshots, a pointer to the current version of RT, contributed
patches, and lots of other great stuff.
To keep up to date on the latest RT tips, techniques and extensions,
you probably want to join the rt-users mailing list. Send a message to:
with the body of the message consisting of only the word:
If you're interested in hacking on RT, you'll want to subscribe to
<>. Subscribe to it with instructions
similar to those above.
Address questions about the stable release to the rt-users list, and
questions about the development version to the rt-devel list. If you feel
your questions are best not asked publicly, send them personally to
RT's a pretty complex application, and as you get up to speed, you might
run into some trouble. Generally, it's best to ask about things you
run into on the rt-users mailinglist (or pick up a commercial support
contract from Best Practical). But, sometimes people do run into bugs. In
the exceedingly unlikely event that you hit a bug in RT, please report
it! We'd love to hear about problems you have with RT, so we can fix them.
To report a bug, send email to
# This software is Copyright (c) 1996-2010 Best Practical Solutions, LLC
# <>
# (Except where explicitly superseded by other copyright notices)
# This work is made available to you under the terms of Version 2 of
# the GNU General Public License. A copy of that license should have
# been provided with this software, but in any event can be snarfed
# from
# This work is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
# 02110-1301 or visit their web page on the internet at
# (The following paragraph is not intended to limit the rights granted
# to you to modify and distribute this software under the terms of
# the GNU General Public License and is only of importance to you if
# you choose to contribute your changes and enhancements to the
# community by submitting them to Best Practical Solutions, LLC.)
# By intentionally submitting any modifications, corrections or
# derivatives to this work, or any other work intended for use with
# Request Tracker, to Best Practical Solutions, LLC, you confirm that
# you are the copyright holder for those contributions and you grant
# Best Practical Solutions, LLC a nonexclusive, worldwide, irrevocable,
# royalty-free, perpetual, license to use, copy, create derivative
# works based on those contributions, and sublicense and distribute
# those contributions and any derivatives thereof.
Jump to Line
Something went wrong with that request. Please try again.