How often, with how many TH/s do people hit on Solo?
Does anyone have some averages that they have experienced?
Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 245. (Read 1514780 times)
January 10, 2016, 07:56:20 PM
January 10, 2016, 07:24:45 PM
There was a DDoS at solo main again that appeared to have lasted about an hour which was mitigated by the ddos protection but connection to the pool at the time was affected as the attack size saturated the connection. All appears normal again now.
With the return of DDoS attacks I'll be reinstituting the front end redirector on the main solo pool to allow miners to keep mining even if the front end gets interrupted. This means that some rental services may be unhappy again unless they use port 3334. None of this will affect anyone currently mining with there being no pool restarts or reconnects unless they reconnect themselves once the dns for solo.ckpool.org updates.So should I continue using port 3333 for MRR as I already have a couple going ?
January 10, 2016, 07:21:35 PM
There was a DDoS at solo main again that appeared to have lasted about an hour which was mitigated by the ddos protection but connection to the pool at the time was affected as the attack size saturated the connection. All appears normal again now.
With the return of DDoS attacks I'll be reinstituting the front end redirector on the main solo pool to allow miners to keep mining even if the front end gets interrupted. This means that some rental services may be unhappy again unless they use port 3334. None of this will affect anyone currently mining with there being no pool restarts or reconnects unless they reconnect themselves once the dns for solo.ckpool.org updates.So should I continue using port 3333 for MRR as I already have a couple going ?
January 10, 2016, 07:11:58 PM
There was a DDoS at solo main again that appeared to have lasted about an hour which was mitigated by the ddos protection but connection to the pool at the time was affected as the attack size saturated the connection. All appears normal again now.
With the return of DDoS attacks I'll be reinstituting the front end redirector on the main solo pool to allow miners to keep mining even if the front end gets interrupted. This means that some rental services may be unhappy again unless they use port 3334. None of this will affect anyone currently mining with there being no pool restarts or reconnects unless they reconnect themselves once the dns for solo.ckpool.org updates. January 10, 2016, 03:43:31 PM
There was a DDoS at solo main again that appeared to have lasted about an hour which was mitigated by the ddos protection but connection to the pool at the time was affected as the attack size saturated the connection. All appears normal again now.
January 10, 2016, 01:48:58 PM
Pool is down?
All of my rentals failed over to the de pool and show solo as dead..
Yup. Same here.
Interesting...
Looks like when i switched my miner on, the pool went down
Some of my rigs have switched
January 10, 2016, 01:20:51 PM
Pool is down?
All of my rentals failed over to the de pool and show solo as dead..
Yup. Same here.
Interesting...
Looks like when i switched my miner on, the pool went down
January 10, 2016, 01:17:49 PM
Pool is down?
All of my rentals failed over to the de pool and show solo as dead..
Yup. Same here.
January 10, 2016, 01:03:14 PM
Do any of you guys run a full node at home?
I do.
January 10, 2016, 12:44:15 PM
Do any of you guys run a full node at home?
January 10, 2016, 12:32:49 PM
Pool is down?
All of my rentals failed over to the de pool and show solo as dead..
January 10, 2016, 12:31:21 PM
Pool is down?
January 10, 2016, 10:57:38 AM
HK mining node is currently down. For some reason the VPS provider I have for that node have it in their head that the way to cope with lots of concurrent connections is to suspend the service. Fuck you hostus.us . Never going to use them again. Luckily they're not responsible for solo or de.
Good to know. I manage a few sites...been looking to change provider after almost ten years as they've "grown" perhaps a bit too much. Anyway...had my machines on HK the past several days, but my agreed-to solo mining jaunt (with my principal) is over, and I've switched them over to a pool.
It's been fun, bunkies. I'll still see you on these boards regularly, though. It's decent conversation..and this fellow is, imho, the one to listen to.
Peace be with us.
January 10, 2016, 10:03:32 AM
HK mining node is currently down. For some reason the VPS provider I have for that node have it in their head that the way to cope with lots of concurrent connections is to suspend the service. Fuck you hostus.us . Never going to use them again. Luckily they're not responsible for solo or de.
January 09, 2016, 10:42:19 PM
Thanks for the bug report. If anyone else spots any issues with the combined stats on solo.ckpool.org, please speak up, but I won't be removing the remote node stats for a while yet.
No problem, thanks for fixing it so quickly.
January 09, 2016, 10:20:24 PM
Thanks for the bug report. If anyone else spots any issues with the combined stats on solo.ckpool.org, please speak up, but I won't be removing the remote node stats for a while yet.
January 09, 2016, 10:11:20 PM
Alas I found a bug and will need to perform yet another restart. Luckily they don't really cause any downtime.
Working now
Edit: bestever was at zero, and best share was 30 million
After restart new best share was around 54 million and Bestever was the same.
Now best share is 361 million and Bestever hasn't changed and still shows 54 million
That would be hard to tell because user bestever is much higher than current Bestever for worker
And it's working now
January 09, 2016, 10:10:16 PM
Alas I found a bug and will need to perform yet another restart. Luckily they don't really cause any downtime.
Working now
Edit: bestever was at zero, and best share was 30 million
After restart new best share was around 54 million and Bestever was the same.
Now best share is 361 million and Bestever hasn't changed and still shows 54 million
That would be hard to tell because user bestever is much higher than current Bestever for worker
January 09, 2016, 10:07:00 PM
Alas I found a bug and will need to perform yet another restart. Luckily they don't really cause any downtime.
Working now
Edit: bestever was at zero, and best share was 30 million
After restart new best share was around 54 million and Bestever was the same.
Now best share is 361 million and Bestever hasn't changed and still shows 54 million
That would be hard to tell because user bestever is much higher than current Bestever for worker
January 09, 2016, 10:05:16 PM
Alas I found a bug and will need to perform yet another restart. Luckily they don't really cause any downtime.
Working now
Edit: bestever was at zero, and best share was 30 million
After restart new best share was around 54 million and Bestever was the same.
Now best share is 361 million and Bestever hasn't changed and still shows 54 million
Jump to: