Miner Had Been Working, but Now is Syncing/Offiline

Article author
Customer Support
  • Updated

Your Blockchain.db is Reset

If the blockchain.db is too big (over 40G for Bobcat), the blockchain.db will be deleted and resynced from the latest snapshot.

Your Network Has Issues 

Take a look at your Miner’s LED. If it’s Red, restart the Miner. If it’s Yellow, test the WiFi it’s using. If it’s connecting to a Cable, connect the Cable to another device to test the Internet. If the internet is OK, restart the Miner and wait until it’s back to Green. All these operations should be after you reserved your miner’s IP address.

The issue can also be a laggy WiFi connection. Some have low latency, some are high.

{
  "DownloadSpeed": "5 Mbit/s",
  "UploadSpeed": "9 Mbit/s",
  "Latency": "24.621771ms"
}

{
  "DownloadSpeed": "55 Mbit/s",
  "UploadSpeed": "20 Mbit/s",
  "Latency": "85.234333ms"
}

The Explorer Status is Wrong

Too many hotspots are joining everyday. The Helium API servers keep scaling out but sometimes it can’t catch up with the speed that hotspots are being added. In this case, it’s possible the API shows laggy height and wrong status.

Router and State Channel details: https://blog.helium.com/helium-state-channels-383ade2368d0

Blockchain is Moving Too Fast

This often happens after a chain halt. The fastest speed of producing blocks is 50 seconds. The expected block time is 60 seconds. After a chain halt, the blockchain will try to run as it’s fastest speed to produce blocks. In this case, some miners may not be able to catch up with this speed. Once the blockchain is back in the 60 seconds, your hotspot will go back to being synced.

 

Was this article helpful?

2 out of 37 found this helpful

Comments

0 comments

Please sign in to leave a comment.