Skip to content
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.

Polygon Edge 0.6.2 still got cannot parse RLP: cannot parse long array: cannot parse array value: cannot parse empty string #1245

Open
AnggaPvr opened this issue Feb 22, 2023 · 1 comment

Comments

@AnggaPvr
Copy link

cannot parse RLP: cannot parse long array: cannot parse array value: cannot parse empty string

Description

Got an "cannot parse RLP: cannot parse long array: cannot parse array value: cannot parse empty string" issue on v0.6.x, upgraded to v0.6.2 based on This issue. After upgraded, still got the issue.

Your environment

  • OS and version : Ubuntu 22.04.1 LTS
  • The version of the Polygon Edge : v0.6.2
  • The branch that causes this issue : Using binary from release page
  • Locally or Cloud hosted (which provider) : Cloud AWS

Steps to reproduce

  • using polygon edge v0.6.x
  • got an error : cannot parse RLP: cannot parse long array: cannot parse array value: cannot parse empty string
  • Stop polygon-edge service
  • upgrade polygon-edge binary to v0.6.2 (download from release page)
  • start polygon-edge service
  • still got same issue

Logs

Feb 22 08:21:09 ip-172-31-15-206 systemd[1]: Stopped Polygon Edge Node Service.
Feb 22 08:21:09 ip-172-31-15-206 systemd[1]: Started Polygon Edge Node Service.
Feb 22 08:21:09 ip-172-31-15-206 polygon-edge[933076]: 2023-02-22T08:21:09.172Z [INFO]  polygon.server: Data dir: path=./data-dir
Feb 22 08:21:09 ip-172-31-15-206 polygon-edge[933076]: 2023-02-22T08:21:09.172Z [DEBUG] polygon.server: DataDog profiler disabled, set DD_PROFILING_ENABLED env var to enable it.
Feb 22 08:21:09 ip-172-31-15-206 polygon-edge[933076]: 2023-02-22T08:21:09.247Z [INFO]  polygon.blockchain: Current header: hash=0x0000000000000000000000000000000000000000000000000000000000000000 number=10885974
Feb 22 08:21:09 ip-172-31-15-206 polygon-edge[933076]: 2023-02-22T08:21:09.247Z [INFO]  polygon.blockchain: genesis: hash=0x02605d0f8f1ce0bf97d2cc4d6a8cbcd3952ec3d0e96f78b2980dd7bd6d70cfe0
Feb 22 08:21:09 ip-172-31-15-206 polygon-edge[933076]: 2023-02-22T08:21:09.247Z [INFO]  polygon.server.ibft.fork_manager.snapshot_validator_set: syncing past snapshots: from=10885973 to=10885974
Feb 22 08:21:09 ip-172-31-15-206 polygon-edge[933076]: cannot parse RLP: cannot parse long array: cannot parse array value: cannot parse empty string
Feb 22 08:21:09 ip-172-31-15-206 systemd[1]: polygon-edge-client.service: Deactivated successfully.
Feb 22 08:21:10 ip-172-31-15-206 systemd[1]: polygon-edge-client.service: Scheduled restart job, restart counter is at 1097.
Feb 22 08:21:10 ip-172-31-15-206 systemd[1]: Stopped Polygon Edge Node Service.
Feb 22 08:21:10 ip-172-31-15-206 systemd[1]: Started Polygon Edge Node Service.
Feb 22 08:21:10 ip-172-31-15-206 polygon-edge[933081]: 2023-02-22T08:21:10.411Z [INFO]  polygon.server: Data dir: path=./data-dir
Feb 22 08:21:10 ip-172-31-15-206 polygon-edge[933081]: 2023-02-22T08:21:10.411Z [DEBUG] polygon.server: DataDog profiler disabled, set DD_PROFILING_ENABLED env var to enable it.
Feb 22 08:21:10 ip-172-31-15-206 polygon-edge[933081]: 2023-02-22T08:21:10.505Z [INFO]  polygon.blockchain: Current header: hash=0x0000000000000000000000000000000000000000000000000000000000000000 number=10885974
Feb 22 08:21:10 ip-172-31-15-206 polygon-edge[933081]: 2023-02-22T08:21:10.505Z [INFO]  polygon.blockchain: genesis: hash=0x02605d0f8f1ce0bf97d2cc4d6a8cbcd3952ec3d0e96f78b2980dd7bd6d70cfe0
Feb 22 08:21:10 ip-172-31-15-206 polygon-edge[933081]: 2023-02-22T08:21:10.505Z [INFO]  polygon.server.ibft.fork_manager.snapshot_validator_set: syncing past snapshots: from=10885973 to=10885974
Feb 22 08:21:10 ip-172-31-15-206 polygon-edge[933081]: cannot parse RLP: cannot parse long array: cannot parse array value: cannot parse empty string
Feb 22 08:21:10 ip-172-31-15-206 systemd[1]: polygon-edge-client.service: Deactivated successfully.
@spudgy
Copy link

spudgy commented Mar 10, 2023

#996 (comment)

The new version only applies a mitigation to this, it does not fix the current state.
You will have to apply a back-up to a previous state or start over.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants