"Cannot start mining without coinbase: no keys in store" error message from Go CLI client

acrosacros Member Posts: 63 ✭✭
I get this error message:

# ethereum -mine
Welcome to the FRONTIER
2015/03/12 23:09:08 Making Cache
2015/03/12 23:09:08 [CHAIN] Last block (#0) b5d6d8402156c5c1dfadaa4b87c676b5bcadb17ef9bc8e939606daaa0d35f55d TD=0
2015/03/12 23:09:08 Took: 74.715784ms
2015/03/12 23:09:08 [CLI] Starting Ethereum(G)/v0.9.0/linux/go1.4.2
2015/03/12 23:09:08 [P2P Server] Starting Server
2015/03/12 23:09:10 [P2P Discovery] Listening, enode://5a619e04ea52b6b584d8d016da28654da0a1b8297aa94059914d942e048033d57[email protected][::]:30303
2015/03/12 23:09:10 [Blockpool] Started
2015/03/12 23:09:10 [P2P NAT] mapping error: no devices discovered
2015/03/12 23:09:10 [P2P Server] Listening on [::]:30303
2015/03/12 23:09:10 [SHH] Whisper started
2015/03/12 23:09:10 [P2P NAT] mapping error: no devices discovered
2015/03/12 23:09:10 [SERV] Server started
2015/03/12 23:09:10 [SERV] Cannot start mining without coinbase: no keys in store

How does one go about generating keys with the go client?

I found this: https://github.com/ethereum/cpp-ethereum/wiki/Using-AlethZero, but it was for AlethZero ("create addresses")

Thanks!

Comments

  • drcodedrcode Member Posts: 62 ✭✭
    edited March 2015
    I'd like to know the answer to this, as well... FYI, you can get past this step by using an option in the Mist menus to generate a key, but then I'm just stuck with the message "could not unlock sender account"
  • acrosacros Member Posts: 63 ✭✭
    unfortunately I'm on a headless server, so no Mist/AlethZero for me at this point :(
  • drcodedrcode Member Posts: 62 ✭✭
    Hi @acros, this was answered in the other thread-
    1. run "ethereum accounts new"...
    2. run something like "ethereum --unlock=55e718902a0c1529047f49093acbcbb1ced51a66:passwordfoo"

    I'm still getting a js error of "could not unlock sender account" though...
  • larzlarz Sussex, EnglandMember Posts: 17
    Hi @drcode, @acros,

    I've got the same issue. I created a new account (btw. The syntax is 'ethereum account new', not accounts) and ran ethereum with --unlock=key:password.

    This is the output;

    2015/03/14 13:24:10 [CHAIN] Last block (#0) 585cc2ac13f8dfa38fc8bc48b23dbf578623b8a193afe006b14959f92a2dea56 TD=0
    2015/03/14 13:24:10 Making Cache
    2015/03/14 13:24:10 Took: 181.542089ms
    2015/03/14 13:24:10 [CLI] Starting Ethereum(G)/v0.9.0/linux/go1.2.1
    2015/03/14 13:24:10 [P2P Server] Starting Server
    2015/03/14 13:24:12 ssdp: got unexpected search target result "upnp:rootdevice"
    2015/03/14 13:24:12 ssdp: got unexpected search target result "uuid:2f402f80-da50-11e1-9b23-00178812b5a1"
    2015/03/14 13:24:12 ssdp: got unexpected search target result "urn:schemas-upnp-org:device:basic:1"
    2015/03/14 13:24:12 ssdp: got unexpected search target result "upnp:rootdevice"
    2015/03/14 13:24:12 ssdp: got unexpected search target result "uuid:2f402f80-da50-11e1-9b23-00178812b5a1"
    2015/03/14 13:24:12 ssdp: got unexpected search target result "urn:schemas-upnp-org:device:basic:1"
    2015/03/14 13:24:12 [P2P NAT] mapping error: no devices discovered
    2015/03/14 13:24:12 [P2P Discovery] Listening, enode://a0229b1b1739f082767303ed2e847f0de469d443416d1e5f3b325024067e87816[email protected]2.103.220.31:30303
    2015/03/14 13:24:12 [P2P Server] Listening on [::]:30303
    2015/03/14 13:24:12 [Blockpool] Started
    2015/03/14 13:24:12 [SHH] Whisper started
    Fatal: Unlock account failed 'read /home//.ethereum/keys: is a directory'
    2015/03/14 13:24:12 [SERV] Server started


    Why am I getting these 'unexpected search target result' warnings and why does the key seem to point at a directory rather than a key file (penultimate line)?
    Surely I'm missing something, but what!

    Thanks a lot for any help!
  • larzlarz Sussex, EnglandMember Posts: 17
    ... and when I start ethereum with --mine, I get an out of memory error (Ubuntu 14.04 on a Core i7 with 16GB RAM):

    $ ethereum --mine

    Welcome to the FRONTIER
    2015/03/14 14:32:57 [CHAIN] Last block (#0) 585cc2ac13f8dfa38fc8bc48b23dbf578623b8a193afe006b14959f92a2dea56 TD=0
    2015/03/14 14:32:57 Making Cache
    2015/03/14 14:32:57 Took: 183.833517ms
    2015/03/14 14:32:57 [CLI] Starting Ethereum(G)/v0.9.0/linux/go1.2.1
    2015/03/14 14:32:57 [P2P Server] Starting Server
    2015/03/14 14:32:59 ssdp: got unexpected search target result "upnp:rootdevice"
    2015/03/14 14:32:59 ssdp: got unexpected search target result "uuid:2f402f80-da50-11e1-9b23-00178812b5a1"
    2015/03/14 14:32:59 ssdp: got unexpected search target result "urn:schemas-upnp-org:device:basic:1"
    2015/03/14 14:32:59 ssdp: got unexpected search target result "upnp:rootdevice"
    2015/03/14 14:32:59 ssdp: got unexpected search target result "uuid:2f402f80-da50-11e1-9b23-00178812b5a1"
    2015/03/14 14:32:59 ssdp: got unexpected search target result "urn:schemas-upnp-org:device:basic:1"
    2015/03/14 14:32:59 [P2P NAT] mapping error: no devices discovered
    2015/03/14 14:32:59 [P2P Discovery] Listening, enode://a0229b1b1739f082767303ed2e847f0de469d443416d1e5f3b325024067e87816[email protected]2.103.220.31:30303
    2015/03/14 14:32:59 [P2P Server] Listening on [::]:30303
    2015/03/14 14:32:59 [Blockpool] Started
    2015/03/14 14:32:59 [SHH] Whisper started
    2015/03/14 14:32:59 [SERV] Server started
    2015/03/14 14:32:59 Generating dag
    2015/03/14 14:32:59 No dag found in '/tmp/dag'. Generating new dago(takes a while)...
    runtime: out of memory: cannot allocate 1073741824-byte block (36700160 in use)
    fatal error: out of memory
  • drcodedrcode Member Posts: 62 ✭✭
    Hi @larz ... did you remove the "0x" from the account number when passing through the CLI? That might resolve the specific problem you're seeing (I'm stuck a step after that one...)
  • larzlarz Sussex, EnglandMember Posts: 17
    thanks @drcode, I just tried that, but get the fame error message

    Fatal: Unlock account failed 'read /home/MY_USERNAME/.ethereum/keys: is a directory'

    So you're getting one step further but end up with a "could not unlock sender account" error?
  • drcodedrcode Member Posts: 62 ✭✭
    Yes exactly @lars, my go-ethereum seems to be 100% unlocked but then I still get that error from the javascript rpc. I'm going to give up for now and focus on UI stuff and then try again in a week or two.
  • larzlarz Sussex, EnglandMember Posts: 17
    @drcode I've decided to start from scratch with a fresh Ububtu 14.04 and installs ethereum from PPA. And lo and behold, it seems to work. Created a new account (is that actually necessary or would ethereum create a coinbase upon fest start anyway?) and called ethereum --mine. It seems like it happily mines away in the testnet - interestingly enough at a much higher has rate than the cpp implementation on the same machine (?)
  • acrosacros Member Posts: 63 ✭✭
    Hi @drcode and @larz, thanks a lot for the input!

    Thanks to your comments, I also got past the error :)

    I stuck with command-line though, but in a nutshell what solved it for me was:

    $ ethereum account new # without 's' indeed
    $ ethereum --unlock=0b16XXXXXXX:mypassphrase-from-the-first-command
    $ ethereum --mine

    It seems to mine fine (though only at ~88Khash). I still get "[P2P NAT] mapping error: no devices discovered", I'm not sure if that's something to be worried about.

    PS: note that I checked out commit 0b8f66e (somewhat arbitrarily) from the GO client, as the head on develop was broken (at the time I tried that is)
  • larzlarz Sussex, EnglandMember Posts: 17
    hi @acros,

    I do indeed also get the [P2P NAT] mapping error when I call ethereum with --mine. Hash rate wise I get around 130kHs.
Sign In or Register to comment.