Current User: Guest Login
Please consider registering


Lost Your Password?

Search Forums:


 






Minimum search word length is 4 characters – Maximum search word length is 84 characters
Wildcard Usage:
*  matches any number of characters    %  matches exactly one character

Logfile check

Reply to Post Add a New Topic
UserPost

10:34 pm
October 5, 2012


tomfree

Rockville, MD

New Member

posts 2

I need a custom logfile check.  We're running Apache, but using it to generate an IIS-ish logformat.  It's just odd enough to not work with any of the pre-configured options.  I've experimented with custom formats, and it's still failing.  Here are the log file headers, a sample log file line,  as well as custom formats I've tried.

 

Header:

#Fields: c-ip cs-username  date time cs-method cs-uri-stem  cs-version 
cs(Referer) sc-status sc-bytes time-taken cs(User-Agent

Sample logfile line 1 (IP addresses changed to protect the innocent):

999.0.0.1 888.77.666.555  -  2012-09-30 20:03:53   
GET /appl/images/headbar_right.gif HTTP/1.0   -   200  2067  0   "-"

Sample logfile line 2 (bogus IPs again)

444.333.222.1 -  2012-09-30 20:01:30   GET /appl/applInit.do HTTP/1.0   -   
302  -  0   "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) 
AppleWebKit/534.57.2 (KHTML, like Gecko) Version/5.1.7 Safari/534.57.2"

Custom log formats tried:

 

LogFormat="%host %logname %time2 %methodurl %referer %code %bytesd %other 
%uaquot"
LogFormat="%host %other %logname %time2 %methodurl %referer %code %bytesd 
%other %uaquot"
LogFormat="c-ip cs-username date time cs-method cs-uri-stem cs-version 
cs(Referer) sc-status sc-bytes time-taken cs(User-Agent)"

 

Error output when I try to analyze

AWStats did not find any valid log lines that match your LogFormat parameter, 
in the 50th first non commented lines read of your log.
Your log file D:/logs/Commons/AWStats/server_access_log.2012-10-01 must have 
a bad format or LogFormat parameter setup does not match this format.

 

The exact error output text varies with the format tried, but the error above is consistent.  This is a brand new installation of AWStats.  I'm an admin on the box (Windows), and I have full rights and permissions to the AWStats directory, the PERL directory, and the logfile directory.

 

I've also tried running with -showcorrupted and -debug=4 switches.  They provided very little, if any additional value.

9:37 pm
October 25, 2012


tomfree

Rockville, MD

New Member

posts 2

I could still use a hand with this if anyone has some suggestions for tuning the LogFile format

Reply to Post

Reply to Topic:
Logfile check

Guest Name (Required):

Guest Email (Required):

NOTE: New Posts are subject to administrator approval before being displayed

Smileys
Confused Cool Cry Embarassed Frown Kiss Laugh Smile Surprised Wink Yell
Post New Reply

Guest URL (required)

Math Required!
What is the sum of:
2 + 2
   


About the InternetOfficer.com Forum

Forum Timezone: UTC 1

Most Users Ever Online: 302

Currently Online:
19 Guests

Currently Browsing this Topic:
1 Guest

Forum Stats:

Groups: 2
Forums: 9
Topics: 639
Posts: 2710

Membership:

There are 257 Members
There have been 304 Guests

There is 1 Admin
There is 1 Moderator

Top Posters:

cssfsu – 55
deepakgupta – 34
albert_newton – 30
cosminpana – 20
DTNMike – 19
ahtshun83 – 17

Recent New Members: raju, todd2taylor, sbdcunha, mansigill1987, ThomasDuh, ThomasKic

Administrators: Jean-Luc (1125 Posts)

Moderators: Jean-Luc (1125 Posts)