-
Notifications
You must be signed in to change notification settings - Fork 1.7k
crash Parity/v1.4.0-beta-170bd03-20161107/x86_64-linux-gnu/rustc1.12.1parity on json call #3267
Comments
What was the block number you were requesting? |
I can confirm this issue with beta (tracing on), with or without --pruning archive Executing the following causes the crash curl http://localhost:8546 -X POST --data "{"jsonrpc":"2.0","method":"eth_getUncleByBlockNumberAndIndex","params":["0x26e0f9", "0x0"],"id":1}" -H "Content-Type: application/json" ---- console log --== |
Have you synced on new version from scratch or did you use some older DB? |
Reproduced in master |
@arkpar @gavofyork Issue still persists in Master. Is a resync required ? 2016-11-10 01:45:07 Starting Parity/v1.5.0-unstable-29add4e-20161109/x86_64-windows-msvc/rustc1.12.0 |
@mtbitcoin commit 29add4e from your version string is a bit old and does not have the fix. Please try building the latest. |
@arkpar that worked, thanks! |
When I call
getBlockByNumber
with a block as parameter and transactions included on a parity node, it crashes. The node was not yet fully synced, but it had already synced the requested block.This was the command to start parity:
parity --tracing on --mode active --pruning archive
For me this is reproducible.
2016-11-08 13:27:39 UTC Syncing #2370963 797b…9ec1 6 blk/s 65 tx/s 6 Mgas/s 0+ 5958 Qed #2376924 0/ 8/25 peers 179 KiB db 875 KiB chain 52 MiB queue 2 MiB sync thread '<unnamed>' panicked at 'DecodeError: RlpExpectedToBeList, a0d4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3', util/rlp/src/rlpin.rs:120 stack backtrace: 1: 0x560bad64df19 - <unknown> 2: 0x560bad65698c - <unknown> 3: 0x560bad655859 - <unknown> 4: 0x560bad655f48 - <unknown> 5: 0x560bad655da2 - <unknown> 6: 0x560bad655d10 - <unknown> 7: 0x560bad04e159 - <unknown> 8: 0x560bad1a8388 - <unknown> 9: 0x560bacc9da2e - <unknown> 10: 0x560bacb7978b - <unknown> 11: 0x560bacb1983c - <unknown> 12: 0x560bacf6a159 - <unknown> 13: 0x560bacf6b45f - <unknown> 14: 0x560bacf6a829 - <unknown> 15: 0x560bacf6d88c - <unknown> 16: 0x560bacf48d3e - <unknown> 17: 0x560bacf40f35 - <unknown> 18: 0x560bacf410a0 - <unknown> 19: 0x560bacf40df5 - <unknown> 20: 0x560bacf3ee6c - <unknown> 21: 0x560bacf3d0c6 - <unknown> 22: 0x560bacf3063d - <unknown> 23: 0x560bacf385cf - <unknown> 24: 0x560bacf2fed7 - <unknown> 25: 0x560bad65e476 - <unknown> 26: 0x560bacf3a761 - <unknown> 27: 0x560bad6544f2 - <unknown> 28: 0x7fca246cd709 - start_thread 29: 0x7fca2517382c - clone 30: 0x0 - <unknown> 2016-11-08 13:27:43 UTC Finishing work, please wait... thread 'main' panicked at 'called
Result::unwrap()on an
Err` value: Closed', ../src/libcore/result.rs:788stack backtrace:
1: 0x560bad64df19 -
2: 0x560bad65698c -
3: 0x560bad655859 -
4: 0x560bad655f48 -
5: 0x560bad655da2 -
6: 0x560bad655d10 -
7: 0x560bad655c91 -
8: 0x560bad69338f -
9: 0x560bad325155 -
10: 0x560bad33b0fd -
11: 0x560bacf51f49 -
12: 0x560bacd022ab -
13: 0x560bacd0dac5 -
14: 0x560bacd1852d -
15: 0x560bad65e476 -
16: 0x560bad654fd2 -
17: 0x7fca2508d82f - __libc_start_main
18: 0x560bacadf4ad -
19: 0x0 -
`
The text was updated successfully, but these errors were encountered: