Help with eruptor blade on Slush's pool

[morrisford]

I have a new eruptor blade on an existing account at Slush's and I am having a problem with not seeing any activity in the worker. The blade is set up and connecting through mining_proxy.py to the pool and I see many accepted messages at the proxy as well as the blade is showing many accepts. The pool just does't show any worker activity and I am not getting credit for all the shares.

Any ideas?

Morris

[1713398803]

1713398803

[1713398803]

1713398803

[1713398803]

1713398803

[grimsparkle]

Hi Morris,

Where are you not seeing the expected results? If it is on the Accounts page, it does take a bit before the Mhash/s registers.

Grim

[morrisford]

I am looking at the accounts/profile page. I figured that it might take a while so I let it run for almost 2 hours with no activity. My other miners (usb eruptors ) show up pretty quickly. I am currently suspicious of the mining_proxy.py because I connected up to bitminter through the proxy and it acted the same. I then connected direct to bitminter and it comes right up.

Morris

[gbsray]

Not sure it helps but lots of people are having issues with the Blades. I can only get mine to work at the rated 10+ GHz when connecting to the cloud proxy that someone on the boards setup.

[xandriel]

I have 2 blades working fine with Slush's pool...maybe I can be of help.

It sounds like mining_proxy is working fine, so I would suggest logging in to the blade and checking the user:pass field. Make sure it is set to your user and pass for the pool....twice (separated by a ,)

Connect to the blade via [ip address]:8000

[DrunkenSailor]

I've got a v2 blade working fine with Slush's pool. Could you post some of your proxy log? That might help folks point you in the right direction.  Also, it does take some time for the worker to show up, and even more time for the Mh/s to be shown accurately for the worker. Having said that, 2 hours should have been more than enough for the worker to at least show up...

[grimsparkle]

One other thought... make sure the blade's configuration points to the IP address of the computer running mining_proxy under Server addresses:

Ports: 8332,8332 
Server Addresses: your Mac's IP address, your Mac's IP address
user:pass: username.worker1:password,username.worker1:password

Blade port 8332 ---->Proxy(Mac 'server' running mining_proxy.py) port 3333 ----> Slush's Pool

[morrisford]

(xandriel)

<<I have 2 blades working fine with Slush's pool...maybe I can be of help.

<<It sounds like mining_proxy is working fine, so I would suggest logging in to the blade and checking the user:pass <<field. Make sure it is set to your user and pass for the pool....twice (separated by a ,)

<<Connect to the blade via [ip address]:8000

I did a test of pointing the blade to a non-existent worker at the pool and things did not appear to work at the proxy. I then created that worker at the pool and the proxy started spitting accepted messages and the blade started showing accepted count. I took that to mean that the blade was talking through the proxy to the pool server.

(DrunkenSailor)

>>I've got a v2 blade working fine with Slush's pool. Could you post some of your proxy log? That might help folks >>point you in the right direction.  Also, it does take some time for the worker to show up, and even more time for the >>Mh/s to be shown accurately for the worker. Having said that, 2 hours should have been more than enough for the >>worker to at least show up…

It is very encouraging to hear that both you and grim xandriel have blades talking to slush. That means I just have to find the right combination.
I will try to post some proxy log a bit later. I have to get it from across the network.

(grimsparkle)

>>One other thought... make sure the blade's configuration points to the IP address of the computer running >>mining_proxy under Server addresses:

>>Ports: 8332,8332 
>>Server Addresses: your Mac's IP address, your Mac's IP address
>>user:pass: username.worker1:password,username.worker1:password

>>Blade port 8332 ---->Proxy(Mac 'server' running mining_proxy.py) port 3333 ----> Slush's Pool

I am pretty sure that is how I had it set up. I will check a bit later after it has run for a while on bitminter.

I also have to eat dinner. I certainly appreciate all the help especially knowing that it will work.

Morris

[morrisford]

Interestingly, I just was looking through the stats on slush pool and I found that during the time that I had the blade trying to run there that the reward for that round was about 9 times higher than other rounds. I guess that means that even though the worker did not show activity it was being accepted. Very strange. I guess I'll hook it up to that pool again and let it run through the night and see what I see. I'll report back.

Morris

[grimsparkle]

It could be that the blade connected and was able to test up its Vardiff. Slush talks about how that works in the FAQs, under Pool Features (http://mining.bitcoin.cz/faq/#pool-features).
In any case, glad to hear you're getting some success from it.

[zzgundam]

I have similar problem.

My computer ip is 192.168.1.2, and I have tried to swith to some other ip addresses for the DNS and none of them work.  I tried to use a proxy but the only thing I got was "false" messages.  I also tried to use the BFGminer, but it could not detect my blade.

Total MHS: 00000
Received: 0000000000
Accepted: 0000000000
Per Minute: 000.00
Efficiency: 000.00%
Up Time: 0d,00h,01m,09s

Current Server: 192.168.1.2:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

IP 192.168.1.254
Mask 255.255.255.0
Gateway 192.168.1.1
WEB Port 8000
Primary DNS 192.168.1.2
Secondary DNS 8.8.8.8
Ports 8332,8332
Server addresses 192.168.1.2,192.168.1.2

If I change to slush's pool, then I can only get the received score but no other things.

Total MHS:   00000
Received:   0000000047
Accepted:   0000000000
Per Minute:   000.00
Efficiency:   000.00%
Up Time:   0d,00h,00m,30s

Current Server: api.bitcoin.cz:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

IP 192.168.1.254
Mask 255.255.255.0
Gateway 192.168.1.1
WEB Port   8000
Primary DNS 8.8.8.8
Secondary DNS 8.8.4.4
Ports 8332,8332
Server addresses api.bitcoin.cz,api.bitcoin.cz

When I point to the stratum pool, I got nothing.

Total MHS:   00000
Received:   0000000000
Accepted:   0000000000
Per Minute:   000.00
Efficiency:   000.00%
Up Time:   0d,00h,01m,02s

Current Server: stratum.bitcoin.cz:3333
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

IP 192.168.1.254
Mask 255.255.255.0
Gateway 192.168.1.1
WEB Port   8000
Primary DNS 8.8.8.8
Secondary DNS 8.8.4.4
Ports 3333,3333
Server addresses stratum.bitcoin.cz,stratum.bitcoin.cz


I change to the eligius pool and I can get some harsh rates, but it's too low and it will reset automatically in about 2 mins.

Total MHS: 00627
Received: 0000000029
Accepted: 0000000005
Per Minute: 010.71
Efficiency: 017.24%
Up Time: 0d,00h,00m,28s

Current Server: mining.eligius.st:8337
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
IP 192.168.1.254
Mask 255.255.255.0
Gateway 192.168.1.1
WEB Port 8000
Primary DNS 192.168.1.2
Secondary DNS 8.8.8.8
Ports 8337,8332
Server addresses mining.eligius.st,192.168.1.2

I think it must be something related to my config, but I don't know how to set it up though.
Could some one help me?  Thank you very much!

[grimsparkle]

zzgundam,

Looking at your setup based on slush's pool...

 - you have to have a stratum mining proxy program running on your computer
 - your blade's Current Server should point to your computer's IP
 - Your Primary DNS should be whatever your PCs DNS is (usually your router or cable modem's IP)

In my case my computer was 192.168.1.109

My config read:

IP           192.168.1.254
Mask       255.255.255.0
Gateway  192.168.1.1
WEB Port  8000
Primary DNS   192.168.1.1
Secondary DNS 8.8.8.8
Ports 8332,8332
Server Addresses   192.168.1.109,192.168.1.109
user:pass    myuser.worker1:password,myuser.worker1:password

The mining_proxy program that Slush refers to will handle the connection using stratum port 3333. It listens to your network for blades on 8332 and passes it along.

The setup that worked for me was:

Blade (port 8332) ----> My PC running stratum proxy program (port 3333) ----> Slush's pool

Hope this helps

[morrisford]

Well, I found the problem. I had previously been using the mining_proxy instance to mine lite coins and when I started using it for bit coins I just changed the -o parameter to slush's pool but I left the other parameters the same. To mine litecoins there is a -pa script parameter and having that still there caused the proxy to spit accepted messages but the pool ignored them. So the running command line for the mining proxy is:

python mining_proxy.py -o stratum.bitcoin.cz -p 3333

Sometimes I amaze myself by how dumb I can be.

Anyway, thanks to everyone who helped.

Morris

[zzgundam]

zzgundam,

Looking at your setup based on slush's pool...

 - you have to have a stratum mining proxy program running on your computer
 - your blade's Current Server should point to your computer's IP
 - Your Primary DNS should be whatever your PCs DNS is (usually your router or cable modem's IP)

In my case my computer was 192.168.1.109

My config read:

IP           192.168.1.254
Mask       255.255.255.0
Gateway  192.168.1.1
WEB Port  8000
Primary DNS   192.168.1.1
Secondary DNS 8.8.8.8
Ports 8332,8332
Server Addresses   192.168.1.109,192.168.1.109
user:pass    myuser.worker1:password,myuser.worker1:password

The mining_proxy program that Slush refers to will handle the connection using stratum port 3333. It listens to your network for blades on 8332 and passes it along.

The setup that worked for me was:

Blade (port 8332) ----> My PC running stratum proxy program (port 3333) ----> Slush's pool

Hope this helps

Grimsparkle, Thank you for your reply! 

My computer's IP address is 192.168.1.2, and as you can see, I tried several times by using this IP address and failed to connect it.
I also tried to run the mining_proxy, and I only got the message of "clean_jobs = false".  Don't know why.

[zzgundam]

My problem has been solved!
It's something related to my computer firewall and windows services.  When I solved the problem of the windows firewall, the blade then could connect to my pc automatically!  Very happy mining now!  Thanks for the people who have helped me, thank you very much!

[gbsray]

A kind of related question. If you have multiple blades connection to the stratum proxy, do they all have to have unique usernames or can say all 10 blades use the same worker name?

Any help much appreciated. Thanks

[xandriel]

They can all use the same worker