Official FutureBit Apollo BTC Software/Image and Support thread

MegatronOHMICAVT

brand new

Activity: 0

Merit: 0

Quote from: jstefanop on September 16, 2024, 12:31:23 PM

Quote from: cryptocrow on September 16, 2024, 06:21:22 AM

Aha this may work. Lets see, its processing.

screen -dmS node /opt/apolloapi/backend/node/bitcoind -reindex -datadir=/media/nvme/Bitcoin -conf=/opt/apolloapi/backend/node/bitcoin.conf

Yep, next release has a "Reindex node" option before the formate node drive as away to recover the node database without going to the extreme of wiping the drive in case of hard shutdowns etc

Hi fellow Apollo node-runners. Long time follower here with a first time question, possibly on this issue above.

Updating my Apollo BTC MCU2 unit to a 2TB nvme, and also updating to 2.0.5.

Node stops sync and refuses connection, alerting disk space full. Log shown below.

The nvme drive isn't showing up when checking lsblk in command line, but the drive is functioning when the node connects, at least initially.

The -reindex command will allow node to reconnect. And also re-flashed, confirming checksum. But it will refuse connection shortly after all of this.

Would -reindex-chainstate command make a difference here? Maybe the micro SD is damaged in some way?

Please advise if anything looks familiar.

Code:

2024-11-02T02:47:19Z UpdateTip: new best=0000000000000000cfef544b24af88f6552deaea28be61cf96b10d5ccefb576c height=286202 version=0x00000002 log2_work=76.626933 tx=33033093 date='2014-02-16T15:44:31Z' progress=0.032903 cache=434.2MiB(3180596txo)
2024-11-02T02:47:19Z *** Disk space is too low!
2024-11-02T02:47:19Z Error: Disk space is too low!
2024-11-02T02:47:19Z ERROR: SaveBlockToDisk: FindBlockPos failed
2024-11-02T02:47:19Z ERROR: ProcessNewBlock: AcceptBlock FAILED (AcceptBlock: Failed to find position to write new block to disk)
2024-11-02T02:47:19Z tor: Thread interrupt
2024-11-02T02:47:19Z Shutdown: In progress...
2024-11-02T02:47:19Z opencon thread exit
2024-11-02T02:47:19Z torcontrol thread exit
2024-11-02T02:47:19Z addcon thread exit
2024-11-02T02:47:19Z net thread exit
2024-11-02T02:47:19Z UPNP_DeletePortMapping() returned: 0
2024-11-02T02:47:19Z mapport thread exit
2024-11-02T02:47:19Z UpdateTip: new best=0000000000000000860990bd046f2d7635cefc0519aaef94c3251a448e4df5e2 height=286203 version=0x00000002 log2_work=76.627072 tx=33033574 date='2014-02-16T15:49:05Z' progress=0.032904 cache=434.2MiB(3180630txo)
2024-11-02T02:47:19Z msghand thread exit
2024-11-02T02:47:20Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-11-02T02:47:21Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.90s)
2024-11-02T02:47:21Z scheduler thread exit
2024-11-02T02:47:21Z Writing 0 unbroadcast transactions to disk.
2024-11-02T02:47:21Z Dumped mempool: 0.00189343s to copy, 0.0098008s to dump
2024-11-02T02:47:21Z Flushed fee estimates to fee_estimates.dat.
2024-11-02T02:48:56Z *** Disk space is too low!
2024-11-02T02:48:56Z Error: Disk space is too low!
2024-11-02T02:48:56Z ForceFlushStateToDisk: failed to flush state (Disk space is too low!)
2024-11-02T02:48:56Z *** Disk space is too low!
2024-11-02T02:48:56Z Error: Disk space is too low!
2024-11-02T02:48:56Z ForceFlushStateToDisk: failed to flush state (Disk space is too low!)
2024-11-02T02:49:03Z Shutdown: done

heslo

legendary

Activity: 1202

Merit: 1181

Quote from: rnproject on November 01, 2024, 08:16:06 AM

Quote from: jstefanop on October 25, 2024, 06:52:37 PM

2.0.6 is finally merged on production and doing a public test before pushing to everyone next week

If anyone wants to test ssh into your device (futurebit/password you set for your dashboard) and

Code:

cd /opt/apolloapi/backend/

sudo ./update

to manually force an update

reminder can take up to 20 min to rebuild the system and it will auto reboot when finished. Close your UI tab and clear cache so your browser does not load the old version.

Please shoot any build issue or bugs...this will definitely fix all the graphql errors small number of users have seen

Sorry this took way longer than planned!

I tried forcing the update manually, but the version in the GUI seems to remain at 2.0.5.

The update log also shows it as v2.0.5 to v2.0.5.

Code:

futurebit@futurebit-apollo-2:/opt/apolloapi/backend$ sudo ./update
rm: cannot remove '/tmp/update_progress': No such file or directory
Now using node v21.6.2 (npm v10.2.4)
---> Updating API modules
HEAD is now at d6ba154 Update image_update
remote: Enumerating objects: 86, done.
remote: Counting objects: 100% (86/86), done.
remote: Compressing objects: 100% (46/46), done.
remote: Total 86 (delta 53), reused 69 (delta 40), pack-reused 0 (from 0)
Unpacking objects: 100% (86/86), 13.52 KiB | 28.00 KiB/s, done.
From https://github.com/jstefanop/apolloapi-v2
d6ba154..fd67cf6 main -> origin/main
* [new tag] v2.0.5 -> v2.0.5
Updating d6ba154..fd67cf6

Is there a way to check the Apollo OS version from the command line?

Shows 2.0.5 for me after the update as well

rnproject

newbie

Activity: 0

Merit: 0

Quote from: jstefanop on October 25, 2024, 06:52:37 PM

2.0.6 is finally merged on production and doing a public test before pushing to everyone next week

If anyone wants to test ssh into your device (futurebit/password you set for your dashboard) and

Code:

cd /opt/apolloapi/backend/

sudo ./update

to manually force an update

reminder can take up to 20 min to rebuild the system and it will auto reboot when finished. Close your UI tab and clear cache so your browser does not load the old version.

Please shoot any build issue or bugs...this will definitely fix all the graphql errors small number of users have seen

Sorry this took way longer than planned!

I tried forcing the update manually, but the version in the GUI seems to remain at 2.0.5.

The update log also shows it as v2.0.5 to v2.0.5.

Code:

futurebit@futurebit-apollo-2:/opt/apolloapi/backend$ sudo ./update
rm: cannot remove '/tmp/update_progress': No such file or directory
Now using node v21.6.2 (npm v10.2.4)
---> Updating API modules
HEAD is now at d6ba154 Update image_update
remote: Enumerating objects: 86, done.
remote: Counting objects: 100% (86/86), done.
remote: Compressing objects: 100% (46/46), done.
remote: Total 86 (delta 53), reused 69 (delta 40), pack-reused 0 (from 0)
Unpacking objects: 100% (86/86), 13.52 KiB | 28.00 KiB/s, done.
From https://github.com/jstefanop/apolloapi-v2
d6ba154..fd67cf6 main -> origin/main
* [new tag] v2.0.5 -> v2.0.5
Updating d6ba154..fd67cf6

Is there a way to check the Apollo OS version from the command line?

poonasor

jr. member

Activity: 49

Merit: 5

Quote from: Hotstryker on July 11, 2023, 01:51:23 PM

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.

I'm running btc pay server on a raspberry pi and is looking into connecting the btcnode to the apollo but no luck so far - just wondering if anyone else who went down this rabbit hole?

jstefanop

legendary

Activity: 2162

Merit: 1401

Quote from: eagleye on October 30, 2024, 12:43:09 PM

Quote from: ? on October 30, 2024, 01:28:03 AM

Quote from: jstefanop on October 29, 2024, 08:39:00 PM

Quote from: ? on October 29, 2024, 05:47:58 PM

Hey I had some issues with the Apollo2. After a week of running fine, the system wouldn't come awake when logging in so i had to turn it off by switch. It came back and had more freezing issues so I attempt to flash the sd with v2.0.5 mcu2. But Etcher gives an error message when I try to flash, "Attention Something went wrong. If it is a compressed image, please check that the archive is not corrupted. Can't configure or trim a source that is not randomly readable, skipping". Any info on this error would be great.

It's an issue with etcher, download the previous version linked in the flash guide on the support page.

Verified I was using the linked version, balenaEtcher-1.18.11.dmg. Downloaded both etcher and mcu2 again to be sure. Unfortunately still getting the same error message from etcher when attempting flash.

Have you tried a second microsd card?

I got a second memory card programmed that fine and system is running stable.

I had more problems with the supplied microsd card. Maybe the card is old. Only 16GB. The newer card has more memory and is much faster than the original supplied microsd card.

Sounds more like an image corruption issue, I would checksum the image and make sure the download didn't corrupt or try and re-download the image.

eagleye

newbie

Activity: 58

Merit: 0

Quote from: ? on October 30, 2024, 01:28:03 AM

Quote from: jstefanop on October 29, 2024, 08:39:00 PM

Quote from: ? on October 29, 2024, 05:47:58 PM

Hey I had some issues with the Apollo2. After a week of running fine, the system wouldn't come awake when logging in so i had to turn it off by switch. It came back and had more freezing issues so I attempt to flash the sd with v2.0.5 mcu2. But Etcher gives an error message when I try to flash, "Attention Something went wrong. If it is a compressed image, please check that the archive is not corrupted. Can't configure or trim a source that is not randomly readable, skipping". Any info on this error would be great.

It's an issue with etcher, download the previous version linked in the flash guide on the support page.

Verified I was using the linked version, balenaEtcher-1.18.11.dmg. Downloaded both etcher and mcu2 again to be sure. Unfortunately still getting the same error message from etcher when attempting flash.

Have you tried a second microsd card?

I got a second memory card programmed that fine and system is running stable.

I had more problems with the supplied microsd card. Maybe the card is old. Only 16GB. The newer card has more memory and is much faster than the original supplied microsd card.

rayday11

sr. member

Activity: 347

Merit: 251

Quote from: ? on October 30, 2024, 01:28:03 AM

Quote from: jstefanop on October 29, 2024, 08:39:00 PM

Quote from: ? on October 29, 2024, 05:47:58 PM

Hey I had some issues with the Apollo2. After a week of running fine, the system wouldn't come awake when logging in so i had to turn it off by switch. It came back and had more freezing issues so I attempt to flash the sd with v2.0.5 mcu2. But Etcher gives an error message when I try to flash, "Attention Something went wrong. If it is a compressed image, please check that the archive is not corrupted. Can't configure or trim a source that is not randomly readable, skipping". Any info on this error would be great.

It's an issue with etcher, download the previous version linked in the flash guide on the support page.

Verified I was using the linked version, balenaEtcher-1.18.11.dmg. Downloaded both etcher and mcu2 again to be sure. Unfortunately still getting the same error message from etcher when attempting flash.

Before reflashing I always wipe the partitions, recreate the partition and then format the card?

heslo

legendary

Activity: 1202

Merit: 1181

Quote from: heslo on October 30, 2024, 12:41:32 AM

Quote from: jstefanop on October 29, 2024, 08:38:29 PM

Quote from: heslo on October 28, 2024, 11:21:44 PM

jstefanop, just a question. Say I'm solo mining on the Apollo2 and point another device to it (a BitaxeGamma) If I then stop mining on the Apollo, does my solo pool still work? Because you can't access the Solo Mining page unless the miner is actually mining. If it indeed does still run in the background is there any way we can still look at the solo pool stats without the Apollo hashing away?

I believe it's currently tied with the miner, not sure if this was fixed in 2.0.6 or not but will double check.

you can check with

systemctl status ckpool

or

screen -dr ckpool

Sweet, I'll check that tonight and report back; currently running the 2.0.6 test as well

Can report it still runs, you just can't see it on the front end.

Any chance you can just make the page stay active all the time before the new release drops?

?

Activity: -

Merit: -

Quote from: jstefanop on October 29, 2024, 08:39:00 PM

Quote from: ? on October 29, 2024, 05:47:58 PM

Hey I had some issues with the Apollo2. After a week of running fine, the system wouldn't come awake when logging in so i had to turn it off by switch. It came back and had more freezing issues so I attempt to flash the sd with v2.0.5 mcu2. But Etcher gives an error message when I try to flash, "Attention Something went wrong. If it is a compressed image, please check that the archive is not corrupted. Can't configure or trim a source that is not randomly readable, skipping". Any info on this error would be great.

It's an issue with etcher, download the previous version linked in the flash guide on the support page.

Verified I was using the linked version, balenaEtcher-1.18.11.dmg. Downloaded both etcher and mcu2 again to be sure. Unfortunately still getting the same error message from etcher when attempting flash.

heslo

legendary

Activity: 1202

Merit: 1181

Quote from: jstefanop on October 29, 2024, 08:38:29 PM

Quote from: heslo on October 28, 2024, 11:21:44 PM

jstefanop, just a question. Say I'm solo mining on the Apollo2 and point another device to it (a BitaxeGamma) If I then stop mining on the Apollo, does my solo pool still work? Because you can't access the Solo Mining page unless the miner is actually mining. If it indeed does still run in the background is there any way we can still look at the solo pool stats without the Apollo hashing away?

I believe it's currently tied with the miner, not sure if this was fixed in 2.0.6 or not but will double check.

you can check with

systemctl status ckpool

or

screen -dr ckpool

Sweet, I'll check that tonight and report back; currently running the 2.0.6 test as well

jstefanop

legendary

Activity: 2162

Merit: 1401

Quote from: heslo on October 28, 2024, 06:10:08 PM

Quote from: jstefanop on October 28, 2024, 03:26:24 PM

cant believe it...make no mistake everyone in the futurebit community just made history today

10 years of grinding for this and its surreal...today we took bitcoin back

Congrats to you, must feel pretty awesome!

yes but back to work...one block while amazing its the first, wont change anything...need at least one block a day

jstefanop

legendary

Activity: 2162

Merit: 1401

Quote from: ? on October 29, 2024, 05:47:58 PM

Hey I had some issues with the Apollo2. After a week of running fine, the system wouldn't come awake when logging in so i had to turn it off by switch. It came back and had more freezing issues so I attempt to flash the sd with v2.0.5 mcu2. But Etcher gives an error message when I try to flash, "Attention Something went wrong. If it is a compressed image, please check that the archive is not corrupted. Can't configure or trim a source that is not randomly readable, skipping". Any info on this error would be great.

It's an issue with etcher, download the previous version linked in the flash guide on the support page.

jstefanop

legendary

Activity: 2162

Merit: 1401

Quote from: heslo on October 28, 2024, 11:21:44 PM

jstefanop, just a question. Say I'm solo mining on the Apollo2 and point another device to it (a BitaxeGamma) If I then stop mining on the Apollo, does my solo pool still work? Because you can't access the Solo Mining page unless the miner is actually mining. If it indeed does still run in the background is there any way we can still look at the solo pool stats without the Apollo hashing away?

I believe it's currently tied with the miner, not sure if this was fixed in 2.0.6 or not but will double check.

you can check with

systemctl status ckpool

or

screen -dr ckpool

?

Activity: -

Merit: -

Hey I had some issues with the Apollo2. After a week of running fine, the system wouldn't come awake when logging in so i had to turn it off by switch. It came back and had more freezing issues so I attempt to flash the sd with v2.0.5 mcu2. But Etcher gives an error message when I try to flash, "Attention Something went wrong. If it is a compressed image, please check that the archive is not corrupted. Can't configure or trim a source that is not randomly readable, skipping". Any info on this error would be great.

iomon

newbie

Activity: 5

Merit: 0

Congrats to the miner for winning this Lotto Ticket. It give us hope!!!!
Is time to leave XEC and go back to BTC..........

Do we know if it was a single miner or had redirected more TH on his solo ckpool?

Hamster123

brand new

Activity: 0

Merit: 0

Quote from: cryptocrow on October 29, 2024, 08:43:18 AM

Can anyone tell me why under Node Status I only ever see 10/32. So I only ever have 10 connections despite setting 32 connections as my maximum.

Is there anyway I can increase this? Is there some reliance on an open firewall port or something?

Thanks

I had the same issue until I went into settings-->node-->extra options-->changed max connections to 50. My primary miner/node (used for solo mining pool) is consistently connected to 49 nodes. After making the change I restarted the unit and all has been good since. Hope this helps.

cryptocrow

newbie

Activity: 18

Merit: 0

Can anyone tell me why under Node Status I only ever see 10/32. So I only ever have 10 connections despite setting 32 connections as my maximum.

Is there anyway I can increase this? Is there some reliance on an open firewall port or something?

Thanks

heslo

legendary

Activity: 1202

Merit: 1181

jstefanop, just a question. Say I'm solo mining on the Apollo2 and point another device to it (a BitaxeGamma) If I then stop mining on the Apollo, does my solo pool still work? Because you can't access the Solo Mining page unless the miner is actually mining. If it indeed does still run in the background is there any way we can still look at the solo pool stats without the Apollo hashing away?

heslo

legendary

Activity: 1202

Merit: 1181

Quote from: jstefanop on October 28, 2024, 03:26:24 PM

cant believe it...make no mistake everyone in the futurebit community just made history today

10 years of grinding for this and its surreal...today we took bitcoin back

Congrats to you, must feel pretty awesome!

jstefanop

legendary

Activity: 2162

Merit: 1401

cant believe it...make no mistake everyone in the futurebit community just made history today

10 years of grinding for this and its surreal...today we took bitcoin back

Topic: Official FutureBit Apollo BTC Software/Image and Support thread (Read 46915 times)