Duke Hillard ([EMAIL PROTECTED]; Tuesday, February 11, 2003 4:23 PM):

> Jeremy Wadsack wrote:

>>With your first attempt, you should have gotten all reports except
>>Directory with data unless Analog could not find the VHOST section
>>in your LOGFORMAT. In this case it should throw a warning (if you
>>have those enabled).
>>
>>For the SUBDIR, command, use this instead:
>>
>> SUBDIR http://*/*
>>

> Jeremy, thanks for your response.  I think that Analog sees the VHOST
> because my config file specifies a log format.  I didn't always specify one
> but it became necessary after switching from one host to virtual hosting.
> I won't list my entire config file in this message, but I will list commands
> that seem relevant to the situation.  In addition to these, I use ERRFILE
> on the command line to specify an error file.  I also tried SETTINGS ON
> and everything seemed normal.  Additional suggestions are appreciated.

> APACHELOGFORMAT (%v %h %l %u %t "%r" %>s %b "%{Referer}i" "%{User-Agent}i")
> WARNINGS -ER # ERRFILE command used & turning off empty reports
> ERRLINELENGTH 80 # screen width (in columns) of ERRFILE
> PROGRESSFREQ 10000 # notate ERRFILE after every 10K lines read in from 
> logfile
> DEBUG S


If Analog isn't able to find the virtual host entry in the line it
spits that out as a corrupt line warning. Add DEBUG C to get the
message (reason) for that.

You might try running a report with only the newer logs (those with
VHOSTs in them) to see if Analog isn't dropping lines with VHOST (or
something)

-- 

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
+------------------------------------------------------------------------

Reply via email to