Opened 11 years ago

Closed 2 years ago

#5958 closed defect (out of date)

MSN protocol - notification server / switchboard error

Reported by: Lysander Owned by: khc
Milestone: Component: MSN
Version: 2.4.2 Keywords: switchboard notification
Cc:

Description

I've been noticing issues in Pidgin while using the MSN protocol. For some reason, some times it can take quite a few times in order to sucesfuly connecto to a server, with notification server errors like:

(17:21:45) dns: DNS query for 'nexus.passport.com' queued
(17:21:45) dns: Created new DNS child 32423, there are now 1 children.
(17:21:45) dns: Successfully sent DNS request to child 32423
(17:22:18) dns: Got response for 'nexus.passport.com'
(17:22:18) dnsquery: IP resolved for nexus.passport.com
(17:22:18) proxy: Attempting connection to 65.54.179.216
(17:22:18) proxy: Connecting to nexus.passport.com:443 with no proxy
(17:22:18) proxy: Connection in progress
(17:22:34) msn: servconn read error, len: 0 error: Success
(17:22:34) msn: Connection error from Notification server (207.46.110.117): Reading error
(17:22:34) msn: C: NS 000: OUT
(17:22:34) account: Disconnecting account 0x81728e0
(17:22:34) connection: Disconnecting connection 0x846cfc8

These errors appeared every now and then, but lately they've become quite worse, to the point i haven't been able to get Pidgin to login to MSN (using three different MSN accounts) for the past two days. The official MSN client seems to work fine.

Another problem is that, even when i DO get connected, i keep getting this random issues with the switchboard error:

(16:18:45) msn: servconn read error, len: -1 error: Remote host closed connection.
(16:18:45) msn: Connection error from Switchboard server (207.46.26.85): Reading error
(16:18:45) msn: destroy httpconn (01B65A58)
(16:18:51) msn: new httpconn (026ECCB8)
(16:18:51) msn: C: NS 000: XFR 15 SB

These either manifest as a "failed to send due to switchboard error" warning on the conversation window (which ends up working after a few tries), or a subsequent disconnection, and it can happen every 5 minutes or every 5 hours - completely random. Sometimes it works fine for days and sometimes i get disconnected every time i try to open a new conversation.

Using the HTTP method to connect didn't help to solve these issues, or to change how often they appear. Other protocols seem to work quite fine, and the client doesn't crash or misbehaves when these appear.

Both of this issues are present on every Pidgin version from on the 2.2.x to 2.1.2 (it might very well happen before, but i haven't been keeping track). or whatever is worth, it might be linked to the MSNP version used, since the server insists on sending update urls for the official client whenever i get through - is this something we might expect to get fixed with the merge of MSNP14?

Attached to this ticket is a log of a series of connections attemps, all failed. Will gladly help with anything i can. Thanks in advance.

Attachments (1)

purple-debug.log (10.5 KB) - added by Lysander 11 years ago.
Purple debug log - Failure to connect to MSN server

Download all attachments as: .zip

Change History (10)

Changed 11 years ago by Lysander

Purple debug log - Failure to connect to MSN server

comment:1 Changed 11 years ago by Lysander

Pidgin versions should be 2.1.x to 2.4.2, sorry about the typo

comment:2 Changed 11 years ago by Lysander

After further testing, it seems that this problem is timeout related - whenever i hog the bandwidth (Bittorrent, f.ex.) the issue aries and freeing bandwidth again alleviates it. The program never reports it as a timed out connection though - perhaps this is something to fix? Or maybe adding a configuration option to allow finer control over timeout periods?

comment:3 Changed 11 years ago by Lysander

Setting up QoS on the network router so stuff like BT has lower priority almost makes the problem dissapear. Seems to definitely be some kind of connection timeout problem.

comment:4 Changed 11 years ago by Lysander

Just for clarification, other MSN clients (notably, the official one) works perfectly under the same conditions Pidgin fails.

comment:5 Changed 11 years ago by Lysander

For posterity's sake, the unnoficial "msn-pecan" (http://code.google.com/p/msn-pecan/) MSN protocol plugin solves this problem altogheter; i suggest giving it a try until the MSN protocol in libpurple is updated.

comment:6 Changed 11 years ago by bernmeister

Does this still occur in 2.5.1 which uses MSNP15? Can you please verify?

comment:7 Changed 11 years ago by Lysander

Yes - the problem appears to manifest less often, but it is still there. This is with Pidgin 2.5.1, built freshly from source:

(...)
(02:17:33) msn: C: SB 005: MSG 17 U 96
(02:17:38) msn: C: NS 000: PNG
(02:17:39) msn: servconn read error,len: -1, errno: 104, error: Connection reset by peer
(02:17:39) msn: Connection error from Notification server (207.46.108.91): Reading error
(02:17:39) msn: C: SB 005: OUT
(02:17:39) msn: destroy httpconn (0x8e154b8)
(02:17:39) msn: C: SB 003: OUT
(02:17:39) msn: destroy httpconn (0x91cf1d8)
(02:17:39) msn: C: SB 002: OUT
(02:17:39) msn: destroy httpconn (0x8c41b00)
(02:17:39) msn: C: SB 001: OUT
(02:17:39) msn: C: SB 001: OUT
(02:17:39) msn: destroy httpconn (0x836c788)
(02:17:39) msn: C: NS 000: OUT
(02:17:39) msn: Connection error from Notification server (207.46.108.91): Writing error
(02:17:39) account: Disconnecting account 0x8184c10
(02:17:39) connection: Disconnecting connection 0x83af790
(02:17:39) connection: Deactivating keepalive.
(02:17:39) msn: destroy the OIM 0x83ac8d0
(02:17:39) msn: destroy httpconn (0x8d73800)
(02:17:39) jabber: jabber_actions: have pep: NO
(02:17:39) jabber: jabber_actions: have pep: NO
(02:17:39) connection: Destroying connection 0x83af790
(02:17:44) util: Writing file accounts.xml to directory /home/lys/.purple
(02:17:44) util: Writing file /home/lys/.purple/accounts.xml
(02:17:45) util: Writing file blist.xml to directory /home/lys/.purple
(02:17:45) util: Writing file /home/lys/.purple/blist.xml
(02:17:45) jabber: Recv (ssl)(1):  
(02:17:54) autorecon: do_signon called
(02:17:54) autorecon: calling purple_account_connect
(02:17:54) account: Connecting to account pinlisandro@hotmail.com
(02:17:54) connection: Connecting. gc = 0x845c200
(02:17:54) msn: new httpconn (0x8bfa470)
(02:17:54) dns: DNS query for 'messenger.hotmail.com' queued
(...)

One (apparently new) thing i've noticed several times in the logs is this:

(02:12:01) msn: Unhandled content-type 'text/x-keepalive'

Seems like the client isn't responding the server keepalive messages :(

comment:8 Changed 10 years ago by Lysander

Still observed in 2.5.4

comment:9 Changed 2 years ago by dx

  • Resolution set to out of date
  • Status changed from new to closed

Closing all MSN tickets, since it has been removed in pidgin 2.12.0 after being broken for a couple of years (see http://ismsndeadyet.com/). The skypeweb plugin can be used as an alternative (yes, it supports MSN logins too)

If this issue is still present in any other protocols supported by pidgin, please leave a comment and we will reopen it.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!