Sync fails and Omnicore shutdown with Exception(Tag v0.3.1-alpine)
Trying to sync the omnicore, but it fails with an exception:
2018-10-30 14:30:07 getAcceptAmountRemaining(); buyer still wants = 1000 2018-10-30 14:30:07 getAcceptAmountRemaining(); buyer still wants = 942000 2018-10-30 14:30:07 VerifyCheckpoint(): consensus hash mismatch - expected 1a1923a644bee373649e01a0a825daae8d0b862a3488e7f5b092599862169fb7, received 2bafb80a3fcea97a5e4bdfd511e233ce4d7d7d0cc12f8aaa95cff4d09069ef67 2018-10-30 14:30:07 Shutting down due to failed checkpoint for block 310000 (hash 0000000000000000125a28cc9e9209ddb75718f599a8039f6c9e7d9f1fb021e0). Please restart with -startclean flag and if this doesn't work, please reach out to the support. 2018-10-30 14:30:07 *** Shutting down due to failed checkpoint for block 310000 (hash 0000000000000000125a28cc9e9209ddb75718f599a8039f6c9e7d9f1fb021e0). Please restart with -startclean flag and if this doesn't work, please reach out to the support.
2018-10-30 14:30:07 Error: Shutting down due to failed checkpoint for block 310000 (hash 0000000000000000125a28cc9e9209ddb75718f599a8039f6c9e7d9f1fb021e0). Please restart with -startclean flag and if this doesn't work, please reach out to the support.
Error: Shutting down due to failed checkpoint for block 310000 (hash 0000000000000000125a28cc9e9209ddb75718f599a8039f6c9e7d9f1fb021e0). Please restart with -startclean flag and if this doesn't work, please reach out to the support.
2018-10-30 14:30:07 tor: Thread interrupt 2018-10-30 14:30:07 torcontrol thread exit 2018-10-30 14:30:07 scheduler thread interrupt 2018-10-30 14:30:07 addcon thread interrupt 2018-10-30 14:30:07 opencon thread interrupt 2018-10-30 14:30:07 net thread interrupt 2018-10-30 14:30:07 msghand thread interrupt 2018-10-30 14:30:07 Shutdown: In progress... 2018-10-30 14:30:07 StopNode() 2018-10-30 14:30:09 COmniFeeCache closed 2018-10-30 14:30:09 COmniFeeHistory closed 2018-10-30 14:30:09 Omni Core shutdown completed 2018-10-30 14:30:09 Shutdown time: 2018-10-30 14:30:09 2018-10-30 14:30:09 Omni Core shutdown completed 2018-10-30 14:30:09 Shutdown: done
I restart it with -startclean flag, it falls with exception:
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_9gregorian8bad_yearEEEEE Year is out of valid range: 1400..10000 bitcoin in AppInit()
2018-10-31 02:21:08
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_9gregorian8bad_yearEEEEE Year is out of valid range: 1400..10000 bitcoin in AppInit()
2018-10-31 02:21:08 Shutdown: In progress... 2018-10-31 02:21:08 scheduler thread interrupt 2018-10-31 02:21:08 StopNode() 2018-10-31 02:21:08 COmniFeeCache closed 2018-10-31 02:21:08 COmniFeeHistory closed 2018-10-31 02:21:08 Omni Core shutdown completed 2018-10-31 02:21:08 Shutdown time: 2018-10-31 02:21:08 2018-10-31 02:21:08 Omni Core shutdown completed
When I got the Tag back to v0.3.0-alpine, and run a new container. This problem has gone.
There must be some problem in v0.3.1-alpine.
@PetersonZhao thanks for report
diff v0.3.0-alpine/Dockerfile v0.3.1-alpine/Dockerfile
1c1
< FROM alpine:3.7
---
> FROM alpine:3.8
3c3
< LABEL maintainer="Maksym Pugach <[email protected]>"
---
> LABEL maintainer="Maksym Pugach <[email protected]>, Daniel Zhou <[email protected]>"
17c17
< git clone -b v0.3.0 https://github.com/OmniLayer/omnicore.git $BITCOIN_REPO && \
---
> git clone -b v0.3.1 https://github.com/OmniLayer/omnicore.git $BITCOIN_REPO && \
here is the difference between those two
so the issue must be in alpine version (can you check it please?) or in omnicore itself
There is a related issue in omnicore https://github.com/OmniLayer/omnicore/issues/731
It can come from the boost version used in alpine 3.8
- alpine 3.7 : boost version is 1.62.0-r5
- alpine 3.8 : boost version is 1.66.0-r0
@PetersonZhao can you give a shoot at using alpine:3.7 to see if the bug trig with a boost version < 1.65 ?
@mpugach @ang-st
I'm working on it, just switch alpine 3.8 to alpine 3.7.
The Omnicore synchronized on height 311226 now, everything is fine.
@PetersonZhao thanks pal
@nerdDan FUI
I'm testing a fresh install of v0.5.0-alpine and still having this issue :( Can you please switch to alpine 3.7, with older boost version?
@profforg sure, PRs are welcome
looks like problem is fixed in v0.7.0