At 12:28 PM +0100 3/16/01, Oliver Fleischmann wrote:
> Hello to everyone out there!
>
> Yet another time we have the same old problem we experience since
> ages with the current qpopper 3.1.2 on Linux (2.2.16 SMP).
>
> Here are the logs:
>
> Mar 16 08:50:33 chlothar popper[22179]: [drac]: login by ba3760 from host
> p3E9E2191.dip.t-dialin.net (62.158.33.145)
> Mar 16 08:55:01 chlothar popper[22179]: Stats: ba3760 15 2018046 0 0
> p3E9E2191.dip.t-dialin.net 62.158.33.145
> Mar 16 09:32:36 chlothar popper[23979]: [drac]: login by ba3760 from host
> p3E9E2005.dip.t-dialin.net (62.158.32.5)
> Mar 16 09:32:36 chlothar popper[23979]: Stats: ba3760 0 0 0 0
> p3E9E2005.dip.t-dialin.net 62.158.32.5
>
> Two times, everything was OK.
>
> Mar 16 09:35:32 chlothar popper[24123]: [drac]: login by ba3760 from host
> p3E9E2005.dip.t-dialin.net (62.158.32.5)
> Mar 16 09:35:34 chlothar popper[24124]: I/O Error from ba3760 at
> 62.158.32.5 (p3E9E2005.dip.t-dialin.net): [-1] 104 (Connection reset by
> peer); 0 (Success)
>
> The connection got interrupted somehow.
>
> Mar 16 09:35:45 chlothar popper[24129]: ba3760 at
> p3E9E2005.dip.t-dialin.net (62.158.32.5): -ERR [IN-USE]
> /var/spool/mail/.ba3760.pop lock busy! Is another session active? (11)
>
> Now he can't log in any more:
>
> Mar 16 09:36:14 chlothar popper[24156]: ba3760 at
> p3E9E2005.dip.t-dialin.net (62.158.32.5): -ERR [IN-USE]
> /var/spool/mail/.ba3760.pop lock busy! Is another session active? (11)
> Mar 16 09:36:27 chlothar popper[24169]: ba3760 at
> p3E9E2005.dip.t-dialin.net (62.158.32.5): -ERR [IN-USE]
> /var/spool/mail/.ba3760.pop lock busy! Is another session active? (11)
> Mar 16 11:25:57 chlothar popper[29214]: ba3760 at
> p3E9E214E.dip.t-dialin.net (62.158.33.78): -ERR [IN-USE]
> /var/spool/mail/.ba3760.pop lock busy! Is another session active? (11)
> Mar 16 11:27:00 chlothar popper[29261]: ba3760 at
> p3E9E214E.dip.t-dialin.net (62.158.33.78): -ERR [IN-USE]
> /var/spool/mail/.ba3760.pop lock busy! Is another session active? (11)
>
> The qpopper-process (PID 24123) was still laying around at this time,
> as well as the .ba3760.pop - lock-file. Killing it with -HUP does nothing,
> I need to use -TERM, which removes the process from the table, but
> doesn't clean up the lock file. So I have to clean up myself.
>
> We are experiencing this every now and then, and only with some
> users. But those few users trigger the problem almost every day. At
> least one of them used Microsoft Outlook (don't know which version).
>
> Do I need to go for another POP3 server software? Is there still any
> ongoing development for the free version of qpopper?
>
> Sincerely,
> Oliver Fleischmann
>
> --
> Oliver Fleischmann [EMAIL PROTECTED]
> Seba Dynatronic http://www.sebadyn.de
> Mess- und Ortungstechnik GmbH Tel. +49-9544-68211
> Dr.-Herbert-Iann-Str. 6 Fax. +49-9544-68202
> D-96148 Baunach
Next time it happens, can you get a trace of system calls on the hung
stack? This is done by running the system trace facility. This
differs depending on the flavor of Unix. On Solaris it is truss(1);
on Linux it is strace(1). Other platforms may have one of these or
something else. Usually a 'man -k trace' shows it. For example, on
Solaris, if the hung stack is pid 1234, use 'truss -p 1234 -o
truss-out'
It would also be helpful to enable debug tracing in Qpopper.
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
4. Send inetd a HUP signal.
This causes detailed tracing to be written to the syslog (if you used
'-d') or to the file specified as 'tracefile'.
