On 15 Feb, 16:56, "Jamin W. Collins" <[email protected]> wrote: > With the recent release of Debian's latest stable version (Lenny), I > updated my server. The distribution update was the only change made. > The system had previously been running pymsnt v0.11.2 without any major > issue. However, now with 0.11.3 I get the following error message back > when trying to connect: > > Failed to connect to MSN servers: [Failure instance: Traceback (failure > with no frames): <type 'exceptions.Exception'>: Timeout > ] > > Searching seems to indicate some problem with packet fragmenting or > normalizing with routers, but I've made no change of any kind to my > router between this working and not, only the server update from Etch to > Lenny. > > Any other ideas or help in tracking this down and resolving it? I tried > rolling back to the 0.11.2 package, but it seems there have been a > number of changes in Twisted from the pid check to the daemonize routines.
I don't know about you, but I track testing on my server, and these problem have been happening for a few months now. I just assumed it was just transient problems due to changes on MS's end. It would be wonderful if it were a bug, as that would of course mean there's a chance of it being rectified and my users could then stop moaning about how rubbish jabber is because it keeps "crashing" and logging them out. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
