[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] FW: Raq2 POP3 server error
- Subject: Re: [cobalt-users] FW: Raq2 POP3 server error
- From: "Larry E. Smith" <lesmith@xxxxxxxxxxxxxx>
- Date: Wed Oct 31 11:57:40 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Wed, Oct 31, 2001 at 02:04:22PM -0500, Keith Charlton wrote:
>
> We have been experiencing a POP3 sever error on one of our RaQ2 machines
> whereby all users are rejected for user name and password error. A reboot of
> the machine takes care of the issue, but it now takes place every couple of
> hours. Has anyone experienced this problem and did you come up with a
> resolution.? You may reply to kcharlton@xxxxxxxxxxxxx
>
Keith,
What you might be running into is the "maximum" port connection
"bug" that all Linux systems have. If a particular port sees
more than a certain number of connections in a relative period
(cannot remember the specs), inetd will "shutdown" access to
the port for about five minutes, then restart the service.
Background to this I believe has to do with the possibility of
a port being "probed" or a run-away process.
You should be able to ADD to the number of pop processes the
inetd daemon will support by editing your /etc/inetd.conf file
and modifying such as:
MY ORIGINAL:
pop-3 stream tcp nowait root /usr/sbin/tcpd in.qpopper -R
MY MODIFIED:
pop-3 stream tcp nowait.400 root /usr/sbin/tcpd in.qpopper -R
Which basically says "allow up to 400 connections per minute
(or whatever time frame) before locking the port.....
Hope this helps.
Larry Smith
SysAd ECSIS.NET
sysad@xxxxxxxxx