pool 0 is issuing work for an old block problem with gridseed blade.

Encounter a problem related to the pool or have a request for a feature? Post your issue here and we will help you out.
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.

Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.

We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Locked
thebobinater
Posts: 4
Joined: Fri Mar 04, 2016 10:50 am

pool 0 is issuing work for an old block problem with gridseed blade.

Post by thebobinater » Tue Apr 05, 2016 2:19 pm

hi, i have 1 gridseed blade and two zeus blizzards connected. The gridseeds use their own instance of bfgminer, as do the two blizzards. the blizzards are hashing away just fine, however, my gridseed bfgminer keeps saying "pool 0 is issuing work for an old block" and then lists the block #. But it does connect and have the normal hashrate that it should have. The version of bfg that I am using for the blade is 3.10.0. is there anything wrong?
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: pool 0 is issuing work for an old block problem with gridseed blade.

Post by Steve Sokolowski » Wed Apr 06, 2016 12:17 pm

I think we've seen this error before with bfgminer, and I seem to recall that the solution was simply to ignore the error. The reason is that we are switching networks from a coin that has more blocks to one that has fewer blocks. bfgminer assumes that we are always mining the same network and believes that we are mining a previous block on the same network, which doesn't make sense to do.

I'll ask Chris to investigate this to confirm, but unless we tell you otherwise, just ignore the error. Profitability is unaffected.
thebobinater
Posts: 4
Joined: Fri Mar 04, 2016 10:50 am

Re: pool 0 is issuing work for an old block problem with gridseed blade.

Post by thebobinater » Wed Apr 06, 2016 1:14 pm

ok thanks. good to know.
Locked