I can't get solo mining to work at all :(

[jondecker76]

I've spent the entire day trying to get bitcoind set up for solo mining on a spare server (runing Ubuntu 12.04 server edition) after getting some Asicminer Erupter blades in today.  I have the latest bitcoind installed and working fine (I.e. I have an rpc user/password setup in bitcoin.conf, and can connect to the daemon and issue commands such as getinfo, etc. just fine)


I think the problem is that I'm trying to access the bitcoin server from outside of localhost (127.0.0.1)
I've searched everywhere and I can't find any instances where people are solo mining where bitcoind is running on remote machines.  I am quite positive that everything is configured correctly - this is driving me crazy!  I'm a very experienced linux administrator and programmer, so having such problems doing something so trivial is pretty frustrating.

Here is my bitcoin.conf (edited with fictional information of course)

Code:

rpcallowip=192.168.50.* #have tried rpcallowip=* as well

rpcconnect=127.0.0.1
rpcuser=my_user_name
rpcpassword=my_password
server=1 #to allow my miners to be able to solo mine

I am starting bitcoind like this:

Code:

bitcoind -daemon

I've tried various miners on my 192.168.50.* subnet, including my new ASICminer blades, an Android CPU miner and cpuminer on another computer.  None of them will even connect successfully.  I can run cpuminer on localhost just fine - i just can't get anything to work from outside of localhost.  I've even tried rpcallowip=* with no success.


Does anyone have any idea at all what is wrong??  Yes, I understand that there is a good chance that I won't ever solve a block solo mining and I'm well aware of the odds - but it is something that I would like to do.

Thanks!

[1714722914]

1714722914

[1714722914]

1714722914

[1714722914]

1714722914

[1714722914]

1714722914

[jondecker76]

Still playing with this and watching the debug log..  What does all of this mean? :

Code:

2013-12-14 01:18:02 AcceptToMemoryPool: 96.241.49.200:8333 /Satoshi:0.8.5/ : accepted 2c9a3570a3f11a80c1edb9520aec4cd39f6aaca0655b06fa22c25ab005d2cdfa (poolsz 85)
2013-12-14 01:18:02 AcceptToMemoryPool: 178.10.249.13:8333 /Satoshi:0.8.1/ : accepted c8f1e41b0f0826d7a64a276f5ab4f9c30f7283dfd9014b8f1f37a98ef4d3bc65 (poolsz 86)
2013-12-14 01:18:04 received getdata (5 invsz)
2013-12-14 01:18:06 Added 1 addresses from 75.162.16.46: 8 tried, 8517 new
2013-12-14 01:18:06 AcceptToMemoryPool: 96.241.49.200:8333 /Satoshi:0.8.5/ : accepted 4e1dd02e3f132cfe36f98737e36bbc899cfa1e03a1914543941e2e3d3d117e06 (poolsz 87)
2013-12-14 01:18:06 AcceptToMemoryPool: 54.238.206.212:8333 /Satoshi:0.8.6/ : accepted d0b2f9b790a874097a02fd91238f59309230fc2a4ec6777cf657a87d57dd32ab (poolsz 88)
2013-12-14 01:18:06 AcceptToMemoryPool: 96.241.49.200:8333 /Satoshi:0.8.5/ : accepted 7741f75324b0957f79e1c4566b2bfb20e3ff365e9f2286433df1ec4204cd764e (poolsz 89)
2013-12-14 01:18:07 AcceptToMemoryPool: 96.241.49.200:8333 /Satoshi:0.8.5/ : accepted 5a7b099c59851ce6ee573f1a405db5b8fad8e6eef728d8e7e9b3356ea61c17bf (poolsz 90)
2013-12-14 01:18:07 AcceptToMemoryPool: 75.162.16.46:8333 /Satoshi:0.8.6/ : accepted 2d57f75ef452a1aa18321f3fa4a8581f47f351849b4a382a1c57670b948edded (poolsz 91)
2013-12-14 01:18:07 AcceptToMemoryPool: 75.162.16.46:8333 /Satoshi:0.8.6/ : accepted 2da7dcce59d3e649e1ecf12a76497c302d5cbea5adece497a244e4510dce9ce9 (poolsz 92)
2013-12-14 01:18:07 AcceptToMemoryPool: 75.162.16.46:8333 /Satoshi:0.8.6/ : accepted bd6c76fec6d1af18db8cfc40da8685dbf818e5f4fba864d9fc62b44d88227ac1 (poolsz 93)
2013-12-14 01:18:08 AcceptToMemoryPool: 83.97.210.126:8333 /Satoshi:0.8.5/ : accepted 97087d5da56fd0211cd9652351227b3a033285cc29bf7f003c070f346e6414ee (poolsz 94)

[traiz]

Try bgminer and cgminer (just to see if it works)
There may be a conflict since you're using an ASIC

[jondecker76]

Try bgminer and cgminer (just to see if it works)
There may be a conflict since you're using an ASIC

The blade has it's own integrated mining software, so it's not possible to slave the ASICs with other software. 

There shouldn't be a problem, as the blade uses the getwork protocol used by bitcoind

I'm about to give up for the night.  At least I have it set up through a stratum mining proxy for now hashing on a pool.

[Trongersoll]

Try bgminer and cgminer (just to see if it works)
There may be a conflict since you're using an ASIC

The blade has it's own integrated mining software, so it's not possible to slave the ASICs with other software. 

There shouldn't be a problem, as the blade uses the getwork protocol used by bitcoind

I'm about to give up for the night.  At least I have it set up through a stratum mining proxy for now hashing on a pool.

Blades maybe(are) too fast for bitcoind to keep up with. try putting a proxy between the blades and bitcoind.