Description
Blockscout could not import some transactions to DB.
Seems like it having problem with type 2 transactions.
Error started appearing after QA team updated Regression testnet to 2.4 beta versions, and was spotted after type 2 transactions take place on most of the chains. On chains where there are no type 2 transactions DB and backend continue to work correctly.
Additional problem with this issue is that when there are problems in backend in prints a lot of logs, which can fill up disk space fast.
Maybe @yavrsky can add more details.
Logs:
logs_backend.log
logs_db.log
Type of the installation
Docker-compose
Type of the JSON RPC archive node
geth
Type of the chain
No response
Link to the page
No response
Steps to reproduce
No response
Backend version
2.0.0
Frontend version
1.28.1
Elixir & Erlang/OTP versions
Operating system
No response
Additional information
No response
Description
Blockscout could not import some transactions to DB.
Seems like it having problem with type 2 transactions.
Error started appearing after QA team updated Regression testnet to 2.4 beta versions, and was spotted after type 2 transactions take place on most of the chains. On chains where there are no type 2 transactions DB and backend continue to work correctly.
Additional problem with this issue is that when there are problems in backend in prints a lot of logs, which can fill up disk space fast.
Maybe @yavrsky can add more details.
Logs:
logs_backend.log
logs_db.log
Type of the installation
Docker-compose
Type of the JSON RPC archive node
geth
Type of the chain
No response
Link to the page
No response
Steps to reproduce
No response
Backend version
2.0.0
Frontend version
1.28.1
Elixir & Erlang/OTP versions
Operating system
No response
Additional information
No response