Re: Apache httpd 2.0.54 on Debian Stable -- processes stuck in "Read" mode; Apache does not respond.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/26/07, John Schofield <schoflist@xxxxxxxxx> wrote:

The Apache server's internal ip is 192.168.61.10. It's on a DMZ;
internal network is 192.168.60.x. Firewall/router is a Juniper
Netscreen 25.

Is it possible some juniper timeout is removing the TCP session from
it's internal table, then Apache is initiating a close which is
silently discarded by the juniper (because it's originating from the
wrong side)?  A subsequent request from the client would have been
passed through, but not when Apache tries to use the connection after
the timeout

--
Eric Covener
covener@xxxxxxxxx

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux