Author

Topic: [BTC-TC] Virtual Community Exchange [CLOSED] - page 105. (Read 316534 times)

member
Activity: 77
Merit: 10
I'm unable to get the /transfers to load at all. /security/*, /account, and /portfolio load fine now, most of the time, but /transfers won't load at all.
hero member
Activity: 938
Merit: 502
Hi all.

More DDoS this morning.  I'm pretty sure they got around the DDoS protection by extracting the server's IP from the emails the site sends.  They were attacking the server's base IP and email is the only real give-away I can think of.  (open to suggestions from you other site operators out there.)

We've had to move the server and all outbound emails have been suspended for the time being.


Thanks for the prompt update burnside
legendary
Activity: 938
Merit: 1000
What's a GPU?
I'm actually leaning toward the bottleneck being something CPU related.  When the site slows down, the cpu on bitcoind pegs at 100% and disk IO does not seem to spike a whole lot.  (I've been graphing the system via collectd.)

Since bitcoind is not multithreaded, I think I'm pretty much at it's limit.

I've never seen it done before, but would running two bitcoind servers (and subsequently moving half of the accounts to the new one) mitigate the problem?
legendary
Activity: 1106
Merit: 1006
Lead Blockchain Developer
The site is currently made up of 4 servers.  Not going to go into detail regarding the layout, but bitcoind as of last week (when I posted about working on a server improvement) has been running on a dedicated SSD-backed server.  It has a 140 MB wallet and still takes ages to process getBalance requests.  My guess is that it's iterating through all of the thousands of transactions in the BerkeleyDB on every request or something because it performs very poorly.

Cheers.


Have you thought about using a ramdrive to host the wallet? Should improve things quite significantly speed-wise. Obviously it should have sane backup procedures in case of power loss.

I'm actually leaning toward the bottleneck being something CPU related.  When the site slows down, the cpu on bitcoind pegs at 100% and disk IO does not seem to spike a whole lot.  (I've been graphing the system via collectd.)

Since bitcoind is not multithreaded, I think I'm pretty much at it's limit.
hero member
Activity: 634
Merit: 500
Given the track record of former exchanges even the slightest bump makes me a little uncomfortable. I really hope this one isn't going the way of the dodo too...

I have confidence in Burnside. Hosting servers is his business (seriously, look at his sig).
Besides, even if there is a catastrophic event, all the asset issuers have API access to all the shareholder data (and emailed twice a day just to be sure). It would be very easy to move on--this is one of the best features of btct.co/litecoinglobal.com.

Have you thought about using a ramdrive to host the wallet? Should improve things quite significantly speed-wise. Obviously it should have sane backup procedures in case of power loss.

I think the only way to really resolve the bitcoind wallet problem is to move the wallet from a Berkeley DB file into a dedicated database like MySQL or MariaDB. I have no idea how other sites do this, but it would take care of the problem.
full member
Activity: 196
Merit: 100
If this attacker thinks he can lower the share price, he's mistaken.  I think people are more likely to hold onto a good dividend paying stock through something like this.  If the share price goes down, it becomes even dumber to sell because the dividend % will be higher.  If we only depended on share price, then maybe this would have more of an affect.
If manipulating price is his motivation, he's a fool Cheesy
sr. member
Activity: 248
Merit: 252
The site is currently made up of 4 servers.  Not going to go into detail regarding the layout, but bitcoind as of last week (when I posted about working on a server improvement) has been running on a dedicated SSD-backed server.  It has a 140 MB wallet and still takes ages to process getBalance requests.  My guess is that it's iterating through all of the thousands of transactions in the BerkeleyDB on every request or something because it performs very poorly.

Cheers.


Have you thought about using a ramdrive to host the wallet? Should improve things quite significantly speed-wise. Obviously it should have sane backup procedures in case of power loss.
hero member
Activity: 518
Merit: 500
Hi all.

More DDoS this morning.  I'm pretty sure they got around the DDoS protection by extracting the server's IP from the emails the site sends.  They were attacking the server's base IP and email is the only real give-away I can think of.  (open to suggestions from you other site operators out there.)

We've had to move the server and all outbound emails have been suspended for the time being.


Talk to topace/lightbox, he figured this out I think.
legendary
Activity: 1106
Merit: 1006
Lead Blockchain Developer
Hi all.

More DDoS this morning.  I'm pretty sure they got around the DDoS protection by extracting the server's IP from the emails the site sends.  They were attacking the server's base IP and email is the only real give-away I can think of.  (open to suggestions from you other site operators out there.)

We've had to move the server and all outbound emails have been suspended for the time being.


Given the track record of former exchanges even the slightest bump makes me a little uncomfortable. I really hope this one isn't going the way of the dodo too...

Not if I can help it.

Looks to me like growing pains. Pretty serious volume last few days.

All of this growth is great for BTC-TC.  By my count, it looks like BTC-TC has traded more than 20k BTC worth of securities so far for May. 

I hope the DDoS issue resolves itself.  I understand that DDoS is a particularly difficult/tedious problem to resolve (it's akin to playing whack-a-mole), but I have faith in burnside's ability.   Just be patient, and don't lose confidence.  If this is another DDoSer, that's exactly what they want.

Thank you, I definitely appreciate that.

I'll work today on figuring out how to restore the email system.

Cheers.
member
Activity: 67
Merit: 10
Given the track record of former exchanges even the slightest bump makes me a little uncomfortable. I really hope this one isn't going the way of the dodo too...
full member
Activity: 194
Merit: 100
My guess is that in addition to any ddos that may be happening, people are trying to get in a last-minute purchase before ASICminer dividends hit.  Or hammering the server trying to see how rich they are this morning.  
member
Activity: 97
Merit: 10
Looks to me like growing pains. Pretty serious volume last few days.

All of this growth is great for BTC-TC.  By my count, it looks like BTC-TC has traded more than 20k BTC worth of securities so far for May. 

I hope the DDoS issue resolves itself.  I understand that DDoS is a particularly difficult/tedious problem to resolve (it's akin to playing whack-a-mole), but I have faith in burnside's ability.   Just be patient, and don't lose confidence.  If this is another DDoSer, that's exactly what they want.
legendary
Activity: 1806
Merit: 1003
The bottleneck is bitcoind.  I spent a bunch of time last night working on shifting requests away from bitcoind, that code is live now on litecoinglobal.com.  If it holds up, I'll roll it out to btct.co soon.  Eventually we'll shift everything but deposits/withdrawals out of bitcoind, but it will be a very slow process unfortunately.
Why don't you run bitcoind on a seperated server? It doesn't fix the problem but at least bitcoind won't slow down normal trading.
Personally I don't care if I have to wait a few minutes for my withdrawal or deposit to show up but I hate it when I can't execute trades.

The site is currently made up of 4 servers.  Not going to go into detail regarding the layout, but bitcoind as of last week (when I posted about working on a server improvement) has been running on a dedicated SSD-backed server.  It has a 140 MB wallet and still takes ages to process getBalance requests.  My guess is that it's iterating through all of the thousands of transactions in the BerkeleyDB on every request or something because it performs very poorly.

Cheers.


Why not regularly shrink the wallet size? 140MB wallet is pretty outrageous. I don't think anyone else is running bitcoind with a wallet of that size.
vip
Activity: 812
Merit: 1000
13
Quote
Error:
backend server failure at 145

What's this?
hero member
Activity: 492
Merit: 500
Looks to me like growing pains. Pretty serious volume last few days.
member
Activity: 108
Merit: 10
Is the site down for maintenance?  Or under DDOS? Hate to see Cloudflare.
hero member
Activity: 546
Merit: 500
errrrr not sure if I should transfer more to my btct.co wallet with site being wonky
legendary
Activity: 1106
Merit: 1006
Lead Blockchain Developer
The bottleneck is bitcoind.  I spent a bunch of time last night working on shifting requests away from bitcoind, that code is live now on litecoinglobal.com.  If it holds up, I'll roll it out to btct.co soon.  Eventually we'll shift everything but deposits/withdrawals out of bitcoind, but it will be a very slow process unfortunately.
Why don't you run bitcoind on a seperated server? It doesn't fix the problem but at least bitcoind won't slow down normal trading.
Personally I don't care if I have to wait a few minutes for my withdrawal or deposit to show up but I hate it when I can't execute trades.

The site is currently made up of 4 servers.  Not going to go into detail regarding the layout, but bitcoind as of last week (when I posted about working on a server improvement) has been running on a dedicated SSD-backed server.  It has a 140 MB wallet and still takes ages to process getBalance requests.  My guess is that it's iterating through all of the thousands of transactions in the BerkeleyDB on every request or something because it performs very poorly.

Cheers.
hero member
Activity: 968
Merit: 515
The bottleneck is bitcoind.  I spent a bunch of time last night working on shifting requests away from bitcoind, that code is live now on litecoinglobal.com.  If it holds up, I'll roll it out to btct.co soon.  Eventually we'll shift everything but deposits/withdrawals out of bitcoind, but it will be a very slow process unfortunately.
Why don't you run bitcoind on a seperated server? It doesn't fix the problem but at least bitcoind won't slow down normal trading.
Personally I don't care if I have to wait a few minutes for my withdrawal or deposit to show up but I hate it when I can't execute trades.
legendary
Activity: 1106
Merit: 1006
Lead Blockchain Developer
Wow, volume on the exchange is just huge.

4,242.73 last 24h Shocked
Its great, but about 90-95% is ASICMINER

I'd definitely like to see more diversity, but I'm not going to look a gift horse in the mouth.  Smiley


btct.co becomes what Gox was some weeks ago. ~.~

Oh come on now, that's not fair  Undecided Burnside will provide updates and ensure that people still own their shares. Such is life when a certain asset sky rockets...

Or worse, what GLBSE was... ugh.   Tongue

The bottleneck is bitcoind.  I spent a bunch of time last night working on shifting requests away from bitcoind, that code is live now on litecoinglobal.com.  If it holds up, I'll roll it out to btct.co soon.  Eventually we'll shift everything but deposits/withdrawals out of bitcoind, but it will be a very slow process unfortunately.


Cheers.

Jump to: