retitle 488769 Better log messages if pymsnt cannot connect to Jabber server severity 488769 wishlist thanks
On Sat, 2008-07-05 at 09:25 +0200, Kiko Piris wrote: > 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! Brilliant, thanks for tracking this problem down! > 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> I agree, better log messages are needed here. > I feel embarrased, I guess I souldn’t file some bugreports until I’m > fully awake ;). > > Please, close it and sorry for the “noise”. Not at all, all bug reports are welcomed. :) -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
