InternetOfficer.com

I have AWSTATS 6.7 with all w3c extensions and custom formats plus query isolation reads running great on custom logformat with one caveat:

For what ever reason, IIS 6 is inserting hashed (#) comments throughout the log content, not just the top.

It appears that awstats terminates reading the log file upon hitting the second or third group of hashed comments.

I can't find a switch like SkipFile where AWSTATS would ignore record lines beginning with the hashmark (#) nor a plugin.

Since I copy the logs nightly over to a dedicated stats machine I attempted to write a perl script that would scrub these lines out. But alas my perl is about as good as my Latin and I don't speak Latin.

Has anyone faced this and resolved it or can give me some direction?

Thanks 

There is no termination message. It just doesn't read lines after the second (or possibly later) group of hash marks.

I am fairly confident that I have just verified that on other sites where I am using the alternate log format of:

LogFormat="date time cs-method cs-uri-stem cs-username c-ip cs-version cs(User-Agent) cs(Referer) sc-status sc-bytes"

That the same is happening.

Without an errror message showing it is difficult to explain this. At first glance the output pages appear good until I noticed it looked significantly short.

I am not adverse to sending you the logs, conf's, etc. with my observations. I can send you a small log example off list if you wish. You can get my email from your records to respond to. Am graylisting, so resend in 10 to expedite. 

Interesting. I think you are onto it: newly introduced glitch. I don't know about 6.6 but I just ran same conf and batch file in an old awstats 6.1 and the report is fine and includes the missing records in 6.7.

I don't write perl so well, but I can read and edit. I'm going to see if I can find the difference in the process while I await your reply to my previous post.