On Mon, Jun 30, 2008 at 4:31 PM, Jamin W. Collins <[EMAIL PROTECTED]> wrote:
> The transport finally stopped completing login requests again last > night. I have the entire session logged with the dumpProtocol enabled. > I assume there are at least some bits in the dump that should not be > revealed (user/pass and such) so I'm hesitant to send it to the list. > What inside the log should I be looking for? The output doesn't appear > to have any form of a timestamp. > Hey Jamin, Got the logs -- when the transport stops logging in, does it still respond to service discovery, etc? Can you reproduce the logs of where you tried to logout/login to poke the transport to disconnect/re-connect. Something else I noticed, is that "yahoo.localhost/registered" is the entry on your roster. Now "/registered" was removed a long time back, so you probably want to remove the entry and re-register with the transport so the the correct entry goes back. (This should re-init your subscriptions too). I'm not sure how important is it to have the resource removed, but running with "/registered" isn't a supported configuration anymore. 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 -~----------~----~----~----~------~----~------~--~---
