On 05/07/2008 at 01:06 +0100, Sam Morris wrote: > However, I think this is a symptom of your problem, rather than the > actual cause. twistd.removePID is only called from the callback inside > the App.shuttingDown method in main.py; and App.shuttingDown is only > called when the reactor shuts down. > > So it appears that something else is causing pymsnt to shut down, and > these messages are logged as a result of that. As for tracking down the > root cause of the problem, I can only suggest ramping debugLevel up to 4 > and trawling through the log file. Unfortunately a lot of uninteresting > stuff will be logged, but maybe there will be a grain of useful > information in there too.
Doing this I realised that that error was logged when *I* was shutting down pymsnt. And indeed it had nothing to see with the “problem”. And the “problem” was that the lines of the MSN Transport were missing from ejabberd.cfg :-[ No wonder it wasn’t working!, ejabberd wasn’t listening for pymsnt connections! Although it is not an excuse for me, I think that a line on pymnst’s log noticing that it can not connect to jabber server would be helfpul. With debugLevel 2 there was no message at all in it, and raising it to 4 this was logged: | [2008-07-05 08:39:28] Starting factory <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory object at 0xb7d0aacc> | [2008-07-05 08:39:28] <twisted.internet.tcp.Connector instance at 0xa62598c> will retry in 59 seconds | [2008-07-05 08:39:28] Stopping factory <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory object at 0xb7d0aacc> Which is quite cryptic to me. But I repeat, this is not an excuse for my incompetence :) I feel embarrased, I guess I souldn’t file some bugreports until I’m fully awake ;). Please, close it and sorry for the “noise”. Cheers! -- Kiko Private mail is preferred encrypted: http://www.pirispons.net/pgpkey.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
