Brad wrote:
> > Sending httpd a SIGHUP will kill off any child process immediately. If
> > any clients are connected at the time, they will typically display an
> > error along the lines of `connection reset by peer'.
>
> Like I said, I've killed the daemon and restarted it afresh. Even rebooted
> the system (again). That *one* domain STILL gets this "connection reset by
> peer" thing on a regular basis even when I haven't killed anything. I'm so
> stuck here... =:(
Well, one would assume that there must be something about that domain
that is different to the others.
Are you using name-based or IP-based virtual hosts?
If it's name-based, check the DNS. If it's IP-based, check all of the
networking configuration (not just on the web server, but on the rest
of the network as well), plus the DNS.
Beyond that, the only remaining thing that I can suggest is to use
tcpdump, to see if that provides any clues.
--
Glynn Clements <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
