dequis / purple-facebook

Facebook protocol plugin for libpurple (moved from jgeboski/purple-facebook)
GNU General Public License v2.0
954 stars 88 forks source link

ERROR_QUEUE_OVERFLOW #308

Closed Dodger395 closed 7 years ago

Dodger395 commented 7 years ago

I am using the latest dll located at https://dl.voidium.net/pidgin/ and I am getting a "ERROR_QUEUE_OVERFLOW" error when trying to enable the account. This started first thing this morning.

The pidgin System Log says I signed on and then immediately signed off again.

dequis commented 7 years ago

boop https://github.com/dequis/purple-facebook/wiki/Debugging-Logs

Dodger395 commented 7 years ago

email sent with debug log

dequis commented 7 years ago

Thanks for the debug log, it had everything needed to figure this one out.

You're using an extremely old version, a34b993324e4, from Jul 6, 2015, because you have another copy of the same dll in the same directory. Remove that other copy.

(16:56:49) plugins: probing C:\Program Files\Pidgin\plugins\Copy of libfacebook.dll
[...]
(16:56:50) plugins: probing C:\Program Files\Pidgin\plugins\libfacebook.dll

Other interesting bits of the debug log if anyone is curious:

Writing message (topic: /messenger_sync_create_queue)
  00000000  7b 22 64 65 6c 74 61 5f  62 61 74 63 68 5f 73 69  |{"delta_batch_si|
  00000010  7a 65 22 3a 31 32 35 2c  22 6d 61 78 5f 64 65 6c  |ze":125,"max_del|
  00000020  74 61 73 5f 61 62 6c 65  5f 74 6f 5f 70 72 6f 63  |tas_able_to_proc|
  00000030  65 73 73 22 3a 31 32 35  30 2c 22 73 79 6e 63 5f  |ess":1250,"sync_|
  00000040  61 70 69 5f 76 65 72 73  69 6f 6e 22 3a 32 2c 22  |api_version":2,"|
  00000050  65 6e 63 6f 64 69 6e 67  22 3a 22 4a 53 4f 4e 22  |encoding":"JSON"|
  00000060  2c 22 69 6e 69 74 69 61  6c 5f 74 69 74 61 6e 5f  |,"initial_titan_|
  00000070  73 65 71 75 65 6e 63 65  5f 69 64 22 3a 30 2c 22  |sequence_id":0,"|
  00000080  64 65 76 69 63 65 5f 69  64 22 3a 22 64 63 30 32  |device_id":"dc02|
  00000090  xx xx xx xx xx xx xx xx  xx xx xx xx xx xx xx xx  |xxxx-xxxx-xxxx-x|
  000000a0  39 33 61 2d 38 61 64 64  32 65 36 35 33 31 61 32  |93a-8add2e6531a2|
  000000b0  22 2c 22 64 65 76 69 63  65 5f 70 61 72 61 6d 73  |","device_params|
  000000c0  22 3a 7b 7d 7d                                    |":{}}|
  000000d0
Reading 4 (flags: 0x2)
  00000000  42 02 00 04                                       |B...|
  00000010
Reading 3 (flags: 0x0)
  00000000  30 4c 00 05 2f 74 5f 6d  73 78 da 63 a8 56 2a 2c  |0L../t_msx.c.V*,|
  00000010  4d 2d 4d 75 cd 2b c9 2c  a9 f4 4c 51 b2 32 34 32  |M-Mu.+.,..LQ.242|
  00000020  34 b0 30 05 01 1d a5 d4  a2 a2 fc 22 e7 fc 94 54  |4.0........"...T|
  00000030  25 2b 25 d7 a0 20 ff a0  f8 c0 50 d7 50 d7 78 ff  |%+%.......P.P.x.|
  00000040  30 d7 20 37 1f ff 70 a5  5a 00 83 96 13 9f        |0..7..p.Z.....|
  00000050
Reading message (topic: /t_ms)
  00000000  00 7b 22 71 75 65 75 65  45 6e 74 69 74 79 49 64  |.{"queueEntityId|
  00000010  22 3a 31 32 31 30 38 35  35 35 35 35 2c 22 65 72  |":1210855555,"er|
  00000020  72 6f 72 43 6f 64 65 22  3a 22 45 52 52 4f 52 5f  |rorCode":"ERROR_|
  00000030  51 55 45 55 45 5f 4f 56  45 52 46 4c 4f 57 22 7d  |QUEUE_OVERFLOW"}|
  00000040
Parsing JSON: {"queueEntityId":1210855555,"errorCode":"ERROR_QUEUE_OVERFLOW"}

Main thing that sticks out as weird is the sync_api_version=2.

Also, right above that:

Parsing JSON: {"data":[{"name":"thread_list_ids","fql_result_set":[{"sync_sequence_id":"0"}]}]}

The result from a FQL query, which says {"sync_sequence_id":"0"}. Sounds familiar.

Above that:

Writing 1 (flags: 0x0)
  00000000  10 a6 03 00 06 4d 51 49  73 64 70 03 ca 00 3c 00  |.....MQIsdp...<.|
  00000010  xx xx xx xx xx xx xx xx  xx xx xx xx xx xx xx xx  |.xxxxxxxxxxxxxxx|
  00000020  xx xx xx xx xx 00 ce 7b  22 63 68 61 74 5f 6f 6e  |xxxxx..{"chat_on|
  00000030  22 3a 74 72 75 65 2c 22  66 67 22 3a 66 61 6c 73  |":true,"fg":fals|
  00000040  65 2c 22 6e 6f 5f 61 75  74 6f 5f 66 67 22 3a 74  |e,"no_auto_fg":t|
  00000050  72 75 65 2c 22 6d 71 74  74 5f 73 69 64 22 3a xx  |rue,"mqtt_sid":x|
  00000060  xx xx xx xx xx xx xx xx  xx 2c 22 6e 77 74 22 3a  |xxxxxxxxx,"nwt":|
  00000070  31 2c 22 6e 77 73 74 22  3a 30 2c 22 61 22 3a 22  |1,"nwst":0,"a":"|
  00000080  46 61 63 65 62 6f 6f 6b  20 41 70 70 20 2f 20 70  |Facebook.App./.p|
  00000090  75 72 70 6c 65 2d 66 61  63 65 62 6f 6f 6b 20 2f  |urple-facebook./|
  000000a0  20 61 33 34 62 39 39 33  33 32 34 65 34 22 2c 22  |.a34b993324e4","|
  000000b0  64 22 3a 22 64 63 30 32  36 33 61 34 2d 33 34 65  |d":"dc0263a4-34e|
  000000c0  xx xx xx xx xx xx xx xx  xx xx xx xx xx xx xx xx  |x-xxxx-xxxx-xxxx|
  000000d0  32 65 36 35 33 31 61 32  22 2c 22 70 66 22 3a 22  |2e6531a2","pf":"|
  000000e0  6a 7a 22 2c 22 75 22 3a  22 xx xx xx xx xx xx xx  |jz","u":"xxxxxxx|
  000000f0  xx xx xx 22 7d 00 xx xx  xx xx xx xx xx xx xx xx  |xxx"}..xxxxxxxxx|

MQIsdp (old protocol), directly readable json payload (it uses compressed thrift nowadays), user agent says Facebook App / purple-facebook / a34b993324e4

Dodger395 commented 7 years ago

Thanks. I'm just curious as to why pidgin would use "Copy of libfacebook.dll" instead of "libfacebook.dll". Removing that old renamed copy did fix the issue.

Edit: I missed the "probing" part and figured out why it was looking at it. I had other old versions but had changed the extension so they weren't looked at. Thanks again for your help.

dequis commented 7 years ago

Yay