New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
got no confirmation from server! busy? #283
Comments
Are you sure you have the right mining info and submission url? |
Pretty sure: https://50-50-pool.burst.cryptoguru.org/ under Info tab
|
When I configure the connection using the -s option, I also get an error: 20:12:33: Mininginfo I can ping 50-50-pool.burst.cryptoguru.org just fine: $ ping 50-50-pool.burst.cryptoguru.org |
Could this issue be due to a defective plot? I now changed the pool url of miner A to another miner B running creepMiner (as a forwarder) and now the deadlines of miner A are confirmed. But once miner B submits those deadlines to 50-50-pool.burst.cryptoguru.org the same issue occurs. The deadlines found by miner B however, are confirmed just fine. |
Ok, must have been due to a defective plot. I replotted and it works now. |
Version: 2.8.0
OS: Debian 9
19:29:14: Dir /plots/disk_1 read in 4.016s (~73.08 MB/s)
19:29:14: 1 file (1.15 TB)
19:29:17: Wallet: nonce found (1m 18d 00:53:26)
19:29:17: nonce: 4,254,360
19:29:17: in: /plots/disk_1/12374030639820508813_0_4809000_4809000
19:29:17: Processed block 450,646
19:29:17: round time: 6.817s
19:29:17: best deadline: 1m 18d 00:53:26
19:29:17: Wallet: nonce submitted (1m 18d 00:53:26)
19:29:17: nonce: 4,254,360
19:29:17: in: /plots/disk_1/12374030639820508813_0_4809000_4809000
19:29:45: Wallet: got no confirmation from server! busy? (1m 18d 00:53:26)
This is happening with all my deadlines. This is the config I am using:
"urls" : {
"miningInfo" : "http://50-50-pool.burst.cryptoguru.org:8124",
"submission" : "http://50-50-pool.burst.cryptoguru.org:8124",
"wallet" : "https://wallet.burstcoin.ro"
}
Any suggestion how to debug this issue?
The text was updated successfully, but these errors were encountered: