[CLOSED] Semi-private mining pool

[jamesg]

Giga, just wanted to say thanks.

You are most welcome. 

Best pool I have been in.  Things just work, and work smoothly.

I am glad you like the pool. I certainly feel the same, but I am bias. 

[1715606607]

1715606607

[1715606607]

1715606607

[Morblias]

So I got my replacement M-board after the first one was DOA for BitFury, and it doesn't seem to want to connect to the pool. I have tried multiple pools and it seems like it does not like pools that use stratum+tcp:// at the beginning to connect to them. If I leave out the stratum+tcp:// for this pool, it starts, but is it sending the shares to my correct worker then? It shows my speed starting to go up, but still shows Alive? No.

Edit: I guess the chainminer software doesn't work like cgminer and you can't put in stratum+tcp://. I have it connected to pool without using that at beginning and it keeps showing this in log:


So I think it is accepting shares? But on pool it still says Alive? No and Total Shares: 0 after about 10 minutes connected. Does it take time or is it not actually accepting shares?

[Cablez]

To connect you have to put the pool:port:user:pass details in all 3 sections repeated on the web interface.

The only part you need for pool is after the http://     Check on the web interface first to see if the board is hashing then later it will start to be picked up by the pool. It takes a shift or 2.

[Morblias]

To connect you have to put the pool:port:user:pass details in all 3 sections repeated on the web interface.

The only part you need for pool is after the http://     Check on the web interface first to see if the board is hashing then later it will start to be picked up by the pool. It takes a shift or 2.

Yeah it shows the hash rate on the pool, so I think it is accepting? I will wait for a shift and hopefully it is accepting shares and changes it to alive and ups the total shares.

Edit: it just updated.. but... lol

(690% rejects)


I was using difficulty 128. Should I change this or is there something else I should do?

[Cablez]

The pool would not let me set the diff less than 100 so YMMV.  Its ok though as I had a high stale rate for the first shift. It get much better with time.

[mdbssm]

To connect you have to put the pool:port:user:pass details in all 3 sections repeated on the web interface.

The only part you need for pool is after the http://     Check on the web interface first to see if the board is hashing then later it will start to be picked up by the pool. It takes a shift or 2.

Yeah it shows the hash rate on the pool, so I think it is accepting? I will wait for a shift and hopefully it is accepting shares and changes it to alive and ups the total shares.

Edit: it just updated.. but... lol

(690% rejects)


I was using difficulty 128. Should I change this or is there something else I should do?

Email James and request to have him set that worker to 25 diff. Worked nicely for my 1 board rig.

Just setting up my 16 board rig and using 256 initial diff per ck's recommendations. Also got very high initial rejects but it is slowly trending down.

[Morblias]

Ahh yes, after the 2nd update it shows 271% reject rate so it is going down. I will let it run through the night and check back in tomorrow and it will hopefully be all gravy baby. Thanks guys!

[mdbssm]

Ahh yes, after the 2nd update it shows 271% reject rate so it is going down. I will let it run through the night and check back in tomorrow and it will hopefully be all gravy baby. Thanks guys!

How'd it go overnight? Despite lots of fiddling I couldn't get my full BF rig to work properly. Very high rejected share rate that levelled at ~110%. Max pool reported worker speed was ~360GH. After 1 hour it kept getting worse, ~260GH.

Emailed James, put it on 50BTC for now. Pool speed = expected miner speed with no rejected shares there.

BTCguild was having a similar problem last week that required a fix on the pool end.

https://bitcointalk.org/index.php?topic=250249.msg3089367#msg3089367

My BF starter kit rig is still reporting 4x the rejected shares of my avalons (2% vs .5%) after 5 days on the pool.

[Morblias]

Seemed to went really well overnight. It dropped to 17.73% so far, and will continue to drop (barely getting any rejects now). Most of the rejects must have came when I was running it at 128 min diff. When I changed it back down to 100 I barely got any rejects. The only problem I have now is that the pool is reporting it running between 20-21GH/s, while on my webUI it shows it pushing 29GH/s so I emailed James asking if it was possible to change min difficulty lower so I can see if that fixes the issue.

[jamesg]

To all bitfury miners:

The bitfury miners are using Slush's stratum proxy which does NOT correctly follow the stratum protocol. I need to patch the stratum servers  so that these miners stop seeing high reject rates.

Unfortunately I'm back on the road at the moment and won't be able to get to this until the weekend at the earliest.

[Morblias]

To all bitfury miners:

The bitfury miners are using Slush's stratum proxy which does NOT correctly follow the stratum protocol. I need to patch the stratum servers  so that these miners stop seeing high reject rates.

Unfortunately I'm back on the road at the moment and won't be able to get to this until the weekend at the earliest.

Good enough for me! Thanks James!

[eleuthria]

For those running the stratum proxy, the problem is due to the proxy sending the authorization prior to the subscribe.  If you want to get your hands dirty, it shouldn't be too hard to edit the proxy code to put these in the correct order.

[jamesg]

For those running the stratum proxy, the problem is due to the proxy sending the authorization prior to the subscribe.  If you want to get your hands dirty, it shouldn't be too hard to edit the proxy code to put these in the correct order.

https://github.com/slush0/stratum-mining-proxy/blob/master/mining_proxy.py

lines 86 - 107

Per the stratum documentation, subscribe should come before authorize. It is backwards in the on_connect() callback.

Switching them around will make your rejects go back to fractions of a percent.

[daserpent1]

Whats the minimum hashrate needed to get into your pool now? And whats the pool's total hashrate?

[DrHaribo]

For those running the stratum proxy, the problem is due to the proxy sending the authorization prior to the subscribe.  If you want to get your hands dirty, it shouldn't be too hard to edit the proxy code to put these in the correct order.

Isn't it easier if Slush fixes this?

[jjiimm_64]

Update password on site not working.

on submit, I see a page not found error, and the old password still works.

edit:  the page not found error is from the site, not error in browser.

[jamesg]

Update password on site not working.

on submit, I see a page not found error, and the old password still works.

edit:  the page not found error is from the site, not error in browser.

I'll look into this first thing tomorrow.

[jamesg]

For those running the stratum proxy, the problem is due to the proxy sending the authorization prior to the subscribe.  If you want to get your hands dirty, it shouldn't be too hard to edit the proxy code to put these in the correct order.

Isn't it easier if Slush fixes this?

It should be if he was around. I'll fork the repo tomorrow and send a pull request back to him.

[Blazed]

Have to say that this pool has been rock solid for me for a few months now.  Keep up the good work Mr. PetaVPS 

[jamesg]

Have to say that this pool has been rock solid for me for a few months now.  Keep up the good work Mr. PetaVPS 

It's nice to be able to sleep at night knowing that the pool will still be running in the morning.