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

node crash and cant find smeshing directory after a reinstall #1716

Open
picaye opened this issue Apr 14, 2024 · 2 comments
Open

node crash and cant find smeshing directory after a reinstall #1716

picaye opened this issue Apr 14, 2024 · 2 comments

Comments

@picaye
Copy link

picaye commented Apr 14, 2024

Environment

  • Smapp version: 1.4.6
  • Node version: 1.4.6
  • OS: Windows 11

Describe the bug

Had to reinstall spacemesh. after reinstall it does not load my proof of space files located at d:\smeshing - and node reports repea
app-log.1.4.6.txt
spacemesh-log-7c8cef2b.txt
tedly crashes

Steps to reproduce

start spacemesh. crashes.

Expected behavior

should start smeshing

Logs

@fasmat
Copy link
Member

fasmat commented Apr 14, 2024

The node was started with C:\Users\pino\post\7c8cef2b as post directory. Since this PoST directory did not contain any key.bin file a new identity was initialized for your node in C:\Users\pino\AppData\Roaming\Spacemesh\node-data\7c8cef2b\identities\local.key.

You ran with this configuration from 2024-04-12 ~ 02:40 until ~ 11:45 and then changed your configuration to use d:\smeshing as your PoST data directory which also contained a key (d:\smeshing\key.bin). Now your node is confused about which of those keys it is supposed to use.

Be careful not to mix keys and PoST data directories or your node will not be able to properly participate in the network.

To fix your issue, stop your node and open your C:\Users\pino\AppData\Roaming\Spacemesh\node-data\7c8cef2b\identities directory. Rename local.key (to e.g. local.key.bak). Copy d:\smeshing\key.bin to the identities directory and name it local.key and in the d:\smeshing directory rename it to key.bin.bak. That should allow your node to start again.

I'd recommend to keep the backup of your keys, but you can delete the *.bak files if everything works as expected.

@brusherru
Copy link
Member

@picaye did it solve the problem?

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

No branches or pull requests

3 participants