Troubleshooting method of low lucky value

[dayou5168]

Troubleshooting method of low lucky value

If you find that your lucky value is low in the block browser if your storage power is not higher than 1PB under the current network storage power of 12.76 EB. It is normal for your lucky value to fluctuate. If your lucky value is lower than 100% for a long time, for example, more than a month, you can use the following methods to check. Of course, if everything is normal, you may just have bad luck. Don't worry too much. Our luck is the same.

Don't miss the election

There are 2880 rounds of winning block elections every day. If the Lotus Damon network is unstable, some storage providers may not monitor the network status, so you may not feel it sometimes. You can check whether these rounds are sufficient by filtering the log. You can use the command: cat miner. log | grep < date > | grep 'completed mineone' | wc - l. Actual examples:

cat miner.log | grep 2021-09-29 | grep 'completed mineOne' |wc -l

If you get 2880, it's normal.

Check whether winningpost timed out

The time consumption of winningpost can be viewed through the following log:

storageminer storage/miner.go:295 GenerateWinningPoSt took 1.863073709s

You can filter your storage provider logs:

cat miner.log | grep 'GenerateWinningPoSt took'

If the time is longer than 15 seconds, you should pay attention. You can check the reason why the calculation is too slow. An important reason for wining post timeout is that winning post and windows post calculations conflict. If your winningpost takes more than 10 minutes. Probably because the system is processing windows post. This is a known problem and is being improved. At present, only by improving the hardware and shortening the duration of windows post can we reduce the probability of conflict.

Check whether orphan blocks are generated

If your previous troubleshooting is normal and there are no problems, you can check whether orphan blocks are generated. The log of a winning block is as follows:

2021-10-09T15:20:38.825+0900 INFO miner miner/miner.go:568 mined new block {"cid": "bafy2bzacedjwoq54i54vfouj7oypbtnqrirlpq2afbr5bqrei2xfrb5smidr2", "height": 1181802, "miner": "f0401254", "parents": ["f01138014","f020378"], "parentTipset": " {bafy2bzacebmjsfzhfkbpnt3qgpxx37fqrdmx277jeztqlljppkpnumho4g2q4,bafy2bzacearifujqqvrczbpugkfjnrryv4i7mlusnvab554ogxcovgx634lyy}", "took": 2.819712038}

You can filter your logs like this:

cat miner.log | grep 'mined new block'

Then, for each block record, you can check whether you have received the block reward in the browser to judge whether the orphan block has been generated. The orphan block is generally generated because the parent block is not fully received. You can view the parents field in the log and compare it with the parent block in the block browser. There is no clear method to effectively avoid orphan blocks, for the storage provider, improving the network Network stability is the main idea to avoid the orphan block.