Are there still S4 nodes?
No, they were just for testing. S4s work fine on the regular solo pool, and even better with the new binary I put up. 
Topic: [∞ YH] solo.ckpool.org 1% fee solo mining USA/DE 251 blocks solved! - page 467. (Read 1514164 times)
October 21, 2014, 08:03:42 AM
October 21, 2014, 08:01:53 AM
... I've set up extra solo pool nodes so the same conditions as the solo.ckpool.org (ie solo mine to your bitcoin address)
First runs diff of 2048:
s4.ckpool.org:3333
Second starts at diff 1 like ghash would:
s4.ckpool.org:3334
Bear in mind that ckpool adjusts diff VERY quickly so it may still work okay.
Are there still S4 nodes?
October 21, 2014, 06:58:50 AM
Server migration to beefier VPS complete. This one should be much more stable though it costs me 10x more to run (as always, you get what you pay for 
).
You will not need to do anything, your DNS will pick up the new solo.ckpool.org IP address and your miners will switch to it whenever they reconnect. The only thing you may notice is your stats will be reset. Those who switched to solo2 are on the same server already, it points to the same address, and port 3334 on that one is the new tube pool. When I can see no one mining on the old server I will shut it down.
Good luck with your solo mining!
). You will not need to do anything, your DNS will pick up the new solo.ckpool.org IP address and your miners will switch to it whenever they reconnect. The only thing you may notice is your stats will be reset. Those who switched to solo2 are on the same server already, it points to the same address, and port 3334 on that one is the new tube pool. When I can see no one mining on the old server I will shut it down.
Good luck with your solo mining!
October 21, 2014, 05:46:27 AM
EDIT: It seems the stability of solo 1 was short lived, will proceed with migration ASAP.
October 21, 2014, 03:18:43 AM
Point your clients at:
solo2.ckpool.org:3334
Is this change permanent?solo2.ckpool.org:3334
October 21, 2014, 03:11:57 AM
Point your clients at:
solo2.ckpool.org:3334
Is this change permanent? solo2.ckpool.org:3334
October 21, 2014, 12:49:35 AM
I've recruited a new server to cover this outage as it seems the hoster still hasn't weathered the storm of the DDoS.
EDIT: No need to use this any more, I migrated the server somewhere more stable. Don't change anything.
Point your clients at:
solo2.ckpool.org:3334
Same login conditions etc. Unfortunately there are no stats pages set up, but consider this temporary till the DDoS is over. I have this pool starting at diff1 too since so many clients have slow devices mining here, but it ramps up very quickly if you have a faster device so don't worry (or you can add --suggest-diff if you're using the latest cgminer if you really want to force the issue).
EDIT: No need to use this any more, I migrated the server somewhere more stable. Don't change anything.
solo2.ckpool.org:3334
Same login conditions etc. Unfortunately there are no stats pages set up, but consider this temporary till the DDoS is over. I have this pool starting at diff1 too since so many clients have slow devices mining here, but it ramps up very quickly if you have a faster device so don't worry (or you can add --suggest-diff if you're using the latest cgminer if you really want to force the issue).
October 20, 2014, 11:59:54 PM
Yes you are correct. I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.
So, it was a "5 gh/s" shy of 2,000 GH/s or was it 200 GH/s shy ["1.8 TH/s average," like in your first statement.] shy of the 2 TH/s guarantee?
The reason I'm curious is because I'm about to purchase my first S4 in a couple more days. I've almost mined the BTC needed to purchase it from Bitmaintech.com.
I'm just saying, I would be disappointed if it's not hashing the 2000 GH/s guaranteed. I would need to send my S4 back if it was 200 GH/s shy of the 2000 GH/s guaranteed. If it was just 5 GH/s shy of the 2000 GH/s, I could probably live with that; but not 200 GH/s shy of the guarantee.
no this was a pool issue. my underclocked s-3 runs at 400-410gh. the last two hours it has dropped out and back and is a mess. but most of the time I get my 400-410gh here . my s-3 is clocked to freq 200 so 400-410 is normal.
gotcha!
Thanks for clarifying!!!
I was beginning to get very concerned.
October 20, 2014, 11:58:31 PM
Yes you are correct. I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.
So, it was a "5 gh/s" shy of 2,000 GH/s or was it 200 GH/s shy ["1.8 TH/s average," like in your first statement.] shy of the 2 TH/s guarantee?
The reason I'm curious is because I'm about to purchase my first S4 in a couple more days. I've almost mined the BTC needed to purchase it from Bitmaintech.com.
I'm just saying, I would be disappointed if it's not hashing the 2000 GH/s guaranteed. I would need to send my S4 back if it was 200 GH/s shy of the 2000 GH/s guaranteed. If it was just 5 GH/s shy of the 2000 GH/s, I could probably live with that; but not 200 GH/s shy of the guarantee.
no this was a pool issue. my underclocked s-3 runs at 400-410gh. the last two hours it has dropped out and back and is a mess. but most of the time I get my 400-410gh here . my s-3 is clocked to freq 200 so 400-410 is normal.
October 20, 2014, 11:52:44 PM
Yes you are correct. I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.
So, it was a "5 gh/s" shy of 2,000 GH/s or was it 200 GH/s shy ["1.8 TH/s average," like in your first statement.] shy of the 2 TH/s guarantee?
The reason I'm curious is because I'm about to purchase my first S4 in a couple more days. I've almost mined the BTC needed to purchase it from Bitmaintech.com.
I'm just saying, I would be disappointed if it's not hashing the 2000 GH/s guaranteed. I would need to send my S4 back if it was 200 GH/s shy of the 2000 GH/s guaranteed. If it was just 5 GH/s shy of the 2000 GH/s, I could probably live with that; but not 200 GH/s shy of the guarantee.
October 20, 2014, 11:25:29 PM
Yes you are correct. I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.
October 20, 2014, 11:19:03 PM
k. Thanks for checking. It's probably this instance of bfgminer I'm running 
I see what you did there. Now that's funny right there 
Updated the S4 with your release today and pointed it at the solo pool. I'm seeing an average of about 1.8t with it. Does that sound about right? Isn't it amazing we are up to a point where 200gh/s can be within 10% tolerance?
Specifications:
* Chip Operating Voltage: 0.72V
* Chip Quantity per unit: 160
* Hash Rate: 2,000GH/s guaranteed
* Power Efficiency: 0.69Watt/GH/s at the wall
* Over clocking: About 10%, but not guaranteed
* 3U Rack 432mm*442mm*133mm
* PSU inside: 1400W, 80PLUS gold, C14 input socket. Power line not included. You may look for one line with no less than 16A in your local market
* Temperature: 40-50 degree Celsius tested in the mining farm
* Fan Speed: 3900RPM
* Stable but a little bit noisy
* Ethernet connection, Stand alone
* Certificate Compliance: FCC/CE
I don't understand... The 10% tolerance regards "Over Clocking," which is "...not guaranteed."
However, a "Hash Rate: 2,000 GH/s (2 TH/s) is guaranteed."
October 20, 2014, 11:15:32 PM
Host provider seems to be having intermittent networking issues again, sorry - last time this happened one of the other servers on their subnet was experiencing a DDoS. Put in a support ticket but there's not much I can do about it at this time. If the pool was bigger I could probably justify moving to a more expensive provider with better connectivity guarantees.
No biggie here. I think it's a great idea for a pool. Beats me having to maintain my own solo side. Although when things slow down at work, I plan to try setting up one of these. From what I've seen so far with this and the other pool, it looks very good. In the morning I'll point the S4 over to eligius and see what kind of rates I get there. Thanks for what you are doing!
FYI: With the updated cgminer, the S4's gui doesn't report 5s hashrate. Shows avg just fine though. Just in case you didn't know.
October 20, 2014, 10:50:01 PM
Host provider seems to be having intermittent networking issues again, sorry - last time this happened one of the other servers on their subnet was experiencing a DDoS. Put in a support ticket but there's not much I can do about it at this time. If the pool was bigger I could probably justify moving to a more expensive provider with better connectivity guarantees.
October 20, 2014, 09:46:41 PM
k. Thanks for checking. It's probably this instance of bfgminer I'm running
I see what you did there. Now that's funny right there Updated the S4 with your release today and pointed it at the solo pool. I'm seeing an average of about 1.8t with it. Does that sound about right? Isn't it amazing we are up to a point where 200gh/s can be within 10% tolerance?
October 20, 2014, 11:49:36 AM
k. Thanks for checking. It's probably this instance of bfgminer I'm running
I see what you did there. Now that's funny right there 
October 20, 2014, 03:18:22 AM
nobody found a block since 21 September?
is there any place beside blockchain to see pool stats?
Pretty much. It's not like we're going to find many blocks averaging 40TH. It also makes zero difference to each individual miner what the overall hashrate of the pool is. The only stats are those linked on the front page and doesn't include blocks since they all show up in blockchain. The pool is intentionally lean and no fuss and accordingly very low fee. Just raw mining at its best.is there any place beside blockchain to see pool stats?
You can expect anywhere from 1 to 344 days.
More than 430 days would be quite rare.
... of course as diff rises so does the expected time to find one ...
October 20, 2014, 12:27:00 AM
nobody found a block since 21 September?
is there any place beside blockchain to see pool stats?
Pretty much. It's not like we're going to find many blocks averaging 40TH. It also makes zero difference to each individual miner what the overall hashrate of the pool is. The only stats are those linked on the front page and doesn't include blocks since they all show up in blockchain. The pool is intentionally lean and no fuss and accordingly very low fee. Just raw mining at its best.is there any place beside blockchain to see pool stats?
October 19, 2014, 10:31:01 PM
I've seen this a few times today. And then it needs to work the diff down before I start seeing shares. Can you tell if this is server side or client?
[2014-10-19 19:36:45] Stratum from pool 0 requested work update
[2014-10-19 19:36:47] Accepted 0d36c508 AMU 2 pool 0 Diff 19/5
[2014-10-19 19:37:08] Pool 0 stratum share submission failure
[2014-10-19 19:37:08] Stratum connection to pool 0 interrupted
[2014-10-19 19:37:10] Message from pool 0: Authorised, welcome to solo.ckpool.o
rg 1PEapF6rZNMkykfoJrfDSKT4Z7neGbF5ku!
[2014-10-19 19:37:10] Stratum from pool 0 requested work update
[2014-10-19 19:37:15] Stratum from pool 0 requested work update
[2014-10-19 19:37:46] Stratum from pool 0 requested work update
[2014-10-19 19:38:16] Stratum from pool 0 requested work update
[2014-10-19 19:38:46] Stratum from pool 0 requested work update
[2014-10-19 19:39:16] Stratum from pool 0 requested work update
I checked the logs and it's only your one worker that is disconnecting, with no other clients doing it at the same time so I suspect it's client side. [2014-10-19 19:36:45] Stratum from pool 0 requested work update
[2014-10-19 19:36:47] Accepted 0d36c508 AMU 2 pool 0 Diff 19/5
[2014-10-19 19:37:08] Pool 0 stratum share submission failure
[2014-10-19 19:37:08] Stratum connection to pool 0 interrupted
[2014-10-19 19:37:10] Message from pool 0: Authorised, welcome to solo.ckpool.o
rg 1PEapF6rZNMkykfoJrfDSKT4Z7neGbF5ku!
[2014-10-19 19:37:10] Stratum from pool 0 requested work update
[2014-10-19 19:37:15] Stratum from pool 0 requested work update
[2014-10-19 19:37:46] Stratum from pool 0 requested work update
[2014-10-19 19:38:16] Stratum from pool 0 requested work update
[2014-10-19 19:38:46] Stratum from pool 0 requested work update
[2014-10-19 19:39:16] Stratum from pool 0 requested work update
k. Thanks for checking. It's probably this instance of bfgminer I'm running
October 19, 2014, 09:07:07 PM
I've seen this a few times today. And then it needs to work the diff down before I start seeing shares. Can you tell if this is server side or client?
[2014-10-19 19:36:45] Stratum from pool 0 requested work update
[2014-10-19 19:36:47] Accepted 0d36c508 AMU 2 pool 0 Diff 19/5
[2014-10-19 19:37:08] Pool 0 stratum share submission failure
[2014-10-19 19:37:08] Stratum connection to pool 0 interrupted
[2014-10-19 19:37:10] Message from pool 0: Authorised, welcome to solo.ckpool.o
rg 1PEapF6rZNMkykfoJrfDSKT4Z7neGbF5ku!
[2014-10-19 19:37:10] Stratum from pool 0 requested work update
[2014-10-19 19:37:15] Stratum from pool 0 requested work update
[2014-10-19 19:37:46] Stratum from pool 0 requested work update
[2014-10-19 19:38:16] Stratum from pool 0 requested work update
[2014-10-19 19:38:46] Stratum from pool 0 requested work update
[2014-10-19 19:39:16] Stratum from pool 0 requested work update
I checked the logs and it's only your one worker that is disconnecting, with no other clients doing it at the same time so I suspect it's client side. [2014-10-19 19:36:45] Stratum from pool 0 requested work update
[2014-10-19 19:36:47] Accepted 0d36c508 AMU 2 pool 0 Diff 19/5
[2014-10-19 19:37:08] Pool 0 stratum share submission failure
[2014-10-19 19:37:08] Stratum connection to pool 0 interrupted
[2014-10-19 19:37:10] Message from pool 0: Authorised, welcome to solo.ckpool.o
rg 1PEapF6rZNMkykfoJrfDSKT4Z7neGbF5ku!
[2014-10-19 19:37:10] Stratum from pool 0 requested work update
[2014-10-19 19:37:15] Stratum from pool 0 requested work update
[2014-10-19 19:37:46] Stratum from pool 0 requested work update
[2014-10-19 19:38:16] Stratum from pool 0 requested work update
[2014-10-19 19:38:46] Stratum from pool 0 requested work update
[2014-10-19 19:39:16] Stratum from pool 0 requested work update
Jump to: