Title: PROCESSMESSAGE MESSAGESTART NOT FOUND Post by: kingcoin on March 13, 2013, 08:56:34 AM I'm a Linux user and I've recently installed bitcoind/bitcoin-qt (version v0.6.3.0-g6e0c5e3-beta) and built cpuminer (minerd version 1.0.2) but I can't get them to work together.
I start bitcoind: Code: bitcoind -datadir=mydatadir -conf=mybitcoin.conf -printtoconsole Code: curl --user myrpcuser --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/ Code: {"result":{"version":60300,"protocolversion":60001,"walletversion":60000... Then I start the miner: Code: ./minerd --userpass myrpcuser:myrpcpass -P --url http://localhost:8333 Code: ... In the bitcoind session I can observe the following output: Code: accepted connection 127.0.0.1:51079 Any clues as how I can resolve this? Title: Re: PROCESSMESSAGE MESSAGESTART NOT FOUND Post by: kingcoin on March 13, 2013, 01:21:04 PM I compiled the bitcoind program from the latest git source (1a9ee) to make sure I had the latest versjon of both bitcoind and mined. When I run the json query I get a much more recent protocol version:
Code: curl --user myrpcuser --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/ But it also says that my balance is zero? What happened to my bitcoins? I guess these are not typical newbie questions, so hopefully I'll get access to post somewhere else soon. Title: Re: PROCESSMESSAGE MESSAGESTART NOT FOUND Post by: kingcoin on March 13, 2013, 01:40:48 PM The minerd result is the same using the git version of bitcoind
Code: * Empty reply from server But I'm worried about the zero balance. Should I start the old version of bitcoind or will that skrew things up even more? Title: Re: PROCESSMESSAGE MESSAGESTART NOT FOUND Post by: kingcoin on March 13, 2013, 01:57:51 PM I tried the version tagged v0.7.2 (32a928e). Here I can at least observe that my balance is not zero.
But the minerd behavior is the same. Title: Re: PROCESSMESSAGE MESSAGESTART NOT FOUND Post by: kingcoin on March 13, 2013, 02:23:00 PM This seem to be caused by a very stupid mistake. I used the wrong port number in the minderd test. Changing it from 8333 to 8332 caused lots of json messages passed back and forth and my load to get close to 8
Hopefully others will get a hit on my message thread on Google if they make the same silly mistake. |