On Jul 25, 1:34 am, Martin Sebald <[EMAIL PROTECTED]> wrote:
> Hello!
>
> >> I'm having some trouble with PyICQt 0.8b. First of all my setup: I'm
> >> running PyICQt with ejabberd on Debian. I'm using the Debian package
> >> but I also tried the original files (by copying these files into the
> >> directory), which did not help.
> >> First of all some ICQ transport users are shown as offline to some,
> >> not all (!) ICQ users.
> > It can depends from authorization. Not authorized contacts should be
> > visible as offline, it's normal
>
> Ah interesting. I tested this with one friend of mine who saw me
> offline all the time and this worked. But he was once authorized,
> years ago. Can this change or be forgotten by the transport or ICQ?
Seems yes. I'm using usual ICQ client for setting auth.
>
> I'll do some more testing!
>
> >> The second issue is, that some, not all (!) Jabber users which are
> >> registered with this transport cannot (auto)logon to the transport.
> >> When I restart the transport these people can connect.
> > You can reproduce it? May be any records in logs, strange messages to
> > users etc
>
> No this is completly unreproducable. :-(
>
> Sometimes people can logon to the transport which works automaticly
> most of the time, sometimes it does not work.
>
> I have logging active with the -d option in start-stop-daemon of
> Debian and PyICQt logs stuff like this:
>
> ---------------------------------------------
>
> [2008-07-23 23:04:57] Traceback (most recent call last):
> File "/usr/share/pyicqt/src/main.py", line 468, in main
> reactor.run()
> File "/usr/lib/python2.5/site-packages/twisted/internet/
> base.py", line 1048, in run
> self.mainLoop()
> File "/usr/lib/python2.5/site-packages/twisted/internet/
> base.py", line 1060, in mainLoop
> self.doIteration(t)
> File "/usr/lib/python2.5/site-packages/twisted/internet/
> epollreactor.py", line 215, in doPoll
> log.callWithLogger(selectable, _drdw, selectable, fd,
> event)
> --- <exception caught here> ---
> File "/usr/lib/python2.5/site-packages/twisted/python/
> log.py", line 51, in callWithLogger
> return callWithContext({"system": lp}, func, *args, **kw)
> File "/usr/lib/python2.5/site-packages/twisted/python/
> log.py", line 36, in callWithContext
> return context.call({ILogContext: newCtx}, func, *args,
> **kw)
> File "/usr/lib/python2.5/site-packages/twisted/python/
> context.py", line 59, in callWithContext
> return self.currentContext().callWithContext(ctx, func,
> *args, **kw)
> File "/usr/lib/python2.5/site-packages/twisted/python/
> context.py", line 37, in callWithContext
> return func(*args,**kw)
> File "/usr/lib/python2.5/site-packages/twisted/internet/
> epollreactor.py", line 244, in _doReadOrWrite
> self._disconnectSelectable(selectable, why, inRead)
> File "/usr/lib/python2.5/site-packages/twisted/internet/
> posixbase.py", line 196, in _disconnectSelectable
> selectable.connectionLost(failure.Failure(why))
> File "/usr/lib/python2.5/site-packages/twisted/internet/
> tcp.py", line 576, in connectionLost
> Connection.connectionLost(self, reason)
> File "/usr/lib/python2.5/site-packages/twisted/internet/
> tcp.py", line 416, in connectionLost
> protocol.connectionLost(reason)
> File "/usr/share/pyicqt/src/legacy/icqt.py", line 58, in
> connectionLost
> LogEvent(INFO, self.session.jabberID, message)
> exceptions.AttributeError: 'NoneType' object has no attribute
> 'jabberID'
>
> ---------------------------------------------
>
> This was the last log entry and these entries occur not often, only
> zero to two times a day.
Before this traceback should be line like "ICQ connection lost!
Reason". You can will show it?
>
> What happened to me earlier this evening was, that every ICQ contact
> went offline at once. I checked the transport via service discovery
> and found it working. There was an option "logon" but it had no effect
> when clicking onto it. After restarting the transport, I got logged
> into the transport automaticly and all ICQ contacts are there again
> and online as usual.
>
> Also users are complaining that they cannot use ICQ transport anymore.
> I have to talk to them to find out what really is the problem. Really
> not anymore all the time or the same like here with my account.
>
> How can I log/debug this issue further? This really sucks. Everything
> worked great before upgrading to ejabberd v2 from v1 and changing from
> PyICQt 0.8b to the same version but the official Debian package.
May be you changed also other software? Python or Twisted?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
