[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
Synopsis: Some log entries do not have full IP address
The following reply was made to PR mod_log-any/2229; it has been noted by GNATS.
From: Dean Gaudet [EMAIL PROTECTED]
To: Wei Lin [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: mod_log-any/2229: Some log entries do not have full IP address
Date: Sun, 7 Jun 1998 23:29:40 -0700 (PDT)
Try
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
Synopsis: Some log entries do not have full IP address
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
Synopsis: Some log entries do not have full IP address
A good way to test might be to log all IP addresses for now
and use the logresolve program to debug further.
Yes, we have been doing so (turning hostname lookup). That should
rule out name resolver as a possible cause, I presume?
The typical log entries are like these:
199.243.210.240 - -
A good way to test might be to log all IP addresses for now
In an earlier reply I reported the logformat I used. Just changed
%h to %a to see if it would make a difference. (presumably the same
when hostname lookup is already off but maybe %a is more straight.)
After kill and start the server
Number: 2229
Category: mod_log-any
Synopsis: Some log entries do not have full IP address
Confidential: no
Severity: serious
Priority: medium
Responsible:apache
State: open
Class: sw-bug
Submitter-Id: apache
Arrival-Date: Wed May 13
