Problem Syncing

[bitcoincapitalcorp]

I'm running Ubuntu 18.04.1 LTS

I moved computers and am trying to sync to a custom data directory. I installed and everything ran fine for an hour while syncing then it threw

N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_9gregorian8bad_yearEEEEE 
year is out of valid range: 1400..10000
bitcoin in AppInit()

I'm just wondering what i can do to clear this.

[achamely]

@bitcoincapitalcorp
The issue is due to the version of boost shipped by Ubuntu 18 which causes this issue.
If possible, try downgrading to boost 1.58 (though you may need to jump through hoops and compile it yourself).
The other option which is known to have worked for others is to switch back to Ubuntu 16.04 in the interim

[dexX7]

Hi @bitcoincapitalcorp, can you please clarify which version you are running?

[myishuohuo]

You need to rebuild the database using -reindex-chainstate to change -txindex.

[myishuohuo]

You need to rebuild the database using -reindex-chainstate to change -txindex.
Please restart with -reindex or -reindex-chainstate to recover. This problem occurred after I downloaded the entire packet

[bitcoincapitalcorp]

Thanks for the help! I am going to try what myishuohuo said first if that doesn't work i'll downgrade to 16.04 i'll report back. thanks.

[zhanghuahua0708]

You need to rebuild the database using -reindex-chainstate to change -txindex.

how to do it? I have the same problem.

[zhanghuahua0708]

You need to rebuild the database using -reindex-chainstate to change -txindex.

how to do it? I have the same problem.

I get it ,use "omnicored -reindex"

[zhanghuahua0708]

You need to rebuild the database using -reindex-chainstate to change -txindex.

how to do it? I have the same problem.

I get it ,use "omnicored -reindex"

It dosen't work, I reinstalled new OS

[dgpv]

the workaround is to set msc_debug_packets to 0 in

omnicore/src/omnicore/log.cpp

Line 55 in c0738a9

bool msc_debug_packets = 1;

(Edit: this workaround is not enough. It would prevent this particular exception, but there will be others. The fix is in #874)

but the problem is deeper, as described in #872

@dexX7 the problem is present in develop branch.