Error Codes

Here is an overview of the most common error codes and possible fixes.

E0001 Out of Order Share detection

Meessage

The block with height <i> found share <x> which is < than <y> of block <j> | Sometimes stratum inserts

Example

2013-10-24 9:03:43 - FATAL --> E0001: The block with height 107643 found share 18 which is < than 19 of block 107642

Explanation

The findblocks cron has found a block which has a share ID lower than a previous block found. This can happen with fast block finding coins.

Fix

This is not a fatal error yet. findblocks will try to autofix the issue by changing the shares. It will re-order the shares so a following run should not fail.

E0002 Upstream shares not found

Meessage

E0002: Failed to fetch both offending shares: <x> and <y>. . Block height: <n>

Explanation

findblocks was not able to fetch both shares that are causing the Out of Order problem. Sometimes, if blocks have been accounted for already, shares can't be fetched because they were deleted.

Fix

Since we already accounted for a block you will need to manually assign a share to this found block <n>. Some things to keep in mind:

• Do not use a valid upstream_result share
• Do not include a valid upstream_result share in that round
• Use more than just a few shares if possible to make it a round
• Add valid block finder ID for block <n>
• Add valid total shares for block <n>

E0003 Failed share update

Meessage

E0003: Failed to change shares order!

Explanation

findblocks tried to fix the shares order by updating both shares. This failed for some reason.

Fix

None

E0004 Failed to reset block

Meessage

Failed to reset block in database: <n>

Explanation

findblocks successfully changed the out of order shares but failed to update the shares, share_id and account_id information in the block <n>.

Fix

You can manually reset that block and try again.

E0005 Unable to fetch blocks upstream share

Meessage

E0005: Unable to fetch blocks upstream share, aborted: <error>

Explanation

None of the available shares were matched for this block. This should never happen due to the fallbacks implemented to match a block against a share. If you do have an issue, try assigning your own shares (see E0002).