DrHaribo (OP)
Legendary
Offline
Activity: 2730
Merit: 1034
Needs more jiggawatts
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 08:43:01 AM |
|
A new server is up and running.
Still 40 Stratum workers and 700 gbt/getwork workers on the old server.
If you are one of those then you won't see your hashrate on the website and it won't be included in the total pool hashrate. It pulls stats only from one server - this will be fixed soon. Hashrates on shifts and blocks pages are correct, but the live hashrates are not. If you don't see your hashrate you can try restarting your miner, that should make it connect to the new server (should not be necessary with BitMinter client).
The old server will be taken down for a bit of maintenance at some point, but I'll wait until there are fewer workers connecting there.
|
|
|
|
Guardian of Forever
Newbie
Offline
Activity: 55
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 01:19:36 PM |
|
Do I need to point my BFGMiner, on stratum, to a different server, or just shut it down and restart?
|
|
|
|
westkybitcoins
Legendary
Offline
Activity: 980
Merit: 1004
Firstbits: Compromised. Thanks, Android!
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 01:23:16 PM |
|
I'm having trouble getting my BFL Jalapeno to connect with the Beta Java client. It can (usually) see my ASIC just fine, but once I start it, no hashing occurs, and the stats on the site don't show I'm sending any results. Turning on the CPU results in some hashing, so there's no bad connection or anything, and EasyMiner lets me connect to Eclipse without incident.
I'm running the latest version of Java, on Parallels (64-bit Win 7) on a Mac. The client worked fine until the DDOS attacks began this weekend; now for some strange reason I can't hash with it, despite it showing I'm connected to the server.
Anything change in the client I should know about? Or something new I need to do?
EDIT: I have verbose logs turned on; client keeps saying "New connection established" followed by "Connection closed after X request-response exchanges", where X is any number from 0 to 3.
|
Bitcoin is the ultimate freedom test. It tells you who is giving lip service and who genuinely believes in it.
... ... In the future, books that summarize the history of money will have a line that says, “and then came bitcoin.” It is the economic singularity. And we are living in it now. - Ryan Dickherber... ... ATTENTION BFL MINING NEWBS: Just got your Jalapenos in? Wondering how to get the most value for the least hassle? Give BitMinter a try! It's a smaller pool with a fair & low-fee payment method, lots of statistical feedback, and it's easier than EasyMiner! (Yes, we want your hashing power, but seriously, it IS the easiest pool to use! Sign up in seconds to try it!)... ... The idea that deflation causes hoarding (to any problematic degree) is a lie used to justify theft of value from your savings.
|
|
|
Paulizei
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 98
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 01:49:15 PM |
|
Servers down again!
|
|
|
|
Guardian of Forever
Newbie
Offline
Activity: 55
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 01:50:02 PM |
|
I noticed a change in the Bitminter client over the weekend. You might need to check your options, and see if the client is set to start your rigs. I am just guessing, as I am still waiting on my BFL order..............And waiting.... Also looks like a new attack is under way...
Good luck
|
|
|
|
OmegaNemesis28
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 02:08:35 PM Last edit: June 19, 2013, 02:42:25 PM by OmegaNemesis28 |
|
Servers down again!
Yeah Im getting connection timeout EDIT: Came back up, went back down: :41] Communication error, HTTP status code 500 2013.06.19 [10:41] Communication error, HTTP status code 500 2013.06.19 [10:41] Communication error, HTTP status code 500 2013.06.19 [10:42] Connection failed: Connection refused: no further information 2013.06.19 [10:43] Connection timed out 2013.06.19 [10:43] Connection timed out 2013.06.19 [10:43] Connection timed out
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4228
Merit: 8451
'The right to privacy matters'
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 02:23:55 PM Last edit: June 19, 2013, 02:44:30 PM by philipma1957 |
|
Servers down again!
Yeah Im getting connection timeout Yeah this truly looks like a full out attack bent on killing off bitminter. Bitminter is the only easy way to set a miner up and they are under heavy attack. but if you look at this chart http://bitcoincharts.com/ you will see the network has really dropped off. As I see it since asic miner is a stand alone dedicated solo miner and now all the competition is under attack. leaving them easier hashing. not that the diff is easier still 19 mill but less playing for the pot of blocks what is it 2100 blocks at 19 mill. Now that 45Th is knocked off and only 115Th is working and asic miner has about 40Th of the 115Th it gives them more blocks at this diff point of 19 mill. If 160Th was going at the pile of blocks at 19 mill diff asic miner would earn 40Th/160Th . but now we are at 40Th/115Th as long as this attack is maintained asic miner stock holders get more short term earnings. since they pay div weekly any larger stock holder can score serious cash by doing a long attack. So 40/115 is 34 percent vs 40/160 25 percent. so right now asic miner gets 34 percent of 2100 blocks vs 25 percent or 714 blocks of 25 vs 525 blocks at diff of 19 mill . big difference in dividends. if you have a good amount of shares doing a ddos pays off. pool operators must adjust to this problem since it will not go away without a real fix. the fix is need without miners doing the work. auto switching the top 10 pools with no work by any miner to do the setup would end these attacks. If not BTC will die. pools need an auto switching program agreement. you the miner pick one pool if it goes done you do not have a backup picked you go to auto switching. Why because 1 backup set by you the miner is not enough to stop the problem. A 3 or 4 pool attack kills the backup lowers the network hash allowing AM to go at the pile of gold with less competition.
|
|
|
|
Paulizei
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 98
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 03:20:58 PM |
|
Servers down again!
Yeah Im getting connection timeout Yeah this truly looks like a full out attack bent on killing off bitminter. Bitminter is the only easy way to set a miner up and they are under heavy attack. but if you look at this chart http://bitcoincharts.com/ you will see the network has really dropped off. As I see it since asic miner is a stand alone dedicated solo miner and now all the competition is under attack. leaving them easier hashing. not that the diff is easier still 19 mill but less playing for the pot of blocks what is it 2100 blocks at 19 mill. Now that 45Th is knocked off and only 115Th is working and asic miner has about 40Th of the 115Th it gives them more blocks at this diff point of 19 mill. If 160Th was going at the pile of blocks at 19 mill diff asic miner would earn 40Th/160Th . but now we are at 40Th/115Th as long as this attack is maintained asic miner stock holders get more short term earnings. since they pay div weekly any larger stock holder can score serious cash by doing a long attack. So 40/115 is 34 percent vs 40/160 25 percent. so right now asic miner gets 34 percent of 2100 blocks vs 25 percent or 714 blocks of 25 vs 525 blocks at diff of 19 mill . big difference in dividends. if you have a good amount of shares doing a ddos pays off. pool operators must adjust to this problem since it will not go away without a real fix. the fix is need without miners doing the work. auto switching the top 10 pools with no work by any miner to do the setup would end these attacks. If not BTC will die. pools need an auto switching program agreement. you the miner pick one pool if it goes done you do not have a backup picked you go to auto switching. Why because 1 backup set by you the miner is not enough to stop the problem. A 3 or 4 pool attack kills the backup lowers the network hash allowing AM to go at the pile of gold with less competition. Plausible! Damn!!
|
|
|
|
derekleong75
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 03:28:47 PM |
|
Thats a very depressing conspiracy theory...
|
|
|
|
SilentSonicBoom
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 04:22:55 PM |
|
Which mining pools are being attacked by DDos? Is it only certain ones or are all the top 10 by hashrate experiencing issues simultaneously with other mining pools? This really is not good news for the "little guy" if solo mining groups are benefitting from these attacks.
|
|
|
|
not.you
Legendary
Offline
Activity: 1726
Merit: 1018
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 04:26:22 PM |
|
I have seen on many pools where my miner is diverted to another address either by IP or name when I connect. I think what is needed is for a pool owner to have a bunch of IP's that they can divert miners to as they connect. Anyone who wanted to DDOS would need to connect a miner (or at least receive and examine the packet responses) and see where the miner's were being diverted and then DDOS that IP. They could of course DDOS the initial connection address but miners keep trying to connect so eventually the response that diverts the miner should get back through to the miner and send it connecting to the alternate address. Since DDOS is usually accomplished with a lot of zombie machines it takes time to divert them all to different addresses so as long as the pool owner can switch his mining addresses fairly quickly it should take a very large botnet to completely stop a pool from mining.
|
|
|
|
miner49dk
Newbie
Offline
Activity: 22
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 04:33:19 PM |
|
[19.06.13 18:32:44] Connecting to: http://mint.bitminter.com:8332/ [19.06.13 18:32:44] Using Apple OpenCL 1.2 (Aug 24 2012 00:53:09) [19.06.13 18:32:46] Added ATI Radeon HD 5770 (#1) (10 CU, local work size of 128) [19.06.13 18:33:02] ERROR: Cannot connect to mint.bitminter.com: Read timed out [19.06.13 18:33:17] ERROR: Cannot connect to mint.bitminter.com: Read timed out [19.06.13 18:33:33] ERROR: Cannot connect to mint.bitminter.com: Read timed out I think i might cry soon. Or better, find the attackers and make them cry !!
|
|
|
|
Optics
Newbie
Offline
Activity: 12
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 04:33:48 PM |
|
Which mining pools are being attacked by DDos?
BTCguild is under attack too.
|
|
|
|
PCMiner
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 05:03:54 PM |
|
[19.06.13 18:32:44] Connecting to: http://mint.bitminter.com:8332/ [19.06.13 18:32:44] Using Apple OpenCL 1.2 (Aug 24 2012 00:53:09) [19.06.13 18:32:46] Added ATI Radeon HD 5770 (#1) (10 CU, local work size of 128) [19.06.13 18:33:02] ERROR: Cannot connect to mint.bitminter.com: Read timed out [19.06.13 18:33:17] ERROR: Cannot connect to mint.bitminter.com: Read timed out [19.06.13 18:33:33] ERROR: Cannot connect to mint.bitminter.com: Read timed out I think i might cry soon. Or better, find the attackers and make them cry !! You can bump the 5770 up to 256 work size. (or at least 192, I can't quite recall)
|
|
|
|
m3ta
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 05:18:19 PM |
|
Which mining pools are being attacked by DDos?
BTCguild is under attack too. However, BTCGuild made 32 blocks in the last 24 hours. AM did 21, and BM did... 2.
|
|
|
|
mazedk
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 06:14:28 PM |
|
up Again it seems.
Was it a DDOS or hardware failure?
|
|
|
|
PCMiner
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 06:49:01 PM Last edit: June 19, 2013, 07:21:19 PM by PCMiner |
|
Dr, can you clarify a little about what's going on with your server switch you mentioned earlier? At this time I'm seeing the following:
I have: 5 Machines listed on my worker list page, I used to have 10. Each machine currently listed in the workers list page is a Java client. 2 of the 5 machines in my worker list are showing as active, one machine (the one I'm typing on actually) is also active, but hasn't shown as active on the website since I started checking about 40 min ago. The other 2 listed machines are shut down at the moment, but do show up as inactive on my workers page. I'm missing 5 other workers from my list. Of these missing 5, 3 are currently active. (and looking at them here, they are hashing) Of the missing machines, 2 are Java clients, 1 is a cgminer machine. The remaining 2 missing machines are not active at this time (machines are powered down). [/edit I have moved my cgminer box to a backup pool since posting this]
The worker machine total hash, and the main stats page total hash don't add even nearly close. (showing 1500 on main stats, 190 on worker)
I don't think anything nefarious is going on, but just looking for some clarity here. I can understand this whole DDoS thing is annoying as fuck for you, and everyone else.
In a nutshell, every machine locally is hashing when I look at them, but only some are showing up on the site, and some others aren't showing up. And my hash numbers on the site are all screwy.
Also should add each Java client is running 1.4 of your software, and each machine has the latest Java update that was pushed out a few days ago. (Java 7 update 25?)
/edit Added more info and clarified.
|
|
|
|
DrHaribo (OP)
Legendary
Offline
Activity: 2730
Merit: 1034
Needs more jiggawatts
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 07:41:54 PM |
|
I set TTL (time-to-live) on the DNS entry to just 10 minutes. So after I switched mint.bitminter.com over to point at the new us1.bitminter.com workers should have followed fairly quickly.
But still there are 600 getwork/gbt miners and 2 stratum miners at the old server. These don't currently show up with a hashrate at the website. But if you wait 1 minute and reload the page you should see their accepted proofs of work have gone up. Live hashrates are only gathered from one server. Currently anti DDoS and stable mining has priority over fixing this.
BitMinter client specifically sets the java virtual machine to not cache DNS lookups for long. I suspect there are some (broken) DNS servers out there that ignore TTL settings. Maybe they'll cache for 24 hours no matter what TTL is.
|
|
|
|
eleuthria
Legendary
Offline
Activity: 1750
Merit: 1007
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 07:45:45 PM |
|
I set TTL (time-to-live) on the DNS entry to just 10 minutes. So after I switched mint.bitminter.com over to point at the new us1.bitminter.com workers should have followed fairly quickly.
But still there are 600 getwork/gbt miners and 2 stratum miners at the old server. These don't currently show up with a hashrate at the website. But if you wait 1 minute and reload the page you should see their accepted proofs of work have gone up. Live hashrates are only gathered from one server. Currently anti DDoS and stable mining has priority over fixing this.
BitMinter client specifically sets the java virtual machine to not cache DNS lookups for long. I suspect there are some (broken) DNS servers out there that ignore TTL settings. Maybe they'll cache for 24 hours no matter what TTL is.
I can guarantee DNS caching will give you headaches for the rest of your days. It may not even be DNS servers, but local home routers which are caching the DNS beyond the TTL. To this day, I have just come to accept that DNS voodoo will leave some people stranded and there's nothing you can do to make it work for everyone.
|
RIP BTC Guild, April 2011 - June 2015
|
|
|
PCMiner
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 07:53:21 PM |
|
I set TTL (time-to-live) on the DNS entry to just 10 minutes. So after I switched mint.bitminter.com over to point at the new us1.bitminter.com workers should have followed fairly quickly.
But still there are 600 getwork/gbt miners and 2 stratum miners at the old server. These don't currently show up with a hashrate at the website. But if you wait 1 minute and reload the page you should see their accepted proofs of work have gone up. Live hashrates are only gathered from one server. Currently anti DDoS and stable mining has priority over fixing this.
BitMinter client specifically sets the java virtual machine to not cache DNS lookups for long. I suspect there are some (broken) DNS servers out there that ignore TTL settings. Maybe they'll cache for 24 hours no matter what TTL is.
Ok, that clears up some of the mystery here. What about the workers that are no longer listed on my workers page? Do I need to re-enter this information? Also for the one machine that I use with cgminer do I need to change any settings? (It's currently on a backup pool but I would like to return to bitminter with it as it's my most powerful box)
|
|
|
|
|