Common Error Logs in "Miner (5s)”

Article author
Customer Support
  • Updated

Error: Block Checksum Mismatch

*error.*badmatch.*Corruption.*block checksum mismatch.*
"Please try resetting then fast syncing your Bobcat If you continue to see this error please contact Bobcat support"

Points to: EMMC / Memory issue

Why does this error happen?

This error is related to the EMMC (Embedded MultiMediaCard) in your miner. This is a blockchain error you can potentially snapshot past. This is NOT related to your RAM size.  

What you can try
1. Reset
2. Fast Sync
3. Monitor for Error After it Has Fully Synced
What to provide customer support if unable to resolve
1. Keep your miner online so that our engineers can work on your miner.
2. You might notice your miner resyncing while our engineers are working on your miner. The process can take some time so please be patient and cooperative.

Error: Compression Method or Corrupted.

*error.*badmatch.*Corruption.*compression method or corrupted.*
 "You can ignore it if your hotspot is working. If it’s not working resync may solve this issue"

Points to: EMMC / Memory issue

Why does this error happen?

This points to an error related to the EMMC (Embedded MultiMediaCard) in your miner. Resyncing might get rid of this error. This is NOT related to your RAM size.  

What you can try
1. Resync
What to provide customer support if unable to resolve
1. Keep your miner online so that our engineers can work on your issue.
2. You might notice your miner resyncing while our engineers are working on your miner. The process can take some time so please be patient and cooperative.

Error: too_many_lookup_attempts

*DNS.*lookup.*of.*seed\.helium\.io.*error.*too_many_lookup_attempts.*
"Diagnoser will add more DNS nameservers for you. If you see this error again please try to change your DNS settings; for example, use 8.8.8.8 as your DNS server"

Points to: DNS server settings

Why does this error happen?

This error occurs when your DNS server cannot find the correct nameserver. Normally, the Bobcat miner will automatically add the appropriate nameserver for you.  

What you can try
1. If this error continues to appear and your miner is not behaving as expected you can try setting your DNS server to 8.8.8.8.
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Tell us what color your LED is.
3. If you can't access your Diagnoser, please open port 22
4. Provide the miner's public IP address.
5. Use this Link to Confirm Port 22 is Open (Include a Screenshot of this Page)

Error: onboarding\.dewi\.org.*nxdomain.

*badmatch.*failed_connect.*onboarding\.dewi\.org.*nxdomain.*
 "Diagnoser will add more DNS nameservers for you. If you see this error again please try to change your DNS settings; for example, use 8.8.8.8 as your DNS server"

Points to:  DNS server settings

Why does this error happen?

This error occurs when your DNS server cannot find the correct nameserver. Normally, the Bobcat will automatically add the appropriate nameserver for you.  

What you can try
If this error continues to appear and your miner is not behaving as expected you can try setting your DNS server to 8.8.8.8.
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Tell us what color your LED is.
3. If you can't access your Diagnoser please open port 22
4. Provide the miner's public IP address.
5. Use this Link to Confirm Port 22 is Open (Include a Screenshot of this Page)

Error: failed_to_start_child.

*miner_critical_sup.*ecc_compact.*failed_to_start_child.*
 "Please try to power off then power on. If that doesn't work contact support",

Points to: Faulty ECC chip

Why does this error happen?

This usually means that there is either a ECC chip fault or it’s a firmware issue.

What you can try
1. Reset
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Tell us what color your LED is.
3. If you can't access your Diagnoser please open port 22
4. Provide the miner's public IP address.
5. Use this Link to Confirm Port 22 is Open (Include a Screenshot of this Page) 

Error: not_a_dets_file.

*not_a_dets_file.*
"Blockchain database is broken. Please try to resync."

Points to: Broken Blockchain but this shouldn’t be an issue anymore with the latest firmware.

Why does this error happen?

There is probably a corruption in the database

What you can try
1. Resync
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Tell us what color your LED is.
3. If you can't access your Diagnoser please open port 22
4. Provide the miner's public IP address.
5. Use this Link to Confirm Port 22 is Open (Include a Screenshot of this Page)

Error: snapshots\.helium\.wtf

*failed_connect.*snapshots\.helium\.wtf.*443.*nxdomain.*
"Diagnoser will add more DNS nameservers for you. If you see this error again please try to change your DNS settings; for example, use 8.8.8.8 as your DNS server"

Points to: DNS issue

Why does this error happen?

Miner is unable to connect to DNS servers. New Diagnoser should automatically add Google DNS so it should get rid of this issue. 

What you can try

1. Add 8.8.8.8 to your DNS server
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Tell us what color your LED is.
3. If you can't access your Diagnoser please open port 22
4. Provide the miner's public IP address.
5. Use this Link to Confirm Port 22 is Open (Include a Screenshot of this Page)
6. Double check with your ISP to see if there is a strict firewall.

Error: snapshot download or loading failed

*snapshot download or loading failed because.*error.*timeout.*
"Snapshot download timeout error. This could mean your network is slow. Please do a Speed Test in the main menu. Maybe your wifi signal is not strong enough"

Points to: Miner is unable to download the latest snapshot from the blockchain

Why does this error happen?

There may be too many miners trying to download the snapshot at the same time or your internet connection may be too slow.

What you can try
1. Check that your miner is connected via ethernet and that your internet connection is stable, otherwise, the situation should eventually sort itself out.
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Tell us what color your LED is.
3. If you can't access your Diagnoser please open port 22
4. Provide the miner's public IP address.
5. Use this Link to Confirm Port 22 is Open (Include a Screenshot of this Page)

Error: no plausible blocks in batch

*no plausible blocks in batch.*
"Maybe your miner stopped syncing. If your gap is increasing try a resync, leave it there for a few hours, then check again"

Points to: Helium Network Bug error

Why does this error happen?

This is a Helium network bug that affects miners across all manufacturers. Helium is actively trying to solve the issue. 

What you can try
1. Helium recommends that you continue to resync and reset until your miner is able to get past the snapshot. Unfortunately, if that doesn’t work then you will have to wait for Helium OTA update to fix the issue.
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Tell us what color your LED is.
3. If you can't access your Diagnoser please open port 22
4. Provide the miner's public IP address.
5. Use this Link to Confirm Port 22 is Open (Include a Screenshot of this Page)

Error: RPC to 'miner@127.0.0.1' failed

RPC to 'miner@127.0.0.1' failed: timeout

Points to: Docker container or ECC fault

Why does this error happen?

You might see this during a reset, reboot, or OTA. This is related to the status of the ECC chip. If this error goes away then nothing is wrong. If you continue to see the error you can try the following.

What You Can Try
1. First Try Reboot
2. Then Try Reset
3. Make Sure Your Miner is Connected to the Internet. What color is the miner's LED?
What to provide customer support if unable to resolve
1. If possible, send screenshots of your Diagnoser.
2. Indicate miner's LED color
3. Open Port 22, if unable to access the Diagnoser
4. Provide the miner's public IP address.
5. Use this Link to confirm port 22 is open (Include a Screenshot of this Page)

Was this article helpful?

5 out of 26 found this helpful

Comments

0 comments

Please sign in to leave a comment.