1 2016-11-15 15:06:44 <thermoman> just upgraded some nodes from 0.11.2 to 0.13.1 and now RPC command listtransactions '*' 100 doesnt work anymore
 2 2016-11-15 15:06:50 <thermoman> bitcoin-cli listtransactions '*' 100
 3 2016-11-15 15:06:51 <thermoman> error: couldn't parse reply from server
 4 2016-11-15 15:06:56 <thermoman> any ideas?
 5 2016-11-15 15:09:01 <luke-jr> thermoman: is this a really big wallet?
 6 2016-11-15 15:09:08 <thermoman> luke-jr: yes, it is
 7 2016-11-15 15:09:19 <luke-jr> I wonder if it's hitting a timeout or size limit
 8 2016-11-15 15:09:30 <luke-jr> I guess the 100 should rule out the size possibility
 9 2016-11-15 15:10:01 <luke-jr> does it take significant time?
10 2016-11-15 15:10:24 <thermoman> the error get returned almost instant
11 2016-11-15 15:10:36 <thermoman> oh stop
12 2016-11-15 15:10:42 <thermoman> the wallet in question is a very small one
13 2016-11-15 15:10:56 <luke-jr> do other RPCs work? how about just normal listtransactions?
14 2016-11-15 15:11:40 <thermoman> listtransactions without parameters = same error
15 2016-11-15 15:12:36 <thermoman> Keys: 368 plaintext, 0 encrypted, 368 w/ metadata, 368 total
16 2016-11-15 15:12:43 <thermoman> mapWallet.size() = 40
17 2016-11-15 15:12:47 <thermoman> from debug.log
18 2016-11-15 15:13:01 <thermoman> wallet.dat is 444 kBytes
19 2016-11-15 15:13:05 <luke-jr> how about getnetworkinfo and getwalletinfo?
20 2016-11-15 15:15:05 <moli> luke-jr, how about:  listtransactions "*" 100 0   ?
21 2016-11-15 15:15:09 <thermoman> both are working. txcount: 40 (the small 444kByte wallet) and 848 (other node, same problem, 8.6 MByte wallet.dat)
22 2016-11-15 15:15:18 <sdaftuar> is this potentially an incompatibility between an old version of bitcoin-cli and a newer version bitcoind?  what does bitcoin-cli --version return?
23 2016-11-15 15:15:49 <thermoman> bitcoin-cli --version
24 2016-11-15 15:15:50 <thermoman> Bitcoin Core RPC client version v0.13.1.0-g03422e5
25 2016-11-15 15:15:58 <thermoman> it's selfcompiled
26 2016-11-15 15:16:05 <thermoman> with bitcoind and cli are from the same source
27 2016-11-15 15:16:18 <thermoman> any way to debug this further?
28 2016-11-15 15:16:46 <luke-jr> I'd probably wireshark it about now
29 2016-11-15 15:16:56 <thermoman> listtransactions "*" 100 0 -- same error
30 2016-11-15 15:16:58 <luke-jr> see what it's actually doing on the networking level
31 2016-11-15 15:18:15 <thermoman> ok, stand by
32 2016-11-15 15:22:14 <thermoman> ok boys and girls
33 2016-11-15 15:22:42 <thermoman> the server does return JSON. but it seems there is a comment in one of the TXs that has a german umlaut
34 2016-11-15 15:23:44 <luke-jr> thermoman: are you using the bundled Univalue, or an external library?
35 2016-11-15 15:24:07 <thermoman> the german umlaut is 0xFC, latin1 for ue
36 2016-11-15 15:24:27 <luke-jr> JSON is UTF-8
37 2016-11-15 15:24:46 <thermoman> i just used tcpdump -X and i see it's only 1 byte
38 2016-11-15 15:24:54 <thermoman> so there is latin1 there
39 2016-11-15 15:25:00 <luke-jr> that's probably your issue
40 2016-11-15 15:25:09 <thermoman> comment might have been added some time ago
41 2016-11-15 15:25:30 <thermoman> can i modify the comment for a TX?
42 2016-11-15 15:28:35 <luke-jr> not afaik
43 2016-11-15 15:29:53 <thermoman> it worked with 0.11.2
44 2016-11-15 15:30:27 <thermoman> can I safely do a db_dump of the wallet.dat, modify the comment somehow and reimport it to a new wallet.dat?
45 2016-11-15 15:30:40 <thermoman> or are there checksums that wouldn't match?
46 2016-11-15 15:32:26 <luke-jr> thermoman: I suspect if you use 0.11.2's RPC client, it will work still.
47 2016-11-15 15:35:48 <thermoman> luke-jr: this doesn't make it better ;)
48 2016-11-15 15:36:05 <thermoman> so how would you fix this if you were me right now?
49 2016-11-15 15:39:43 <luke-jr> I would join #bitcoin-core-dev and start a discussion with other developers about how to cleanly handle upgrading non-UTF8 wallets ☺
50 2016-11-15 15:40:50 <thermoman> :D
51 2016-11-15 15:41:35 <jonasschnelli> thermoman: you say this one does not work "bitcoin-cli listtransactions '*' 100", right?
52 2016-11-15 15:41:43 <jonasschnelli> How long does it take until you get the response?
53 2016-11-15 15:41:50 <jonasschnelli> Is bitcoin-cli (the binary) also from 0.13?
54 2016-11-15 15:42:44 <jonasschnelli> thermoman: this usually means, you haven't got back a JSON object.
55 2016-11-15 15:43:18 <jonasschnelli> Ah... while reading back I see the German Umlaut problem..
56 2016-11-15 15:43:24 <jonasschnelli> let me try to reproduce this
57 2016-11-15 15:45:36 <thermoman> jonasschnelli: the response is instant
58 2016-11-15 15:45:57 <thermoman> tcpdump reveals the response is instant. it really is the parser i guess