From owner-freebsd-sparc64@FreeBSD.ORG Fri Mar 19 06:01:54 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDC9716A4CE for ; Fri, 19 Mar 2004 06:01:54 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DA9643D46 for ; Fri, 19 Mar 2004 06:01:54 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id EF3CDC3; Fri, 19 Mar 2004 08:01:53 -0600 (CST) Date: Fri, 19 Mar 2004 08:01:53 -0600 From: Tillman Hodgson To: FreeBSD-Sparc64 Message-ID: <20040319140153.GD3884@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.6i Subject: After 64bTT, Apache logs have some interesting entries X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2004 14:01:55 -0000 Howdy folks, I finally noticed that awstats wasn't working properly and sure enough it was producing an error: Update for config "/usr/local/www/cgi-bin/awstats.www.rospa.ca.conf" With data in log file "/var/log/rospa-prod-access.log"... Phase 1 : First bypass old records, searching new record... Direct access after last updated record successfull (after line 125032) 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 /var/log/rospa-prod-access.log must have a bad format or LogFormat parameter setup does not match this format. Your AWStats LogFormat parameter is: 1 This means each line in your web server log file need to have "combined log format" like this: 111.22.33.44 - - [10/Jan/2001:02:14:14 +0200] "GET / HTTP/1.1" 200 1234 "http://www.fromserver.com/from.htm" "Mozilla/4.0 (compatible; MSIE +5.01; Windows NT 5.0)" And this is a sample of records AWStats found in your log file (the record number 50 in your log): 218.94.42.221 - - [06/Jun/651184215:17:42:56 -0600] "GET /scripts/nsiislog.dll" 404 0 "-" "-" The log format problem I'm still working on. But take a closer look at the date on in the log: [06/Jun/651184215:17:42:56 -0600] That ain't right ;-) Feb 18th was my last log entry with a "normal" date entry. I believe, though my memory is fuzzy, that that was the date I upgrade to 64bTT. Note that after upgrade to 64bTT I made sure re-compile every port (including Apache), just to be safe. Is anyone else running Apache on 64bTT? How do you logs look? -T -- A: Because it reverses the logical flow of conversation. Q: Why is putting a reply at the top of the message frowned upon? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?