Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 78. (Read 379078 times)
June 29, 2011, 09:37:20 PM
We got an invalid on a 2 second block. Does that mean someone else solved it in under 2 seconds? :O
June 29, 2011, 09:13:23 PM
June 29, 2011, 07:37:15 PM
Lulz
June 29, 2011, 06:57:03 PM
June 29, 2011, 06:53:33 PM
June 29, 2011, 06:43:17 PM
USWEST is dead?
June 29, 2011, 04:51:07 PM
I was in the middle of wondering wtf when el posted. Unfortunaly, I'm still getting loads of errors. Hope it's fixed soon.
You also need to explain about uswest? You mean the server is going away? Will people have to go and switch their miners to point to another new host again?
You also need to explain about uswest? You mean the server is going away? Will people have to go and switch their miners to point to another new host again?
Tomorrow I will be modifying the DNS to point uswest away from that server. After a few hours (well past the TTL), the pool will be shut down on the uswest server, leaving only the website. East, Central, NL, NL2, and DE can all handle significantly more volume now before choking, so the removal of US West's pool server will not be an issue.
June 29, 2011, 04:42:42 PM
I was in the middle of wondering wtf when el posted. Unfortunaly, I'm still getting loads of errors. Hope it's fixed soon.
You also need to explain about uswest? You mean the server is going away? Will people have to go and switch their miners to point to another new host again?
You also need to explain about uswest? You mean the server is going away? Will people have to go and switch their miners to point to another new host again?
Tomorrow I will be modifying the DNS to point uswest away from that server. After a few hours (well past the TTL), the pool will be shut down on the uswest server, leaving only the website. East, Central, NL, NL2, and DE can all handle significantly more volume now before choking, so the removal of US West's pool server will not be an issue.
June 29, 2011, 04:39:44 PM
I was in the middle of wondering wtf when el posted. Unfortunaly, I'm still getting loads of errors. Hope it's fixed soon.
You also need to explain about uswest? You mean the server is going away? Will people have to go and switch their miners to point to another new host again?
You also need to explain about uswest? You mean the server is going away? Will people have to go and switch their miners to point to another new host again?
June 29, 2011, 04:32:19 PM
I was wondering what happened to the site. I came to this thread looking for info - apparently a lot has been going on!
Thanks for the updates.
Thanks for the updates.
June 29, 2011, 04:25:30 PM
US West, East, and Central have been restarted with the bitcoind patch. West is kicking in some DDoS protection right now from the miner reconnect flooding, so the website has been temporarily taken down to avoid any calculation/communication errors between the pools. West will be back up shortly along with the website.
June 29, 2011, 02:02:33 PM
Stress testing is complete for JoelKatz' bitcoind patch. The server was able to run around 1 TH/sec before tossing out miner idles. NL1 has been returned to its original location, while NL2 is remaining pointed at EU (DE) for the time being.
NL1 and NL2 have had the bitcoind patch pushed live so far. US East and Central will receive the patch this afternoon. US West pool will be closed off tomorrow night now that we have a patch that drastically increases each server's capacity. This will speed up the site in general, and also stop new pool calculations from slowing down people that used to connect to uswest.
If we're lucky, JoelKatz (now known as our Savior) might be able to locate the new bottleneck within bitcoind to push it even further.
NL1 and NL2 have had the bitcoind patch pushed live so far. US East and Central will receive the patch this afternoon. US West pool will be closed off tomorrow night now that we have a patch that drastically increases each server's capacity. This will speed up the site in general, and also stop new pool calculations from slowing down people that used to connect to uswest.
If we're lucky, JoelKatz (now known as our Savior) might be able to locate the new bottleneck within bitcoind to push it even further.
June 29, 2011, 01:15:18 PM
Any chance of the "You generated x.yy BTC in the last 24 hours." stat being exposed through the API?
Will be added shortly.
Currently stress testing EU (DE)'s patch to bitcoind by pointing NL1 at the server. So far the results are looking good.
Thanks!!
June 29, 2011, 01:04:57 PM
Any chance of the "You generated x.yy BTC in the last 24 hours." stat being exposed through the API?
Will be added shortly.
Currently stress testing EU (DE)'s patch to bitcoind by pointing NL1 at the server. So far the results are looking good.
June 29, 2011, 12:56:36 PM
Any chance of the "You generated x.yy BTC in the last 24 hours." stat being exposed through the API?
June 29, 2011, 11:42:14 AM
Not that it matters much with the huge difficulty, but what happened to the 'Blocks found' column? I know it doesn't really do anything and mostly useless but it was nice to know how many winners your workers were responsible for. 
Blocks found hasn't been working properly since the split to multiple servers. The information is there, but spread among all of the servers currently. I'll probably get around to setting up the servers to synchronize block finds this weekend so that Blocks Found and Hall of Fame can return.
UPDATE: A couple quick restarts on EU (DE) to push a patched bitcoind that uses threaded RPC calls and keep alive connections. Stress testing the new setup now.
June 29, 2011, 11:39:38 AM
Not that it matters much with the huge difficulty, but what happened to the 'Blocks found' column? I know it doesn't really do anything and mostly useless but it was nice to know how many winners your workers were responsible for.
June 29, 2011, 08:42:11 AM
UK's load balance service crashed and failed to restart overnight. The new block allocation script assumes when a pool server returns 0 shares for a round, there was a sync error and it aborts calculating the block.
Taking UK offline, it's causing a lot of problems and part of it is due to using a software level load balancer for a job that truly needs either a hardware or custom kernel/OS level balancer.
UK's addresses are now pointing at NL2 for the time being. Going to work on getting a similar setup to the server I ordered (should be delivered by next Monday), but as a dedicated host lease in the EU until the US server is setup, tested, and running live.
UPDATE: Banned an entire range of IPs from Brazil. It has been hitting NL1/NL2 hard the last few days, and now the entire range has been banned to speed up the auto ban process.
Taking UK offline, it's causing a lot of problems and part of it is due to using a software level load balancer for a job that truly needs either a hardware or custom kernel/OS level balancer.
UK's addresses are now pointing at NL2 for the time being. Going to work on getting a similar setup to the server I ordered (should be delivered by next Monday), but as a dedicated host lease in the EU until the US server is setup, tested, and running live.
UPDATE: Banned an entire range of IPs from Brazil. It has been hitting NL1/NL2 hard the last few days, and now the entire range has been banned to speed up the auto ban process.
June 29, 2011, 08:36:01 AM
Either the round times are still not updating, or the "round shares" number in the site header seems to be way too low...
June 29, 2011, 08:24:00 AM
The round time didn't reset after the last block it's currently up to 3hr 55min (should be around 50 minutes).
Everything else looks good though. =)
Everything else looks good though. =)
Yep, looks to be just the round time stats, but the rounds are rolling along mostly like normal. The round that ended at 01:25 local time seems to have been one of the longest I have seen since turning on monitoring though.
Jump to: