Topic: MORE DDoS on Deepbit? (Read 4707 times)
Well it seems clear that a lot of computer power is entering the network and a lot of pools are having problems.
I cant connect to slushes pool. It says the site was DDoSED and to look at the forum thread but I cant find it. Would be helpful if there was a link on the site to go to...
Sadly I too had to switch away from deepbit. Too big of a pain constantly keeping an eye on the miners making sure that they haven't stalled because of connection issues requiring a manual restart. Switched over to bitcoins.lc and in the last 24 hours have mined nearly 2 bitcoins vs the 1 bitcoin per day I could mine on deepbit. Not regretting the switch at all now. Also, no fees either on bitcoins.lc. No where near as good of a website, but damn I can't argue with the results.
Which mining software stalls like this? Sounds like they need to be bug-fixed so they detect the "stalled" state and retry. A main thread spawns worker thread with a built in timeout setting, and if the worker thread hasn't done any work for more time than the timeout setting, kill it and restart it.
phoenix
hardly thats deepbit-specific.
but ironically, DDoS'ing anyone won't matter/help anyway, unless software become solo-mining-friendly and/or work at least[in that mode].
but ironically, DDoS'ing anyone won't matter/help anyway, unless software become solo-mining-friendly and/or work at least[in that mode].
Sadly I too had to switch away from deepbit. Too big of a pain constantly keeping an eye on the miners making sure that they haven't stalled because of connection issues requiring a manual restart. Switched over to bitcoins.lc and in the last 24 hours have mined nearly 2 bitcoins vs the 1 bitcoin per day I could mine on deepbit. Not regretting the switch at all now. Also, no fees either on bitcoins.lc. No where near as good of a website, but damn I can't argue with the results.
Which mining software stalls like this? Sounds like they need to be bug-fixed so they detect the "stalled" state and retry. A main thread spawns worker thread with a built in timeout setting, and if the worker thread hasn't done any work for more time than the timeout setting, kill it and restart it.
Sadly I too had to switch away from deepbit. Too big of a pain constantly keeping an eye on the miners making sure that they haven't stalled because of connection issues requiring a manual restart. Switched over to bitcoins.lc and in the last 24 hours have mined nearly 2 bitcoins vs the 1 bitcoin per day I could mine on deepbit. Not regretting the switch at all now. Also, no fees either on bitcoins.lc. No where near as good of a website, but damn I can't argue with the results.
totally offtopic, but, YAY, less people in deepbit!
Sadly I too had to switch away from deepbit. Too big of a pain constantly keeping an eye on the miners making sure that they haven't stalled because of connection issues requiring a manual restart. Switched over to bitcoins.lc and in the last 24 hours have mined nearly 2 bitcoins vs the 1 bitcoin per day I could mine on deepbit. Not regretting the switch at all now. Also, no fees either on bitcoins.lc. No where near as good of a website, but damn I can't argue with the results.
I too have had massive problems with Deepbit over the last 24 hours, many miners die after a few minutes, some won't connect at all and are seemingly banned by IP. I've switched those to Slush permanently; if I encounter any more issues in the short-term i'll just switch them all.
0 MHash/s Switching back to http://f1.deepbit.net:8332
0 MHash/s Couldn't connect to server
0 MHash/s Couldn't connect to server
Switching to http://f2.deepbit.net:8332
0 MHash/s Switching back to http://f1.deepbit.net:8332
0 MHash/s Couldn't connect to server
0 MHash/s Couldn't connect to server
Switching to http://f2.deepbit.net:8332
Is it possible I need to update my DNS cache?
Because my machine & Internet (router, etc.) has been on for a long time now.
0 MHash/s Couldn't connect to server
0 MHash/s Couldn't connect to server
Switching to http://f2.deepbit.net:8332
0 MHash/s Switching back to http://f1.deepbit.net:8332
0 MHash/s Couldn't connect to server
0 MHash/s Couldn't connect to server
Switching to http://f2.deepbit.net:8332
Is it possible I need to update my DNS cache?
Because my machine & Internet (router, etc.) has been on for a long time now.
aisde posted above A v4 IP, 2nd resolved is 46.4.55.54 in my case.
Why are my other miners still connected, but my main rig can't connect? We're all on the same IP.
I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
No, there is no limit unless you are using same worker credentials on more than 20 workers.I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
Can you try to ping pit.deepbit.net and tell me what IP address it shows ?
72.8.190.23
Why are my other miners still connected, but my main rig can't connect? We're all on the same IP.
I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
No, there is no limit unless you are using same worker credentials on more than 20 workers.I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
Can you try to ping pit.deepbit.net and tell me what IP address it shows ?
Did anyone figure this out yet?
Slush's seems to be affected as well.
I think some script kiddies are throwing a tantrum; trying to drive miners away to "lower the difficulty" so they can make money. Idiots!
I think some script kiddies are throwing a tantrum; trying to drive miners away to "lower the difficulty" so they can make money. Idiots!
I *just* tried starting up one of my miners, and here's the message I got:
[error] (ocl_bitcoin.c:318) Failure connecting and authenticating to server deepbit.net at port 8332!
Why are my other miners still connected, but my main rig can't connect? We're all on the same IP.
Also -- is it possible that I'm getting caught in some kind of anti-DDoS dragnet?
I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
Thanks,
Matthew
[error] (ocl_bitcoin.c:318) Failure connecting and authenticating to server deepbit.net at port 8332!
Why are my other miners still connected, but my main rig can't connect? We're all on the same IP.
Also -- is it possible that I'm getting caught in some kind of anti-DDoS dragnet?
I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
Thanks,
Matthew
Am getting the same error for some of my cards. Know what the problem is?
I *just* tried starting up one of my miners, and here's the message I got:
[error] (ocl_bitcoin.c:318) Failure connecting and authenticating to server deepbit.net at port 8332!
Why are my other miners still connected, but my main rig can't connect? We're all on the same IP.
Also -- is it possible that I'm getting caught in some kind of anti-DDoS dragnet?
I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
Thanks,
Matthew
[error] (ocl_bitcoin.c:318) Failure connecting and authenticating to server deepbit.net at port 8332!
Why are my other miners still connected, but my main rig can't connect? We're all on the same IP.
Also -- is it possible that I'm getting caught in some kind of anti-DDoS dragnet?
I have several miners here at my location -- is it possible I'm crossing some kind of limit of connections per IP? Did I get caught in some kind of flood control?
Thanks,
Matthew
No DDoSes today.
Those two interruptions were caused by software bug and server restart.
Those two interruptions were caused by software bug and server restart.
yep, just went down briefly a few minutes ago....
I thought he had the problem fixed! Apparently not.
Jump to: