[Mailman-Developers] another traceback
Chuq Von Rospach
chuqui at plaidworks.com
Thu Feb 20 12:29:56 EST 2003
On Thursday, February 20, 2003, at 10:24 AM, Barry A. Warsaw wrote:
>
>>>>>> "CVR" == Chuq Von Rospach <chuqui at plaidworks.com> writes:
>
> CVR> going through my error log, I see another, unrelated
> CVR> traceback. I have no idea what caused this one yet.....
>
> That's one's strange for sure. Does it happen just once?
Just happened again. Seems like my incoming SMTP goes away for some
reason, and then mailman doesn't handle it quite right.
*** ../../logs//post ***
Feb 20 12:13:12 2003 (24496) post to sharks from xxx at rcn.com,
size=2769, success
*** ../../logs//bounce ***
Feb 20 12:14:43 2003 (24493) sharks: xxx at pmfc.com already scored a
bounce for today
Feb 20 12:15:43 2003 (24493) sharks: xxx at ix.netcom.com already scored a
bounce for today
*** ../../logs//smtp ***
Feb 20 12:17:01 2003 (24496) All recipients refused: (61, 'Connection
refused')
Feb 20 12:17:02 2003 (24496) All recipients refused: please run
connect() first
Feb 20 12:17:02 2003 (24496) All recipients refused: please run
connect() first
Feb 20 12:17:02 2003 (24496) All recipients refused: please run
connect() first
Feb 20 12:17:05 2003 (24496) All recipients refused: please run
connect() first
Feb 20 12:17:05 2003 (24496) All recipients refused: please run
connect() first
Feb 20 12:17:05 2003 (24496) All recipients refused: please run
connect() first
Feb 20 12:17:05 2003 (24496) All recipients refused: please run
connect() first
*** ../../logs//error ***
Feb 20 12:17:05 2003 (24496) Uncaught runner exception: please run
connect() first
Feb 20 12:17:05 2003 (24496) Traceback (most recent call last):
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in
_oneloop
self._onefile(msg, msgdata)
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in
_onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61,
in _dispose
self._func(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 149,
in process
conn.quit()
File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 79, in
quit
self.__conn.quit()
File
"/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py",
line 671, in quit
self.docmd("quit")
File
"/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py",
line 352, in docmd
self.putcmd(cmd,args)
File
"/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py",
line 308, in putcmd
self.send(str)
File
"/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py",
line 300, in send
raise SMTPServerDisconnected('please run connect() first')
SMTPServerDisconnected: please run connect() first
Feb 20 12:17:05 2003 (24496) SHUNTING:
1045772208.148375+f793e73e6ea24d4fd7e4ae681fb86ebe3143f667
Hmm. Looks like I had a wave of spam come in,a nd I set the # of
daemons on the listener port too low, so it stopped accepting
connections, and if that happens in the middle of a batch (I have
SMTP_MAX_SESSIONS_PER_CONNECTION = 2 set), mailman doesn't handle it
right.
if it fails opening a connection, it seems to be okay. RE-opening a
connection seems to be this problem.
--
Chuq Von Rospach, Architech
chuqui at plaidworks.com -- http://www.plaidworks.com/chuqui/blog/
Stress is when you wake up screaming and you realize you haven't fallen
asleep yet.
More information about the Mailman-Developers
mailing list