Buy crypto anonymously on the Incognito pDEX   

Does websocket work?

#21

I have this same issue. I followed method 2, but i get the same errors when sending the curl command to check beacon status. I have no idea what I am doing wrong.

Log from today shows a lot of errors that I don’t understand…
…
…
…
…

2020-12-10 00:00:00.265 shardprocess.go:173 [INF] BlockChain log: SHARD 4 | Update NumOfBlocksByProducers, block height 112222 with hash fc1f162e9cb618afaa3f2e43cf77aaf20694b6f1e4c1797049f16dce5ea7baae

2020-12-10 00:00:00.265 shardprocess.go:185 [INF] BlockChain log: SHARD 4 | SKIP Verify Post Processing, block height 112222 with hash fc1f162e9cb618afaa3f2e43cf77aaf20694b6f1e4c1797049f16dce5ea7baae

2020-12-10 00:00:00.265 shardprocess.go:188 [INF] BlockChain log: SHARD 4 | Update Beacon Instruction, block height 112222 with hash fc1f162e9cb618afaa3f2e43cf77aaf20694b6f1e4c1797049f16dce5ea7baae

2020-12-10 00:00:00.265 shardprocess.go:193 [INF] BlockChain log: SHARD 4 | Store New Shard Block And Update Data, block height 112222 with hash fc1f162e9cb618afaa3f2e43cf77aaf20694b6f1e4c1797049f16dce5ea7baae

2020-12-10 00:00:00.265 shardprocess.go:1013 [INF] BlockChain log: SHARD 4 | Process store block height 112222 at hash fc1f162e9cb618afaa3f2e43cf77aaf20694b6f1e4c1797049f16dce5ea7baae
2020-12-10 00:00:00.265 shardprocess.go:1015 [CRT] BlockChain log: processStoreShardBlock/CrossTransactions map[2:[{111772 5a8c490bc2ac4419d44cee7a3b557167b89fdd0fc669e378f10ece94c99d6586 [{[{0xc00987adc0 0xc0055251a0}] ffd8d42dc40a8d166ea4848baf8b5f6e912ad79875f4373070b59392b1756c8f Ethereum pETH 2 false 0}] []}]]
2020-12-10 00:00:00.266 accessor_transaction.go:573 [CRT] BlockChain log: Fetch Cross transaction map[2:[{111772 5a8c490bc2ac4419d44cee7a3b557167b89fdd0fc669e378f10ece94c99d6586 [{[{0xc00987adc0 0xc0055251a0}] ffd8d42dc40a8d166ea4848baf8b5f6e912ad79875f4373070b59392b1756c8f Ethereum pETH 2 false 0}] []}]]
2020-12-10 00:00:00.267 estimatefee.go:220 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 112222; new height is 112222, shardID 4
2020-12-10 00:00:00.267 shardchain.go:209 [ERR] BlockChain log: -1067: Store Shard Block Error
leveldb/table: corruption on data-block (pos=212536): checksum mismatch, want=0x74ac36c5 got=0x67b407aa [file=030715.ldb]
Store Shard Block Error
github.com/incognitochain/incognito-chain/blockchain.NewBlockChainError
/Users/autonomous/projects/incognito-chain/blockchain/error.go:363
github.com/incognitochain/incognito-chain/blockchain.(*BlockChain).processStoreShardBlock
/Users/autonomous/projects/incognito-chain/blockchain/shardprocess.go:1112
github.com/incognitochain/incognito-chain/blockchain.(*BlockChain).InsertShardBlock
/Users/autonomous/projects/incognito-chain/blockchain/shardprocess.go:195
github.com/incognitochain/incognito-chain/blockchain.(*ShardChain).InsertBlk
/Users/autonomous/projects/incognito-chain/blockchain/shardchain.go:207
github.com/incognitochain/incognito-chain/syncker.InsertBatchBlock
/Users/autonomous/projects/incognito-chain/syncker/utils.go:51
github.com/incognitochain/incognito-chain/syncker.(*ShardSyncProcess).streamFromPeer
/Users/autonomous/projects/incognito-chain/syncker/shardsyncprocess.go:256
github.com/incognitochain/incognito-chain/syncker.(*ShardSyncProcess).syncShardProcess
/Users/autonomous/projects/incognito-chain/syncker/shardsyncprocess.go:183
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357
2020-12-10 00:00:00.308 utils.go:55 [ERR] Syncker log : Insert block 112222 hash [174 186 167 94 206 109 241 73 112 121 193 228 241 182 148 6 242 170 119 207 67 46 63 170 175 24 182 156 46 22 31 252] got error -1067: Store Shard Block Error
leveldb/table: corruption on data-block (pos=212536): checksum mismatch, want=0x74ac36c5 got=0x67b407aa [file=030715.ldb]
Store Shard Block Error
/fullnode/data_fullnode/-2020-12-10.log

#22

Anyone have any ideas on this?

I’m stuck in the water on my full node…

#23

Hey @brico84,

I’m a little bit sick. So I was away from my PC. Sorry for the late response.

Method2 does not work. You should follow method1. Note that there are two disadvantages of method1:

1- Since method1 does not use docker, it won’t benefit from Docker’s restart-always feature. A validator/full node sometimes may crash. That feature restarts the node in such cases, so the users usually do not notice these crashes. You should find a way to restart the node software in such cases.

2- Unlike method2 does, method1 does not update the node software when a new version is released. For the new releases of the fullnode, you should track Github repository of Incognito Chain.