Closed sbayegan closed 5 years ago
What network are you connecting to? a private network?
based on the Status information, it sounds like the pool is not able to query the Kernel for block confirmations. Is the API on kernel configured with net
?
Pool calculates hashrate based on how often it confirms blocks, so with no confirmation, there isn't any hashpower calculatioin. You can look at the individual miner hashrate.
net
is added in the enable APIs here
<apis-enabled>web3,eth,personal,stratum,ops,net</apis-enabled>
and is using the default configuration
256 p2p://c33d1066-8c7e-496c-9c4e-c89318280274@13.92.155.115:30303 p2p://c33d2207-729a-4584-86f1-e19ab97cf9ce@51.144.42.220:30303 p2p://c33d302f-216b-47d4-ac44-5d8181b56e7e@52.231.187.227:30303 p2p://c33d4c07-6a29-4ca6-8b06-b2781ba7f9bf@191.232.164.119:30303 p2p://c33d5a94-20d8-49d9-97d6-284f88da5c21@13.89.244.125:30303 p2p://741b979e-6a06-493a-a1f2-693cafd37083@66.207.217.190:30303 0.0.0.0 30304 false 128 128
I don't know what each
@sbayegan,
Any news on your side regarding this problem? It seems like a connection issue either from the pool side to the kernel, or from the kernel to other peers.
The issue was caused by account address discrepancies in the configurations under the mining section. Thanks for following up.
On Mon, Feb 4, 2019, 10:24 AM Alin Turbut <notifications@github.com wrote:
@sbayegan https://github.com/sbayegan,
Any news on your side regarding this problem? It seems like a connection issue either from the pool side to the kernel, or from the kernel to other peers.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aionnetwork/aion_pool2/issues/17#issuecomment-460288957, or mute the thread https://github.com/notifications/unsubscribe-auth/ALNqIBkKN44F9-FjqAjqnZckdWr7CYvRks5vKFCpgaJpZM4Y-94Y .
Thanks! Can you close this ticket?
I've cloned this pool and have set it up on a Ubuntu 16.04 machine. The pool is connected to a Kernel and a miner is connected to it.
The miner is submitting shares that are getting accepted by the Daemon but are never confirmed and are not showing up on under the "Last Mined Blocks" on the pool's home page.
When I log into the pool database and look at the blocks table, I see that the "status" of the most recent blocks is "pending" but "orphaned" for all of the other remaining blocks. None of the are confirmed.
Pool hashrate is also stuck at 0 and is not being updated, this is probably because no blocks have been properly mined yet as explained here
No errors are logged by the mining pool either!
Does anyone know what is causing this problem?