Helium hotspot miner

Here is the error log:

Connecting to f92c8c884619beb28feb3308af535c07…
Spawning shell…
/opt/miner # miner info height
32331 1220712
/opt/miner # miner info summary


Miner General Info


±---------------±------------------------------------------------------------+
| name | result |
±---------------±------------------------------------------------------------+
| miner name | rough-chartreuse-mole |
| mac addresses | eth0 : 0242AC110002 |
| | lo : 000000000000 |
| block age | 5442038 |
| epoch | 32331 |
| height | 1220712 |
| sync height | 1220712 |
| uptime | 0 Days, 1 Hours, 29 Minutes, 35 Seconds |
| peer book size | 26617 |
|firmware version|cat: can’t open ‘/etc/lsb_release’: No such file or directory|
|gateway details | gateway not found in ledger |
±---------------±------------------------------------------------------------+


Miner P2P Info


±--------±--------+
| name | result |
±--------±--------+
|connected| yes |
|dialable | yes |
|nat_type |symmetric|
| height | 1220712 |
±--------±--------+


Miner log errors


***** Transaction related errors *****

:
***** POC related errors *****

:
***** General errors *****

: 2022-04-15 14:29:01.476 1 [error] <0.5231.1>@blockchain_worker:start_snapshot_sync:{1057,39} snapshot download or loading failed because {error,{403,<<"\n<META HTTP-EQUIV=“Content-Type” CONTENT=“text/html; charset=iso-8859-1”>\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=“1px”>\nRequest blocked.\nWe can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=“all”>\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=“all”>\n<HR noshade size=“1px”>\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: _la9nPYLWV30VyoeusxPQIhG0tsrf3eRQlqdqIJpoDI3Uo_PC9x3iA==\n
\n\n\n">>}}: [{blockchain_worker,do_snap_source_download,2,[{file,“blockchain_worker.erl”},{line,1182}]},{blockchain_worker,’-start_snapshot_sync/1-fun-0-’,4,[{file,“blockchain_worker.erl”},{line,1042}]}]
2022-04-15 14:29:01.390 1 [error] <0.1542.0>@blockchain_worker:fetch_and_parse_latest_snapshot:{1083,21} Couldn’t fetch latest-snap.json because {error,{403,<<"\n<META HTTP-EQUIV=“Content-Type” CONTENT=“text/html; charset=iso-8859-1”>\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=“1px”>\nRequest blocked.\nWe can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=“all”>\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=“all”>\n<HR noshade size=“1px”>\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: hwvRcgXBTvHfqw93rhBNTpqFnnOnoElDwXMWftK-e9Z67bC2KP4-Gg==\n
\n\n\n">>}}: [{blockchain_worker,get_latest_snap_data,2,[{file,“blockchain_worker.erl”},{line,1117}]},{blockchain_worker,fetch_and_parse_latest_snapshot,1,[{file,“blockchain_worker.erl”},{line,1080}]},{blockchain_worker,start_snapshot_sync,1,[{file,“blockchain_worker.erl”},{line,1035}]},{blockchain_worker,snapshot_sync,1,[{file,“blockchain_worker.erl”},{line,838}]},{blockchain_worker,handle_info,2,[{file,“blockchain_worker.erl”},{line,640}]},{gen_server,try_dispatch,4,[{file,“gen_server.erl”},{line,695}]},{gen_server,handle_msg,6,[{file,“gen_server.erl”},{line,771}]},{proc_lib,wake_up,3,[{file,“proc_lib.erl”},{line,236}]}]
2022-04-15 14:29:01.302 1 [error] <0.5230.1>@blockchain_worker:start_snapshot_sync:{1057,39} snapshot download or loading failed because {error,{403,<<"\n<META HTTP-EQUIV=“Content-Type” CONTENT=“text/html; charset=iso-8859-1”>\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=“1px”>\nRequest blocked.\nWe can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=“all”>\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=“all”>\n<HR noshade size=“1px”>\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: K2vqLAvLqmXwqac9Bv0jJM6U5uAIY3UHLHIePzI1xm6s5IHETMaf9w==\n
\n\n\n">>}}: [{blockchain_worker,do_snap_source_download,2,[{file,“blockchain_worker.erl”},{line,1182}]},{blockchain_worker,’-start_snapshot_sync/1-fun-0-’,4,[{file,“blockchain_worker.erl”},{line,1042}]}]sort: standard output: Broken pipe

2022-04-15 14:29:01.217 1 [error] <0.1542.0>@blockchain_worker:fetch_and_parse_latest_snapshot:{1083,21} Couldn’t fetch latest-snap.json because {error,{403,<<"\n<META HTTP-EQUIV=“Content-Type” CONTENT=“text/html; charset=iso-8859-1”>\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=“1px”>\nRequest blocked.\nWe can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=“all”>\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=“all”>\n<HR noshade size=“1px”>\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: iG8RmV9YgsD8YaIRMitLROFqlzky78-HM0Gn78_6YNvDmYDArJS47w==\n
\n\n\n">>}}: [{blockchain_worker,get_latest_snap_data,2,[{file,“blockchain_worker.erl”},{line,1117}]},{blockchain_worker,fetch_and_parse_latest_snapshot,1,[{file,“blockchain_worker.erl”},{line,1080}]},{blockchain_worker,start_snapshot_sync,1,[{file,“blockchain_worker.erl”},{line,1035}]},{blockchain_worker,snapshot_sync,1,[{file,“blockchain_worker.erl”},{line,838}]},{blockchain_worker,handle_info,2,[{file,“blockchain_worker.erl”},{line,640}]},{gen_server,try_dispatch,4,[{file,“gen_server.erl”},{line,695}]},{gen_server,handle_msg,6,[{file,“gen_server.erl”},{line,771}]},{proc_lib,wake_up,3,[{file,“proc_lib.erl”},{line,236}]}]
2022-04-15 14:29:01.132 1 [error] <0.5229.1>@blockchain_worker:start_snapshot_sync:{1057,39} snapshot download or loading failed because {error,{403,<<"\n<META HTTP-EQUIV=“Content-Type” CONTENT=“text/html; charset=iso-8859-1”>\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=“1px”>\nRequest blocked.\nWe can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=“all”>\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=“all”>\n<HR noshade size=“1px”>\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: ES2bSmBDdt8SxARIUR6GNQSUNsz_d8HTJlxc-MV0O_eGrc3cKgX-nw==\n
\n\n\n">>}}: [{blockchain_worker,do_snap_source_download,2,[{file,“blockchain_worker.erl”},{line,1182}]},{blockchain_worker,’-start_snapshot_sync/1-fun-0-’,4,[{file,“blockchain_worker.erl”},{line,1042}]}]

Thanks for sharing @mantoles

Actually i get timeout when i type miner info summary! LOL not sure if this is a Helium issue.

I’m worried about gateway not found in ledger. Is the miner name still the same?

Are you using a repo compatible with EU region?

will keep digging. I just pushed another release.

Mark, I think you may be correct seems to be helium network related issue:

miner info height
32331 1220712
/opt/miner # Error response from daemon: Container 56e2ab74358c9edf2a9cddaa6957734ddfd3123d7754b39ab72c52710d06e92d is not running
SSH session disconnected
SSH reconnecting…
SSH reconnecting…
Spawning shell…
/opt/miner # Disconnected
Connecting to f92c8c884619beb28feb3308af535c07…
Spawning shell…
/opt/miner # miner info height
35037 1311295
/opt/miner # miner info height
35037 1311295
/opt/miner # miner info height
35037 1311296
/opt/miner # miner info summary


Miner General Info


±---------------±----------------------------------------------------------------------------------------------------------+
| name | result |
±---------------±----------------------------------------------------------------------------------------------------------+
| miner name | rough-chartreuse-mole |
| mac addresses | eth0 : 0242AC110002 |
| | lo : 000000000000 |
| block age | 122275 |
| epoch | 35037 |
| height | 1311296 |
| sync height | 1311296 |
| uptime | 0 Days, 5 Hours, 32 Minutes, 30 Seconds |
| peer book size | 26850 |
|firmware version| cat: can’t open ‘/etc/lsb_release’: No such file or directory |
|gateway details |Gateway location: 631307052196045823Owner address: /p2p/13GYh8bnLHyVVa1HBAkWPA9KC1n9gHguA3PQXs7kT5dTyLg85Fw|
±---------------±----------------------------------------------------------------------------------------------------------+


Miner P2P Info


±--------±--------+
| name | result |
±--------±--------+
|connected| yes |
|dialable | yes |
|nat_type |symmetric|
| height | 1311297 |
±--------±--------+


Miner log errors


***** Transaction related errors *****

:
***** POC related errors *****

:
***** General errors *****

:
/opt/miner #

Hello @mantoles sorry that i write you here very late.

Is this working properly now? Let me know the latest status of this!

Let’s stay connected

@mpous, I turned off the device. It has not been working for a very long time. Do time to troubleshoot. Plus it is in a different country and I dont have physicall access to it. The radio was not transmitting or receiving packets last I checked. So while it synchronized with the chain it was not getting widnessed.

Sad to hear that! sorry for writing super late! today i was doing some housekeeping and i found your message!

Let me know if you try to ressurrect it anytime!

Let’s stay connected