[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers

[allinvain]

hehehe..well such is life..shit breaks...hope you get it fixed soon. Until then Slush here I come.

[1714939937]

1714939937

[1714939937]

1714939937

[1714939937]

1714939937

[1714939937]

1714939937

[1714939937]

1714939937

[eleuthria]

8:14 AM (PST): Just got off the phone with support at the datacenter, they're going to take a look at the switch and see if they can diagnose the problem.  If not they will be performing a factory reset to see if that solves it.
8:55 AM (PST): Support responded.  This was a DDoS attack, not a switch failure.  The attack has been filtered upstream and service should be returning shortly.
9:05 AM (PST): Servers are coming back online.
9:15 AM (PST): Pool servers are back online.  Website coming up shortly.

[Website Status]:  Online
[Database Status]:  Online
[US-Getwork Status]:  2/3 Online as normal, other server DNS has changed
[US-Stratum Status]:  Online
[MergedMining Status]:  Online
[Germany-Getwork Status]:  Online
[Germany-Stratum Status]:  Online

[eleuthria]

Everything is back up and running smoothly.  I will be going through and removing payouts that were recorded but not properly made (due to bitcoind timeouts).

[eleuthria]

Fixing DNS for those that can't reconnect.  Hopefully your DNS isn't cached too long.

[segabtc]

please look at 24 hour earning calculation, I think it might be wrong.

Pool Speed
      2,880.06 GH/s             24 Hour Earnings       69.68643596 BTC       PPS Rate       0.0000070470992508


24 hour earning is 69 btc??? that is not correct. decimal has moved a few places. or is that for the whole pool.

[sokay]

The mining pool as well as the website both seem to be down again.

EDIT - The website is giving database connectivity errors.

[Frequency]

The mining pool as well as the website both seem to be down again.

EDIT - The website is giving database connectivity errors.

yep:

"Failed to connect to BTC Guild database. Please try again later."

But the DE.BTCGUILD server is mining my workers are hashing so we just wait on..

[eleuthria]

Contacting the DC again to null another IP.  Sorry again, but there's not much you can do when your server is being flooded for 6-10 (best range the DC has given me so far) gbps on a 2 gbps uplink.  The switch has no option but to drop 66%+ of the packets.

[eleuthria]

Another IP has been nulled, the website is back up and responding.  I'd recommend using the de or mergedmining servers at this time, since the attack is ongoing.  I will not be moving DNS again until I believe it is safe.

[segabtc]

thank you for the update. wow 6 to 10 gbs ddos thats a serious player right there! there is only a few guys that can have that kind of power.

[bce]

thank you for the update. wow 6 to 10 gbs ddos thats a serious player right there! there is only a few guys that can have that kind of power.

Ancient Mayan Hackers!

[eleuthria]

I'm putting up some temporary servers to pickup the DNS entries that were nullrouted.  Most DNS entries still work, except the 'default' most people use, regular btcguild.com .  Using any of the other DNS entries should work normally (mine1, mine2, de, mergedmining, etc.).  Regular btcguild.com may be somewhat laggy for getwork based users.  Stratum users shouldn't worry since the getwork server will send you an IP to connect to, which re-establishes the connection rather than being proxied.

[ilovethebtc]

I seem to be having issues with payouts.  I attempted a payout this morning which did not go through and the bitcoins went back into my account later and I attempted a payout again and got this message:

A payout request is already being processed for your account (you may have clicked the link twice).

[eleuthria]

I seem to be having issues with payouts.  I attempted a payout this morning which did not go through and the bitcoins went back into my account later and I attempted a payout again and got this message:

A payout request is already being processed for your account (you may have clicked the link twice).

This should be fixed now.  I have quite a few security measures in place to make sure BTC isn't paid out multiple times.  When an attack like today's happens, sometimes those measures don't get properly reset on accounts that were active during the attack.


For Stratum users, if you're not seeing shares show up on your workers, try restarting the miner (or stratum proxy).  All servers should be working now, though the getwork servers may have some occasional delayed work due to one server still being offline.

[ilovethebtc]

This should be fixed now.  I have quite a few security measures in place to make sure BTC isn't paid out multiple times.  When an attack like today's happens, sometimes those measures don't get properly reset on accounts that were active during the attack.


For Stratum users, if you're not seeing shares show up on your workers, try restarting the miner (or stratum proxy).  All servers should be working now, though the getwork servers may have some occasional delayed work due to one server still being offline.

Looks to be working now.  Thank you sir.

[beekeeper]

Guys, despite the fact that I think (IMO) that something is wrong with btc vardiff implementation, I personally think that eleuthria is one of the best pool admins around, and basically I do think that whatever he says is mostly 99% truth, so, whenever he says one thing is like that, most of the time that's the truth, so, just chill and wait..

[eleuthria]

Guys, despite the fact that I think that something is wrong with btc vardiff implementation, I personally think that eleuthria is one of the best pool admins around, and basically I do think that whatever he says is mostly 99% truth, so, whenever he says one thing is like that, most of the time that's the truth, so, just chill and wait..

What do you think is wrong with vardiff implementation?  Current settings are it will double your difficulty if your shares per minute is above 40.  Which means:

Difficulty 1 for users that are between 0 MH/s and 2800 MH/s..
Difficulty 2 for users that are between 2800 MH/s and 5600 MH/s.
Difficulty 4 for users that are between 5600 MH/s and 8400 MH/s.

This is on a per-connection basis, so if you have multiple copies of mining software open, but each one is running separately (instead of through a stratum proxy), the vardiff is applied to each miner.  This gives an expected SPM range of 20-40, the average being 30.  This is the highest SPM target of any other pool at the moment, chosen specifically because it provides very little variance even in a small window (15-30 minutes).  Obviously this only applies to Stratum.  There is no vardiff for getwork and never will be.

[beekeeper]

As I said before, I can't exactly point, it is just my feeling. Tried to figure it out but I didn't give it enough scrutinizing time, so it is just IMO (I will edit my post).

[deadwoodluke]

Are we still being attacked? The website cannot connect to the database.
Never mind, seems to be fixed now but it is very slow.

[eleuthria]

Are we still being attacked? The website cannot connect to the database.
Never mind, seems to be fixed now but it is very slow.

The attack keeps moving an hour or two after each nullroute.  Called the DC again to have them nullroute the next one, and I'm juggling servers around to try to keep things running as much as possible.