Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing and re-adding an exex causes error reading notification wal #13429

Open
1 task done
0xalex88 opened this issue Dec 17, 2024 · 0 comments
Open
1 task done

Removing and re-adding an exex causes error reading notification wal #13429

0xalex88 opened this issue Dec 17, 2024 · 0 comments
Assignees
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled

Comments

@0xalex88
Copy link

Describe the bug

While working on an exex, I've removed it from the code to allow for faster syncing (it's an OP chain, so syncing is done block by block and the exex slows it down), when I've added it back, I got the error logged below during the node startup.
After deleting the exex folder the node started properly again.

Steps to reproduce

  1. create a node with an exex attached to it
  2. remove the install_exex call
  3. run the node again for a while
  4. add install_exex again

Node logs

2024-12-17T06:15:18.187317Z ERROR reth::cli: shutting down due to error
Error: notification {id} not found

Location:
 /usr/local/cargo/git/checkouts/reth-36d3ea1d1152b20c/15fac08/crates/exex/exex/src/wal/storage.rs:122:45

Platform(s)

Linux (x86)

Container Type

Docker

What version/commit are you on?

1.1.4 git dependencies

What database version are you on?

2

Which chain / network are you on?

fraxtal

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

  • I agree to follow the Code of Conduct
@0xalex88 0xalex88 added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Dec 17, 2024
@shekhirin shekhirin self-assigned this Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled
Projects
Status: Todo
Development

No branches or pull requests

2 participants