Corrupt Log File Lines in Analog

How do lines get corrupted in Log Files?

[kilo]

Hi I was just wondering what it exactly means when Analog finds corrupted Lines while analyzing a log file? How do the lines get corrupted? is there a while to fix them? and is it normal when 300 lines are shown as being corrupted out of 1,402,545 file requests counted in the log?

[Sanenet]

Could be an error if you're downloading the logs, especially if you're using multipart FTP on a large file.

Or, could be simply that the logfile is in a different format from the one Analog expects - double check to make sure you have the correct format selected.

[kilo]

But why is that only a few lines are corrupted and not all?

Arent each configured the same way?

[Glacai]

Whenever I've had corrupt lines its been because of extra quote marks in the referrer or browser field.

Try putting
ERRFILE errorfile.log
in your config file then analog will tell you which lines are corrupt.

[kilo]

It looks like there are two types of corrupted lines that keep showing on the Error file when i run Analog...

198.65.155.205 - - [02/Oct/2004:08:47:47 -0400] "GET /products/ " 400 147 <- - -

and

www.site.com - - [08/Oct/2004:23:51:43 -0400] "GET /users/getinfo.cgi?PASSWORD=pass&E_MAIL=email%40somewhere.com" 200 0 <- - -

any ideas as to why these lines are corrupted?