gethashespersec Returns a recent hashes per second performance measurement while generating.
Bitcoin clients haven't had ability to "generate" (CPU Mine) since ver 0.3.2.1. So this is meaningless for solo mining. My Solo mining setup returns a 0 as well and I am definitely mining as my hash rate, WU: and Best share: show.
Topic: 8,6 TH/S in SOLO (Read 3644 times)
gethashespersec is 0 so bitcoin-qt doesn't mine
I don't know what that is supposed to mean.
But this from your OP says differently
Avg. Hash Rate - 315 Gh/s
WU - 4658
Difficulty Accepted - 0
WU - 4658
Difficulty Accepted - 0
It says you are mining as you have a hash rate and a Worker Utility. The Difficulty Accepted will be 0 until you find a share that meets or exceeds current difficulty which would be a block finding share.
What is your Best Share: ?
gethashespersec is 0 so bitcoin-qt doesn't mine
I've tryed to solo 1 KnC Jupiter with bitcoin-qt.
1.bitcoin.conf
listen=1
gen=0
rpcallowip=192.168.0.100
rpcuser=username
rpcpassword=password
server=1
daemon=1
2.Restarted bitcoin-qt
3.In KncMiner mining tab set as pool 192.168.0.102:8332, username and password from bitcoin.conf
4.Restarted CGMiner in KnCMiner Mining tab
5.Result in KnC Miner web GUI:
CGMiner Status - Running (pid=xxxx)
Last Checked - Wed Nov 27 15:56:11 UTC 2013
Avg. Hash Rate - 315 Gh/s
WU - 4658
Difficulty Accepted - 0
6.Result in bitcoin-qt:
gethashespersec is 0
How can I solve this?
1.bitcoin.conf
listen=1
gen=0
rpcallowip=192.168.0.100
rpcuser=username
rpcpassword=password
server=1
daemon=1
2.Restarted bitcoin-qt
3.In KncMiner mining tab set as pool 192.168.0.102:8332, username and password from bitcoin.conf
4.Restarted CGMiner in KnCMiner Mining tab
5.Result in KnC Miner web GUI:
CGMiner Status - Running (pid=xxxx)
Last Checked - Wed Nov 27 15:56:11 UTC 2013
Avg. Hash Rate - 315 Gh/s
WU - 4658
Difficulty Accepted - 0
6.Result in bitcoin-qt:
gethashespersec is 0
How can I solve this?
I started a thread similar to this one, and I suppose I'm exactly where the OP is in set up. I have a few ASIC blades I'd like to solo with but I can't verify that the blades are connecting and receiving the block headers from bitcoind running on a linux server. I've tried commands like '$ ss' and cannot see the blade IP addresses in the output. Should I run as -testnet and point the blades at port 18332 and let it run for a while and see if testcoins end up in my wallet?
Also, for bitcoin.conf setting gen=0 will tell bitcoind to not hash using server resources, but will still give block headers to the blades to solve?
Also, for bitcoin.conf setting gen=0 will tell bitcoind to not hash using server resources, but will still give block headers to the blades to solve?
nice mining speed u got there buddy
if i where you id start with 1THs work out the bugs so everything works smooth then move the rest over to solo. you do risk going a few days with no blocks at all but thats tge risk with solo mining. a big must is make sure your bitcoin client thats linked to the solo mining has a rock solid connection to the network
I agree with this. Solo is a longshot and you don't want to give up your guaranteed earnings from pools. At the most do half of your hashing power for solo starting out till you get the hang of it.
Triplemining has about your hashrate at 6000 GH/s @ https://www.triplemining.com/stats and you can see how often they solve blocks. ~1 every 5 days, but sometimes even longer. One block took over 500 hours.
not sure but id imagine less than 1gb
How many Mb can the server with 8,6 Th/s download/upload per 24 hours?
go into bitcoin qt in the debug use the line "gethashespersec" should come back with you hash rate
dont have a clue on linux but the commands are the same
dont have a clue on linux but the commands are the same
Try mining against solopool.net too. That uses stratum as opposed to getwork when mining against Bitcoin-QT.
How to be sure Bitcoin-Qt works in normal mining mode (before I find first block)?
hmmm interesting well all the miners should achieve 90-100% capacity any less id assume you having hardware problems or even problems with you internet connection
migjt be worth sticking them on bitminter for a while and see what they get. bitminter is probably the most stable pool out thre
migjt be worth sticking them on bitminter for a while and see what they get. bitminter is probably the most stable pool out thre
Thanks for your answers ))
Now I can compare BFL and KnC.
KnC Jupiters work from 510 Gh/s till 820 Gh/s.
BFL Singles work about 90-100% of its capacity.
But BFL MiniRigs usually work 40-60% of it's capacity. I don't know is it BFL low quality product or Netsolus-EclipseMC bad performance.
I'm very upset of BFL MiniRigs!
Now I can compare BFL and KnC.
KnC Jupiters work from 510 Gh/s till 820 Gh/s.
BFL Singles work about 90-100% of its capacity.
But BFL MiniRigs usually work 40-60% of it's capacity. I don't know is it BFL low quality product or Netsolus-EclipseMC bad performance.
I'm very upset of BFL MiniRigs!
looks about right. not going to be much help im a massive Linux noob 
never really got around to learning it. if you get stuck ill try to help out.
never really got around to learning it. if you get stuck ill try to help out.
I'm going to use this manual for Solo mining with KnCMiner:
1.On Ubuntu modify local (appdata) bitcoin.conf:
listen=1
gen=0
rpcallowip=192.168.1.xxx (the ip had to be the ip of your miner, it allows it to connect to bitcoin-qt)
rpcuser=yourusername (used for the mining tab)
rpcpassword=yourpw (used for the mining tab)
server=1
daemon=1
2.Ensure that my firewall does not block bitcoin-qt
3.Restart bitcoin-qt
4.In KncMiner mining tab set as pool 192.168.1.xxx:8332, user and password whatever you have in bitcoin.conf
5.Restart CGMiner in KnCMiner Mining tab (web GUI)
Bitcoin-qt had to run to connect the miner with the network
Hope this is right manual
1.On Ubuntu modify local (appdata) bitcoin.conf:
listen=1
gen=0
rpcallowip=192.168.1.xxx (the ip had to be the ip of your miner, it allows it to connect to bitcoin-qt)
rpcuser=yourusername (used for the mining tab)
rpcpassword=yourpw (used for the mining tab)
server=1
daemon=1
2.Ensure that my firewall does not block bitcoin-qt
3.Restart bitcoin-qt
4.In KncMiner mining tab set as pool 192.168.1.xxx:8332, user and password whatever you have in bitcoin.conf
5.Restart CGMiner in KnCMiner Mining tab (web GUI)
Bitcoin-qt had to run to connect the miner with the network
Hope this is right manual
i love mining. i have a small setup but its made its money back a few times now... use to be even more fun when i used gpus in winter. nothing better than getting paid to warm up my room
low ping. id go with atleast 8GB RAM and a good CPU atleast a dual core and Raid or SSD harddrive.
Frankly to say if I had second chance I wouldn't buy miners at all (especially from BFL). But now I have at least to reduce my loss.
Jump to: