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

My Apollo II was syncing happily and up to almost 80% synced. After a restart of the machine however the Node now refuses to come online. The UI and miner is working fine but node gives error "warning
Connection refused. Your node is not running."

I tried to manually start and it still refuses to startup

Checking the syslog on console I get this


Any ideas on how I fix this. Is the blockchain database corrupt or something and how do I get this node to start up again? Do I need to clear the bitcoin DB and how can I do this?


I also notice when I do a shutdown from the UI the fans stay on high permanently. Seems the shutdown command on the UI does not spin the fans down, only stops the services. Not sure if its normal.

Thanks in advance!

Is your S19K running on your LAN or is it on an external network vs. your Apollo?

If your S19K is outside the LAN you must setup port forwarding on your router to allow traffic on port 3333 to be directed to the internal IP your Apollo.

If your S19K is inside your LAN then you should be able to use the data that is listed on the solo-mining page of your Apollo GUI.
"SOLO LAN Mining
Point any Bitcoin Miner on your local network to your Solo Pool with the following URL: X.X.X.X:3333 Username: "

Or try:
stratum+tcp://x.x.x.x:3333    And replace the x's with your internal IP address.

I cant seem to point my s19k pro with braiins operating software to my solo mining on my apollo unit.  it says invalid url.

This is a known issue, update to fix is a little late but will def be out next week.

FYI it's just a front end bug and does not affect the miner or node operation.

From this monday i got an error every 24h

[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2262360428

I did change to long btc adres then put i back to short one for solo mining to the node, dint change the errror.
When error happens miner tab in UI shuts down, node continue working.

I did write to support futurebit, they ignore my messange.

Please help.

Hardwired is the way!

I'd be willing to bet now the ping time to the same device cabled should be < or = to 1ms

Maybe this helps or maybe not . . . but I had some early wifi issues and I turned my unit on it's side and it seemed to help directionally - but I eventually hardwired it and that was much better. Also, something I found in Futurebit's guide mentioned the following . . .

"Please note our wi controller only works reliably on 2.4GHz wifi networks. 5GHz/Mixed 2.4/5GHz network
might not connect. Most routers have options to separate the networks on two separate SSIDs. Use the 2.4GHz
network to connect your Apollo if using wifi."

Cheers!

I was on wifi. I put it in the exact spot my old node was in and man its rough. I had 31 connections then it would just disconnect. I ended up moving and hardwiring.  It the internal node and all external miners disconnecting.

I check latency on wifi and im at 18ms-23ms

Hi, thanks for sharing the config! Regarding the two options:

"nonce1length": Usually set to 4 by default for solo mining.
"nonce2length": Typically set to 8 as a default.
Unless you're customizing your setup, leaving these as default values should be fine. Glad to hear your sync is complete and running smoothly! Keep an eye on that NVMe usage, though—71% seems like it's getting up there!

Hi All,

Do we need the bellow two options in the ckpool.conf or used as defaults?

 "nonce1length": 4,
 "nonce2length": 8,

BTW, Synch finished few hours ago and solo is up and running. Nvme is 71% Used  

What is disconnecting the network (are you hardwired or running on wireless?) , is it the internal node, internal miner, external miner (connected via USB) or network connected miner (on the LAN or coming through the WAN) ??

Are you seeing more than 12 connections to the node?

I have several PH remotely and locally mining through to my Apollo II full node with no issues at all. My node is hardwired though.

I highly recommend going hardwired if you are solomining to reduce network latency.

Also you may just want to actually shut the Apollo II down fully for a few minutes and restart and let the services come up gracefully without clicking on things. If that doesn't work I would reflash to play it safe.

Just set up the apollo 2 node. Fully synced and it seems to keep disconnecting. My apollo 1 node never had any issues and I just disconnected today. The Apollo 2 node has port 3333 open.

Also on the dashboard whenever it says i'm disconnected from the CKpool the power button at the top right flashes a yellow/orange and when I click it I see at the button under version a red exclamation point next to V2.0.5. Any ideas why I keep randomly getting disconnected even though my internet is still up?

Exciting! I'm so pumped to be sending some more hashrate to my own node.

Unfortunately not but I do know its a work in progress.

Awesome!! Did you ever get a rough estimate on release?

I know this was requested by me to be fixed in the next release. Hopefully we will see this soon!

I have miners about to be pointed from offsite locations to my apollo 2 node. Is there are way for me to see each offsite miner on the dashboard so I know if and when a minter is offline?

Right now I have 5 miners working but Only see 4 in the total pools and hashboards section.

Cheers

Much appreciated for your reply. Yes finally i will use only the custom settings.  LOW setup during Day Time (higher Temp and cost for Khw/h) and HIGH Settings during night time.
I set a crontab job to switch between these setting automatically. The only problem is that the GUI still shows the old values. (Not sure how to force a refresh)

I noticed also that increasing the Frequency (same Power) there are no changes in Speed,Watt/T,Temp etc.

Hard question to answer as your question actually creates more questions than answers. Regardless, the short answer is it's the luck of the silicon draw. In other words, it's simply all the variables involved that creates the inconsistency in the expected values. First of all, you're trying to replicate a hard-coded algorithm preassigned to accommodate all those variables when you try to do it via the custom settings. It's probably not going to happen. Maybe pretty close, but no cigar (which I think you already achieved). I have found for instance, if I do a simple reboot of the miner I will see a variation of 3-4 watts just because I restarted. Don't know why. And it will stay that way until another reboot in the future. Then it will change a little. Sometimes it's just because the fan is running at a slightly different speed. Sometimes it's because I'm pulling more power to other units on the same circuit and starving the Apollo a bit (guess). I've even noticed that some pools put more of a drag (slight) on my system than in other cases such as my own node or solo.ckpool. Then, of course, there's heat and humidity, and maybe even the alignment of the stars and moon phase (just kidding). All kidding aside, unless there's a good reason to try and replicate what the algorithm is doing I would sincerely suggest using the custom settings to your advantage in promoting higher hash-rates without overheating your units. Just my opinion but cheers anyway!

Hi, Just got also the New Apollo II.

Can someone confirm what are the ECO default values.

I saw in an older post that is Power:48 Freq:30 (-brd_ocp 48  -osc 30) but when i use these as custom i have totally different behavior.

After 10min

Power     Freq      Watt         Watts/T    Temp   Speed
48        30      173            35           62           4.97
eco   Mode      197            37           68           5.35


Thank you