Hi Everyone. Just received and setup my Apollo Full Node miner. Its running fine, and connected to the pool but the whole OS will freeze after about 45-60 minutes. No mouse control, no keyboard input. The red light on the Apollo is still blinking, but it doesn't connect to the pool anymore, no hashing being reported. The only way to get it back is to flip the switch off, and then flip it back on. It freezes even if the miner is off, and yes its still syncing the blockchain, but if its going to keep freezing even without the miner running its going to take more than 48 hours to sync this blockchain. Its not hot to the touch really, but with the miner on its temp is about 76 C.
Any ideas on why this would be freezing and what can be done to fix it?
I think I may have figured it out. It appears that the thermal/temp sensor was flopping around inside the case, as in it was just dangling near the bottom, so it wasn't taking proper readings of the temps. I took off the right side panel, and sort of wedge it in as best as possible next to the plate that the CPU heatsink sits on. Not really sure if that is where it goes or not, but so far the miner has been running without issues for a few hours now. I ordered some thermal tape and plan on taping it into place so that it doesn't start flopping around again. Anyone have any ideas where exactly the sensor is supposed to be located so I can put it in its proper place? I think you might have moved the WiFi antenna, not a temp sensor. You could be right although I've never seen a wifi antenna like that before. Thanks for the help I guess... Is it wrapped in black shrink-wrap with 2 segments under the wrap? Can you put it outside of the metal housing through the rubber plug in the hole in the metal? If so, that the antenna. And if you put it out of the metal box and orientate it vertically up or down, you might get much better connection. Thank you for the guidance. Ok, back to square one then. Why the freezing? It has been running fine all day except one freeze in the morning. Is it due to it losing wifi connectivity? What temp do you see on the top menu bar (CPU temp of controller). This could indicate the heatsink on the blue controller is not properly installed, and from your description I can't really tell if you installed it back on right. It sides on top of the blue controller and you'll need to remove the side plate and the controller (two screws on bottom lip) to get it on there right. There is a grove in the heatsink where the audio jack is for proper alightment, and you need to press it down on top of silver CPU cap. Attached is an image of what it should look like installed. Be careful with the ribbon cable attachment as this can pop off while moving the controller around. https://i.imgur.com/A30ePkr.jpeg |
|
|
|
Hello,
I've been running the BTC miner with full node for a while now, but since this week end the node randomly goes offline and does not reconnect.
Anyone having this issue? I need the node to stay online.
The miner is still mining but the node just goes offline
I have been having the exact same issue, which means it's not us but something wrong on futurebit's end. I wrote them and they never wrote back  Good luck trying to get support, its almost non existent, if not EXTINCT... Not sure where you are coming up with this, we respond to every email and im looking at our support que right now and there are only 10 outstanding tickets that will probably be answered in the next few hours (and we only have queues after weekends). So if your definition of non existent support means not answering your immediate question within 10 minutes, then yes we have non existent support and will continue to have non existent support. Im not hiring random support agents from India and driving up costs of our units by 20% to satisfy this urge. All our support emails are answered by my team that work on the units themselves (including myself) and can actually answer your question, but this means you might not have a response for a few days. Now in terms of the nodes issues we are not seeing anything on our test systems, nor any widespread outages (my first thought was the ordinals/BRC-20 fiasco causing issues, but even with 1G mempool we have plenty of memory overhead). Second issue could be if you have a recent system (bought after Nov/Dec last year), we switch to a new controller heatsink and some units were assembled without the heatsink adhesive properly installed. If your node/system is shutting down, or your your MCU temp (the one on the top menu bar) is higher than 85c then this could be the issue. You'll need to remove the side panel the MCU is on and remove the MCU and reseat the heatsink (press down on it hard for at least 10 seconds to make sure the thermal pad is stuck on there well). Second step if your still having an issue is to reflash your SD card to make sure there is no corruption that could be causing system instability, if your still having node issues email us with two below logs: take a screenshot of system monitor while the node is still active (preferably after it has started up and synced), you can open a terminal and type htop for this send log file of bitcoind, its in the Bitcoin folder inside the node drive (debug.log) So it appears the node goes offline only when I connect to it after a few minutes (via Sparrow Wallet). Can it be because it is overheating, connecting to the node actually makes it run hotter?!? I bought the unit couple years ago and I just cleaned it so it shouldn't overheat? The fan is on Auto as well. No, unless sparrow wallet is doing something crazy when you connect to it. Can you email us your logs after this happens (logs are in node drive /Bitcoin folder). Any updates on this? Having the same issue. This is a known issue with the wallet devs, problem is on their end and how they query data from low memory nodes like ours. I believe latest version has fixed it but reach out to their support. Craig Raw believes that the issue stems from the Apollo running bitcoin core v.22. Is there a way to upgrade to v.24? Yes you can just swap out the arm binary in /opt/apolloapi/backend/node/bin We will be updating to latest core with our solo mining mode update soon as well |
|
|
|
Hello,
I've been running the BTC miner with full node for a while now, but since this week end the node randomly goes offline and does not reconnect.
Anyone having this issue? I need the node to stay online.
The miner is still mining but the node just goes offline
I have been having the exact same issue, which means it's not us but something wrong on futurebit's end. I wrote them and they never wrote back Good luck trying to get support, its almost non existent, if not EXTINCT... Not sure where you are coming up with this, we respond to every email and im looking at our support que right now and there are only 10 outstanding tickets that will probably be answered in the next few hours (and we only have queues after weekends). So if your definition of non existent support means not answering your immediate question within 10 minutes, then yes we have non existent support and will continue to have non existent support. Im not hiring random support agents from India and driving up costs of our units by 20% to satisfy this urge. All our support emails are answered by my team that work on the units themselves (including myself) and can actually answer your question, but this means you might not have a response for a few days. Now in terms of the nodes issues we are not seeing anything on our test systems, nor any widespread outages (my first thought was the ordinals/BRC-20 fiasco causing issues, but even with 1G mempool we have plenty of memory overhead). Second issue could be if you have a recent system (bought after Nov/Dec last year), we switch to a new controller heatsink and some units were assembled without the heatsink adhesive properly installed. If your node/system is shutting down, or your your MCU temp (the one on the top menu bar) is higher than 85c then this could be the issue. You'll need to remove the side panel the MCU is on and remove the MCU and reseat the heatsink (press down on it hard for at least 10 seconds to make sure the thermal pad is stuck on there well). Second step if your still having an issue is to reflash your SD card to make sure there is no corruption that could be causing system instability, if your still having node issues email us with two below logs: take a screenshot of system monitor while the node is still active (preferably after it has started up and synced), you can open a terminal and type htop for this send log file of bitcoind, its in the Bitcoin folder inside the node drive (debug.log) So it appears the node goes offline only when I connect to it after a few minutes (via Sparrow Wallet). Can it be because it is overheating, connecting to the node actually makes it run hotter?!? I bought the unit couple years ago and I just cleaned it so it shouldn't overheat? The fan is on Auto as well. No, unless sparrow wallet is doing something crazy when you connect to it. Can you email us your logs after this happens (logs are in node drive /Bitcoin folder). Any updates on this? Having the same issue. This is a known issue with the wallet devs, problem is on their end and how they query data from low memory nodes like ours. I believe latest version has fixed it but reach out to their support. |
|
|
|
I'm having two separate issues with my Apollo Node (Full + Standard) affecting its continued operation:
(1) The unit randomly stops working while maintaining power and the appearance of hashing activity. The miners remain on with the fans running, but the unit does not "wake up" when the mouse or keyboard are manipulated and there is no output from the video (HDMI) port to my monitor. I have tried all possible layer 1 manipulations to wake the machine, but my mining pool shows a reported hashrate of 0, and the only way to regain control of the system is a hard shutdown and restart. This wastes both my time and my power at a premium.
(2) My machine is randomly dropping off the network with a syslog error reporting a failed handshake and stating my device has the WRONG KEY. However, the password has not changed since Ive owned the Apollo and it is the only one on my network to drop its LAN connection in this manner. Unfortunately, I don't know what (if anything) the following log dump is telling me, due to my limited, but anyone venture a guess as to why my LAN connection keeps dropping or how I might fix it?
Mar 18 18:55:44 futurebitbtc wpa_supplicant[1558]: wlan0: Trying to associate with **:**:**:**:**:** (SSID='*****WiFi' freq=5200 MHz)
Mar 18 18:55:44 futurebitbtc wpa_supplicant[1558]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=**:**:**:**:**:** status_code=1
Mar 18 18:55:45 futurebitbtc kernel: [2534781.191339] unisoc_wifi unisoc_wifi wlan0: sprdwl_report_connection sm_state (5), status: (2)!
Mar 18 18:55:45 futurebitbtc kernel: [2534781.191399] unisoc_wifi unisoc_wifi wlan0: sprdwl_report_connection *****WiFi failed status code:1!
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.0030] device (wlan0): supplicant interface state: completed -> associating
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.0032] device (p2p-dev-wlan0): supplicant management interface state: completed -> associating
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.0179] device (wlan0): supplicant interface state: associating -> disconnected
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.0181] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnect>
Mar 18 18:55:45 futurebitbtc gnome-shell[1803871]: An active wireless connection, in infrastructure mode, involves no access point?
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.1072] device (wlan0): supplicant interface state: disconnected -> scanning
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.1074] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: Trying to associate with **:**:**:**:**:** (SSID='*****WiFi' freq=2462 MHz)
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: CTRL-EVENT-DISCONNECTED bssid=**:**:**:**:**:** reason=0
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.8560] device (wlan0): supplicant interface state: scanning -> associating
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.8563] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: Associated with **:**:**:**:**:**
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: nl80211: kernel reports: key not allowed
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=**:**:**:**:**:**)
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: CTRL-EVENT-DISCONNECTED bssid=**:**:**:**:**:** reason=1 locally_generated=1
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Mar 18 18:55:45 futurebitbtc wpa_supplicant[1558]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="*****WiFi" auth_failures=1 duration=10 reason=WRONG_KEY
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9110] device (wlan0): supplicant interface state: associating -> disconnected
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9112] device (p2p-dev-wlan0): supplicant management interface state: associating -> disconnect>
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9116] device (wlan0): supplicant interface state: disconnected -> 4-way handshake
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9117] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> 4-way han>
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <warn> [1679180145.9139] sup-iface[0xaaab0a17a100,wlan0]: connection disconnected (reason -1)
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9143] device (wlan0): supplicant interface state: 4-way handshake -> disconnected
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9245] device (wlan0): Activation: (wifi) disconnected during association, asking for new key
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9253] device (wlan0): state change: activated -> need-auth (reason 'supplicant-disconnect', sy>
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9261] dhcp4 (wlan0): canceled DHCP transaction
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9263] dhcp4 (wlan0): state changed extended -> done
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9333] manager: NetworkManager state is now CONNECTING
Mar 18 18:55:45 futurebitbtc dbus-daemon[1514]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatche>
Mar 18 18:55:45 futurebitbtc NetworkManager[1515]: <info> [1679180145.9836] device (p2p-dev-wlan0): supplicant management interface state: 4-way handshake -> discon>
Mar 18 18:55:45 futurebitbtc systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 18 18:55:46 futurebitbtc NetworkManager[1515]: <info> [1679180146.0302] device (wlan0): supplicant interface state: disconnected -> inactive
Mar 18 18:55:46 futurebitbtc NetworkManager[1515]: <info> [1679180146.0304] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Mar 18 18:55:46 futurebitbtc dbus-daemon[1514]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 18 18:55:46 futurebitbtc systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 18 18:55:47 futurebitbtc kernel: [2534783.200532] Purging 4202496 bytes
Mar 18 18:55:47 futurebitbtc kernel: [2534783.216659] Purging 4198400 bytes
Mar 18 18:55:47 futurebitbtc kernel: [2534783.222814] Purging 4399104 bytes
Mar 18 18:55:57 futurebitbtc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Mar 18 18:57:31 futurebitbtc Tor[1780]: Tor has not observed any network activity for the past 107 seconds. Disabling circuit build timeout recording.
Mar 18 18:57:46 futurebitbtc NetworkManager[1515]: <warn> [1679180266.0625] device (wlan0): no secrets: No agents were available for this request.
Mar 18 18:57:46 futurebitbtc NetworkManager[1515]: <info> [1679180266.0629] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state:>
Mar 18 18:57:46 futurebitbtc NetworkManager[1515]: <info> [1679180266.0695] manager: NetworkManager state is now DISCONNECTED
Mar 18 18:57:46 futurebitbtc gnome-shell[1803871]: An active wireless connection, in infrastructure mode, involves no access point?
Mar 18 18:57:46 futurebitbtc NetworkManager[1515]: <warn> [1679180266.0813] device (wlan0): Activation: failed for connection '******WiFi'
Mar 18 18:57:46 futurebitbtc NetworkManager[1515]: <info> [1679180266.0863] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'm>
Mar 18 18:57:46 futurebitbtc gnome-shell[1803871]: An active wireless connection, in infrastructure mode, involves no access point?
Mar 18 18:57:46 futurebitbtc gnome-shell[1803871]: message repeated 2 times: [ An active wireless connection, in infrastructure mode, involves no access point?]
Mar 18 19:00:01 futurebitbtc CRON[1834468]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Mar 18 19:01:49 futurebitbtc Tor[1780]: Failed to find node for hop #1 of our path. Discarding this circuit.
Mar 18 19:01:49 futurebitbtc Tor[1780]: Our circuit 0 (id: 127850) died due to an invalid selected path, purpose General-purpose client. This may be a torrc configur>
Mar 18 19:05:01 futurebitbtc CRON[1834483]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 18 19:05:27 futurebitbtc Tor[1780]: Failed to find node for hop #1 of our path. Discarding this circuit.
Thought I had this figured out, but it turns out both issues are still occuring --random shutdowns and random network drops, not that I've received any responses from the group. How do I get on the "respond to my query" list? What kind of wifi interface do you have? Wifi controllers on these boards usually can't handle anything complex like mix mode/WPA3/etc. Try separating networks and using WPA2 with no spaces or special characters in SSID. Could also be a distance issue (try brining closer to base station), or corruption issue on SD card (reflash SD card and see if error goes away). |
|
|
|
One of my Apollo's has a problem and I want to figure out how to fix it or at least diagnose what is wrong.
...
I can temporarily get rid of the problem by unplugging the USB cable to the standard unit, then plug it in again and then restart the miner. Then it will run for maybe half a day before becoming erratic again, as shown below:  It seems to me there is something wrong, either related to the USB ports (they are fickle and often don't work) or maybe related to total power requirements of the OrangePi not being met at times, so that either an extra USB plugged in, or the HDMi cable plugged in will kick it over the edge into malfunction. This looks like an internet connectivity issue, if you're running on wifi can you try ethernet and see if it resolves? Adding another device via USB wont increase power requirements for controller, standard units have internal USB power and only use data lines on USB cords. One usb port is les reliable than the rest on the device (keep forgetting which it is but think its one of the USB 3 ports), and a good way to avoid is to use a USB hub (trying to get this fixed in time for the next major upgrade to the OS) HDMI does activate the GPU on the controller which does use a lot more power, also double check your heatsink on the controller is firmly attached and has not come loose. |
|
|
|
Hello,
I've been running the BTC miner with full node for a while now, but since this week end the node randomly goes offline and does not reconnect.
Anyone having this issue? I need the node to stay online.
The miner is still mining but the node just goes offline
I have been having the exact same issue, which means it's not us but something wrong on futurebit's end. I wrote them and they never wrote back Good luck trying to get support, its almost non existent, if not EXTINCT... Not sure where you are coming up with this, we respond to every email and im looking at our support que right now and there are only 10 outstanding tickets that will probably be answered in the next few hours (and we only have queues after weekends). So if your definition of non existent support means not answering your immediate question within 10 minutes, then yes we have non existent support and will continue to have non existent support. Im not hiring random support agents from India and driving up costs of our units by 20% to satisfy this urge. All our support emails are answered by my team that work on the units themselves (including myself) and can actually answer your question, but this means you might not have a response for a few days. Now in terms of the nodes issues we are not seeing anything on our test systems, nor any widespread outages (my first thought was the ordinals/BRC-20 fiasco causing issues, but even with 1G mempool we have plenty of memory overhead). Second issue could be if you have a recent system (bought after Nov/Dec last year), we switch to a new controller heatsink and some units were assembled without the heatsink adhesive properly installed. If your node/system is shutting down, or your your MCU temp (the one on the top menu bar) is higher than 85c then this could be the issue. You'll need to remove the side panel the MCU is on and remove the MCU and reseat the heatsink (press down on it hard for at least 10 seconds to make sure the thermal pad is stuck on there well). Second step if your still having an issue is to reflash your SD card to make sure there is no corruption that could be causing system instability, if your still having node issues email us with two below logs: take a screenshot of system monitor while the node is still active (preferably after it has started up and synced), you can open a terminal and type htop for this send log file of bitcoind, its in the Bitcoin folder inside the node drive (debug.log) So it appears the node goes offline only when I connect to it after a few minutes (via Sparrow Wallet). Can it be because it is overheating, connecting to the node actually makes it run hotter?!? I bought the unit couple years ago and I just cleaned it so it shouldn't overheat? The fan is on Auto as well. No, unless sparrow wallet is doing something crazy when you connect to it. Can you email us your logs after this happens (logs are in node drive /Bitcoin folder). |
|
|
|
Hello,
I've been running the BTC miner with full node for a while now, but since this week end the node randomly goes offline and does not reconnect.
Anyone having this issue? I need the node to stay online.
The miner is still mining but the node just goes offline
I have been having the exact same issue, which means it's not us but something wrong on futurebit's end. I wrote them and they never wrote back Good luck trying to get support, its almost non existent, if not EXTINCT... Not sure where you are coming up with this, we respond to every email and im looking at our support que right now and there are only 10 outstanding tickets that will probably be answered in the next few hours (and we only have queues after weekends). So if your definition of non existent support means not answering your immediate question within 10 minutes, then yes we have non existent support and will continue to have non existent support. Im not hiring random support agents from India and driving up costs of our units by 20% to satisfy this urge. All our support emails are answered by my team that work on the units themselves (including myself) and can actually answer your question, but this means you might not have a response for a few days. Now in terms of the nodes issues we are not seeing anything on our test systems, nor any widespread outages (my first thought was the ordinals/BRC-20 fiasco causing issues, but even with 1G mempool we have plenty of memory overhead). Second issue could be if you have a recent system (bought after Nov/Dec last year), we switch to a new controller heatsink and some units were assembled without the heatsink adhesive properly installed. If your node/system is shutting down, or your your MCU temp (the one on the top menu bar) is higher than 85c then this could be the issue. You'll need to remove the side panel the MCU is on and remove the MCU and reseat the heatsink (press down on it hard for at least 10 seconds to make sure the thermal pad is stuck on there well). Second step if your still having an issue is to reflash your SD card to make sure there is no corruption that could be causing system instability, if your still having node issues email us with two below logs: take a screenshot of system monitor while the node is still active (preferably after it has started up and synced), you can open a terminal and type htop for this send log file of bitcoind, its in the Bitcoin folder inside the node drive (debug.log) |
|
|
|
|
You wouldn't be able to get much higher exhaust heat from air cooled devices even if you ran ASIC temps higher, air is such a bad carrier of heat it requires ALOT of it to move significant heat (ie high RPM fans) which means that air will be significantly cooler than what its trying to cool.
There are some silicon formulations in fabs that can be run over 100c continually, and here it gets interesting because you can use distilled water to cool the ASICs directly and actually boil the water, steam is a much more useful wast heat. We are playing around with some of these types of ASICs.
|
|
|
|
Is there one? If so, what is it? I've reached out through multiple direct channels for help with a failed unit < 90 days old and have received no response (yet). Is this typical post sales support?
If it's a warranty case, check back with your reseller first. He should be able to directly sort that out with you or file a support case on Futurebit side. I bought direct from futurebit and have tried all the usual support channels (chat, email, replying to my order email etc) over the past week but no response. Wondering is that was to be expected or an anamoly? We respond to all support emails and as far as I can see we dont have any open tickets right now so maybe your email is not going through? FYI all Apollos comes with a standard one year warranty. |
|
|
|
~snip~ Well someone here solve the last ckpool solo block using 10TH worth of Apollos  Probably why the pool has attracted more Apollo users since then. The benefit is that you are using your own node to construct and broadcast the bitcoin block if found, with ckpool, the pool itself has control over the block creation (and therefor could theoretically censor transactions). Until we release our own implimination of solo mining I would not suggest trying to do this on your own unless you know your node is well connected to other pools (which is hard to do on an individual level). We are working with pool partners to directly connect all Apollo solo miners to major pools once our implementation launches. You mentioned in theory ckpool can censor transactions, wouldn't exactly the same statement apply to the "Apollo Pool" since you said the plan is to connect to other servers? At the end of the day using any pool you need to trust the person behind it. By connect to other servers I mean your node will be highly connected to the major mining pool backbone for faster block propagation. You would still be your own "pool" and mining your own blocks/transactions. FYI cool functionality we are building out is that solo mining will essentially be your own stratum pool (so the pool will run locally on your device and your hashboard will be connected to that internal pool), but the fun part is that you can use it as your own pool infrastructure, so if you have other miners (even non Apollo hardware) you could point all of them to the Apollo and solo mine. "Pool in a box" |
|
|
|
Any updates on the new version of the Apollo?
Not yet, had to do a lot of board level redesigns on prototypes but making progress towards production version |
|
|
|
For solo mining directly on your Apollo node, you can install Docker, then build and run a docker image of the solo ckpool using this repository: https://github.com/golden-guy/docker-ckpoolSince I don't have a full node Apollo, I cannot test and verify this myself there unfortunately. But I tested this successfully in similar setups on other SBCs (RPi/Odroid) running Debian/Ubuntu - and the Apollo's OrangePi SBC running Armbian should support the Docker installation as well, as documented here: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-run-dockerWould be great if somebody tried and can give feedback if that has worked out. At least that would be a viable workaround for now for those who feel the itch to solo mine on their Apollo node. ckpool is solving a block more often since I've add my 3 Apollo miner a month ago and it's attracting more miner.s We went from 26P to 98P. The only problem is it's not me solving the blocks with my 14 Th/s Is there any benefits using the docker as oppose to just entering the pool info? Well someone here solve the last ckpool solo block using 10TH worth of Apollos Probably why the pool has attracted more Apollo users since then. The benefit is that you are using your own node to construct and broadcast the bitcoin block if found, with ckpool, the pool itself has control over the block creation (and therefor could theoretically censor transactions). Until we release our own implimination of solo mining I would not suggest trying to do this on your own unless you know your node is well connected to other pools (which is hard to do on an individual level). We are working with pool partners to directly connect all Apollo solo miners to major pools once our implementation launches. |
|
|
|
What does it mean "Dead Project" ??
Let me quote the Apollo BTC "Getting Started document"
----------------------------------
The Apollo Full Node runs the latest release binaries from bitcoincore.org, and is automatically configured and setup at the system level. It will start syncing a clean chain state from block 0 on your nvme SSD on first boot, and is capable of downloading a full unpruned node on its 500 GB drive with a 1-2 year buffer. This is the core that will enable us to release additional apps and services in the coming months and years (solo mining, block explorer, Lightning network all planned in the short term), and allow you the user to verify your own transactions and chain state without needing to trust anyone else.
-----------------------------------------------------------------------------------
Solo mining, block explorer, Lightning network and such have been promised for a long time, and in ("short term"), and having the chance to solo mining my own node was one of the features for which I decided to buy an Apollo.
So I can understand the difficulties, delays, all is legit,...but I cannot accept a "dead project", I would like to have answers to this.
It does not satisfy the premises underlying the moral contract between the seller and the customer.
Is there a responsible who can answer, please?
I'm kindly inviting the one who is responsible for this project to give clarification to all of us.
Thank you very much.
D.
Already answered this, we decided late last year to scrap all updates and refresh the entire OS/web UI with a modern architecture since the Apollo UI is over 5 years old now. Thats probably going to delay all these features until later this year. Also the Apollo UI is open source, anyone can modify it and do whatever they wish with it. Ive also said this multiple times, FutureBit is not a VC funded company with dozens of full time engineers. It's a small group of people working part-time when we can, and the whole company essentially operates as a non profit. Anything beyond the hardware we provide is a perk, and like with everything bitcoin is up to the individual to DYOR and install the apps and services you want. Yes we want to make one click installs to make this easy for everyone, but our main focus is hardware (and past year has been focused on Gen 2 that all Apollo Gen 1 will benefit from software wise). |
|
|
|
Just use ckpool, that's what I'm doing
The point of mining solo directly on our node is it might be a little bit faster. Any fraction of a seconds counts to get the edge. ckpool is not the best with one block per 4 months and all the intermediate connections. FutureBit told me solo mining was not ready for release yet. Hopefully soon. Solo mining to your own node may have the opposite effect. ckpool's VPS is in very well-connected paid datacentre, and most likely connected to maximum amount of 125 peers. ckpool can push the block to 125 connected nodes, and to the entire world, in a matter of few seconds. What is your home upload? Most likely in tens of Mbits or slower, no match for 1Gbit upload from datacentres. If your block is not propagated well, then 20ms delay you save by not connecting to ckpool means nothing if you propagate your block in 30000ms (30s) and by then someone faster pushes hit block and yours become an orphan. Currently my node is connected with 18 other nodes and upload for a few kb nonces cmon u dont need 1Gbit. I just bought this full node package for mining the own node. Sure ck.pool is not bad and the only option right now not supporting the big boys like ant/via etc. 18 connections? That's very low. I connect ONLY via Tor, no IPv4/v6 connections as all, and have 32 peers. I was reading a bit today about block propagation in Bitcoin network and apparently it's still an important factor, especially for big miners who hit blocks often. You must be extremely lucky to hit the block within your lifetime if you own one, or even 10, Apollos. Then, you must be extremely unlucky to have that block orphaned by not propagating fast enough, but it is possible. Yes this is one of the reasons we have not released it yet, we are building infrastructure on the backend that will allow each individual node to connect to the back bone of the main pools. Number of connections is not as important for new block propagation as how close your node is to the nodes of main pools. Its in the interest of small miners to send the block to the main pools first, because as soon as the large pools node sees the Block they will stop mining on the previous block header and move work immediately to the next. If a small miner is on the fringes of the node network, by the time the block propagates to the pool nodes they could have very well found another block and will orphan yours. This would be a horrible outcome, your device actually finds a 6BTC valid block but you lose out because of slow propagation. We are currently spinning up super nodes that are on fast connections and directly connected with major pools, in a future update all futurebit nodes will have our infrastructure nodes as a seed nodes, so once we enable solo mining direct to node if you do find a block the first "hop" will be to our backbone super nodes, so at worst your block will be two hops away from all the major pools. This should significantly increase odds of small solo miners not orphaning blocks, but want to make it perfectly clear its still worse than solo mining directly to ckpool for example (and the degree of how much worse depends on your upload speed). If your on dialup or DSL you should not be solo mining on your own node, and would not recommend anything less than a 30-40 mpbs upload speed and direct ethernet only (worst case 500ms delay with ~1.5MB blocks). Not bad but obviously not as good as a 30-50ms upload speed of a few kb pool share to ckpool. So for example to be on par with solo mining to ckpool you would need beat ~50ms share propagation to ckpool + ckpools 50ms block propagation (assuming his setup is near perfect which I would assume it to be), so 100ms for ~1.5MB you would need a 120-150 mbps upload speed. I also dont want to discourage people and blow the issue out of proportion either, bitcoin has 10 minute blocks for a reason its extremely unlikely anyone will find two blocks within a few seconds of each other...for each second you delay uploading a block there is 1/600 chance you'll orphan the block. This is also a good exercise in remembering why we won the block size war...if we did not no one on low end hardware or slow internet connections would ever have a good chance at solo mining... |
|
|
|
Good afternoon! I’ve had my Apollo running for just under three days now. I’m having two issues: the first, I’m having trouble setting up port forwarding, and I’m stuck on 10/32 connections. I’ve logged into my router admin page, and I updated the port forwarding section with my units IP, and TCP + UDP, with WAN Port 8333~8333, LAN host port 8333~8333.
Any ideas how I can remedy this?
My second issue is, this morning my internet connectivity dropped out (only on the Apollo, the home internet never stopped working), and on the dashboard, I was prompted with a “Disconnected” under eth0 network (direct Ethernet connection) - this happened without any apparent reason, and I was no longer able to access the admin page from the router. I’ve since did a hard reset on the router, but that isn’t solved the issue.
My only workaround for the second issue is to connect to wifi, which I’ve been able to do, but I would really like to sort out the hard wired connection issue. My Apollo won’t show an Ethernet connection at all even though the green light turns on when I plug the cable in to the port.
I’m also seeing a red “internal error” message when I first launch the Apollo dashboard, right at the top of the page overtop of where I see the online status and TH/S.
I’ve emailed Futurebit, but thought I’d try here too.
Thanks!
Your node wont show more than 10 connections until it is fully synced, so it's not a port forward issue. As for wifi/ethernet, this is a know bug in the underlying system, if you enable wifi then try and connect ethernet it wont work. You need to disable the wifi interface in the system menu (not the dashboard, you need to connect to the system via HDMI), then ethernet will work again. |
|
|
|
They are different products for different types of people.
Well unless you read and write kernel code you have no business mining this should be told to people. Stay strong big farms! Ooo the big farms are finally realizing plebs mining in masses are going to be a threat to their USD profits the future  |
|
|
|
Brand New Setup, multiple issues.
Resolved Issue
First one was Router/ Ethernet connection did not work - Netgear Router completely stopped working now, does not allow Reset. Whatever. Now logged in direct with TV HDMI. My sincere apologies for inconveniencing your Twitter DM Support.
Current Issue 1:
Now getting failure messages on disk space:
I have Rebooted and now it says
"Low Disk Space. This computer has only 0 bytes disk space remaining."
At "System Utilization" it says:
Disk / Usage 13.88GB/ 14.05GB
Disk/ media/ name usage 7.3GB/ 915GB
Issue 2:
At the "Pools" tab I have my Braiins details entered and saved (took saving 3 times before it stuck; have checked the Braiins details multiple times and all characters are correct.
But at Miner>Dashboard>Pools it says:
btc.viabtc.com:3333 Username port forwarded.futurebit
Checking at my pool.braiins.com Dashboard, my Hashrate is not being registered.
What is happening? Why am I not getting my Hashrate to my Pool, it instead going to FutureBit???
I have completely Rebooted and also that did not resolve issue.
Sounds like there is an issue with your nvme drive and node is syncing to the SD card. Have you reached out to support via email? |
|
|
|
Apollo 2 teaser on Twitter.
I was hoping for more info on the forum
Yep, keen as to see more details on this! Will drop the info here and email subscribers first....really excited for this one feels like 8 years of work finally manifesting into the device I always dreamed of making! FYI have lots of DMs about current Apollo Gen 1 owners and recent buyers...dont worry all Apollo Gen 1 owners will get significant discounts (we always sell our first Batch pre-orders at cost to current customers), and you'll be able to plug the upgrade directly to the current unit (controller and software updates will be the same for Gen1/2). Oh and here is another teaser just for you guys  This is why we haven't pushed all the software updates I wanted to get out last year....we decided halfway through the process that the Apollo UI (now 5 years old) is way outdated for the upgrades we were building and decided to scrap the whole project and rewrite from scratch. It will take longer but the upgrade will be worth it! |
|
|
|
Polli at arms length. Why not removing Apollo from its original case? I did that, and it's been running fine for many months. Still using original fan. Without the case, air intake is excellent and it may lower your fan speeds/temperature. https://imgur.com/a/3D2CvsaThe noise from your naked Apollo does not matter where you have installed it. All the other components in the PC case make noise anyway. I am aiming at much quieter operation, to gently heat a bedroom in Winter, for example, without noise. The limiting factor is still that I cannot get a fan that will run slower than 1800rpm but will also run very fast when needed. And I think that maybe (only maybe, I have not systematically tested that) removal of the housing makes part or all of the Apollo hotter: - the entire metal housing is a heat sink - the hottest components I can find are located on the circuit board close to the 12V connectors. See IR photo below. This area receives forced airflow when the housing is in place, the air must flow over these hot components to enter the large heatsink. Without the housing, those 2 hottest components might have to rely on more passive convection cooling and maybe they get hotter than with the housing in place.  Correct the whole case is screwed into the heatsink and provides a good amount of passive radiative cooling that also helps keeps fan speeds slightly lower. Those are the buck regulator fets, and yes they are the hottest part of the power stage and constricted airflow through the back opening helps cool them. They will get hotter if you remove the case. FYI these are designed to operate at 100C, but if you are running custom settings that allow for over 200 watt power I would stick some small heatsinks on these as they would be the first to blow from overclocking. |
|
|
|
|
Show Posts
