going through my error log, I see another, unrelated traceback. I have no idea what caused this one yet.....
Feb 19 23:35:28 2003 (24496) Uncaught runner exception: please run connect() first Feb 19 23:35:28 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
-- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/
No! No! Dead girl, OFF the table! -- Shrek
"CVR" == Chuq Von Rospach chuqui@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? Are there any other error log entries before that that might be related? Any logs in your smtpd that might correlate?
-Barry
On Thursday, February 20, 2003, at 10:24 AM, Barry A. Warsaw wrote:
"CVR" == Chuq Von Rospach chuqui@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@rcn.com, size=2769, success
*** ../../logs//bounce *** Feb 20 12:14:43 2003 (24493) sharks: xxx@pmfc.com already scored a bounce for today Feb 20 12:15:43 2003 (24493) sharks: xxx@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@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/
Stress is when you wake up screaming and you realize you haven't fallen asleep yet.
- Chuq Von Rospach (chuqui@plaidworks.com) wrote:
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.
I've encountered this error with local addresses. When mailman is communicating to the MTA and comes to an address that's invalid, the MTA closes the connection, but mailman trys to keep talking to the connection.
At least that's what it appears to be on my end.
-- Matthew Davis http://dogpound.vnet.net/
APATHY ERROR: Don't bother striking any key.
CVR> Hmm. Looks like I had a wave of spam come in,a nd I set the #
CVR> of daemons on the listener port too low, so it stopped
CVR> accepting connections, and if that happens in the middle of a
CVR> batch (I have SMTP_MAX_SESSIONS_PER_CONNECTION = 2 set),
CVR> mailman doesn't handle it right.
CVR> if it fails opening a connection, it seems to be
CVR> okay. RE-opening a connection seems to be this problem.
This looks like a bit of a pain to fix. Fortunately, once you fix your smtpd and you unshunt the messages, they'll get delivered as normal. Please submit a bug report on this though...
-Barry
participants (3)
-
barry@python.org
-
Chuq Von Rospach
-
Matthew Davis