Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 196. (Read 837101 times)

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.

up Again it seems.

Was it a DDOS or hardware failure?

However, BTCGuild made 32 blocks in the last 24 hours.
AM did 21, and BM did... 2.

You can bump the 5770 up to 256 work size. (or at least 192, I can't quite recall)

BTCguild is under attack too.

[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 !!

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.

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.

Thats a very depressing conspiracy theory...

Plausible! Damn!!

 


  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.

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

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

Servers down again!

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.

Do I need to point my BFGMiner, on stratum, to a different server, or just shut it down and restart?

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.

Thanks. I will check it out in the morning. Right now I need to get some rest 

Did you also install the the UART to COM drivers from here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Here is what my .bat file looks like and its working fine

 
For the COM8 part, put what ever usb port the miner is in. For me on this computer it didn't matter what port I have it in as long as I put COM8. But on another computer I had to switch it to COM3 or COM4 depending on which port I was using.  

Look at the cgminer screen, press the letter P for pools, then add a backup pool, once added, make sure you get back to main screen and press S for settings, then W for Write settings, then enter for default settings file name.. (cgminer.conf) This saves the backup pool in the settings.

Then your set up with a backup pool, you might also need to ENABLE failover, in the Pools menu I mentioned, make sure the screen says failover enabled