On Wed, Jun 18, 2008 at 2:09 AM, Jamin W. Collins <[EMAIL PROTECTED]> wrote:
> I've found that periodically, the yahoo transport will simply stop > logging in for me. Even if I manually request a login for the transport > from my Jabber client (Gajim). When this happens I need to manually > stop and start the transport process and then everything is fine again, > for a while. > > Not quite sure how to begin debugging this as I can't seem to get the > transport to log any errors. I've tried setting the <debugFile/> > directive, which does create an empty file in the designated location. > > I've even tried running the transport in the foreground of a screen > session, no output. > > Any suggestions on how to track down the problem would be most appreciated. > Hi Jamin, debugFile is used for exception logging only, so I suppose one good thing is there are no exceptions being logged. You will need to enable dumpProtocol, and then run the transport under screen to be able to see the data. BTW: Are you using multiple resources or just a single resource for your client connections? Cheers Norman -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
