Integrating RT with apache2

In my case i use RT VERSION 4.4 with standalone mode , and i dont know how i can restart server RT .
So i would like to integrate RT with apache2 modeperl or modefastcgi but i dont know how .

Can any one help me


You know this page?

What is your specific question?

Bye, Daniel

hello Daniel , yes i know it , but no solution .

For example to use mod_fastcgi , what i should do or edit or add , and where i can find this file , tp use RT with apache2
if you can give me a help .
Thank yoiu

My configuration file of Request tracker is on : /opt/rt4/etc
and apache2 is on : /etc/apache2/

you can use official sites docs to configure apache with mod_perl or fast_cgi…

First you need to check which version of apache you are having…I have my apache 4.2 and its path is /etc/httpd/httpd.conf…
Listen portnum

### Optional apache logs for RT
# ErrorLog /opt/rt4/var/log/apache2.error
# TransferLog /opt/rt4/var/log/apache2.access
# LogLevel debug

    AddDefaultCharset UTF-8

    DocumentRoot "/opt/rt4/share/html"
    <Location />
        <IfVersion >= 2.4> # For Apache 2.4
            Require all granted
        <IfVersion < 2.4>  # For Apache 2.2
            Order allow,deny
            Allow from all

        SetHandler modperl
        PerlResponseHandler Plack::Handler::Apache2
        PerlSetVar psgi_app /opt/rt4/sbin/rt-server
        use Plack::Handler::Apache2;

my apache version is 2.4.18 , where i should add this code ? in which file

Do you have /etc/httpd/conf/httpd.conf file , add this code and try to restart apache server. Do not forget to remove cache files before restarting apache and folder of RT inside /opt/rt4/var/mason_data/obj/

no i dont found the /etc/httpd/conf/httpd.conf file , i have only /etc/apache2 path .
and how i can remove cache files.

thank you

first find http.conf file which is the apache configuration file. U can use the command “find / -type f -name httpd.conf”…after u find the httpd configuration file append the configuration for mod_perl…Also u need to install mod_perl…, to remove cache file just go to your RT code directory…in my case it is /opt/rt4/var/mason_data/obj/ .So I try this command …“cd /opt/rt4/var/mason_data/obj” and then remove folder like …rm -rf 3501187538…this two command remove the cache…If in your obj folder, nothing is there, then no need to remove…

hello ,
whene i add the modeperle2 code or modefastcgi , and whene i restart apache i receive this error :
Job for apache2.service failed because the control process exited with error code. See “systemctl status apache2.service” and “journalctl -xe” for details

What operating system is your server? /etc/apache2 sounds like it might be a debian or ubuntu server. What you want is in there, somewhere.

The base apache config file is /etc/apache2/apache2.conf, and you probably shouldn’t touch it.

Miscellaneous config files are in /etc/apache2/conf-available, /etc/apache2/sites-available, and /etc/apache2/mods-available; active ones are linked to from the conf-enabled, sites-enables, and mods-enabled directories.

mod_perl should be in mods-available; if it is, but isn’t active, run:

sudo a2enmod perl

and restart the apache service.

You should probably put your rt4.conf in /etc/apache2/conf-available, and activate it with

sudo a2enconf rt4.conf

You also should probably read up some on getting the apache server configured and running, in case there are more things missing. Start with

or search for “apache” and your OS for other introductory guides.

Good luck,

can you share us error output of the command “systemctl status apache2.service”.

root@RTIR:/etc/apache2# systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
Active: failed (Result: exit-code) since ven. 2017-10-27 12:52:11 WEST; 19s ago
Docs: man:systemd-sysv-generator(8)
Process: 19648 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 19186 ExecReload=/etc/init.d/apache2 reload (code=exited, status=0/SUCCESS)
Process: 19674 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)

oct. 27 12:52:11 RTIR apache2[19674]: *
oct. 27 12:52:11 RTIR apache2[19674]: * The apache2 configtest failed.
oct. 27 12:52:11 RTIR apache2[19674]: Output of config test was:
oct. 27 12:52:11 RTIR apache2[19674]: apache2: Syntax error on line 235 of /etc/apache2/apache2.conf: <IfVersion takes one, two or three arguments, a comparison operator, a version (and a del
oct. 27 12:52:11 RTIR apache2[19674]: Action ‘configtest’ failed.
oct. 27 12:52:11 RTIR apache2[19674]: The Apache error log may have more information.
oct. 27 12:52:11 RTIR systemd[1]: apache2.service: Control process exited, code=exited status=1
oct. 27 12:52:11 RTIR systemd[1]: Failed to start LSB: Apache2 web server.
oct. 27 12:52:11 RTIR systemd[1]: apache2.service: Unit entered failed state.
oct. 27 12:52:11 RTIR systemd[1]: apache2.service: Failed with result ‘exit-code’.
lines 1-20/20 (END)

There is syntax error in your apache .conf file in line 235…You can share your basic apache file so that I can add rt configuration and send you that

ok this is my apache config file :

root@RTIR:/etc/apache2#cat apache2.conf
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream’s suggested way to configure the web server. This is because Debian’s
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
# /etc/apache2/
# |-- apache2.conf
*# | -- ports.conf** **# |-- mods-enabled** **# | |-- *.load** **# |.conf
# |-- conf-enabled
# | -- *.conf** **#– sites-enabled
*# `-- .conf
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections which can be
# customized anytime.
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
# directories contain particular configuration snippets which manage modules,
# global configuration fragments, or virtual host configurations,
# respectively.
# They are activated by symlinking available configuration files from their
*# respective -available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
# their respective man pages for detailed information.
# * The binary is called apache2. Due to the use of environment variables, in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
# work with the default configuration.

# Global configuration

# ServerRoot: The top of the directory tree under which the server’s
# configuration, error, and log files are kept.
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at URL:;
# you will save yourself a lot of trouble.
# Do NOT add a slash at the end of the directory path.
#ServerRoot “/etc/apache2”

# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
Mutex file:${APACHE_LOCK_DIR} default

# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars

# Timeout: The number of seconds before receives and sends time out.
Timeout 300

# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to “Off” to deactivate.
KeepAlive On

# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100

# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 5

# These need to be set in /etc/apache2/envvars

# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., (on) or (off).
# The default is off because it’d be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a
# container, error messages relating to that virtual host will be
# logged here. If you do define an error logfile for a
# container, that host’s errors will be logged there and not here.
ErrorLog ${APACHE_LOG_DIR}/error.log

# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, …, trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# “LogLevel info ssl:warn”
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf

# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.

** Options FollowSymLinks**
** AllowOverride None**
** Require all denied**

<Directory /usr/share>
** AllowOverride None**
** Require all granted**

<Directory /var/www/>
** Options Indexes FollowSymLinks**
** AllowOverride None**
** Require all granted**

#<Directory /srv/>
# Options Indexes FollowSymLinks
# AllowOverride None
# Require all granted

# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
AccessFileName .htaccess

# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch “^.ht”>
** Require all denied**

# The following directives define some format nicknames for use with
# a CustomLog directive.
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
LogFormat “%v:%p %h %l %u %t “%r” %>s %O “%{Referer}i” “%{User-Agent}i”” vhost_combined
LogFormat “%h %l %u %t “%r” %>s %O “%{Referer}i” “%{User-Agent}i”” combined
LogFormat “%h %l %u %t “%r” %>s %O” common
LogFormat “%{Referer}i -> %U” referer
LogFormat “%{User-agent}i” agent

# Include of directories ignores editors’ and dpkg’s backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet