wasmcli does not works.

[westaking]

Summary of Bug

I can't generate a key with the wasmcli command.

Version

os : centos 7
git commit hash: ec7f996

$ wasmd version --long
name: wasm
server_name: wasmd
client_name: wasmcli
version: ""
commit: ec7f996
build_tags: netgo,ledger
go: go version go1.13.6 linux/amd64

Steps to Reproduce

$ wasmcli keys add validator

following this error:

panic: No such interface 'org.freedesktop.DBus.Properties' on object at path /

goroutine 1 [running]:
github.com/cosmos/cosmos-sdk/crypto/keys.keyringKeybase.writeInfo(0x13b2560, 0xc0003522a0, 0x7ffdbe8ea89d, 0x1, 0x13b25e0, 0xc00035a810)
        /home/user777/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.34.4-0.20191114141721-d4c831e63ad3/crypto/keys/keyring.go:444 +0x38c
github.com/cosmos/cosmos-sdk/crypto/keys.keyringKeybase.writeLocalKey(0x13b2560, 0xc0003522a0, 0x7ffdbe8ea89d, 0x1, 0x13b0860, 0xc000b38480, 0x105d674, 0x8, 0xc000b38480, 0xf73380)
        /home/user777/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.34.4-0.20191114141721-d4c831e63ad3/crypto/keys/keyring.go:430 +0x132
github.com/cosmos/cosmos-sdk/crypto/keys.baseKeybase.persistDerivedKey(0x13a2e20, 0xc000162b50, 0xc00035e380, 0x40, 0x40, 0x105d674, 0x8, 0x7ffdbe8ea89d, 0x1, 0xc000c07a90, ...)
        /home/user777/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.34.4-0.20191114141721-d4c831e63ad3/crypto/keys/keybase_base.go:104 +0x155
github.com/cosmos/cosmos-sdk/crypto/keys.baseKeybase.Derive(0x13a2e20, 0xc000162b50, 0x7ffdbe8ea89d, 0x1, 0xc000368140, 0x91, 0x0, 0x0, 0x105d674, 0x8, ...)
        /home/user777/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.34.4-0.20191114141721-d4c831e63ad3/crypto/keys/keybase_base.go:178 +0x16d
github.com/cosmos/cosmos-sdk/crypto/keys.baseKeybase.CreateAccount(0x13a2e20, 0xc000162b50, 0x7ffdbe8ea89d, 0x1, 0xc000368140, 0x91, 0x0, 0x0, 0x105d674, 0x8, ...)
        /home/user777/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.34.4-0.20191114141721-d4c831e63ad3/crypto/keys/keybase_base.go:88 +0x127
github.com/cosmos/cosmos-sdk/crypto/keys.keyringKeybase.CreateAccount(...)
        /home/user777/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.34.4-0.20191114141721-d4c831e63ad3/crypto/keys/keyring.go:78
github.com/cosmos/cosmos-sdk/client/keys.runAddCmd(0xc000334280, 0xc00050eff0, 0x1, 0x1, 0x0, 0x0)
        /home/user777/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.34.4-0.20191114141721-d4c831e63ad3/client/keys/add.go:234 +0x91b
github.com/spf13/cobra.(*Command).execute(0xc000334280, 0xc00050efc0, 0x1, 0x1, 0xc000334280, 0xc00050efc0)
        /home/user777/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826 +0x460
github.com/spf13/cobra.(*Command).ExecuteC(0xc000528500, 0xb9ee40, 0xc000528500, 0x1058d6c)
        /home/user777/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914 +0x2fb
github.com/spf13/cobra.(*Command).Execute(...)
        /home/user777/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
github.com/tendermint/tendermint/libs/cli.Executor.Execute(0xc000528500, 0x12549d0, 0x2, 0xc000b0d740)
        /home/user777/go/pkg/mod/github.com/tendermint/tendermint@v0.32.7/libs/cli/setup.go:89 +0x3c
main.main()
        /home/user777/wasmd/cmd/wasmcli/main.go:77 +0x5d5

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[ethanfrey]

This code is straight from https://github.com/cosmos/cosmos-sdk.

Please file a bug with them about CentOS7 support. You can tag @alessio who probably knows more about the keyring keybase than anyone else on that team.

[ethanfrey]

Assigned "won't fix" as I cannot do anything until upstream support is added. Then I will just update the dependencies (so not closing it - please add a comment if anything changes)

[westaking]

In centos7, other platforms based on tendermint can generate keys without problems. However, wasmcli occurs an error on generating the key.

[ethanfrey]

Tendermint works fine, as does wasmd aparently. The issue is the cosmos-sdk client-side library., which as of the recent master no longer uses a file system storage, but rather os-specific keyring. See cosmos/gaia#164 and cosmos/cosmos-sdk#5180 neither of which is in the 0.37 branch

To isolate the problem, can you please check out the current master branch of https://github.com/cosmos/gaia and make install. Then try the gaiacli keys add validator command (and all the other keys subcommands). If there is a bug, please log it on gaia and cosmos-sdk. If this works perfectly, I can look at it.

I am running on a very recent master, looking to tag to unreleased 0.38. This is much newer than most projects... recent cosmos hub upgrade was to 0.36. Some of the more adventurous projects are on 0.37.5 or so. I don't think anyone is running a net on master... I am waiting for the tagged release to do so as well.

[westaking]

yep, it does not work in the gaia master branch as well. (cosmos-sdk v0.34.4)

[ethanfrey]

cosmos-sdk v0.34.4 that is totally misleading tag (and has confused me many times). It is followed by a git commit, which you can search in cosmos-sdk for.

Can you please raise an issue on gaia and/or cosmos-sdk and link to this? Thank you

[westaking]

If I build directly with cosmos-sdk v0.34.4, generating key with cli works fine.
I'm confused too.

[ethanfrey]

This is due to confusing tagging in cosmos.

If you look at the gaia go.mod, we see:

github.com/cosmos/cosmos-sdk v0.34.4-0.20200110211037-214024431fbd

This is commit 214024431fbd from Jan 10, 2020, which is quite a bit newer than cosmos-sdk v0.34.4

You can also ask them to tag release on master, which would make the go.mod files more understandable. They had some reasoning for the current system to make internal processes better, but it does make it harder to external development.

[ethanfrey]

Okay, I checked in with @alessio and there is a more recent PR that adds support for a file backend, which should work on more systems (like CentOS7 or Docker). cosmos/cosmos-sdk#5355

It was merged Dec 11, which is newer than the version of cosmos-sdk we are using now. When we update to the current master #15 this flag will be enabled, and we can try it out. Hopefully that will resolve the problem.

(#15 is high priority for the release I plan later this week)

[westaking]

It seems that keyring does not support headless server.

So I saw the following article and solved it.

https://ahelpme.com/linux/dbusexception-could-not-get-owner-of-name-org-freedesktop-secrets-no-such-name/

I got a hint from https://askubuntu.com/a/912250

On centos 7,
The keyring used by cosmos-sdk internally activates the gnome-keyring-daemon process.
When the wasmcli keys command is executed for the first time, an error occurs, but from the second run it works fine. However, the keyring console prompt appears TOO SLOW. It takes about 2 minutes.

You can reduce the time by making the following modifications.

$ sudo nano /usr/share/dbus-1/session.conf

# 120000 -> 1000
# <limit name = "service_start_timeout"> 120000 </ limit>
<limit name = "service_start_timeout"> 1000 </ limit>

[ethanfrey]

I'm glad it worked.
Do you want to make a PR adding that link and a little text to the README?

I'd be glad to have your contribution.

[westaking]

updated README.md #40

[ethanfrey]

Closed by #40