On 06/10/05, Daniel Henninger <[EMAIL PROTECTED]> wrote:
>
> On Oct 5, 2005, at 1:11 PM, Adam Chernow wrote:
>
> > Hey Guys and Gals....
> >
> > I had a problem this morning.... I logged on to my Jive Server but
> > neither of my 2 transports (PyAim 0.6 and PyICQ 0.6) logged me in.
> > Finding it odd, I checked service discovery and neither of them
> > were showing up there either. Turned out that my server was
> > rebooted overnight... I SSHed in and reloaded the 2 services,
> > however, now PyICQ is not logging me in and PyAIM logged me in but
> > I got presence on only 1 contact so I hit "log off" on the
> > transport but it kept trying to re log me in which caused AIM to
> > throw a "trying to re-logon too soon" error. PyAIM then kept
> > trying to re-logon. Exiting my PSI client and logging off the
> > server did not help. I ultimately had to kill the PyAIM process.
> >
> > Here's the log from the terminal window that I had used to start
> > PyAIM. I should note that I *HAD* used the & to put it in the
> > background but it kept throwing errors.
> >
>
> - snip extremely long error log.. -
>
> Howdy, this is a known error under Windows which has been fixed
> since, but not in an actual release yet. You can comment out the
> lines that look like this:
> #This does not work under Windows, so we're getting rid of it for now.
> #if (exe.find("python") >= 0):
> # os.execv(exe, [name, sys.argv[0]]+sys.argv[1:])
>
> To eliminate the problem.
>
> Daniel
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
This doesn't look like that problem. From Adam's description it
sounds like he's using a linux server, also the transport had already
been running for a while when this loop occurred. Additionally the
stack trace is huge, which wouldn't happen with the win32 exec issue.
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Thu Oct 6 14:44:58 2005
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Thu Oct 6 14:45:11 2005
Subject: [py-transports] Help!!! PyAim stuck in an infite loop!
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Hrm, you are right. It's not the same thing. What the... I've never
seen that behavior before. Anyone else seen this perchance?
Daniel
On Oct 6, 2005, at 9:21 AM, Norman Rasmussen wrote:
> On 06/10/05, Daniel Henninger <[EMAIL PROTECTED]> wrote:
>
>>
>> On Oct 5, 2005, at 1:11 PM, Adam Chernow wrote:
>>
>>
>>> Hey Guys and Gals....
>>>
>>> I had a problem this morning.... I logged on to my Jive Server but
>>> neither of my 2 transports (PyAim 0.6 and PyICQ 0.6) logged me in.
>>> Finding it odd, I checked service discovery and neither of them
>>> were showing up there either. Turned out that my server was
>>> rebooted overnight... I SSHed in and reloaded the 2 services,
>>> however, now PyICQ is not logging me in and PyAIM logged me in but
>>> I got presence on only 1 contact so I hit "log off" on the
>>> transport but it kept trying to re log me in which caused AIM to
>>> throw a "trying to re-logon too soon" error. PyAIM then kept
>>> trying to re-logon. Exiting my PSI client and logging off the
>>> server did not help. I ultimately had to kill the PyAIM process.
>>>
>>> Here's the log from the terminal window that I had used to start
>>> PyAIM. I should note that I *HAD* used the & to put it in the
>>> background but it kept throwing errors.
>>>
>>>
>>
>> - snip extremely long error log.. -
>>
>> Howdy, this is a known error under Windows which has been fixed
>> since, but not in an actual release yet. You can comment out the
>> lines that look like this:
>> #This does not work under Windows, so we're getting rid of it for
>> now.
>> #if (exe.find("python") >= 0):
>> # os.execv(exe, [name, sys.argv[0]]+sys.argv[1:])
>>
>> To eliminate the problem.
>>
>> Daniel
>> _______________________________________________
>> py-transports mailing list
>> py-transports@blathersource.org
>> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>>
>>
>
> This doesn't look like that problem. From Adam's description it
> sounds like he's using a linux server, also the transport had already
> been running for a while when this loop occurred. Additionally the
> stack trace is huge, which wouldn't happen with the win32 exec issue.
>
> --
> - Norman Rasmussen
> - Email: [EMAIL PROTECTED]
> - Home page: http://norman.rasmussen.co.za/
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
>
>
