Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Hardware
Re: Official FutureBit Apollo BTC Software/Image and Support thread
by
PennyBit
on 15/07/2024, 19:50:51 UTC
Quote from: tarator40 on Today at 08:05:35 AM
Quote from: PennyBit on July 14, 2024, 10:02:28 PM
Quote from: tarator40 on July 14, 2024, 07:40:04 PM
Quote from: PennyBit on July 13, 2024, 07:56:27 PM
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.
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:
Code:
sudo /opt/apolloapi/backend/apollo-miner/miner_stop.sh
sudo /opt/apolloapi/backend/apollo-miner/miner_start.sh
ignore the errors Wink
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.
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...

Sir, I believe you are correct. Also, I found another much longer ["GraphQL" error with more textual information] which happens when I just have the node running (or once when I started the node with the miner already running) but it is very scarce and random, although from what I have been able to read before it disappears it has similar text throughout the error. I will start trying to capture it in the future - but it is random as heck - lol. Just a note for readers - this is all a headless operation on v2.0.5 and may not affect direct connections with monitors/keyboards. I don't know for sure - but feedback would be welcome.