lows commercial message solicitation but the messages are subject to to a 25 cent per
bit delivery fee and all mail users reserve the right to charge 25 cents per bit or
the amount agreed to in a settlement as a reader fee All standard mail services are f
or preauthorized emails private in nature If you do not agree to pay these fees
disconnect and do not send your messages) with SMTP id h068TE128719
for <[EMAIL PROTECTED]>; Mon, 6 Jan 2003 02:29:15 -0600
Message-ID: <003801c2b55d$b0869070$4b02a8c0@destroyer>
From: "James Nelson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Subject: Re: Qpopper Hanging?
Date: Mon, 6 Jan 2003 02:29:05 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
Disposition-Notification-To: "James Nelson" <[EMAIL PROTECTED]>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Call me silly, but I'd try using straight inetd. You will probably have to
tweak some stuff to make it scale, but inetd seems to be a bit more
forgiving from a buffering perspective in my environment. (10K pop users
per pop3 server and I don't force delete mail on pop)
----- Original Message -----
From: "Morgan A. Miskell" <[EMAIL PROTECTED]>
To: "'Randall Gellens'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, January 05, 2003 10:23 AM
Subject: RE: Qpopper Hanging?
> I had to move it outside XINETD and run as a standalone daemon to get it
> working. Unfortunately, I can't put it back into XINETD and let if fail
> again due to load. It appears to be an XINETD related issue. I've got
the
> xinetd.conf file setting the services as unlimited (as well as for the pop
> service specifically). I have also tried using RPM's from Redhat and
custom
> compiling XINETD. Only moving the application outside XINETD solved the
> problem.
>
> -----Original Message-----
> From: Randall Gellens [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 03, 2003 7:09 PM
> To: Morgan Miskell; Subscribers of Qpopper
> Subject: Re: Qpopper Hanging?
>
>
> At 12:48 AM -0400 10/19/02, Morgan Miskell wrote:
>
> > Suddenly got a new development on one of my qpopper servers, have 5
> > machines, all running RH 7.0 with Qpopper 4.03, 4 of them are still
> > fine, the 5th machine now has a "hanging" problem.
> >
> > Symptoms appear to be that ever 3-4 hours the machine gets an error
> > in the logs that looks like the following:
> >
> > Oct 18 08:02:16 qpop5 popper[27438]: I/O error flushing output to
> > client eagleloc at xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx]: Operation not
> > permitted (1) [pop_send.c:689]
> >
> > Then multiple entries in the log that are like:
> > Oct 18 09:52:37 ns5 popper[13502]: (null) at xxx.xxx.xxx.xxx
> > (xxx.xxx.xxx.xxx): -ERR POP EOF or I/O Error [popper.c:820]
> >
> > Once this starts, the only way to get qpopper back to running to
> > restart xinetd. If you telnet to port 110 during this period you
> > successfully connect but never get the initial ok message.
> >
> > I have recompiled and re-installed the binary, rebooted the server,
> > checked the file systems, checked memory and disk space, anyone
> > have any ideas?
> >
> > Yesterday I upgraded the Daemon to 4.04, but that didn't have any
> > effect, I am running the Daemon in server mode via xinetd. Thanks
> > in advance!
> >
> > /etc/xinetd.d/pop3 entry as follows:
> >
> > service pop3
> > {
> > socket_type = stream
> > protocol = tcp
> > wait = no
> > user = root
> > instances = UNLIMITED
> > server = /usr/local/sbin/popper
> > server_args = popper -S -s -T 30 -c -R -C
> > port = 110
> > }
>
> What does strace(1) on the hung process show?
>
>
