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

I think the default is 30 which is a nice number

There is a max connections setting, on the node. What would be the recommendations for setting this?

Central Pools are the main centralization issue with bitcoin mining right now. The Apollo BTC/II circumvents this entirely by running your own "pool". You cant get anymore decentralized in mining than this.

It's great what ocean is doing, but they are still a central entity in the mining peg and can easily be controlled/shutdown etc.

yea thats right.

Hi jstefanop,

Re "screen -dr node", you mentioned that "as long as you see getblocktemplate messages your solo mining".

I don't see any GetBlockTemplate messages but I do see continuous CreateNewBlock() messages. Is that what you meant? Just want to confirm please.

Thanks!

As OCEAN's explains Stratumv2 did not allow to accomplish what they wanted.
I am NOT solo mining, so when I mine with OCEAN am I currently the one to build my one block template? I don't think so. 10x more decentralized in what sence? To my understanding OCEAN's concern is centralization of building block tempaltes. Can I configure my FutureBit Apollo II Full Node BTC Miner to build block templates rejecting ordinals while still mining in a pool?

Overview screen shows averages when mutiple units are connected. Need to fix that formatting error and rethink this.

It is indeed the board current, it's how we get total watts the miner is using.

Hi jstefanop,

Haven't heard from anybody on this question, can you help?

In the first image below, I don't understand why my stat values jump to these laughable odd placement values when I have two Apollo II standard units connected to my Apollo II full node unit. It doesn't occur with a single unit connected to the Apollo II full node unit, only when I have two connected.

https://ibb.co/7kyQGKH

In this second image below, I simply don't know what the "36.97A" is referring to. I have to assume there's no way it's referring to amps. Anyone know?

https://ibb.co/FVty8p1

I'm on v2.0.5.

Thanks for any help.

Cheers!

If there is wide support yes, wasted my time with stratumv2 with no pool support so not going down that route again.


Not sure why you would want this over what the Apollo II already provides, which is a self hosted solo pool to your own node, its 10x more decentralized than what datum wants to do (which at the end of the day is another stratumv2 implementation with the same central control and custodian issues).

Try a different monitor or find the IP address of your unit and SSH into it to see what is going on

Hello!

Will FutureBit consider supporting the emerging DATUM protocol soon?
I wish my FutureBit Apollo II Full Node BTC Miner to use DATUM.

https://ocean.xyz/docs/datum

Hello, we already tried that image that you highlighted in this last message, but it is the same one that we tried the first time. The 1.93 GB MCU2 version. And it does the same...

 And the version of etcher is v1.18.11
The same one that happened to us
 The failure is very rare... and after several tests it remains the same...

Read message 1 the setup guide?
Once it reaches the login screen, type in "futurebit123" as the password.

Hello all,
I just plugged in for the first time my Apollo II, and when I log into the web interface, it asks me to input a password in order to sign in.
Do you know if there is a standard admin password for initial set-up?
Thx!

Has anyone rented Hash power and pointed it to their own node? I've been thinking about doing that but I've been seeing that a lot of them need to be pointed to a solo pool with high differential and I have no idea what that means or how to check and adjust the differential of my Apollo node.

Any insights?

The reindex option is coming in a future update

I would reformat the drive and start a fresh system

I hate to sound like the person on the typical "help line" . . . but honestly, it sounds like you may just need to reformat the node drive via the web based UI with the Format Node SSD selection under SETTINGS / EXTRA. Give it enough time to format (there's no status bar). Once formatted you can either start node (if it doesn't start automatically) or reboot. Personally, I prefer a fresh reboot. That should do it (unless the actual drive has went bad or maybe it's not seated all the way).

That's my best guess. Sorry.

Cheers!

Just got my apollo II full node.  The tape on the microsd card I understand for transport but I think it creates issues with card seating in the slot.  I had boot issues until I removed the tape, re seated the card,  then the apollo booted fine.

But here is my issue. Miner started and works fine.  The node started loading and loading fast connected to ethernet with 10 connections.  then about 25% in it crashed.  now I get the error message "Warning: Connection refused.  Your node is not running."

I thought it was the router but then i finally found the debug.log in the bitcoin directory on the nvme drive.  It said my database was corrupted with a write batch wrong count. see below.

2024-09-26T22:34:36Z UpdateTip: new best=000000000000002a66d9c7eb33bad96b675d9a7c4e8ecec6166e9a157152f5df height=233533 version=0x00000002 log2_work=69.887555 tx=16874573 date='2013-04-28T08:24:48Z' progress=0.017003 cache=716.6MiB(5437775txo)
2024-09-26T22:34:36Z UpdateTip: new best=00000000000000bc1bcdf0a8120e78ca915909716d8bb86340060e7ea1f98ed1 height=233534 version=0x00000002 log2_work=69.887606 tx=16874741 date='2013-04-28T08:28:55Z' progress=0.017003 cache=716.6MiB(5437858txo)
2024-09-26T22:34:45Z Fatal LevelDB error: Corruption: WriteBatch has wrong count
2024-09-26T22:34:45Z You can use -debug=leveldb to get more complete diagnostic messages
2024-09-26T22:34:45Z *** System error while flushing: Fatal LevelDB error: Corruption: WriteBatch has wrong count
2024-09-26T22:34:45Z Error: A fatal internal error occurred, see debug.log for details
2024-09-26T22:34:45Z tor: Thread interrupt
2024-09-26T22:34:45Z addcon thread exit
2024-09-26T22:34:45Z torcontrol thread exit
2024-09-26T22:34:45Z opencon thread exit
2024-09-26T22:34:45Z Shutdown: In progress...
2024-09-26T22:34:45Z ERROR: ProcessNewBlock: ActivateBestChain failed (System error while flushing: Fatal LevelDB error: Corruption: WriteBatch has wrong count)
2024-09-26T22:34:45Z net thread exit
2024-09-26T22:34:45Z msghand thread exit
2024-09-26T22:34:45Z UPNP_DeletePortMapping() returned: 0
2024-09-26T22:34:45Z mapport thread exit
2024-09-26T22:34:45Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
2024-09-26T22:34:45Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.00s)
2024-09-26T22:34:45Z scheduler thread exit
2024-09-26T22:34:45Z Writing 0 unbroadcast transactions to disk.
2024-09-26T22:34:45Z Dumped mempool: 1.3707e-05s to copy, 0.00195496s to dump
2024-09-26T22:34:45Z Flushed fee estimates to fee_estimates.dat.

multiple restart attempts return the same error
2024-09-26T22:35:36Z Using obfuscation key for /media/nvme/Bitcoin/blocks/index: 0000000000000000
2024-09-26T22:35:37Z ERROR: LoadBlockIndexGuts: failed to read value
2024-09-26T22:35:37Z : Error loading block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-09-26T22:35:37Z Aborted block database rebuild. Exiting.
2024-09-26T22:35:37Z Shutdown: In progress...
2024-09-26T22:35:37Z scheduler thread exit
2024-09-26T22:35:37Z Flushed fee estimates to fee_estimates.dat.
2024-09-26T22:35:38Z Shutdown: done

Ok so what I did was make a backup folder in the bitcoin nvme directory. Move all the files in the bitcoin directory to the backup directory in case I needed them.  Virtually deleting the database.  Then I restarted the node and now the Node is downloading the chain from the beginning.  If this works I can delete the backup database later.

Would there have been a way to recover the database through a --reindex command line?  If so what would that have been?

Quick update.  While loading the node and blockchain.  I get the random same error message "connection refused: node not running"  Each time I hit start node and the node connects and continues on.  Any reason why it keeps crashing?  This time the log only shows the last successful data block completed.

I hope this is a simple question as I've not been lucky enough to find any answers through the forum search . . . I'm on v2.0.5.

In the first image below, I don't understand why my stat values jump to these laughable odd placement values when I have two Apollo II standard units connected to my Apollo II full node unit. It doesn't occur with a single unit connected to the Apollo II full node unit, only when I have two connected.

https://ibb.co/7kyQGKH

In this second image below, I simply don't know what the "36.97A" is referring to. I have to assume there's no way it's referring to amps. Anyone know?

https://ibb.co/FVty8p1

Thanks for any help.

Cheers!

Apollo BTC or Apollo II? Make sure you have flashed the correct MCU image for your device otherwise the hashboard wont work.