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

Yes - using 2.0.5. I assume it's a counter variable bug in the UI code. When some miner stat grows above a certain value - the UI gets broken and cannot properly handle it.
However, I am not sure whether we get any mining penalty by restarting the miner every couple of days...

Thanks for the suggestion. I'm assuming you are on v2.0.5 as well which would indicate that the bug did not get fixed from v2.0.4.

I am experiencing the same issue. Also using the unit in headless mode (no monitor/kbd - web only). Workaround is to restart the miner process. However you cannot do it via the web UI. Login via ssh and then:
ignore the errors

I'm attempting to make the unit even quieter, I don't really mind lowering my hash rate. I found the system service `futurebit-miner-v2`, what are the actual limits of these parameters? The UI configuration only allows up to -brd_ocp 30 -osc 25 -fan_temp_low 69 -fan_temp_hi 89.

Hi Apollo Support,

I received a new Apollo 2 (Full Node) on Wednesday and it has finally finished syncing (Hash Rate 0 during sync).

No matter what I do (start, stop, reboot, pool, solo, eco, balanced) the miner sits at 0 h/s

I have checked ckpool and there is no hash rate being displayed.

I have download a fresh image (MC2) and setup with a new SDCard and still the same issue.

Front Status Light is flashing white.

regards

Kim

0.00 H/s

0.00 H/s - 1 hour average

0°C - Miner temperature
42°C - System temperature
0% - Hardware errors

0 watts - Power Usage

5% - CPU usage
31.38% - Memory usage
47.76% - System disk usage


Current block - 852,150

Details

04:22 - Minutes since last block
619.52 GB - Blockchain size
617.15 EH/s - Network hashrate
About 79 trillion Difficulty
31/32 - Connections
30.73% - Remaining space



futurebit@futurebit-apollo-2:/dev$ sudo screen -dr miner

*** BOARDS STAT DELTA (10 secs, 1 boards, 44 chips):
BRD  SOL  ERR   bySol  E/S  byJobs  CR  mW/GHs  EPWC
  0    0    0  0 GH/s   0%  0 GH/s   0    0.00     4

*** BOARDS STAT TOTAL (878 secs, 1 boards, 44 chips):
BRD  SOL  ERR   bySol  E/S  byJobs  CR  mW/GHs  EPWC
  0    0    0  0 GH/s   0%  0 GH/s   0    0.00     4

*** MASTER STATS PER INTERVAL:
INTERVAL   sec  bySol  byDiff  byPool  byJobs  CHIP GHs  mW/GHs  SOL  ERR  ERR(%)  CR
  30 sec   10s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
   5 min  100s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
  15 min  302s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
  1 hour  878s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
   total  878s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0

*** MASTER STATS:
Date: 2024-07-14 12:47:56, UpTime: 878 secs, mbHwVer: 0x0, osc: 0
Smooth osc: step: 1, ignore broken pwc: 0
Found boards:   1
Broken SPI:     1

*** POOL STATS:
Pool: host:port: solo.ckpool.org:3333, user: *******************.Apollo2, diff: 10000, reconnects: 1
extraNonce1: 942d6d72, extraNonce2Size: 8, jobs: 9, rollingEnabled: 1, rollingMask: 1fffe000
INTERVAL   sec  JOBS  clean  SHARES  ok  err  POOL sol  minRespT  avgRespT  maxRespT  loss  INSERVICE       %
  30 sec   10s     1      0       0   0    0         0         0         0         0  0.0%        10s  100.0%
   5 min  100s     4      0       0   0    0         0         0         0         0  0.0%       101s  100.0%
  15 min  302s    11      1       0   0    0         0         0         0         0  0.0%       302s  100.0%
  1 hour  878s    32      3       0   0    0         0         0         0         0  0.0%       878s   99.9%
   total  878s    32      3       0   0    0         0         0         0         0  0.0%       878s   99.9%

*** EVENT STATS:
Legend: SE - subbsribe error (initialising issue)
        DIFF - diff changes, REC - reconnects, RECE - reconnects on error
        SHARES - sent to pool, PSS - pwc shares sent, PSD - pwc shares dropped
        MRS - master received shares, DJS - default job shares
        SJS - stale job shares, DUP - duplicates, LDS - low diff shares
        BDS - big diff shares, BTS - below target shares
        PR - pwc restart, SO - stat overflow
INTERVAL   sec  SE  DIFF  REC  RECE  SHARES  PSS  PSD  MRS  DJS  SJS  DUP  LDS  BDS  BTS  PR  SO
  30 sec   10s   0     0    0     0       0    0    0    0    0    0    0    0    0    0   0   0
   5 min  100s   0     0    0     0       0    0    0    0    0    0    0    0    0    0   0   0
  15 min  302s   0     0    0     0       0    0    0    0    0    0    0    0    0    0   0   0
  1 hour  878s   0     1    0     0       0    0    0    0    0    0    0    0    0    0   0   0
   total  878s   0     1    0     0       0    0    0    0    0    0    0    0    0    0   0   0

FAN INFO:
Slave   RPM
    0  1480

Temp(C) (min/avr/max): 0 / 0 / 0

*** MASTER-SLAVE SPI BUS STATS:
SLAVE                       UID  B-LEN   B-CRC-C   B-CRC-L         VER  TIME  PING    M=>S    rx  err     %    S=>M    rx  err     %  SS  SD  SR  Rst  LastRstT  Packets  Time msec.  Speed(pack./sec)
    0  3D0063001251323532343337      0  00000000  00000000  0x13160100   886   343    4660  4639   20  0.4%    6114  5979  135  2.2%   0   0   0    0         0

Total packets: 4660 in 864882 ms, speed: 5.39 packets/sec
Exporting stat... [done]

Hi,
FYI - It would appear the "[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: ..." problem is still alive and well in v2.0.5. I've had my Apollo 2 for a couple of days now and it has v2.0.5 installed. I'm not sure if the "other overflow bug" you mentioned is the same issue, related, or different - but it would seem to have the same error message? In any case, I can only say that I'm using HTTP / web browser on the network and not a dedicated monitor & keyboard to the unit (if that makes a difference I don't know). I've tried both Windows 11 and Linux Mint with Firefox and Brave browsers on both machines and have the same issue after about 4-5 minutes. I've tried the reboot suggestion and again after 4-5 minutes the same error. This is just an FYI as it doesn't seem to actually be disconnecting the miner as you already clarified, although it is annoying, especially when it pops up back-to-back for 1-2 minutes and then goes away for a few minutes and then comes back to taunt me some more - lol.

If there's a fix or recent information I missed somewhere I apologize.

BTW - Everything else is pretty awesome! Hope to expand this node unit with the standard product in the future. Maybe by the time the node finally gets synchronized my Social Security will pay for it - lol.

Turned out my block chain history had a bad index when I rsync it from another machine. Did the rsync once more and that solved my issue. This thing is very well made, even software components under the hood are very clean and sensible.

I received my Apollo II but my Node tab stays at current block 0 and the details has a warning about connection refused. Says my node is not running. Not sure what else to do. I could SSH into the machine if that helps troubleshooting.

I have the Apollo BTC Full Node and two standard unts. I recently upgraded to the new software and the units continued to work and hash just fine, but recently, it looked like they stopped hashing. The miner shows online, but all three hashboards are showing inactive. The strange thing is, it looks like they might actually be hashing, but not reporting back to the dashboard. If I look at the raw data it looks like they are working. Has anyone seen this before?

I received my Apollo II. I connect to my monitor (I've tried 2 different ones now) made sure the monitor was on and connected properly. The Apollo II fan comes on and runs at very high speed indefinitely. I've let it run almost 20 minutes. No lights on the front of the Apollo. What next?
@jstefanop any advice?
[/quote]

We had a bad batch of SD cards go out last month, probably affected a couple hundred units and yours might have been one of them (image was corrupted and not caught by factory).

Just reflash your SD card following the instructions here:

https://www.futurebit.io/flashing-sd-card

FYI keep in mind latest version of etcher has some major issues, please download the earlier version linked in the instructions above.

Q: I dont see any video on my HDMI monitor
A: Your monitor needs to be powered on and HDMI plugged into your Apollo BEFORE powering on your Apollo. The Apollo will not recognize your monitor if its powered on before the monitor or HDMI cable is plugged in. If this does not work double check your input on the monitor is in the correct HDMI port. Please be aware that not all monitors will work with the Apollo (odd sized monitors, really high resolution tvs etc).
[/quote]

I received my Apollo II. I connect to my monitor (I've tried 2 different ones now) made sure the monitor was on and connected properly. The Apollo II fan comes on and runs at very high speed indefinitely. I've let it run almost 20 minutes. No lights on the front of the Apollo. What next?
@jstefanop any advice?

I have been running for a couple of weeks and get nowhere near 5 on ECO.  The average is always 3.9 or so.

That looks low, have you let the miner run for an hour and whats the 1H average? Should be over 5.5 TH/s on the low end.

You can add that but it wont matter, it takes any incoming miner connection straight via IP:3333 port.

Hey, I am running a full node Apollo II.  I am getting around 3.9 TH/S on ECO mode and the UI is showing around 45 watts per TH/s.  Any suggestions to improve this?  Thanks

Thanks John! Do i need to create a stratum something that looks like this stratum+tcp://btc.f2pool.com:1314 for my Apollo though?

I think all April orders are out right now...starting to work on May after the July 4th holiday, and should probably clear the whole backorder queue by end of may!

they would need to open port 3333 on their WAN address to point to your Apollo's internal ip address (or can be any wan port, just needs to point to port 3333 on the apollo).

What info do I need to point my miners that are currently hosted offsite to my Apollo? I’m currently solo mining from the Apollo and want to add some more hash using my other miners.

Hello,

I have an Apollo 2 that has been running fine for a couple months now. Turbo mode in my garage with on a shelf that has 360 degree air flow. The temps stayed around 74C all the time which, according to the gauge in the software was fine. I upgrade to 2.0.5 and have not been able to to use the Apollo since. It keeps shutting off. I was able to get into for a sec and turn it down to ECO mode but it died again shortly afterwards. I'm not sure what is happening. I can't get it to stay on long enough to troubleshoot. I tried to re-image the SD with 2.0.5 but, I couldn't even get through the start up page. I'm active working on downgrading it back to 2.0.4 right now. Anyone have any ideas??

I reimaged to 2.0.4. It ran for about 3-5 minutes and now it won't stay on for longer then 1 minute.