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

The few times I've had them 9 on 1 the best share was 335B. As I mentioned in the post, I usually allocate them differently in sets of 3.

Cheers!

Hi, thanks so much for the reply. I am very sorry, I am very new in mining -- I got the apollo to learn.

How can I find the ip address of my own node on the webapp?

First of all, check whether other full node actually can initiate connection to your full nodes. You could do that by either using https://bitnodes.io/ or running full node on different device which configured only connect to your full node.

Hi guys, I have a full node and the miner running but my connections are stuck at 10. I already opened port 8333 for forwarding on my router and I am using a ethernet connection. Please advise if any of you had the same problem. Thanks!!

Thank you for the help and guidance!!

samsung pro plus sdxc 128gb was on sale at the local BB store.
180 mb/sec read 130 mb/sec write
I was looking for any new memory card with video grade speed microsdxc.

Curious, what is your BestShare from that 9 on 1 configuration?

So to hit a block, would the miner's Best Share have to be equal to BTC network difficulty?

Has Futurebit learned any more details about how this block was mined?

e.g.:

one miner or multiple miners feeding the solo node?

how many days had the miner/s been running before hitting?

What brand of microsd card did you purchase? I have been running my new Apollo2 for six days and it is 94.35% synced. It has crashed a few times during this process. It has shown usually 16/32 connections. My factory 1tb nvme card has 37% remaining space left. So, I will probably go to a larger nvme also.

Reliability.  The new card is more reliable than the factory supplied card.  Memory wise I haven't found a use other than lots of free space.  Maybe a slight bit faster on boot.  I picked a microsd with the fastest memory access speed I could find and I could only find a card with 128GB on sale.  It's rated industrial or gaming speeds and temps.  Works fine.  I believe my system is more stable.  I seemed to have more crashes with the factory 16GB. Now, almost none.  

That's my experience.

With more memory you could download more programs for your LINUX os running on the raspberry PI Or use the space for downloaded research online.  but then This machine really only has one purpose. Cache memory belongs in ram and on the NVME drive.  They are fast.  The system memory on the microsd is dedicated to OS programs.  That's proper delegation and design.

It's been reported that during IBD you only get 10 connections.  Once you get IDB=false and After the full node is running that jumps to max limit for me.

For those who are old school, I like to see the data from the logs live.  The GUI is great and helpful but when running the node and the miner I want to see real time data.  Some data maybe considered redundant but I setup two screens so I can see on the monitor next to the apollo what is running.

open up two linux terminator windows.  in the first window you can "cd /media/nvme/Bitcoin"  then "tail -F debug.log"  this will show the running output of the node debug log
in the second window you can "cd opt/apolloapi/backend/ckpool/logs" then "tail -f ckpool.log"  this will show you the miners status log.
These two windows use minimal memory.  
I also have the system monitor running. I don't keep the firefox browser up as it consumes memory.  I monitor the GUI remotely.

To me this is the breathing machine When you can see old school real time log status outputs.

And as an example my node stopped running and you get the connection refused message but don't know why.  Quickly I was able to see details on the node screens of the logs live.  I had  a nasty error database corrupted message.  I was able to easily scroll back through the log and see what happened.  I was able to restart the node and watch the recovery.  It failed with the same error database corrupt.  Then stopped the miner that continued to mine worthlessly with a down node,   Then I shutdown the system, turning it off and then back on.  system restarted and node came back to life without error and resynced.

*** Developer Suggestion***  When the node crashes During solo mining The miner does not stop mining even with error messages.  There should be a way to automatically stop the miner.  Or have the option to switch the miner over to a backup pool if the node crashes.  Most basic mining software on mining rigs had this feature to revert to a backup pool when main pool failed. Then, when the node comes back alive, the miner switches back the the node.

Is there any advantage to upgrading the MicroSD card from 16 GB to 32 GB?
Can this additional space be utilized to prevent any system issues?
I plan on upgrading to an “Industrial” grade card since it has a wider functioning temperature range than the consumer grades, and just need to decide if 32 GB will make a difference or not.

Yes, I did add the "listenonion=0" command although I don't use TOR either. I have to admit I don't know much more about those options than the little research I did on the web. So I really don't know enough to guide you into an informed decision in this regard. Sorry. But if you research "onion service" on the web along with TOR you'll get an idea if you need/want to use them or not.

Cheers!

I also use Teamviewer with a barebones pc running at home. I access it with my tablet, anywhere on the planet.

Thanks again, this will help, and I will wait until its fully sync'd before adding. I do see once the number jumps to 11 connections then drops back to 10 in a short while? Did you add the "listenonion=0"? if so what is the reason for that?

I find it easy to just leave a laptop or desktop at home on the network running and use a free version of TeamViewer. I can access from my iPhone as needed.

Guys/Gals
Does anyone have any experience with remote access to the Apollo II??
I do a lot of travel and really need to setup remote access to my miner and thought I would ask if anyone has done this previously before I start down the rabbit hole (maybe save myself some time and pain  )

What software did you use?
any tips/tricks on the process.

Thanks in advance

The display still shows 2.0.5, but after the update there are no more GraphQL errors.

I'm glad no longer have to restart Apollo II due to them!

Take a look at a post from Sledge0001 here: https://bitcointalksearch.org/topic/futurebit-apollo-ii-btc-founders-edition-full-node-review-pic-heavy-5492150

About 2/3 of the way down of his pics he gives a good example using the addnode=IPADDRESS and listenonion=0 commands

Cheers!

Thank you PennyBit for the reply. I switched it over to my piggybacked Eero hoping it might change but it looks like i might need to manually add a couple as well. Can you tell me the steps in adding the other connections? I am thinking at the "Bitcoin node configuration" and if so do I just need to add the IP address of some local nodes?