You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
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:
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
The text was updated successfully, but these errors were encountered: