On Mon, May 29, 2006 at 12:37:11AM +0200, Stian B. Barmen wrote:
> I am sorry to say that one of my users this morning reported this
> problem to me again. He said that he tried to reset his password and for
> a few hours the problem was gone. This evening the problem was back and
> the same message about user logged in elsewere started up again.
Okay, I think I figured out what's going wrong here. My Gaim went nuts
this morning and crashed numerous times - and when I checked my PyMSNt
log, I also noticed the tracebacks again. I found out, that I'm able to
reproduce the issue by signing off shortly after signing on.
When signing on, a msnw.NotificationClient is created by a
msnw.MSNConnection. However, msnw.MSNConnection.notificationClient isn't
set until msnw.MSNConnection._notificationClientReady() is called. If
the user logs out before that happens, msnw.NotificationClient.logOut()
won't get called from msnw.MSNConnection.logOut(). So we'll now have a
stray, reconnecting NotificationClient, that has lost its MSNConnection
- and it will continue to connect and lose its connection infinitely.
I hope this description makes sense. :-)
I don't actually know a proper fix, but I've attached a patch that I
think will at least workaround the issue. Another option is to downgrade
to SVN r139 - that's the last revision that didn't have the reconnecting
NotificationClient.
Best regards,
Lars
-------------- next part --------------
Index: src/tlib/msn/msnw.py
===================================================================
--- src/tlib/msn/msnw.py (revision 165)
+++ src/tlib/msn/msnw.py (working copy)
@@ -384,6 +384,9 @@
self.connectionLost = self.doDisconnect
def connectionLost(self, reason):
+ if not self.factory.msncon:
+ self.factory.stopTrying()
+ return
def wait():
LogEvent(INFO, self.factory.msncon.ident)
msn.NotificationClient.connectionLost(self, reason)
From [EMAIL PROTECTED] Tue May 30 08:29:43 2006
From: [EMAIL PROTECTED] (Bernd Ritter)
Date: Tue May 30 08:28:47 2006
Subject: [py-transports] MySQL-Storage on disk encryption and wiki stuff
Message-ID: <[EMAIL PROTECTED]>
Hi,
i am just new to the jabber and icq-transports world. pyicqt works fine
to me. at my company the employees didnt like that in the mysql-storage
their passwords were saved in plaintext.
so i changed it using AES_ENCRYPT/AES_DECRYPT. I also had to change the
database description.
tell me, if you are interested in these changes, and i will send them in.
regards,
Bernd
PS: I just wanted to edit the tutorial on pyicqt with wildfire, but the
page is still locked. i have created an account and confirmed the email.
what else can be?
--
Bernd Ritter
Software Development
DECOIT GmbH
Fahrenheitstra?e 1
D-28359 Bremen
Germany
Phone: +49 (421) 2208-186
Fax: +49 (421) 2208-150
http://www.decoit.de
