Bitcoin Forum
December 02, 2022, 10:18:32 PM *
News: Reminder: do not keep your money in online accounts
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: eloipool height flip-flopping  (Read 870 times)
holgerr (OP)
Newbie
*
Offline Offline

Activity: 15
Merit: 0



View Profile
June 07, 2013, 09:42:16 AM
 #1

Hi,

I'm testing an eloipool setup with two bitcoind backends (0.8.eligius branch), one configured with priority 0, one with priority 1. Both bitcoinds appear to be reasonably well connected with other peers. From time to time, I see the following in my logs:

Quote
2013-06-07 05:16:52,179 merkleMaker     ERROR   Upstream 'primary' rejected proposed block from 'secondary': stale-prevblk
2013-06-07 05:16:52,389 merkleMaker     INFO    New block: 00000000000000e4250875295568b720fbf9ab87d885fd2d4a6ea76c24d48a9b (height: 240205; bits: 1a011337)
2013-06-07 05:16:52,391 merkleMaker     WARNING Change from height 240206->240205; no longpoll merkleroots available!
2013-06-07 05:16:52,402 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:16:55,974 merkleMaker     INFO    New block: 000000000000001ae26a52e6724f9608bb98580fd668b413d13451db517d17a6 (height: 240206; bits: 1a011337)
2013-06-07 05:16:55,976 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:16:56,636 merkleMaker     ERROR   Upstream 'primary' rejected proposed block from 'secondary': stale-prevblk
2013-06-07 05:16:56,961 merkleMaker     INFO    New block: 00000000000000e4250875295568b720fbf9ab87d885fd2d4a6ea76c24d48a9b (height: 240205; bits: 1a011337)
2013-06-07 05:16:56,963 merkleMaker     WARNING Change from height 240206->240205; no longpoll merkleroots available!
2013-06-07 05:16:57,002 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:00,766 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:01,081 merkleMaker     INFO    New block: 000000000000001ae26a52e6724f9608bb98580fd668b413d13451db517d17a6 (height: 240206; bits: 1a011337)
2013-06-07 05:17:01,082 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:01,458 merkleMaker     ERROR   Upstream 'primary' rejected proposed block from 'secondary': stale-prevblk
2013-06-07 05:17:01,601 merkleMaker     INFO    New block: 00000000000000e4250875295568b720fbf9ab87d885fd2d4a6ea76c24d48a9b (height: 240205; bits: 1a011337)
2013-06-07 05:17:01,601 merkleMaker     WARNING Change from height 240206->240205; no longpoll merkleroots available!
2013-06-07 05:17:01,632 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:05,780 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:06,129 merkleMaker     INFO    New block: 000000000000001ae26a52e6724f9608bb98580fd668b413d13451db517d17a6 (height: 240206; bits: 1a011337)
2013-06-07 05:17:06,131 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:07,156 merkleMaker     ERROR   Upstream 'primary' rejected proposed block from 'secondary': stale-prevblk
2013-06-07 05:17:07,374 merkleMaker     INFO    New block: 00000000000000e4250875295568b720fbf9ab87d885fd2d4a6ea76c24d48a9b (height: 240205; bits: 1a011337)
2013-06-07 05:17:07,488 merkleMaker     WARNING Change from height 240206->240205; no longpoll merkleroots available!
2013-06-07 05:17:07,496 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:10,798 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:11,272 merkleMaker     INFO    New block: 000000000000001ae26a52e6724f9608bb98580fd668b413d13451db517d17a6 (height: 240206; bits: 1a011337)
2013-06-07 05:17:11,275 JSONRPCServer   INFO    Nobody to longpoll
2013-06-07 05:17:11,882 merkleMaker     ERROR   Upstream 'primary' rejected proposed block from 'secondary': stale-prevblk
2013-06-07 05:17:12,031 merkleMaker     INFO    New block: 00000000000000e4250875295568b720fbf9ab87d885fd2d4a6ea76c24d48a9b (height: 240205; bits: 1a011337)
2013-06-07 05:17:12,034 merkleMaker     WARNING Change from height 240206->240205; no longpoll merkleroots available!

It looks like eloipool is getting conflicting information from the two bitcoinds about which is the current block (for about 30 seconds, until whichever one is slower has found out about the new block). I thought that the priorities should take care of that (and for good measure I also adjusted the weight, but that has made no difference) - has anyone else seen this kind of thing? What I really want is for eloipool to always use the local bitcoind unless that one is down for some reason. Has anyone had the same problem? I'm pretty sure I'm doing something wrong here... but what? Any hints appreciated.

Holger
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!