William Ahern wrote:
> We have a box serving as a router/ipmasq, smb/cifs server, webserver,
> sql server, and email and dns host. this box has two nic's, one w/
> a private address, the other with a public. every once in awhile
> nothing can be accessed via the private address and/or the public address.
> when this happens, i can't telnet to the private address (it just hangs), but
> i can to the public. ipmasq continues to work (all the pc's have private
> addresses and can access the internet fine), but nobody can send or receive
> email internally (externally 'netstat' shows incoming connections fine, when
> netstat doesn't freeze). Also, when this occurs i usually cannot get netstat or
> ipchains to list anything; they usually both hang.
>
> is it reaching its process limit? i used to run portsentry, and thought that
> that was the problem. when i killed it, everything would be fine. but, now
> it happens even when portsentry isn't running. the machine has 128MB
> of memory. should i increase the process limit and recompile the kernel,
> or is it something else? the machine has been up for a couple of months now,
> and this problem only lasts for a few minutes.
>
> thanx a million. this is a bit frustrating.
>
> Bill
> MIS, JINSA
If the logs do not say anything about refused connections, it is likely you have
reached a process limit and you should recompile with a higher limit.
Other items to examine--
-Is all the memory being used? # free to find out for sure Sometimes a BIOS
arrangement will prevent recognition of the mem
-Even with 128M, it is possible in some unlikely circumstances that some of your
key processes are being swapped out
I have had a server running L-M 6.1 with the same functions as you have (except no
internal mail--all email is email and you address it to the next desk over the
same way you would for halfway round the world) and I am running 128M on a cookin'
AMD K6-2 with special refrigeration and have been since 6.1 became available
without any sort of stop, reboot, whimper, or hiccup. In fact, it is firewalling
for this message. So I don't think bugs are a likely cause of your problem.
Civileme
