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

Data corruption detected while running Holesky node #8102

Open
1 task done
raa-dev opened this issue May 4, 2024 · 0 comments
Open
1 task done

Data corruption detected while running Holesky node #8102

raa-dev opened this issue May 4, 2024 · 0 comments
Labels
C-bug An unexpected or incorrect behavior

Comments

@raa-dev
Copy link

raa-dev commented May 4, 2024

Describe the bug

After I ended the build process I ran a full node with the following command:

reth node --full --http --http.api all --http.addr 0.0.0.0 --ws --ws.api all --ws.addr 0.0.0.0 --metrics localhost:9001 --chain holesky

Everything went well and smoothly, it ended the sync process with the CL client (lighthouse). For outisider reasons to the node, the host shut down, gave me a blue screen. It worths to mention I'm running the node in a Ubuntu vm, hosted by a Windows 11.
So, after I rebooted the PC, reopen the vm and tried to run the full node again, I got the following log:

image

I tried to reinstall reth, but it still gave me the same problem. Also, I ran a mainnet node, just to double check, and it kept running normally, so it is happening with holesky node only.

Steps to reproduce

Hard for me to say how to reproduce it because the only thing happened was the blue screen, so maybe try to turn off the PC while is working.

Execute reth node --full --http --http.api all --http.addr 0.0.0.0 --ws --ws.api all --ws.addr 0.0.0.0 --metrics localhost:9001 --chain holesky

See the logs to validate if it happens

Node logs

No response

Platform(s)

Linux (x86)

What version/commit are you on?

0.2.0-beta.6-dev

What database version are you on?

2

Which chain / network are you on?

holesky

What type of node are you running?

Full via --full flag

What prune config do you use, if any?

No response

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

RUSTFLAGS="-C target-cpu=native" cargo build --profile maxperf --features jemalloc, asm-keccak

Code of Conduct

  • I agree to follow the Code of Conduct
@raa-dev raa-dev added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels May 4, 2024
@DaniPopes DaniPopes removed the S-needs-triage This issue needs to be labelled label May 6, 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
Projects
Status: Todo
Development

No branches or pull requests

2 participants