Slush's pool actively refusing IP

[mcdougrs]

Not sure if anyone from Slush's pool will see this but why are my two new workers being actively refused by the pool?

[lightenup]

Not sure if anyone from Slush's pool will see this but why are my two new workers being actively refused by the pool?

Apparently, there is a DDOS taking place. Better have some fallback pools at hand... multiple ones, because someone claimed that other pools are also getting attacked.

[nimasha]

Yeah looks like the dDOS is back on the mining_proxy is not able to connect to Slush's pool ATM either.

[cocopuffs1003]

can't help... :\

[mcdougrs]

Oh ok because it looks like my miners at home are still pounding away... maybe he just can't accept new connections but if you got in during a break in the attack your ok?

[claxdog]

Oh ok because it looks like my miners at home are still pounding away... maybe he just can't accept new connections but if you got in during a break in the attack your ok?

are they getting shares?my miners were still showing 1.030 ghs but they were not getting shares.

[VirtualWorld]

Seems like it's still down.
Miner will continue to tell you you're mining, but since it can't connect, your shares won't be submitted.

[mcdougrs]

Well the site says that my home miners have shares coming in. I wonder if this is a Firewall issue. For grins and giggles I tried to use another pool and it said the same thing:

Code:

2013-04-17 10:32:51: Listener for "CPU" started
2013-04-17 10:32:53: Listener for "CPU": 17/04/2013 10:32:53, started OpenCL miner on platform 0, device 1 (Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz)
2013-04-17 10:32:53: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:32:53, checking for stratum...
2013-04-17 10:32:54: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:32:54, no response to getwork, using as stratum
2013-04-17 10:32:55: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:32:55,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-04-17 10:32:56: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:32:56, IO errors - 1, tolerance 2
2013-04-17 10:32:57: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:32:57,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-04-17 10:32:58: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:32:58, IO errors - 2, tolerance 2
2013-04-17 10:32:59: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:32:59,  [Errno 10061] No connection could be made because the target machine actively refused it
2013-04-17 10:33:00: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:33:00, IO errors - 3, tolerance 2
2013-04-17 10:33:00: Listener for "CPU": stratum.bitcoin.cz:3333 17/04/2013 10:33:00, No more backup servers left. Using primary and starting over.

[wetwood]

Its being DDos'd, wondering if there running a network load balancing setup which would solve the issue or atleast reduce the damage the attacks cause.

[Lanidarc]

I think many pools are under coordinated attack. 50BTC has been under DDoS for 5 days by sounds of it.

Some scary shit going on:

http://arstechnica.com/security/2013/04/fueled-by-super-botnets-ddos-attacks-grow-meaner-and-ever-more-powerful/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+arstechnica%2Findex+%28Ars+Technica+-+All+content%29

[Gabi]

Do you know that cpu mining is, like, useless, right?

[mcdougrs]

Do you know that cpu mining is, like, useless, right?

Yeah I know but I have free electricity on this PC so I thought I might be able to get some hashes solved and get a little credit for it 

[UncleMeat]

Do you know that cpu mining is, like, useless, right?

Yeah I know but I have free electricity on this PC so I thought I might be able to get some hashes solved and get a little credit for it 

...which is exactly why Slush started his pool way back when in the first place! Even GPU mining is slow today. It's all about ASICs now.