parity crashes on syncing classic chain

[xlk3099]

Before filing a new issue, please provide the following information.

• Parity Ethereum version: 2.0.6(stable)
• Operating system: Linux
• Installation: one-line installer
• Fully synchronized: no
• Network: classic
• Restarted: yes

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

stack backtrace:
0: 0x55e162395fdc -
1: 0x55e162395d92 -
2: 0x55e162395e08 -
3: 0x55e162394c0a -
4: 0x55e160e73305 -
5: 0x55e1623f5753 -
6: 0x55e1623bda46 -
7: 0x55e1623bce44 -
8: 0x55e161b2ca15 -
9: 0x55e161a4ee65 -
10: 0x55e1617b6dd9 -
11: 0x55e161b47a72 -
12: 0x55e161a781cd -
13: 0x55e161a79617 -
14: 0x55e161a803aa -
15: 0x55e161b0ce7d -
16: 0x55e16241f9c9 -
17: 0x55e161bdf439 -
18: 0x55e1623f81da -
19: 0x55e1623f5d25 -
20: 0x7f3d399676b9 -
21: 0x7f3d3948741c -
22: 0x0 -

Thread 'Verifier #0' panicked at 'assertion failed: rc == -1', util/journaldb/src/archivedb.rs:141

Steps to reproduce:
parity --chain=classic --cache-size=4096 --db-compaction=ssd --pruning=archive --fat-db=on --tracing=on

[jam10o-new]

Hey, if possible can you please share some more information about your system, like the distribution you are running and your specifications; and if possible, the log messages before this panic occurs, ideally with -l sync enabled?

[andresilva]

Can you confirm with the latest beta version instead? We fixed a related issue in #9525 but it seems it wasn't backported to stable.

[debris]

@andresilva was the bug crashing the node immediately or did it cause an invalid state of the database? If the later, maybe we should advise users to rebuild their fatdb in case of a crash?

[cheme]

I think it is a duplicate of #9180 . The fix has been backported to beta, but not stable.

[xlk3099]

After changing to beta, the crash goes away.