Achim Altmann <[EMAIL PROTECTED]> (Monday, September 08, 2003 4:10 AM):
> Hello,
> i use analog analog-5.91beta1 and apache apache_1.3.27 with MOD_GZIP on linux
> redhat 8.0
> if i start analog the i i become the following messages
> /analog: Warning L: Large number of corrupt lines in logfile
> /var/log/www/access_beta_log.3: turn debugging on or try different LOGFORMAT
> Current logfile format:
> %S %j %u [%d/%M/%Y:%h:%n:%j] "%j%w%r%wHTTP%j" %c %b "%f" "%B"\n
> %S %j %u [%d/%M/%Y:%h:%n:%j] "%j%w%r" %c %b "%f" "%B"\n
> %S %j %u [%d/%M/%Y:%h:%n:%j] "%r" %c %b "%f" "%B"\n
mod_gzip should not affect the format of the log files.
> ./analog: Warning L: logfiles /var/log/www/access_achim_log and
> /var/log/www/access_beta_log.4 overlap: possible double counting
> ./analog: Warning L: logfiles /var/log/www/access_beta_log and
> /var/log/www/access_log overlap: possible double counting
> ./analog: Warning L: logfiles /var/log/www/access_beta_log.2 and
> /var/log/www/access_log overlap: possible double counting
If these are multiple hosts providing load-balanced access to the same
site (or multiple logs for the same or similar data) you can ignore
these messages. If not, then you should check the logs to make sure
they do not actually contain the same requests multiply.
> and
> ./analog: Warning F: Can't auto-detect format of logfile
> /var/log/www/error_log.4: ignoring it
> ./analog: Warning F: Can't auto-detect format of logfile
> /var/log/www/error_markus_log: ignoring it
> ./analog: Warning F: Can't auto-detect format of logfile
> /var/log/www/error_webdisk_log: ignoring it
> ./analog: Warning F: Can't auto-detect format of logfile
> /var/log/www/error_webdisk_users_5555_log: ignoring it
> ./analog: Warning F: Can't auto-detect format of logfile
> /var/log/www/erroradmin_log: ignoring it
Analog doesn't read error log files. Those are really meant to be
human readable. Analog gets all the error information it needs from
the access log(s).
> so i have configured in analog.cfg
> LOGFILE *
You should probably use something like
LOGFILE access*
> in my apache httpd.conf i have configured the logformat
> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"
> mod_gzip: %{mod_gzip_compression_ratio}npct." combined
> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" common
> LogFormat "%{Referer}i -> %U" referer
> LogFormat "%{User-agent}i" agent
> #
> CustomLog /var/log/www/access_log common
> AgentLog /var/log/www/agent_log
Your "common" line (which is really Combined Format), is something
that Analog can auto-detect. So you should not need any LOGFORMAT
command at all.
Also, it's somewhat redundant (and space consuming) to use an agent
log in addition to the custom one.
If your log files are in the "combined" format you have listed try
using the APACHELOGORMAT command with the given parameters, or use the
LOGFORMAT command that Analog shows as a sample for "combined" and add
a final "%j" field to match the mod_gzip compression field above.
See http://analog.cx/docs/logfmt.html for details.
--
Jeremy Wadsack
Wadsack-Allen Digital Group
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| Digest version: http://lists.isite.net/listgate/analog-help-digest/
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------
