Replies: 6 comments 3 replies
-
Which keyring backend have you used? |
Beta Was this translation helpful? Give feedback.
-
Hey @eswenson1, it would be helpful to look-in if you can give the list of commands that you ran from the beginning and also the complete error log. |
Beta Was this translation helpful? Give feedback.
-
I followed (exactly) the metrications here: https://tutorials.cosmos.network/tutorials/3-run-node/ All the steps in the first console window, up until and including when I started the single-node server worked just fine. And this meant that the key ring was fine and contained the two keys associated with the transfer of stake. Once I started the server, the steps in this tutorial required a new console window. In it, I was unable to execute (successfully) the first command:
The command was unable to find the b9lab key that had successfully been added before starting As for full logs, where would I find them? (All of this was done on macOS). |
Beta Was this translation helpful? Give feedback.
-
Here is the output of the version command:
I'm wondering if this isn't some issue with the OS keyring (macOS). If you haven't seen this problem on Linux, it might be a Mac keyring issue. |
Beta Was this translation helpful? Give feedback.
-
This is very interesting. It "started working" -- but let me explain what I did. First of all, I let my machine sit for a few days without touching simapp. Before I stopped playing with simapp last week, I aborted the running simd server, since it was just spewing out log messages over and over (this might be another issue). This morning, after I saw your request for version info, I did the following: I restarted the simd server in the original console window. I got a macOS prompt to allow the app to access the keyring (keychain access must have timed out). I provided my macOS password and selected "Always Allow". The server started up and macOS asked me if I wanted to allow inbound connections to the server -- I said yes. Then I went to the "other" console window, where the tutorial had had me issue the Why it didn't work last week is a mystery to me -- since I didn't "do" anything differently this time other than to allow time to pass and to restart the simd server. |
Beta Was this translation helpful? Give feedback.
-
Great that you have found the issue! |
Beta Was this translation helpful? Give feedback.
-
I’m a complete noob here. I installed the cosmos sdk and then tried to follow the tutorial using the .simapp sample app. I got to the point in the tutorial where I started up the single-node blockchain. That seemed to work fine. I created another console window and attempted the next step in the tutorial which is to query the bank balance for the b9lab account. When I did, I got the error message that b9lab is not a valid name or address: decoding bech32 failed: invalid bech32 string length 5. I did a ./simd key list and see that there are no keys. I then went back to the window where the single node blockchain was running and aborted (^C) and tried the same command there, and I got the same error.
So what gives? Everything was going perfectly well until I created a new console window. Now, nothing seems to work any more. I see that the genesis.json does show all the state that it should – I simply don’t have any keys accessible now.
Beta Was this translation helpful? Give feedback.
All reactions