Author

Topic: GUIminer issue after Ddos attack on slush's (Read 754 times)

newbie
Activity: 32
Merit: 0
April 17, 2013, 04:55:45 PM
#6
yeah it seems to be getting hit hard the past day or so, someone really has it out for slush right now.
newbie
Activity: 30
Merit: 0
Still under ddos I believe.

Snipped from Slush right now....


16.04.2013
Pool is under DDoS attack. I'm resolving the issue, please be patient.
 
newbie
Activity: 1
Merit: 0
I'm having the exact same problem and it still has not resolved itself. Any suggestions?
newbie
Activity: 42
Merit: 0
try again
newbie
Activity: 14
Merit: 0
Try it now, i'm mining now.
newbie
Activity: 32
Merit: 0
I can't seem to connect to slush's pool or any pool for that matter at the moment copying my console below

Code:
2013-04-17 05:43:15: Listener for "Fast": api2.bitcoin.cz:8332 17/04/2013 05:43:15,  timed out
2013-04-17 05:43:16: Listener for "Fast": api2.bitcoin.cz:8332 17/04/2013 05:43:16, IO errors - 2, tolerance 2
2013-04-17 05:43:21: Listener for "Fast": api2.bitcoin.cz:8332 17/04/2013 05:43:21,  timed out
2013-04-17 05:43:22: Listener for "Fast": api2.bitcoin.cz:8332 17/04/2013 05:43:22, IO errors - 3, tolerance 2
2013-04-17 05:43:22: Listener for "Fast": api2.bitcoin.cz:8332 17/04/2013 05:43:22, No more backup servers left. Using primary and starting over.
2013-04-17 05:43:27: Listener for "Fast": api2.bitcoin.cz:8332 17/04/2013 05:43:27,  timed out
2013-04-17 05:43:28: Listener for "Fast": api2.bitcoin.cz:8332 17/04/2013 05:43:28, IO errors - 1, tolerance 2
2013-04-17 05:43:32: Listener for "Fast" shutting down
Jump to: