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
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
The text was updated successfully, but these errors were encountered:
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.
Environment
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
The text was updated successfully, but these errors were encountered: