| View previous topic :: View next topic |
| Author |
Message |
jmarcus
Apprentice
Joined: 12 Jun 2004
Posts: 197
|
 Posted: Mon Nov 14, 2005 6:22 pm Post subject: Webalizer and Apache2 problem |
 |
|
I have seen this problem in other posts but haven't been able to resolve it.
Does anyone know how to resolve this issue
| Code: | apache2ctl -t
Syntax error on line 28 of /etc/apache2/modules.d/55_webalizer.conf:
Invalid command 'LogFile', perhaps mis-spelled or defined by a module not included in the server configuration
|
|
|
| Back to top |
|
 |
msalerno
Veteran
Joined: 17 Dec 2002
Posts: 1338
Location: Sweating in South Florida
|
| Posted: Mon Nov 14, 2005 8:12 pm Post subject: |
|
|
You will need to post a few lines of your /etc/apache2/modules.d/55_webalizer.conf
Try posting lines 20 - 35. Other than that, all I can tell you is that you have an invalid command. |
|
| Back to top |
|
|
jmarcus
Apprentice
Joined: 12 Jun 2004
Posts: 197
|
| Posted: Tue Nov 15, 2005 10:25 pm Post subject: |
|
|
I think this should do it.
| Quote: | #
# Sample Webalizer configuration file
# Copyright 1997-2000 by Bradford L. Barrett (brad@mrunix.net)
#
# Distributed under the GNU General Public License. See the
# files "Copyright" and "COPYING" provided with the webalizer
# distribution for additional information.
#
# This is a sample configuration file for the Webalizer (ver 2.01)
# Lines starting with pound signs '#' are comment lines and are
# ignored. Blank lines are skipped as well. Other lines are considered
# as configuration lines, and have the form "ConfigOption Value" where
# ConfigOption is a valid configuration keyword, and Value is the value
# to assign that configuration option. Invalid keyword/values are
# ignored, with appropriate warnings being displayed. There must be
# at least one space or tab between the keyword and its value.
#
# As of version 0.98, The Webalizer will look for a 'default' configuration
# file named "webalizer.conf" in the current directory, and if not found
# there, will look for "/etc/webalizer.conf".
# LogFile defines the web server log file to use. If not specified
# here or on on the command line, input will default to STDIN. If
# the log filename ends in '.gz' (ie: a gzip compressed file), it will
# be decompressed on the fly as it is being read.
LogFile /var/log/apache2/access_log
# LogType defines the log type being processed. Normally, the Webalizer
# expects a CLF or Combined web server log as input. Using this option,
# you can process ftp logs as well (xferlog as produced by wu-ftp and
# others), or Squid native logs. Values can be 'clf', 'ftp' or 'squid',
# with 'clf' the default.
LogType clf
# OutputDir is where you want to put the output files. This should
# should be a full path name, however relative ones might work as well.
# If no output directory is specified, the current directory will be used.
OutputDir /var/www/localhost/htdocs/webalizer
# HistoryName allows you to specify the name of the history file produced
# by the Webalizer. The history file keeps the data for up to 12 months
# worth of logs, used for generating the main HTML page (index.html).
# The default is a file named "webalizer.hist", stored in the specified
# output directory. If you specify just the filename (without a path),
# it will be kept in the specified output directory. Otherwise, the path
# is relative to the output directory, unless absolute (leading /).
#HistoryName webalizer.hist
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
