reth icon indicating copy to clipboard operation
reth copied to clipboard

Cant start reth.exe on windows 10 in powershell

Open Ajes1337 opened this issue 2 years ago • 2 comments

Describe the bug

image

Steps to reproduce

install windows 10 download windows build from github run the node from powershell with command ".\reth.exe node"

Node logs

PS C:\reth> .\reth.exe node
2023-06-21T17:21:43.080472Z  INFO reth::cli: reth 0.1.0-alpha.1 (b245193) starting
2023-06-21T17:21:43.080895Z  INFO reth::cli: Configuration loaded path="C:\\Users\\Admin\\AppData\\Roaming\\reth\\mainnet\\reth.toml"
2023-06-21T17:21:43.081022Z  INFO reth::cli: Opening database path="C:\\Users\\Admin\\AppData\\Roaming\\reth\\mainnet\\db"
Error: Failed to open database: -30784

Location:
    /project/crates/staged-sync/src/utils/init.rs:33:14
PS C:\reth>

Platform(s)

No response

What version/commit are you on?

0.1.0-alpha.1

What database version are you on?

?

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

No response

Code of Conduct

  • [X] I agree to follow the Code of Conduct

Ajes1337 avatar Jun 21 '23 17:06 Ajes1337

Can you try creating the path it tries to open? If that fixes it, then the solution is to create the database path (if it doesn't exist) before opening. This already happens on macOS and Linux I guess, but Windows is always an edge case...

onbjerg avatar Jun 21 '23 19:06 onbjerg

The path was already created when I looked into it, here is screenshot: image

Ajes1337 avatar Jun 22 '23 06:06 Ajes1337

do you have any solution for this? I have the same issue

0xDaizz avatar Jul 03 '23 02:07 0xDaizz

@Ajes1337 @0xDaizz we've just added more verbose opt-in database logs, can you please try running reth built from the latest main branch with --db.log-level error CLI argument?

.\reth.exe node --db.log-level error

shekhirin avatar Jul 04 '23 14:07 shekhirin

@shekhirin how can I build the exe file with the newest branch? when I compile the compiler throws a lot of errors..

0xDaizz avatar Jul 05 '23 18:07 0xDaizz

@0xDaizz Just build from main, unfortunately the Windows release is borked because Windows is Windows. I am working on a fix, but it definitely works when compiling manually now after #3608

No need to add --db.log-level, I know what the underlying issue is.

Thanks for reporting this bug :)

onbjerg avatar Jul 05 '23 21:07 onbjerg

I still have this error in Alpha2 release, also have the error with WSL2

image

Ajes1337 avatar Jul 08 '23 06:07 Ajes1337

reth is working now on WSL2 Ubuntu on windows 10, I had to upgrade from WSL1 to WSL2 👍

Ajes1337 avatar Jul 09 '23 17:07 Ajes1337

reth is working now on WSL2 Ubuntu on windows 10, I had to upgrade from WSL1 to WSL2 👍

Did you successfully finish syncing? I have had some Bus error issues during execution phase several times.

https://github.com/paradigmxyz/reth/issues/3293

0xDaizz avatar Jul 09 '23 17:07 0xDaizz

I have first just started syncing on WSL2, so cant say much yet

Ajes1337 avatar Jul 09 '23 18:07 Ajes1337

Closing as @Ajes1337 confirmed in the Reth Telegram chat that he was actually running WSLv1 instead of v2. @0xDaizz pls confirm you're on WSLv2? Else we can re-open.

gakonst avatar Jul 10 '23 14:07 gakonst

@gakonst

on windows 10, still this error keeps me away from the node.

PS C:\Users\HW\Documents\reth-v0.1.0-alpha.4-x86_64-pc-windows-gnu> ./reth node
2023-07-23T08:01:28.877242Z  INFO reth::cli: reth 0.1.0-alpha.4 (b2b2cbe) starting
2023-07-23T08:01:28.878019Z  INFO reth::cli: Configuration loaded path="C:\\Users\\HW\\AppData\\Roaming\\reth\\mainnet\\reth.toml"
2023-07-23T08:01:28.878065Z  INFO reth::cli: Opening database path="C:\\Users\\HW\\AppData\\Roaming\\reth\\mainnet\\db"
Error: Failed to open database: -30784

Location:
    /project/crates/storage/db/src/lib.rs:125:18
PS C:\Users\HW\Documents\reth-v0.1.0-alpha.4-x86_64-pc-windows-gnu>

Used the pre-made binary on the reth github.

tried this on Adminirator PowerShell on Windows 10.

0xDaizz avatar Jul 23 '23 08:07 0xDaizz

Confirmed that this issue can be solved by building my own binary via $env:RUSTFLAGS="-C target-cpu=native"; cargo build --profile maxperf. sorry for bothering with Windows x(

0xDaizz avatar Jul 24 '23 10:07 0xDaizz