Bitcoin Forum
January 20, 2021, 07:41:42 AM *
News: Latest Bitcoin Core release: 0.21.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: PROCESSMESSAGE MESSAGESTART NOT FOUND  (Read 3263 times)
kingcoin
Sr. Member
****
Offline Offline

Activity: 262
Merit: 250


View Profile
March 13, 2013, 08:56:34 AM
 #1

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
Then I verify that I can communicate with the rpc server:

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/
which responds:
Code:
{"result":{"version":60300,"protocolversion":60001,"walletversion":60000...

Then I start the miner:

Code:
./minerd --userpass myrpcuser:myrpcpass -P --url http://localhost:8333
which outputs:

Code:
...

[2013-03-13 09:50:37] 8 miner threads started, using SHA256 'sse2_64' algorithm.
* Empty reply from server
* Connection #0 to host localhost left intact
[2013-03-13 09:51:30] HTTP request failed: Empty reply from server
[2013-03-13 09:51:30] json_rpc_call failed, retry after 30 seconds

In the bitcoind session I can observe the following output:

Code:
accepted connection 127.0.0.1:51079

PROCESSMESSAGE MESSAGESTART NOT FOUND

Any clues as how I can resolve this?
1611128502
Hero Member
*
Offline Offline

Posts: 1611128502

View Profile Personal Message (Offline)

Ignore
1611128502
Reply with quote  #2

1611128502
Report to moderator
1611128502
Hero Member
*
Offline Offline

Posts: 1611128502

View Profile Personal Message (Offline)

Ignore
1611128502
Reply with quote  #2

1611128502
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1611128502
Hero Member
*
Offline Offline

Posts: 1611128502

View Profile Personal Message (Offline)

Ignore
1611128502
Reply with quote  #2

1611128502
Report to moderator
1611128502
Hero Member
*
Offline Offline

Posts: 1611128502

View Profile Personal Message (Offline)

Ignore
1611128502
Reply with quote  #2

1611128502
Report to moderator
kingcoin
Sr. Member
****
Offline Offline

Activity: 262
Merit: 250


View Profile
March 13, 2013, 01:21:04 PM
 #2

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/
{"result":{"version":80000,"protocolversion":70001,"walletversion":60000,

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.
kingcoin
Sr. Member
****
Offline Offline

Activity: 262
Merit: 250


View Profile
March 13, 2013, 01:40:48 PM
 #3

The minerd result is the same using the git version of bitcoind

Code:
* Empty reply from server
* Connection #0 to host localhost left intact
[2013-03-13 14:38:06] HTTP request failed: Empty reply from server
[2013-03-13 14:38:06] json_rpc_call failed, retry after 30 seconds

But I'm worried about the zero balance.

Should I start the old version of bitcoind or will that skrew things up even more?
kingcoin
Sr. Member
****
Offline Offline

Activity: 262
Merit: 250


View Profile
March 13, 2013, 01:57:51 PM
 #4

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.
kingcoin
Sr. Member
****
Offline Offline

Activity: 262
Merit: 250


View Profile
March 13, 2013, 02:23:00 PM
 #5

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.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!