I really hope I don't have to mess around with the source in this case, because in theory Debian has this already from the package I installed right?
I'm referring to the following citation: https://www.question-defense.com/2009/12/29/invalid-command-fastcgiexternalserver-perhaps-misspelled-or-defined-by-a-module-not-included-in-the-server-configuration On Thu, Apr 7, 2016 at 4:10 PM, John T. Haggerty <jpcoo...@gmail.com> wrote: > So I was able to get into the advice on these installations but it seems > that I've hit another snag on this, namely activating fast cgi, and getting > it to be loaded by RT. Apparently fastcgi is installed in Apache, but > getting Apache to load RT's call to fastcgi (? I guess) is failing. > > The apache.conf is below: > > # This is the main Apache server configuration file. It contains the > # configuration directives that give the server its instructions. > # See http://httpd.apache.org/docs/2.4/ 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 > # NOTE! If you intend to place this on an NFS (or otherwise network) > # mounted filesystem then please read the Mutex documentation (available > # at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>); > # 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 > # > PidFile ${APACHE_PID_FILE} > > # > # 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 > User ${APACHE_RUN_USER} > Group ${APACHE_RUN_GROUP} > > # > # HostnameLookups: Log the names of clients or just their IP addresses > # e.g., www.apache.org (on) or 204.62.129.132 (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 On > > # ErrorLog: The location of the error log file. > # If you do not specify an ErrorLog directive within a <VirtualHost> > # container, error messages relating to that virtual host will be > # If you do not specify an ErrorLog directive within a <VirtualHost> > # container, error messages relating to that virtual host will be > # logged here. If you *do* define an error logfile for a <VirtualHost> > # 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 notice > > # 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. > <Directory /> > Options FollowSymLinks > AllowOverride None > Require all denied > </Directory> > > <Directory /usr/share> > AllowOverride None > Require all granted > </Directory> > > <Directory /var/www/> > Options Indexes FollowSymLinks > AllowOverride None > Require all granted > </Directory> > > #<Directory /srv/> > # Options Indexes FollowSymLinks > # AllowOverride None > # Require all granted > #</Directory> > > > > > # 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 > </FilesMatch> > > > # > # 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 > # To use RT together with mod_fastcgi, available in the > # libapache2-mod-fastcgi package, include this file with: > # > # Include /etc/request-tracker4/apache2-fastcgi.conf > # > # into your Apache configuration file. > # > # You will need to enable the Apache modules: fastcgi > > # You might want to enable this line > # AddDefaultCharset UTF-8 > > # Tell FastCGI to trigger on the handler > #FastCgiServer /usr/share/request-tracker4/libexec/rt-server.fcgi > -initial-env R$ > > # Use the handler > # Note: If you switch the configuration to be served up from / use a > # trailing / - ie: > # ScriptAlias / /usr/share/request-tracker4/libexec/rt-server.fcgi/ > # trailing / - ie: > # ScriptAlias / /usr/share/request-tracker4/libexec/rt-server.fcgi/ > #ScriptAlias /rt /usr/share/request-tracker4/libexec/rt-server.fcgi > > #<Location /rt/> > # DirectoryIndex index.html > #<Location /rt/> > # DirectoryIndex index.html > #</Location> > > # Limit mail gateway access to localhost by default > #<Location /rt/REST/1.0/NoAuth> > # <IfVersion >= 2.3> > # Require local > # </IfVersion> > # <IfVersion < 2.3> > # Order Allow,Deny > # Allow from 127.0.0.1 > # </IfVersion> > #</Location> > > #Include /etc/request-tracker4/apache2-fastcgi.conf > > ==================================================== > > The file was first included in the configuration by me but was commented > out when I had re-read the instructions. I copied the file into > /etc/apache2/'s "configs included" directory, that failed. Adding it as an > include file failed as well. The following error was created. > > The error I got when restarting the server and causes me to revert back to > step 1 is the following: > > sudo systemctl status apache2.service -l > ● apache2.service - LSB: Apache2 web server > Loaded: loaded (/etc/init.d/apache2) > Active: failed (Result: exit-code) since Thu 2016-04-07 15:54:05 MDT; > 37s ago > Process: 4294 ExecStop=/etc/init.d/apache2 stop (code=exited, > status=0/SUCCESS) > Process: 4319 ExecStart=/etc/init.d/apache2 start (code=exited, > status=1/FAILURE) > > Apr 07 15:54:05 Sarnya apache2[4319]: Starting web server: apache2 failed! > Apr 07 15:54:05 Sarnya apache2[4319]: The apache2 configtest failed. ... > (warning). > Apr 07 15:54:05 Sarnya apache2[4319]: Output of config test was: > Apr 07 15:54:05 Sarnya apache2[4319]: AH00526: Syntax error on line 14 of > /etc/apache2/conf-enabled/apache2-fastcgi.conf: > Apr 07 15:54:05 Sarnya apache2[4319]: Invalid command 'FastCgiServer', > perhaps misspelled or defined by a module not included in the server > configuration > Apr 07 15:54:05 Sarnya apache2[4319]: Action 'configtest' failed. > Apr 07 15:54:05 Sarnya apache2[4319]: The Apache error log may have more > information. > Apr 07 15:54:05 Sarnya systemd[1]: apache2.service: control process > exited, code=exited status=1 > Apr 07 15:54:05 Sarnya systemd[1]: Failed to start LSB: Apache2 web server. > Apr 07 15:54:05 Sarnya systemd[1]: Unit apache2.service entered failed > state. > > > =============================================================== > > This is following the steps for getting this working after the install > steps that Debian already recommended (which seem to be copied verbatim > from RT's actually from what it looks like). > -- "The death of one man is a tragedy, the death of 10 million is a statistic" -- Joseph Stalin "Omnia mutantur, nihil interit" (Translation: Everything changes, nothing is lost.) -- Ovid, _Metamorphoses_
