Common Error Logs in Miner section of Diagnoser

Article author
Customer Support
  • Updated

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: 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?