Skip to content
This repository has been archived by the owner on Jun 12, 2023. It is now read-only.

My miner has not send out a beacon in 5 days. #1426

Closed
trader156 opened this issue Feb 8, 2022 · 12 comments
Closed

My miner has not send out a beacon in 5 days. #1426

trader156 opened this issue Feb 8, 2022 · 12 comments

Comments

@trader156
Copy link

Miner is working and is receiving rewards, but is has not send out a beacon in 5 days. Miner is not relayed. It is a Pisces P100

Atomic Honeysuckle Troll

https://explorer.helium.com/hotspots/112NrTub99XuNm9HFkUKMjz3rzBNLDr3Khm54tyE3QvvSAtWLDqg

Miner Version: miner-arm64_2022.01.29.0_GA
@trader156 trader156 reopened this Feb 10, 2022
@trader156
Copy link
Author

I had closed this issue, because for one day the miner was beaconing, but it has stopped once again. If somebody knows how to fix this please help, because it drastically changes my rewards.

@asuib515
Copy link

I could 100% be wrong but I thought rewards came from witnessing beacons.

@serbyxp
Copy link

serbyxp commented Feb 17, 2022

beacons earn the highest rewards per event. Even though the Total hnt allocated to them is less then witnessing, but they are limited now with the new PoCv11 and network changes to about 3-4 per day, I have friends that they haven't beaconed in weeks, The witnessing is more often, depending on location etc.. but remember for every 1 beacon there is a max of 14 witnesses so it gets divided by more hotspots, so it looks like witnessing earns more because it happens more often. I have noticed my friend his beaconing is down to 0 , but I have noticed a lot of issues are occurring in the software side of things, That haven't been resolved. Some issues could be that you are relayed, Or that you are behind a firewall that the challenger can't reach your miner. Different ISP different modems, routers etc.. have different firewall settings, even if you have the port open, you should see if your router is filtering out p2p networks or inbound connections, that could be blocking the challengers from reaching you. Some may get through, it might not be you that's the issue, It could be the hotspots that are challenging you that have the issue. But the Helium p2p Network itself is having issues in properly establishing connections.

@asuib515
Copy link

That's a very good response. I didn't make the post but I appreciate that response.

When you send out a beacon, that is a sure sign that you DO have an incoming peer to peer connection right? Because another hotspot is challenging you to transmit that beacon. I have that right, right?

@serbyxp
Copy link

serbyxp commented Feb 17, 2022 •
edited

in the app diagnostics it should tell you if your dialable if you have inbound and outbound connects. and what NAT type you want to be with NAT type none , If its symmetric, Then your hotspot will most likly be relayed and have Issues with PoC rewards , and peer connections. But you know you have Inbound connections if your miner is " synced" because its receiving the blockchain information from the network. But, The issue can be more then The NAT type. What I know, from my CCNA ,back in highschool like 20 years ago, and the little I know about peer to peer networks, The P2P networks work in way that are a bit diffrent then normal connections. So even if you can receive the messages from the block chain, and the network check says your dialable and your NAT type. But diffrent manufacturers, Have diffrent mechanisms for handling that, Some have Upnp software on them that open up and close ports automaticlly for updates and others may not have anything, and running custom firmware, So you need to figure out what it tells you to do in their documentation, in the manual... So that you can know what their settings are and match them to yours, But like I said alot of diffrent ISP and routers out there, and a bunch of diffrent manufactures. But if your leasing a modem from say comcast or any ISP they got different settings and they change those firmware whenever they want. Similar to how manufacturers and our hotspots operate. So just make sure to check your router settings actually connect to it through its setup page, And theirs usually a Firewall advanced settings page, That has a bunch of filters, That for Video Games and p2p networks. Even though you got port 44158 open, and your miner can sync and it says its reachable through certain requests for "getting" information and for letting people "get" information from you, similar to how websites work with POST and GET . Similar to that, but some of those filters, they let certain traffic through the port depending on how the peer is asking for it , Find all the settings dealing with p2p and figure out which ones need to be let through, depending on what options it gives you. If you got like a raspberry pi running something for your network like PIHOLE or anything like that, it could be filtering that traffic for you so make sure those things have the right settings too...

@abhay
Like for custom setups, That are running in the cloud, and the packet forwarder or radio is not physically connected to the miner, The server running the miner, needs to have ports 1680, and to be safe also 31341, the Official image from helium for the miner , and the documentation says 1680, but if you look at how the jRPC binds the ports, It binds port 1680 to RX and it binds port 31341 to TX Im not sure if Manufacturers or custom setups, Have that port forwarded, It may not be necessary depending on the Concenentrator ( radio controller that runs the UDP packet forwarder ). But make sure 1680/udp is open in the containers, and that 31341/udp is also open in the containers, and/or how your EBUS is set up, because it could be your Beacon issue , That your container can receive RX messages from the radio, but your TX cant get through and establish the jRPC link to the concentrator. and it can " Fail to connect " or push that datagram to the radio.

@asuib515
Copy link

asuib515 commented Feb 17, 2022 via email

@serbyxp
Copy link

serbyxp commented Feb 18, 2022 •
edited

Well, I’m not sure if I mentioned if your on any sort of VPN or some sort of device on your network , another computer or raspberry pi kind of machine running some sort of networking stack or software that is acting like a network traffic filter, that can be an issue also, that you may have over looked. Can you confirm that your miner has the latest image ? If it’s failing to retrieve the latest image, or is running an old image that , maybe an issue also. The cable you have plugged into the thing might have a bad connection to the router or miner ? I’m not sure just going down a simple trouble shooting “checklist” try a different ethernet cable, or try using WiFi just to diagnose what may be the culprit , if you try WiFi and it works then it could be the “network card “ that’s bad, or cable, or just a setting or corrupted driver that didn’t get loaded properly, or something maybe in your “batch” of hotspots from the manufacturer might need a patch for some setting that may have been missed during the original provisioning at the factory. If you have it connected to WiFi, and you have a “range extender” or are behind another switch or router , those devices need to have the same settings of opened port 44158 TCP << not UDP also. Some devices or computers on the network automatically switch and connect to the strongest signal, and can be one of those “ohh” moments.

I had Comcast with the advanced protection set up originally 3 months ago on thanks giving , everything worked fine, it would get once in a while a message that needed to be cleared to get it back out of NAT symmetric, I see you disabled it, but even on some “low settings” the p2p was still being blocked , if it is a Comcast router/modem or something similar, when your in the modem/router settings , the Information is on the bottom of the router/modem to log into it through the Web browser, the APP won’t let you see those settings. Just click alll the options and look through them they are very descriptive, their is another issue that is not very clear so I can’t tell you if it’s an issue or not. But IPv4 settings are mandatory from my understanding with this , so if your miner is getting an IPv6 IP address , which you can see through your router “connected devices” or client list. From the documentation I have seen and gone through, not saying Official helium docs, but related information. Some manufacturers have the ipv6 settings turned off some on , but on your router theirs another section of the firewall that is specific to The two types, ipv4 and ipv6 make sure they correspond, and that your router switch whatever has ipv4 enabled. The /p2p/ uses to formats the peer name /p2p/pub address ( hotspot public key) and it uses an ipv4 address which should be your session listen address when you are not relayed which is /ipv4/yourISPsddress and a local ipv4 /ipv4/yourMinersLocal_ip what you got to remember the local IP address of your miner in that listener address may not reflex the IP address that ypu “statically” assigned it on your router, because some miners use “containers” which use their own internal subnet, so don’t fret on that to much, but know that if your miner is getting an ipv6 address and it’s subnet or containers aren’t properly set for that, or could cause issues, so ensure that your ipv4 settings are working correctly. I don’t know if you have a special manufacturer like say deeper-network hotspots, that have some other VPN software going on that I have no idea about since I don’t got my hands on one.

*ipv4 is what you normally see like 10.0.0.100 or 192.168.0.1 that format, ipv6 is a long weird number and letters with a bunch of : : in between.
Subnet mask, make sure your subnet mask isn’t some custom thing, subnet mask is usually some 255.255.255.0 if it’s different schema, that the firmware on the miner is not automatically accounting for, it could cause issues in the routing tables etc.
Some routers by default have an ip filtering list, that they automatically throw IP addresses into like a “black list” of it automatically threw your miner in there , it needs to be cleared out. Some routers have a “white list” that you can add your miner to to prevent any traffic filtering, if you got outbound connections but you got no inbound , make sure your port forwarding is both in and outbound , apparently all this stuff is a thing, and it’s all manufacture specific to the routers default settings.

also if you by some chance connected via WiFi at some point, and now have it connected to Ethernet cable, make sure the WiFi is actually turned off , it could be auto connecting to the WiFi without you noticing, and depending on how the miner responds to its priorities on network adapters could be ignoring the Ethernet and using the WiFi connections IP.

when in doubt unplug your router for a minute or so and reconnect it some settings may not be saved /loaded properly when not power cycled like actually pulled from the wall outlet.

@trader156
Copy link
Author

So an upgrade on my miner. I had to switch it off for a few days, due to e poe adapter issue and after I think 4 days I turned it back on. Cleared the blockchain data, just to be sure, and synced the device again. Now for the past 3 days it has been working fine and is sending out beacons.

@serbyxp
Copy link

serbyxp commented Feb 18, 2022 •
edited

Yeah power cycling, helps, also if your miner got stuck in a loop which I noticed and others have noticed , is an error to the blockchain handler. Which gives an error that falls into an endless loop, so if that happened then your miner was probably stuck, by waiting for the blockchain to surpass its current “blessed snapshot” height to trigger the mechanism to download the new “blessed snapshot” and clear out the old one, it’s something in the code with the garbage collection or gc. That needs to be adjusted or accounted for or never broken in the first place.
I’ve noticed whoever is in charge of managing the DevOps , surely likes messing with things in the software that aren’t broken, and then they push it out as a release and use us as the testing bed to find bugs, and issues.

I’ve been trying to learn Erlang since this helium image is written in it. And I have noticed a common theme with Erlang, it doesn’t have a traditional fail safe system in place, it goes down it’s code and if it fails somewhere then that “node” or part of the code either restarts the “process” or just keeps systematically going down the same rabbit hole, when the error doesn’t get cleared. Like if you had the blockchain issue, in say a traditional failsafe system it would have like a “watch dog” or pointer that says if blockchain handler height calculated does not match Then gc.blockchaindata, installNewSnapshoot something of the sorts instead it’ll just keep going down it’s process untill some other process gets triggered by a higher priority task
Erlang can do it , but I have noticed the miner image has no error response logic built into it, so when an error happens it’s going to keep happening Untill another task clears it out just by the programs logic based on sheer luck,

@trader156
Copy link
Author

trader156 commented Mar 8, 2022 •
edited

@serbyxp My device seems to be stuck in the loop that you have mentioned. After power cycling it works great for a few days and then the frequency of sending out beacons plummet so does the rewards. I have been trying to fix this for a long long time, so if you have any suggestions please help. Also just to mention I have this issue on 2 different miners.

@asuib515
Copy link

asuib515 commented Mar 14, 2022 via email

@serbyxp
Copy link

serbyxp commented Mar 14, 2022 •
edited

I dunno what to say at this point… but theirs issues , my buddy with like 16 hotspots is the same doesn’t beacon they are all OG helium miner no clue. Mine is beaconing… But I have mine custom… so I can control my setup… if you got access to the the miner through ssh ( if you can get a console / terminal screen) then you can start poking around to fix things that the manufacturer may have incorrect. If you got more then one miner in your network, that can cause some issues possibly. If you do have more then one miner on the same network try to assign a port to each miner and IP …

have you tried plugging it into another internet connection? Like at a friends house or neighbor with different service provider ? If your on a mobile service like 5g lte or something that might mess with things. If your miners are using a custom setup or some specific manufacture that you can check if other people with the same brand are having the same issue…

Heh… put that thing on a smart switch like a programable timer switch that turns it on and off every so often… should not have to do that but 🤷‍♀️ I’m ghetto like that

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@meowshka @serbyxp @asuib515 @trader156