-
Notifications
You must be signed in to change notification settings - Fork 1.7k
stack backtrace: Ubuntu 17.04 #7493
Comments
Am I understanding correctly that the panic happened using the latest build from master on a data directory ( Can you provide a tar file of the manifest files and a few of the sst file from your old database directory For example:
Where Could you also please provide your old data directory structure?
|
Am I understanding correctly that the panic happened using the latest build from master on a data directory (.local/share/io.parity.ethereum) that was created from another git build from >1 year ago? Yes, correct. Can you provide a tar file of the manifest files and a few of the sst file from your old database directory .local/share/io.parity.ethereum/chains/ethereum/db? Yes, but the upload limit here is 10MB, even via Could you also please provide your old data directory structure? |
Also - identical behavior for classic chain, similarly out of sync |
starting from scratch, to an SSD, full sync was achieved with today's build |
Duplicate of #7188 |
understood, thank you |
Before filing a new issue, please provide the following information.
Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
@machine:~/src/ethereum/parity/parity$ target/release/parity
2018-01-07 22:54:41 Starting Parity/v1.9.0-unstable-c37a87e49-20180105/x86_64-linux-gnu/rustc1.23.0
2018-01-07 22:54:41 Keys path /home//.local/share/io.parity.ethereum/keys/Foundation
2018-01-07 22:54:41 DB path /home//.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2018-01-07 22:54:41 Path to dapps /home//.local/share/io.parity.ethereum/dapps
2018-01-07 22:54:41 State DB configuration: fast
2018-01-07 22:54:41 Operating mode: active
2018-01-07 22:54:41 Configured for Foundation using Ethash engine
2018-01-07 22:54:41 Updated conversion rate to Ξ1 = US$1214.10 (98054216 wei/gas)
====================
stack backtrace:
0: 0x561dbf20dc8c - backtrace::backtrace::trace::h88dff4dc401d81d6
1: 0x561dbf20dcc2 - backtrace::capture::Backtrace::new::hc1bdbce336b16eca
2: 0x561dbe6a0f89 - panic_hook::panic_hook::ha4f6f84d07d9cbbd
Thread 'main' panicked at 'Unexpected rlp error: RlpExpectedToBeData', /checkout/src/libcore/result.rs:906
This is a bug. Please report it at:
====================
restarts have identical results but for stack addresses:
@machine:~/src/ethereum/parity/parity$ target/release/parity
2018-01-07 23:28:14 Starting Parity/v1.9.0-unstable-c37a87e49-20180105/x86_64-linux-gnu/rustc1.23.0
2018-01-07 23:28:14 Keys path /home//.local/share/io.parity.ethereum/keys/Foundation
2018-01-07 23:28:14 DB path /home//.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2018-01-07 23:28:14 Path to dapps /home//.local/share/io.parity.ethereum/dapps
2018-01-07 23:28:14 State DB configuration: fast
2018-01-07 23:28:14 Operating mode: active
2018-01-07 23:28:14 Configured for Foundation using Ethash engine
2018-01-07 23:28:14 Updated conversion rate to Ξ1 = US$1213.48 (98104300 wei/gas)
====================
stack backtrace:
0: 0x558b71d3bc8c - backtrace::backtrace::trace::h88dff4dc401d81d6
1: 0x558b71d3bcc2 - backtrace::capture::Backtrace::new::hc1bdbce336b16eca
2: 0x558b711cef89 - panic_hook::panic_hook::ha4f6f84d07d9cbbd
Thread 'main' panicked at 'Unexpected rlp error: RlpExpectedToBeData', /checkout/src/libcore/result.rs:906
This is a bug. Please report it at:
Aborted
==================== CONFIGURATIONS ====================
====================
installation via git, likley > 1 year ago
====================
@machine:~/src/ethereum/parity/parity$ rustup -V
rustup 1.9.0 (57fc3c087 2018-01-04)
@machine:~/src/ethereum/parity/parity$ rustc -V
rustc 1.23.0 (766bd11c8 2018-01-01)
====================
I am NOT synchronized, likely 3-4 months behind.
==================== NOTES ====================
My system lacked this directory:
/home//.local/share/io.parity.ethereum/keys/Foundation
creating it made no difference.
==================== SUBOPTIMAL SOLUTION ====================
Removal of /home//.local/share/io.parity.ethereum
and restarting resulted in apparent success, peers were found and parity began
pulling in the chain.
Thereafter, replacing the newly created /home//.local/share/io.parity.ethereum
directory with the pre-existing one again resulted in the rlp error.
So the issue seems to be caused by something therein, something about
older builds.
The text was updated successfully, but these errors were encountered: