-
Notifications
You must be signed in to change notification settings - Fork 3.8k
could not gain write access to the shared memory file #2142
Comments
Last login: Thu Apr 5 23:51:10 on ttys001 |
Yep, getting the same error here after a clean build of 3.0. |
I get exactly the same error. I think it has to do with this already given problem a while back (#58). Question here is how rerun the first writer in order to start producing blocks again. ( I guess a simple solution is to delete all EOS files now and re-install the whole thing). However I think thats far from the optimal solution. |
I am having the same issue, its after I killed nodeos after its first run, permissions are correct on the file so I don't understand, has anyone fixed this? It seems from the linked previous issue that I am trying to start the same node twice, so how do I fix this? Also some basic questions, where is the blockchain file stored? thanks |
Make sure you're not running another
If so, kill the previous one. |
thanks kenord i was using Is there an internal command to stop nodeos? |
There is no internal command to stop nodeos. That's properly the domain of your operating system. If you configure nodeos as a systemd service, you would use systemd start and stop commands. If you configure nodeos as a FreeBSD rc.d service, you would use FreeBSD start and stop commands. Process management is not a feature of EOS.IO.
|
how to config?
how to fix?
The text was updated successfully, but these errors were encountered: