Re: bug report: modlogan fails when given logfiles with very long urls

Henrik Christian Grove schrieb:
> If I unpack it, and run `modlogan -c config/modlogan.conf <
> prestat/httpd/access-02.log`, modlogan processes 5 records.
>
> If I unpack it, remove the first line of prestat/httpd/access-02.log
> and the run the same command, modlogan processes 383 records.
>
> If I unpack it, and run `head -1 prestat/httpd/access-02.log| modlogan
> -c config/modlogan.conf`, modlogan processes the single record it
> gets.

thanks for your files; i could reproduce it now. i thought about
something yesterday and now i tried it:

i trimmed your first line to *exactly* 4096 chars (from 83.108.160.88 to
54  [nb]" with the ' " ', the whole record) and running modlogan will
only count 6 records. trimming the line to 4095 chars, all records are
processed.

but that does not mean, modlogan does not *try* to process the following
records. it does, because it complains when the following record is
corrupted (e.g. remove one "-" from the next record), it just does not
count it.

but i don't know in which part of modlogan the limit exists
(/src/processor/web/process.c?), maybe the author can comment on that..?


Christian.
-- 
BOFH excuse #201:

RPC_PMAP_FAILURE