-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Thread 'http.worker10' panicked at 'decode db value failed: RlpExpectedToBeList' #11421
Comments
After a multiple restarts its freezes without any messages |
Not sure I understand what you mean by this. Do you mean that syncing is making progress for a few minutes? You see new blocks get imported? Is the node receiving any RPC traffic? If yes, what kind of calls are you making? |
After restart I got new blocks for 1-3 minutes |
Full log with error: Loading config file from /home/eth/bin/config.toml ==================== stack backtrace: Thread 'http.worker10' panicked at 'decode db value failed: RlpExpectedToBeList', src/libcore/result.rs:1165 This is a bug. Please report it at:
2020-01-29 16:39:17 Finishing work, please wait... |
Ok, this could be a bug in the RPC layer. What we need to make progress here is the logs from the RPC request that come in at the time of the panic. Turn on rpc logging with |
This log file |
After 25 minutes I got this log: 2020-01-29 18:08:15 IO Worker #0 INFO import Syncing #9378289 0xefbd…ae7d 33.33 blk/s 5100.0 tx/s 333.1 Mgas/s 0+ 15 Qed #9378309 0/100 peers 257 MiB chain 87 MiB db 1 MiB queue 13 MiB sync RPC: 0 conn, 5 req/s, 1579 µs (15 times Import one block) |
@androzd Would be useful to know which For example at |
I can't restore this information. After 4-5 restarts problem is changed, and now I got a syncing freezes. Syncing delay for 3-5 minutes Most frequent requests is: and not frequent is: personal_newAccount. When freeze starts 100% ram is used (128 GB) |
With disabled RPC works fine. But I need RPC too much |
More info 10 minutes without RPC works fine 2020-01-29 18:52:28 Syncing #9378519 0x2202…c6cb 0.00 blk/s 0.7 tx/s 0.0 Mgas/s 0+ 12 Qed #9378536 18/100 peers 135 MiB chain 79 MiB db 881 KiB queue 9 MiB sync RPC: 0 conn, 0 req/s, 0 µs |
I have the same |
янв 29 21:25:43 ubuntu parity[850]: 2020-01-29 21:25:43 Syncing #9378392 0x6b7e…5996 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 23 Qed #9378416 35/50 peers 74 KiB chain 74 MiB db 2 Mi |
I think we're looking at two separate issues: syncing stalling is likely unrelated to the RPC panic. Let's keep this ticket focused on the panic. Also, to get to the bottom of this we'll need to figure out which RPC is causing the panic. @androzd can you please run RPC calls, one at a time and with logging turned on until we find which one is causing this? Thanks. |
Issue with RPC panic is selfsolved.. I don't know how it solved. And I can't reproduce it. Only issue with syncing now reproduced |
i have open ethereum pool, uses rpc |
Ok, in that case I'm going to close this issue now. Feel free to open a new one if you can reproduce the panic again. |
Parity updated from previous stable version (v2.5.13)
Thread 'http.worker10' panicked at 'decode db value failed: RlpExpectedToBeList', src/libcore/result.rs:1165
Restarts does not helps, after restart syncing work 1-3 minutes and this error appeared again
The text was updated successfully, but these errors were encountered: