Host configuration problem?



Hello all.
I have recently set up a server running FreeBSD 6 to host a test web
site. Nobody really uses it except me. The site is served with Apache
2.2 which forwards dynamic content requests to Tomcat 5.5.9. It is
configured and working (almost). Whenever a request comes in, it will
serve the first and maybe second or third request and then stop
responding. It will stay that way for about 5 minutes or so, and then
jump back into action and the same problem will come up again.
There is absolutely nothing abnormal in any of the logs. When it stops
responding, I try to SSH in, but with no luck, although I can ping the
box and it responds at the normal rate. The machine works fine if I
actually go to the box and work on it there. Also if I check CPU and
memory usage, CPU never dips below 80%ish idle and memory stays pretty
much unused during the "freeze time".
I have tried everything I know to fix this (I don't know a ton about
this stuff, so it is most likely some configuration option I missed).
The only other thing I can think of is my ISP. They don't block port
80 or any other, but could they have a firewall that does some kind of
packet filtering? Thanks in advance!

Machine info
Old Dell PowerEdge 500C
20 GB HD
512 MB RAM
1 Ghz Intel Celeron CPU
FreeBSD 6
Apache 2.2.0.6 that serves static content and forwards dynamic requests
to Tomcat 5.5.9
Java 1.5.0.06 running off the Linux emulator which runs Red Hat
7.3/i386
Running behind a Dlink router (because I have to share internet
connection; not much traffic) which forwards the ports I need (80, 22,
8180, 8005).
I use no-ip.com as my DNS service.
NOTE: Tomcat creates about 20 Java processes that use no memory most of
the time. It also creates about 10 'localhost' listeners that,
according to netstat, are "Established" with no inbound or outbound
packets most of the time. Half of these are established on 8009 with
the other half on different ports higher up somewhere between 49000 and
64000. Don't know if thats normal or not or if more than one process
should be established on the same localhost port.
Another Note: I cannot access the server during a "freeze" either on my
LAN or from the outside. The only way is to actually go to the box.

Thanks again!

.



Relevant Pages

  • Re: Web Chaining - Ausgehender Port für SSL
    ... den isa, weil du ihre browserkonfigurationen angepasst hast. ... somit schickt dein isa die requests an den squid und bittet jenen ... auseinandernimmt und je nach Aufbau an den entsprechenden Port ... Also bekommt der upstream-Proxy das nur auf die entsprechenden Ports ...
    (microsoft.public.de.german.isaserver)
  • Re: ARP question
    ... UDP port 1026, ... As far as I know ARP requests are only made in LANs and it's impossible ... I got 1871 ARP requests, 1870 were from the Cable company, and one was ...
    (Fedora)
  • Re: PPC MSMQ Help!
    ... I believe that Active Sync is the culprit here in blocking requests. ... Here is a snippet about how to allow AS to forward port requests. ... connections being generated from your desktop machine itself, ...
    (microsoft.public.pocketpc.developer)
  • Re: Web Chaining - Ausgehender Port für SSL
    ... isa, weil du ihre browserkonfigurationen angepasst hast. ... somit schickt dein isa die requests an den squid und bittet jenen wiederum ... dass der ISA auf Port 80 ein HTTP-Connect an den Squid stellt.. ... Also bekommt der upstream-Proxy das nur auf die entsprechenden Ports ...
    (microsoft.public.de.german.isaserver)