On 17.07.2006 17:13 CE(S)T, Yves Goergen wrote:
> [2006-07-16 21:35:01] Starting factory
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance at
> 0xb7d22dec>
> [2006-07-16 21:35:01] INFO :: :: PyTransport :: componentDisconnected
> :: {} ::
> [2006-07-16 21:35:01] <twisted.internet.tcp.Connector instance at
> 0xb784c78c> will retry in 2 seconds
> [2006-07-16 21:35:01] Stopping factory
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance at
> 0xb7d22dec>
Since nobody else seems to have the same problem, I tried to disassemble
the whole thing myself and see what exact piece of code is responsible
for those log entries. But I failed, I was not able to locate any code
that could have generated such debug output. I'm not familiar with
Python in special nor do I have intimate knowledge of the Py*t
applications. Maybe one of the developers can tell me how it can be
possible at all to see such log output? When I know that I might be able
to dig further into it and find the actual problem.
--
Yves Goergen "LonelyPixel" <[EMAIL PROTECTED]>
http://beta.unclassified.de ? My web laboratory.
From [EMAIL PROTECTED] Wed Jul 19 19:23:09 2006
From: [EMAIL PROTECTED] (Lars T. Mikkelsen)
Date: Wed Jul 19 19:23:27 2006
Subject: [py-transports] Cannot start PyMSNt and PyICQt
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Wed, Jul 19, 2006 at 08:49:49PM +0200, Yves Goergen wrote:
> On 17.07.2006 17:13 CE(S)T, Yves Goergen wrote:
> > [2006-07-16 21:35:01] Starting factory
> > <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance at
> > 0xb7d22dec>
> > [2006-07-16 21:35:01] INFO :: :: PyTransport :: componentDisconnected
> > :: {} ::
> > [2006-07-16 21:35:01] <twisted.internet.tcp.Connector instance at
> > 0xb784c78c> will retry in 2 seconds
> > [2006-07-16 21:35:01] Stopping factory
> > <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance at
> > 0xb7d22dec>
>
> Since nobody else seems to have the same problem, I tried to disassemble
> the whole thing myself and see what exact piece of code is responsible
> for those log entries. But I failed, I was not able to locate any code
> that could have generated such debug output. I'm not familiar with
> Python in special nor do I have intimate knowledge of the Py*t
> applications. Maybe one of the developers can tell me how it can be
> possible at all to see such log output? When I know that I might be able
> to dig further into it and find the actual problem.
I think the output you see is generated when the transport is able to
connect but not successfully set up an xmlstream (I get similar output
if I use a wrong component secret/password). This part is handled by the
twisted.words.protocols.jabber.component module - unfortunately, it
doesn't do much logging. Did you check if there are any hints in the
logfile of the Jabber server?
Best regards,
Lars
From [EMAIL PROTECTED] Wed Jul 19 19:58:03 2006
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Wed Jul 19 19:57:10 2006
Subject: [py-transports] pyAIMt bugs, take two
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Jul 19, 2006, at 1:39 PM, Matthew Anderson wrote:
> Hi --
>
> I never received any comment of any kind on my last query / message
> to the list, and I still have yet to figure out exactly how to get
> my component to talk to the pyAIMt component.
I don't recall seeing another message. Maybe it got lost in spam. =/
>
> However, I have zeroed in exactly on one of the things that is
> causing a traceback in pyAIMt. If it receives an unexpected
> presence stanza (without a type, indicating available) it suffers a
> meltdown. If I send a <presence type=probe /> stanza instead, it
> simply reports <presence type="unavailable" /> with no traceback.
> I assume this issue would be the same for the other gateways with
> the same foundation code, though I've only attempted to work with
> pyAIMt.
Define meltdown. =) If it weren't capable of testing with a type-
less presence, it wouldn't have gotten very far! =) (ie, it
certainly works with my tests)
> Also, several times now after getting pyAIMt sufficiently confused
> (2-3 tracebacks w/o actually shutting it down), pyAIMt has ceased
> to function entirely, to the point that even a proper jabber client
> can no longer interact with it successfully. Deleting the pyAIMt
> spool files has no effect, restarting the jabberd2 server has no
> effect, rebooting the server has no effect -- in fact, the only way
> I've gotten it working again at all is to do a drop of the jabberd2
> mysql database, run the init script again, and re-register the test
> users.
what the... that's very bizarre!
> Does anybody have any insight as to why these unexpected presence
> fragments would be such a big problem?
Aside from "that shouldn't happen"? ;) Does running it with the -D
option help identify what's going on any? (it being PyAIMt)
> Does anybody have any idea what could be tweaked in system state
> where pyAIMt would be broken, and then fixed by dropping the
> jabberd2 database and making a new one?
Well, like I said, I test it with jabberd2 amongst other servers and
I've never run into such problems. Color me confused.
> If it's helpful, a diff of the mysqldumps before and after the
> database refresh (and after the single user has re-registered) are
> below.
>
> Thanks,
> --
> Matt Anderson
>
>
>
> dominar: [~/Desktop] % diff jabberd-broken.mysql after-resetup.mysql
> 38c38
> < INSERT INTO `active` VALUES ('[EMAIL PROTECTED]',1,1152483537);
> ---
> > INSERT INTO `active` VALUES ('[EMAIL PROTECTED]',1,1153325786);
> 65c65
> < INSERT INTO `authreg` VALUES
> ('matt','bebop','CENSORED','44B180D1',
> 500,'9ab1d87180cd57442f7cfafa7476b4bc38d346c8');
> ---
> > INSERT INTO `authreg` VALUES
> ('matt','bebop','CENSORED','44BE5ADA',
> 500,'5088ade3aaeb32e3ffbaa7aa072ccf3a4ec8e3a4');
> 114d113
> < INSERT INTO `logout` VALUES ('[EMAIL PROTECTED]',2,1152563700);
> 310d308
> < INSERT INTO `roster-items` VALUES ('[EMAIL PROTECTED]',
> 23,'aim.bebop',NULL,0,1,0),('[EMAIL PROTECTED]',
> 9,'[EMAIL PROTECTED]',NULL,1,1,0),('[EMAIL PROTECTED]',
> 16,'[EMAIL PROTECTED]',NULL,1,1,0);
> 377d374
> < INSERT INTO `vcard` VALUES ('[EMAIL PROTECTED]',
> 1,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NUL
> L,NULL,NULL,NULL,NULL,NULL);
>
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
