From chris@dns.sup.nwrain.net Tue May 27 12:18:07 1997 Received: from dns.sup.nwrain.net (dns.sup.nwrain.net [205.134.220.1]) by hyperreal.com (8.8.5/8.8.5) with ESMTP id MAA17963 for ; Tue, 27 May 1997 12:18:05 -0700 (PDT) Message-Id: <338AD161.152D@sup.nwrain.net> Date: Tue, 27 May 1997 12:19:45 +0000 From: chris@dns.sup.nwrain.net (Chris Todd) Reply-To: chris@sup.nwrain.net To: apbugs@hyperreal.com Subject: Multiple Log Entries for a single hit >Number: 627 >Category: mod_log-any >Synopsis: Multiple Log Entries for a single hit >Confidential: yes >Severity: serious >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: unknown >Arrival-Date: Tue May 27 12:20:01 1997 >Last-Modified: Wed Jul 2 13:54:59 PDT 1997 >Originator: chris@dns.sup.nwrain.net >Organization: >Release: 1.1.3 >Environment: >Description: >How-To-Repeat: >Fix: >Audit-Trail: Responsible-Changed-From-To: gnats-admin (GNATS administrator)-apache Responsible-Changed-By: coar Responsible-Changed-When: Tue May 27 12:55:24 PDT 1997 Responsible-Changed-Why: Moving into appropriate category Category-Changed-From-To: pending-mod_log-any Category-Changed-By: coar Category-Changed-When: Tue May 27 12:55:24 PDT 1997 State-Changed-From-To: open-closed State-Changed-By: coar State-Changed-When: Wed Jul 2 13:54:58 PDT 1997 State-Changed-Why: Please upgrade to Apache 1.2. We are no longer addressing problems found in the 1.1 versions. Thank you for using Apache! Originator-Changed-From-To: -chris@dns.sup.nwrain.net Originator-Changed-By: coar Originator-Changed-When: Wed Jul 2 13:54:58 PDT 1997 Release-Changed-From-To: -1.1.3 Release-Changed-By: coar Release-Changed-When: Wed Jul 2 13:54:58 PDT 1997 >Unformatted: Our Apache (1.1.3) is also logging two entries for one hit. I have verified that the server is only getting one hit by telneting into port 80 and sending "GET /~ABCDEFGH HTTP/1.0 ". Sure enough, it logs it twice in the log file. I'm looking through the configuration files currently to see if there is a reason for this (somewhere in httpd.conf), but I can't figure it out. Anyway, the person who responded to this problem report was probably mistaken, though our server only logs two entries per hit, not 400. It does log both of them at the same time, and sometimes (though usually not) only logs one. > From nobody@hyperreal.com Mon Apr 28 21:05:55 1997 > Received: (from nobody@localhost) > by hyperreal.com (8.8.5/8.8.5) id VAA23540; > Mon, 28 Apr 1997 21:05:55 -0700 (PDT) > Message-Id: <199704290405.VAA23540@hyperreal.com> > Date: Mon, 28 Apr 1997 21:05:55 -0700 (PDT) > From: Alec Berry > Reply-To: alec@exit1.com > To: apbugs@hyperreal.com > Subject: single access creates multiple log entries > X-Send-Pr-Version: 3.2 > > >Number: 500 > >Category: mod_log-any > >Synopsis: single access creates multiple log entries > >Confidential: no > >Severity: non-critical > >Priority: medium > >Responsible: apache > >State: closed > >Class: sw-bug > >Submitter-Id: apache > >Arrival-Date: Mon Apr 28 21:10:01 1997 > >Last-Modified: Wed Apr 30 16:25:46 PDT 1997 > >Originator: alec@exit1.com > >Organization: > >Release: 1.2b8 > >Environment: > FreeBSD 2.1, standard install. > >Description: > Three times since upgrading to 1.2b8 (three weeks) a single hit has logged multiple entries to my access logs. > In a few cases, it has logged over 400 hits, over a span of 15 to 20 minutes. > The additional entries are sometimes a second or two apart, sometimes multiple entries in the same second. > There are other accesses taking place in between the times of the multple entries, these accesses are logged correctly. > I have not been lucky enough to be at the server when these episodes have taken place. > The remote machine has always been using Netscape 1.22 (coincidence?). > I am using mod_log_config, with the following settings in httpd.conf: > TransferLog logs/access_log > LogFormat "%h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"" > > >How-To-Repeat: > I have unable to reproduce this. The only thing I found in common is the USER_AGENT = Mozilla/1.22 > >Fix: > No. I grep -v the excess lines out of the log file and restart the server. > I have not completely ruled out the possibility that the remote machine may be hitting me hundreds of times due to something at their end, but I never encountered this before. > %0 > >Audit-Trail: > State-Changed-From-To: open-closed > State-Changed-By: dgaudet > State-Changed-When: Wed Apr 30 16:25:45 PDT 1997 > State-Changed-Why: > This appears to be a browser or proxy error not related to > apache. If it becomes a terrible problem we might be able > to figure out why... but for now it'd be best for you to complain > to webmaster@att.net and ask them for assistance. > > Thanks for using Apache! > Dean > >Unformatted: > >