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
When I then try to run the chain I always get the same error:
panic: Could not lock exclusive.lock. Is a different VM running in the same directory already?
goroutine 1 [running]:
github.com/CosmWasm/wasmd/x/wasm/keeper.NewKeeper({_, _}, {_, _}, {_, _}, {_, _}, {0x0, 0x0}, ...)
/Users/name/go/pkg/mod/github.com/!cosm!wasm/[email protected]/x/wasm/keeper/keeper_cgo.go:86 +0x1012
github.com/cosmos/interchain-security/v5/app/consumer.New({0x1130cd950, 0xc001b7cb60}, {0x11317fa00, 0xc0018cc048}, {0x0, 0x0}, 0x1, {0x113086620, 0xc0015fb6c0}, {0xc00191c460, ...})
...
Ive created a completely new directory where I am sure that no other VM is running but still I keep getting the same error...
Am I missing something in the configuration?
The text was updated successfully, but these errors were encountered:
I am not too familiar with integrating wasmd or the interchain-security repo, but the error you are getting results from this check.
The file is located in the wasm specific subfolder of the node's home directory. For example for wasmd that is ~/.wasmd/wasm/wasm/exclusive.lock. The check is to ensure that no two nodes with CosmWasm are running at the same time, trying to read and write modules to the folder.
Maybe try deleting the file?
Hi,
Im using a clone of the interchain-security repo (https://github.com/cosmos/interchain-security) and try to incorporate the CosmWasm module.
Ive done the following:
installed the package:
go get go get github.com/CosmWasm/[email protected]
Imported the packages into
app.go
:New
method I added the Store Key:NewManager
method:When I then try to run the chain I always get the same error:
Ive created a completely new directory where I am sure that no other VM is running but still I keep getting the same error...
Am I missing something in the configuration?
The text was updated successfully, but these errors were encountered: