: Zeus says the following about the problem:
: "The only way the
: accept() should fail, is either there is a "OS resource problem" which
: prevents the allocation of another socket buffer for the new
: connection, or if the client's TCP stack closes its connection before
: completing the 3-way handshake necessary to establish a TCP
: connection. A third possibility is that someone is flooding your
: TCP/IP stack with SYN packets which is causing the listen queue to
: fill and the OS to drop all connections being established."
That's 100% correct. What's the uptime on your computer? If you haven't
restarted it in a while, do that. Also try cvsupin the latest sources for
FreeBSD 2.2.x, and make a new kernel (keep a backup). Is telnetd working?
(i.e. can you telnet into your machine? you shouldn't really be running
a telnet daemon on a web server tho). On FreeBSD I would really recommend
using Apache 1.2.4 as a web server, I've never heard of Zeus, but I'd be
willing to guess Apache could provide you with on par if not faster
performance. Plus it's free. www.apache.org
: They are looking for a way to keep the server from logging it, but have
: not gotten back to me.
If it logs to its own file, stop the server, remove the log, and symlink
that file to /dev/null. If it uses syslog, edit syslog.conf and restart
: MY QUESTION: What are the things I should look for on my server to figure
: out what is causing this problem in the first place? I don't think it's a
: client problem, because it is now TOO frequent and steady. If it is a "OS
: resource problem" then how do I figure it out? If it is someone "flooding
: your TCP/IP stack with SYN packets" then how can I check to see who's
: doing it?
Check the router logs. If they show nothing abnormal, then start checking
out your computer.
- j. a. zepeda