I'm running PyYIMt from CVS as of I think two days ago. Though I had this problem with CVS from about 9/30/2006 as well. I get it all set up, everything is running well for the most part, though I do get frequent disconnections. However, if I have to restart the PyYIMt process, it loses seems to lose its registration information. When I connect after restarting the process, the transport and all my Yahoo contacts have revoked authorization, and any attempts to send messages to the transport or to my Yahoo contacts has the transport telling me that I'm not registered with it. This is incredibly annoying, as I can't re-register with the client I normally use (mcabber), and have to instead load up Psi to do it. Any ideas? Thanks!
MysticOne [EMAIL PROTECTED] From [EMAIL PROTECTED] Sat Oct 7 17:21:03 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Sat Oct 7 17:21:06 2006 Subject: [py-transports] PyYIMt not saving settings/registration? In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 10/7/06, Daniel <[EMAIL PROTECTED]> wrote: > I'm running PyYIMt from CVS as of I think two days ago. Though I had > this problem with CVS from about 9/30/2006 as well. mmm, can you go back to an older version and see if it has the issues (you can ask cvs to check out from a specific date) > I get it all set > up, everything is running well for the most part, though I do get > frequent disconnections. These are from the Yahoo server right? How many users do you have using your server? (I've found that if I 'force connect' my 7 or 8 users when I restart the transport, that some of the logins fail - I assume due to some Yahoo rate limiting) > However, if I have to restart the PyYIMt > process, it loses seems to lose its registration information. Why do you have to restart it? (i.e. normal system shutdown/reboot, or did it hang?) and how are you restarting it? (i.e. `kill` with TERM(15) or KILL(9), or some other tool) > When I > connect after restarting the process, the transport and all my Yahoo > contacts have revoked authorization, and any attempts to send > messages to the transport or to my Yahoo contacts has the transport > telling me that I'm not registered with it. :-( this should not happen. Are other users also loosing their registrations? The userfile is synced to disk as soon as it's updated. Is the file possibly becoming corrupted? Which version of python are you using (and bdb/bsddb if you can tell) > This is incredibly > annoying, as I can't re-register with the client I normally use > (mcabber), and have to instead load up Psi to do it. Any ideas? I hear you. Heh, swap to Psi :-P -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Sat Oct 7 18:01:46 2006 From: [EMAIL PROTECTED] (Daniel) Date: Sat Oct 7 18:01:52 2006 Subject: [py-transports] PyYIMt not saving settings/registration? In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Oct 7, 2006, at 12:21 PM, Norman Rasmussen wrote: > On 10/7/06, Daniel <[EMAIL PROTECTED]> wrote: >> I'm running PyYIMt from CVS as of I think two days ago. Though I had >> this problem with CVS from about 9/30/2006 as well. > > mmm, can you go back to an older version and see if it has the issues > (you can ask cvs to check out from a specific date) I didn't have a problem before I switched from the released version, I don't think. Any recommendation on which date I should choose? >> I get it all set >> up, everything is running well for the most part, though I do get >> frequent disconnections. > > These are from the Yahoo server right? How many users do you have > using your server? (I've found that if I 'force connect' my 7 or 8 > users when I restart the transport, that some of the logins fail - I > assume due to some Yahoo rate limiting) I usually only have a handful of users on my server (maybe 5-6), but I have no idea how many users are using the Yahoo transport. Since it allows registration from outside my server, it may be quite a few. Do you know of a way to tell? But yes, it seems that Yahoo disconnects me frequently. This is another problem that seemed to become worse with the CVS version. >> However, if I have to restart the PyYIMt >> process, it loses seems to lose its registration information. > > Why do you have to restart it? (i.e. normal system shutdown/reboot, or > did it hang?) and how are you restarting it? (i.e. `kill` with > TERM(15) or KILL(9), or some other tool) I've had a few times where it simply died by itself, but occasionally I'll kill it if I need to reboot the machine or restart the Jabber server, and then I'm just killing the process with kill. >> When I >> connect after restarting the process, the transport and all my Yahoo >> contacts have revoked authorization, and any attempts to send >> messages to the transport or to my Yahoo contacts has the transport >> telling me that I'm not registered with it. > > :-( this should not happen. Are other users also loosing their > registrations? The userfile is synced to disk as soon as it's > updated. Is the file possibly becoming corrupted? Which version of > python are you using (and bdb/bsddb if you can tell) I don't know if it's happening to any others. I haven't received any complaints about it, but I would assume if it's happening to me it's happening to others as well. I'm using Python 2.4.3. As far as bdb, do you mean Berkeley DB? I think I'm using version 4.1.25. That's what's installed from ports anyway (this is a FreeBSD 6.1 machine). Interestingly enough, and I don't know if this matters or not, but if I run strings on yahoouser.dbm.db and grep for my Yahoo username, I get 51 matches. I don't have 51 Yahoo people in my roster, however. >> This is incredibly >> annoying, as I can't re-register with the client I normally use >> (mcabber), and have to instead load up Psi to do it. Any ideas? > > I hear you. Heh, swap to Psi :-P I can't use Psi from work, I can only use a console client. I really like mcabber, and I know the developer is probably going to work on getting disco support at some point in time, but until then... :)
