#287 closed defect (worksforme)
msn protocol: read error 104
Reported by: | xwl | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | BitlBee | Version: | 1.0.3 |
Keywords: | Cc: | william.xwl@… | |
IRC client+version: | Client-independent | Operating System: | Linux |
OS version/distro: | debian unstable gnu/linux |
Description
It looks like that MSN in bitlbee(from cvs) isn't very stable. It keeps disconnecting due to "read error 104" randomly.
When i change to pidgin, its MSN seems pretty stable.
This "read error" is printed by myself, by inserting a line into msn_ns_call(), ns.c:
if( msn_handler( md->handler ) == -1 ) /* Don't do this on ret == 0, it's already done then. */ { serv_got_crap( gc, "read() error: errno = %d", errno); hide_login_progress( gc, "Error while reading from server" ); signoff( gc ); return FALSE; }
i'm running cvs bitlbee on debian(unstable) powerpc.
Attachments (0)
Change History (5)
comment:1 Changed at 2007-07-01T14:01:38Z by
comment:2 Changed at 2007-07-02T06:07:52Z by
Yes, but *randomly* ! I don't know exactly what triggers that. I just cut two screenshot when bitlbee disconnects itself currently.
13:34 <bitlbee> 69 buddies (13 available, 10 away, 46 offline) 13:45 <bitlbee> msn - read() error: errno = 104 13:45 <bitlbee> msn - Login error: Error while reading from server 13:45 <bitlbee> msn - Signing off.. 13:45 <bitlbee> msn - Reconnecting in 20 seconds.. 13:45 <bitlbee> msn - Logging in: Connecting 13:45 <bitlbee> msn - Logging in: Connected to server, waiting for reply 13:45 <bitlbee> msn - Logging in: Transferring to other server 13:45 <bitlbee> msn - Logging in: Connected to server, waiting for reply 13:45 <bitlbee> msn - Logging in: Authenticated, getting buddy list 13:45 <bitlbee> msn - Logged in 13:47 <bitlbee> 69 buddies (11 available, 12 away, 46 offline) 14:02 <bitlbee> msn - read() error: errno = 104 14:02 <bitlbee> msn - Login error: Error while reading from server 14:02 <bitlbee> msn - Signing off.. 14:02 <bitlbee> msn - Reconnecting in 20 seconds.. 14:03 <bitlbee> msn - Logging in: Connecting 14:03 <bitlbee> msn - Logging in: Connected to server, waiting for reply 14:03 <bitlbee> msn - Logging in: Transferring to other server 14:03 <bitlbee> msn - Logging in: Connected to server, waiting for reply 14:03 <bitlbee> msn - Logging in: Authenticated, getting buddy list 14:03 <bitlbee> msn - Logged in
The network environment should be fairly okay, since my colleagues who runs MSN on Window XP don't have such problem. (Actually, ussualy when we are chatting in some MSN group, bitlbee would disconnect now and then..)
comment:4 Changed at 2007-10-11T02:56:46Z by
Are there any updates to bitlbee ?
I'm sorry I have stopped using bitlbee for sometime. I'm using adium now. So i can't tell..
comment:5 Changed at 2007-10-12T00:12:35Z by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Ok.. I'd need some traffic dumps to make any sense from this anyway. The error message makes it pretty likely that the server just terminated your connection. Not sure why Adium doesn't have this problem, possibly it's better at silently reconnecting.
Closing this now.
Does this still happen? errno 104 seems to be "Connection reset by peer". So that's usually not really BitlBee's fault. Do you know when this happens exactly?