After upgrading from parity/parity:v2.5.13-stable to parity/parity:v2.7.2-stable I got error about service transaction cache in parity logs. It appears for existing fully synchronized instances and for fresh ones:
parity_1 | 2020-07-09 12:33:00 UTC Error occurred while refreshing service transaction cache: Invalid data
parity_1 | 2020-07-09 12:33:00 UTC Imported #6653099 0x94af?960e (0 txs, 0.00 Mgas, 3 ms, 0.57 KiB)
parity_1 | 2020-07-09 12:33:05 UTC Error occurred while refreshing service transaction cache: Invalid data
parity_1 | 2020-07-09 12:33:05 UTC Imported #6653100 0x9e07?2c82 (0 txs, 0.00 Mgas, 6 ms, 0.55 KiB)
With some traces on fresh instance:
^[[36mparity_1 |^[[0m 2020-07-09 12:18:10 UTC IO Worker #0 INFO network Public node URL: enode://e96c475fe0d11730d142ee82a1fc194390a11f6a3e18bf7b374302a440ce6d3994c6ae54c7d02c45a3e8170f5a0e4a369309ca34dc69b5720b98cb92765f8f69@172.23.0.2:30303
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #3 DEBUG txqueue Re-computing pending set for block: 0
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #0 DEBUG txqueue Removed 0 stalled transactions. Pool: 0/8192 (0 senders; 0/4096 kB) [minGasPrice: 0 Mwei, maxGas: 6791641]
^[[36mparity_1 |^[[0m
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #3 TRACE txqueue Refreshing certified addresses cache
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #3 ERROR client Error occurred while refreshing service transaction cache: Invalid data
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC Verifier #2 TRACE txqueue Refreshing certified addresses cache
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC Verifier #2 ERROR client Error occurred while refreshing service transaction cache: Invalid data
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #2 DEBUG txqueue Removed 0 stalled transactions. Pool: 0/8192 (0 senders; 0/4096 kB) [minGasPrice: 0 Mwei, maxGas: 6798272]
^[[36mparity_1 |^[[0m
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #0 TRACE txqueue Refreshing certified addresses cache
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #0 ERROR client Error occurred while refreshing service transaction cache: Invalid data
^[[36mparity_1 |^[[0m 2020-07-09 12:18:19 UTC IO Worker #2 DEBUG txqueue Removed 0 stalled transactions. Pool: 0/8192 (0 senders; 0/4096 kB) [minGasPrice: 0 Mwei, maxGas: 7687763]
^[[36mparity_1 |^[[0m
After upgrading from parity/parity:v2.5.13-stable to parity/parity:v2.7.2-stable I got error about service transaction cache in parity logs. It appears for existing fully synchronized instances and for fresh ones:
With some traces on fresh instance:
How to reproduce: You can find whole configuration and chainspec information inside this simple installation file on our repository: https://github.com/energywebfoundation/ewf-rpc/blob/master/ewc-rpc/install-rpc-ubuntu-server-18.04-ewc.bash
Second option is to use these script to install everything automatically on any fresh ubuntu environment like multipass or something.