[EMAIL PROTECTED] wrote:

> Hi all. I'd posted a problem earlier this week about apache not logging
> for certain domains. I recieved some very helpfull advice, but there is
> still something very, very wrong. 
> 
> Two things, actualy: First, apache will now log acccesses from our LAN and
> our dialups, but not form anywhere else.

This sounds like it could be a reverse DNS problem. Or something else.

> Again, it's using the same
> httpd.conf defaults as the domains that log properly, having a virtualhost
> entry that doesn't make any specifications about what to log or not log. 

Very odd. Are you using name-based or IP-based virtual hosts? If
you're using IP-based virtual hosts, is there *anything* different
about the IP addresses that are having problems, *anywhere* in the
network's configuraion?

> Second, and perhaps more importantly (definately more confusing) ever since
> it started logging, anyone who goes to one of these web pages gets "A
> Network error occured while Netscape was recieving data (Network error:
> connection reset by peer)". If you then hit reload, it loads just fine.
> This happens every time Netscape is started fresh, though. I haven't tried
> with IE, Opera, etc but this happens with Netscape on three different
> platforms so it's definately a server thing. 

Even more odd.

Given the amount of trouble you've been having, it might be worthwhile
either compiling it yourself, or trying a precompiled binary
(depending upon what you're using at the moment, try the opposite).

The only other thing that I can suggest is methodical analysis, e.g. 
using tcpdump to monitor connections, running httpd under gdb etc.

-- 
Glynn Clements <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to