Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #166485 > unrolled thread

Re: Failure to install request-tracker4 in Jessie Newest

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Failure to install request-tracker4 in Jessie Newest Christian Seiler <christian@iwakd.de> - 2016-04-06 22:20 +0200
    Re: Failure to install request-tracker4 in Jessie Newest Christian Seiler <christian@iwakd.de> - 2016-04-06 22:30 +0200
      Re: Failure to install request-tracker4 in Jessie Newest "John T. Haggerty" <jpcookie@gmail.com> - 2016-04-07 00:20 +0200
        Re: Failure to install request-tracker4 in Jessie Newest Christian Seiler <christian@iwakd.de> - 2016-04-07 00:40 +0200
          Re: Failure to install request-tracker4 in Jessie Newest "John T. Haggerty" <jpcookie@gmail.com> - 2016-04-07 22:50 +0200
            Re: Failure to install request-tracker4 in Jessie Newest Christian Seiler <christian@iwakd.de> - 2016-04-07 23:10 +0200
              Re: Failure to install request-tracker4 in Jessie Newest "John T. Haggerty" <jpcookie@gmail.com> - 2016-04-08 00:20 +0200
                Re: Failure to install request-tracker4 in Jessie Newest "John T. Haggerty" <jpcookie@gmail.com> - 2016-04-08 21:20 +0200

#166485 — Re: Failure to install request-tracker4 in Jessie Newest

[Multipart message — attachments visible in raw view] — view raw

On 04/06/2016 10:12 PM, John T. Haggerty wrote:
> I would like to get request tracker working but the main package fails to
> install. I am getting the following errors: [...]
> 
>  request-tracker4 : Depends: libhtml-mason-perl (>= 1:1.43) which is a
> virtual package.

libhtml-mason-perl is not actually a virtual package - and the only
way APT would think that is if you don't have an APT source that
includes it, but you do have another APT source that references it.

Since the current version of request-tracker4 is available in both
the main Debian archive as well as the security repository (because
of a security update from last August, see DSA 3335-1), my suspicion
is that you _only_ have the security archive enabled in your
sources.list _or_ the download of the main sources.list failed for
some reason.

Therefore, answers to the following questions will allow us to figure
out what is wrong on your system:

 - what is your /etc/apt/sources.list?
   (Also, are there files in /etc/apt/sources.list.d?)
 - what happens if you do "apt-get update" or "apt update" or
   "aptitude update"?

Regards,
Christian

[toc] | [next] | [standalone]

#166487

[Multipart message — attachments visible in raw view] — view raw

On 04/06/2016 10:23 PM, John T. Haggerty wrote:
> There is a /etc/apt/sources.list.d/ but only have a chrome.txt or something
> like that in there.

That's good to know, but that doesn't answer my other questions: what
is the contents of your /etc/apt/sources.list (without .d) and what
happens when you do the following as root?

apt-get update

Without that information, we won't be able to help you.

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#166489

[Multipart message — attachments visible in raw view] — view raw

The update commend as root updated the list and the like, Reattempting the
install also failed.

The contents are:

#

# deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1
20160123-19:03]/ jessie contrib main

deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1
20160123-19:03]/ jessie contrib main

deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-2
20160123-19:03]/ jessie contrib main

deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-3
20160123-19:03]/ jessie contrib main

deb http://security.debian.org/ jessie/updates main contrib
deb-src http://security.debian.org/ jessie/updates main contrib

# jessie-updates, previously known as 'volatile'
# A network mirror was not selected during install.  The following entries
# are provided as examples, but you should amend them as appropriate
# for your mirror of choice.
#
# deb http://ftp.debian.org/debian/ jessie-updates main contrib
# deb-src http://ftp.debian.org/debian/ jessie-updates main contrib
# wheezy-backports
deb http://ftp.debian.org/debian/ wheezy-backports main
On Apr 6, 2016 14:26, "Christian Seiler" <christian@iwakd.de> wrote:

> On 04/06/2016 10:23 PM, John T. Haggerty wrote:
> > There is a /etc/apt/sources.list.d/ but only have a chrome.txt or
> something
> > like that in there.
>
> That's good to know, but that doesn't answer my other questions: what
> is the contents of your /etc/apt/sources.list (without .d) and what
> happens when you do the following as root?
>
> apt-get update
>
> Without that information, we won't be able to help you.
>
> Regards,
> Christian
>
>

[toc] | [prev] | [next] | [standalone]

#166490

[Multipart message — attachments visible in raw view] — view raw

Hi,

On 04/07/2016 12:14 AM, John T. Haggerty wrote:
> deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1
> 20160123-19:03]/ jessie contrib main
> 
> deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-2
> 20160123-19:03]/ jessie contrib main
> 
> deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-3
> 20160123-19:03]/ jessie contrib main

So here you still have the DVDs as your primary archive source, and no
network mirror. This is possible to do, but if for any reason you (or
something you ran where you didn't necessarily know the side effects
of) deleted your /var/lib/apt/lists/ at some point, apt-get update will
not automatically restore the package lists from the CDs.

You have two options:

A. Switch over to use a network mirror for installations. In that case,
remove the cdrom lines (but _only_ the cdrom lines) and add something
like the following to your sources.list:
deb http://httpredir.debian.org/debian jessie main
Then run apt-get update again.

B. Continue using the DVDs, but have APT re-read the lists of packages.
For that, also remove the cdrom lines, and then run the following
command:
apt-cdrom add 
It will prompt you to insert the DVD. After it has copied the list
from the DVD and you get the command line back, run it again and repeat
the process for all 3 DVDs. Then run apt-get update again.

After either of these procedures, you should be able to install the
package you wanted to install.

IMPORTANT:

There's a subtle difference between both of the methods: the network
mirrors carry only the _latest_  Jessie point release, which is now
8.4. So if you add a network mirror, there will be a few upgrades
available and you'll upgrade to that next point release. If you stick
with the DVDs, you'll remain on 8.3 with the exception of security
updates, which you have enabled.

> # jessie-updates, previously known as 'volatile'
> # A network mirror was not selected during install.  The following entries
> # are provided as examples, but you should amend them as appropriate
> # for your mirror of choice.
> #
> # deb http://ftp.debian.org/debian/ jessie-updates main contrib
> # deb-src http://ftp.debian.org/debian/ jessie-updates main contrib
> # wheezy-backports
> deb http://ftp.debian.org/debian/ wheezy-backports main

This has nothing to do with your problem, but I would not recommend
using wheezy-backports in combination with Jessie. (It shouldn't
hurt, as all packages in wheezy-backports should also be in jessie
in basically the same version, but it's not what you should have
there.) If you need backports _for_ jessie, replace that with
jessie-backports. See http://backports.debian.org/ and
http://backports.debian.org/Instructions/ for details.

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#166513

[Multipart message — attachments visible in raw view] — view raw

That was able to work, however at the moment I've run into an issue that I
think I had years before namely the inability of the base installation
(even with the questions that the system asks during configuration of
request-tracker4) failing to give anything but a 404 error when hitting up
localhost/rt. I can get the basic apache page under localhost however.

So far the tutorials seem to be tailored for anything other than debian, or
a "it worked,no problems" response from most of them.

Ideas?

On Wed, Apr 6, 2016 at 4:36 PM, Christian Seiler <christian@iwakd.de> wrote:

> Hi,
>
> On 04/07/2016 12:14 AM, John T. Haggerty wrote:
> > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1
> > 20160123-19:03]/ jessie contrib main
> >
> > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-2
> > 20160123-19:03]/ jessie contrib main
> >
> > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-3
> > 20160123-19:03]/ jessie contrib main
>
> So here you still have the DVDs as your primary archive source, and no
> network mirror. This is possible to do, but if for any reason you (or
> something you ran where you didn't necessarily know the side effects
> of) deleted your /var/lib/apt/lists/ at some point, apt-get update will
> not automatically restore the package lists from the CDs.
>
> You have two options:
>
> A. Switch over to use a network mirror for installations. In that case,
> remove the cdrom lines (but _only_ the cdrom lines) and add something
> like the following to your sources.list:
> deb http://httpredir.debian.org/debian jessie main
> Then run apt-get update again.
>
> B. Continue using the DVDs, but have APT re-read the lists of packages.
> For that, also remove the cdrom lines, and then run the following
> command:
> apt-cdrom add
> It will prompt you to insert the DVD. After it has copied the list
> from the DVD and you get the command line back, run it again and repeat
> the process for all 3 DVDs. Then run apt-get update again.
>
> After either of these procedures, you should be able to install the
> package you wanted to install.
>
> IMPORTANT:
>
> There's a subtle difference between both of the methods: the network
> mirrors carry only the _latest_  Jessie point release, which is now
> 8.4. So if you add a network mirror, there will be a few upgrades
> available and you'll upgrade to that next point release. If you stick
> with the DVDs, you'll remain on 8.3 with the exception of security
> updates, which you have enabled.
>
> > # jessie-updates, previously known as 'volatile'
> > # A network mirror was not selected during install.  The following
> entries
> > # are provided as examples, but you should amend them as appropriate
> > # for your mirror of choice.
> > #
> > # deb http://ftp.debian.org/debian/ jessie-updates main contrib
> > # deb-src http://ftp.debian.org/debian/ jessie-updates main contrib
> > # wheezy-backports
> > deb http://ftp.debian.org/debian/ wheezy-backports main
>
> This has nothing to do with your problem, but I would not recommend
> using wheezy-backports in combination with Jessie. (It shouldn't
> hurt, as all packages in wheezy-backports should also be in jessie
> in basically the same version, but it's not what you should have
> there.) If you need backports _for_ jessie, replace that with
> jessie-backports. See http://backports.debian.org/ and
> http://backports.debian.org/Instructions/ for details.
>
> Regards,
> Christian
>
>


-- 
"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_

[toc] | [prev] | [next] | [standalone]

#166515

[Multipart message — attachments visible in raw view] — view raw

On 04/07/2016 10:41 PM, John T. Haggerty wrote:
> That was able to work, however at the moment I've run into an issue that I
> think I had years before namely the inability of the base installation
> (even with the questions that the system asks during configuration of
> request-tracker4) failing to give anything but a 404 error when hitting up
> localhost/rt.

RT is a complicated piece of software (it interacts both with the web and
mail server) and there is no sane way to make it work out of the box
without some configuration. Please read, after installing request-tracker4:

/usr/share/doc/request-tracker4/README.Debian.gz
/usr/share/doc/request-tracker4/NOTES.Debian.gz

These will explain how request-tracker can be installed and configured on
Debian.

Generally speaking: Debian-specific installation notes can often be found
in /usr/share/doc/PACKAGENAME/README.Debian.gz.

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#166516

[Multipart message — attachments visible in raw view] — view raw

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).

[toc] | [prev] | [next] | [standalone]

#166541

[Multipart message — attachments visible in raw view] — view raw

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 <jpcookie@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_

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web