Official FutureBit Apollo BTC Software/Image and Support thread

[jstefanop]

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).

[Satayasat]

"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."

You are not the only one, I am having the exact same issue. My node runs fine until I connect remotely to Sparrow, after which it randomly shut down in minutes or hours.

[dmanhump]

"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."

You are not the only one, I am having the exact same issue. My node runs fine until I connect remotely to Sparrow, after which it randomly shut down in minutes or hours.

Same troubles for a while now. No luck fixing the issue but I also have verified that the node goes offline hours after connecting the latest release of Sparrow. Node stays up as long as it is not connected to my wallet. Was not happening before I updated Sparrow to the latest release.

[MrMik]

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 think the fault is in the OrangePi, because the Apollo still mines as it should when I connect it as a Standard unit.

It had been hashing and node-ing away happily until it suddenly stopped to send hashes to the pool, so I had a look.

Turning off the power and turning it back on did not lead to the usual unsupervised resumption of hashing and sharing operations.

Then, it started working again for no apparent reason and I did not post this, that was a few weeks ago.

But now it's playing up again, the connection to the pool is strangely intermittent, see image. Its a full node and a standard node.




The other issue is that the HDMI does not reliably connect to a monitor, and the resolution is all wrong and very grainy.

Another miner is running fine on the same pool and WiFi connection.

[MrMik]

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.

[jstefanop]

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.

[flyingbit]

Hi,
I'm a new Apollo BTC standart unit user, which I control from RasPi. I learned how to start, and stop mining - everything is fine here. I only can't figure out how to safely turn off the standard unit, so it can be disconnected from power? I want to understand how to avoid incidents when I'd need to remove the miner from power.
The second topic is that the stop script which use python inline command, to from what understand, reset the hashboard, is failing while piping to /dev/ttyACM0:
termios.tcsendbreak(3, 0)
termios.error: (32, 'Broken pipe')

What can be the reasons?

Any help is welcomed Thanks, best regards!

[walkerduncan]

HI All,
Running apollo btc full node and 2 miners. Up and running for 2 weeks no issues.

I searched for my node on bitnodes and it was unreachable, even though i have steady 30-32 connections.
1) i restarted my router/modem and also the node - unreachable
2) I tried reaching when there were definately available connections - unreachable
3) I tried both my ipv4 and ipv6 ip address - unreachable

Any advice there appreaciated

Second issue/question
I turned on TOR, restarted the node, and after 24 hours i still have 0/32 connections
I know it says connections can take longer, but what is a reasonable time to start having connections?

I run the node simply to support the network. happily.  Ideally I would be able to reach it on bitnodes to monitor my rank.

Thank you for any advice!!

[SG11]

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?

[jstefanop]

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).

[zcpleb]

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.

[macpilot]

Anyone been able to min on lincoin? whenever I change the pool address the miner won't start. When I change it back to slushpool it works flawlessly.
 I tried it with and without stratum+tcp://

Thanks

PS. any news on the solo mining upgrade? ;-)

[chrisism]

I am selling my FutureBit miners.  Is there an appropriate forum to post on this site?  --Thanks

[nullama]

I am selling my FutureBit miners.  Is there an appropriate forum to post on this site?  --Thanks

Yeah, there's a marketplace section, for a Miner it should be on Goods: https://bitcointalk.org/index.php?board=51.0 or inside there, in Computer Hardware: https://bitcointalk.org/index.php?board=75.0

[chrisism]

Yeah, there's a marketplace section, for a Miner it should be on Goods: https://bitcointalk.org/index.php?board=51.0 or inside there, in Computer Hardware: https://bitcointalk.org/index.php?board=75.0

Thanks for the guidance!

[MrMik]

What is the best process to tune an Apollo miner?

I have a more powerful PSU available and have reduced the noise to low enough to run 2 Apollos in the bedroom.

How do I find the maximum heat output and hashrate without drastically reducing the durability of the ASICs?

I can easily find the highest power setting that allows me to run the miner with an acceptable noise level, but how do I determine the best hashrate for that power level?

[polargeex]

Anyone been able to min on lincoin? whenever I change the pool address the miner won't start. When I change it back to slushpool it works flawlessly.
 I tried it with and without stratum+tcp://

Thanks

PS. any news on the solo mining upgrade? ;-)

Hello,

I'm newbie in mining but i hold few differents crypto.  I received my futurebit last week. On mine same behavior with inactive miner.
I tried doge.zsolo.bid:8057 for dogecoin and  solo.ckpool.org:3333 for BTC.

I went back on this thread and you talked that solo doesn't work. What does it mean? Any solo miner's don't work?

[jstefanop]

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.

[Hotstryker]

Is anyone here successfully running BTCPay Server on their futurebit and getting it to connect to futurebit's node?  I'm having an issue and not getting help from BTCpay crew so was hoping someone here can assist.

[zcpleb]

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?