Pages:
Author

Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 100. (Read 379078 times)

member
Activity: 77
Merit: 10
My GUIMiner is reporting Connection Problems, what's going on? Anybody else with this issue?
legendary
Activity: 2072
Merit: 1001
My gpu usage drops every 1-2minutes to 0% for a few seconds, and diablo miner says "ERROR: Can't connect to Bitcoin: connect timed out"
what's up?

guiminer is complaining of this: 2011-06-13 08:57:15: Listener for "card1": 13/06/2011 08:57:15, upstream RPC error
over and over again.
legendary
Activity: 2072
Merit: 1001
main website (haven't tried https: yet) gives this message: "Failed to connect to BTC Guild database. Please try again later."

when going to the main page and clicking my account i get this:

Failed to connect to US East BTCGuild.
newbie
Activity: 27
Merit: 0
My gpu usage drops every 1-2minutes to 0% for a few seconds, and diablo miner says "ERROR: Can't connect to Bitcoin: connect timed out"
what's up?
newbie
Activity: 56
Merit: 0
btcguild.com running again, both of my miners working again at 2.5% donation. Thanks, eleuth*.

newbie
Activity: 56
Merit: 0
btcguild.com is loading again, share counts are zeroed out and hash count not working, tho.
newbie
Activity: 56
Merit: 0
attempt to connect to http://www.btcguild.com gives error "Failed to connect to UK BTCGuild" when I attempt to load "My Account" page (10:43 AM UTC)
newbie
Activity: 56
Merit: 0
ok, the https:// site partially loads, with message "Failed to connect to UK BTCGuild" in content area on front page.
member
Activity: 77
Merit: 10
newbie
Activity: 56
Merit: 0
well, https://www.btcguild.com is "Loading" in firefox...probably not up at this point.
Miners are inconsistent with connection: one of my miners, (phoenix on pyopencl ubuntu 11.04) which has been solid all day is now at 0 Khash/sec. I will have to restart it.
The other (win 7)  is working.
newbie
Activity: 56
Merit: 0
main website (haven't tried https: yet) gives this message: "Failed to connect to BTC Guild database. Please try again later."
newbie
Activity: 56
Merit: 0
Yep, both of my current miners are going idle about every two to three minutes.
full member
Activity: 168
Merit: 100
hmmmmm.... 6% rejected shares, i think because of the idle miners.  This is not good Sad
full member
Activity: 168
Merit: 100
just the heads up
http://btcguild.com/  shows empty page, thought site wasn't working because moving to a new location until i decided to check www.btcguild.com few hours later


When it doubt, use SSL... https://btcguild.com has worked when earlier http:// was down.

-----------------------

I just started getting more idle miners and random TCP errors.  I may have to switch pools again of this continues.  Are the severs overloaded or what?

Looking at my logs, the last maybe hour or so I've gotten idle miners every 2-3 minutes...
newbie
Activity: 28
Merit: 0
Didn't want to create a whole new topic, so maybe someone here will notice and answer a few questions. First off, what exactly is the "stale" count? What is an average stale count for a round or per some period of time? How do I prevent them? Thank you for the help
legendary
Activity: 2072
Merit: 1001
anyone having rpc connection problem right now? 2 AM eastern time as i post this.
using guiminer, newer version. hostname connected to is btcguild.com

edited to add:
well it might have just been me i guess. the problem is gone. false alarm.
legendary
Activity: 1050
Merit: 1000
just the heads up
http://btcguild.com/  shows empty page, thought site wasn't working because moving to a new location until i decided to check www.btcguild.com few hours later
kjj
legendary
Activity: 1302
Merit: 1026
Statistics has nasty dark corners.

If an event has probability X per attempt, your chances of getting the event after Y attempts is not X * Y.  It is 1 - ((1/X)^Y).

Because this is exponentially decreasing, events that happen before the 50% time will come quicker than the events after it are late.  As in, it takes more attempts to get from 50% to 51% than it does from 49% to 50%.

Consider rolling a die.  You have a 1 in 6 chance of getting a 6.  If you want at least a 30% chance of getting a single 6, you only need to roll it twice.  If you want a 50% chance, you need 4 rolls.  If you want at least a 70% chance, you have to roll it 7 times.

Moving the odds from 50% to 30% saves you 2 rolls, but moving it from 50% to 70% requires 3 more.  If you look at the 1 in 6 and 5 in 6 odds, they are even worse, 1 roll vs. 10 (savings of 3 vs. loss of 6).

Now instead of a die with 6 sides, imagine a bitcoin hash with 2.436 * 10^15 sides...
newbie
Activity: 15
Merit: 0
The thing is, and I've said this about 50 times in various threads around these boards, you can't make any claims about a single event.

If there is some other thread you can point me to where all of this is already covered that would be appreciated.

I originally just wanted to know if there was something going on with reporting, since there have been a lot of those kinds of problems in the last few days due to new servers coming online, and that round was very unusual.

I am now curious as to the statistics at work here.  Most of my analysis, such as it is, is based on the Bitcoin Generation Calculator.  I am assuming that the formula used there to calculate 50% / Average / 95% times to solve a block is valid, because the calculator does seem to predict fairly well how many BTC I will receive in a given time frame at a particular hash rate and difficulty.  I will admit to being a little confused here already, though, because it seems like the numbers for 50% and Average should be the same.  I clearly don't understand the finer points that lead to this distinction, or why my assertion that a 3.5 hour round @ 1.5TH/s is extremely unlikely using those numbers is wrong.  I am trying to learn the math though, so any links are definitely appreciated.  PM me if you don't want to clutter up this thread any further.  Thanks for your help.
legendary
Activity: 1050
Merit: 1000
I guess website is moving to a new home
Pages:
Jump to: