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

woke to find one of my miners not able to connect to uscentral as well , sigh .   sleeping is bad to do when your loosing a miner


Jen

3:30 the previous block and almost 4 hours this one? Are we really being so unlucky or there is something wrong?

now sitting at about 2500, but us central seems to be out of commission.

I am sure we will know once Eleuthria wakes up. I think there was hiccup with most of the servers, but some seemed to have recovered. US Central seems to have bit the dust though. This is why it is nice to have so many because you just have to make a small edit to your miners or have a backup being a different BTC Guild server and you can just keep going on the same block. I feel like the chances of them all going down at once is pretty small.

My miners are still reporting "Trying to fail back to primary server (BTCguild)" ... followed by a failure.

What's going on, a DDoS?

Matthew

no clue, but i just noticed a string of idles on my workers.

must have been a hiccup with BTCGuild. all systems go.

What happened to all the hashing power of BTCGuild?  It was close to 3000 GH/sec.... now its back down to about 1500 GH/sec.

0.3.22 I believe, but there were bugs for some users when used to host solo mining, so the current version 0.3.23 is about it.

I'm not sure whether to apologize or not but I feel like I'm being rather needy tonight.

Round times and round shares are increasing, as are my personal shares, but none of these values, with the exception of round time are increasing as I would normally expect them to be. I don't have any concrete numbers, nor have I wrote them down in the past but from what I recall normally we do a 100%(1379223) of difficulty in 40 minutes or so. A few minutes ago we have done 1.96 M shares in 1:46:00. I'm not a stats person so I'm not even going to attempt a comparison.

What's going on?

Edit:
Confirmed increased NM. Was just crying wolf.

Dang I wish I had your problem with those low latencies ;o)

Hmm before I hit post I tried a ping or three and I am losing packets all of a sudden. Something on your end eluthria?
Pinging uscentral.btcguild.com [69.147.241.114] with 32 bytes of data:
Reply from 69.147.241.114: bytes=32 time=61ms TTL=50
Reply from 69.147.241.114: bytes=32 time=58ms TTL=50
Request timed out.
Reply from 69.147.241.114: bytes=32 time=56ms TTL=50
Request timed out.
Reply from 69.147.241.114: bytes=32 time=65ms TTL=50
Request timed out.
Reply from 69.147.241.114: bytes=32 time=59ms TTL=50
Reply from 69.147.241.114: bytes=32 time=62ms TTL=50
Request timed out.

Ping statistics for 69.147.241.114:
    Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
    Minimum = 56ms, Maximum = 65ms, Average = 60ms

Edit: Sorry I'm a network guy and I abhor people saying it is my problem, which it usually isn't. Are you aware of any changes on uscentral that is causing large packet loss? ;o) and on a side note my latency dropped almost in half as well.

  8    30 ms    34 ms    31 ms  ggr2.attga.ip.att.net [12.122.81.97]
  9    29 ms    29 ms    34 ms  206.111.2.89.ptr.us.xo.net [206.111.2.89]
 10    45 ms    37 ms    31 ms  207.88.14.193.ptr.us.xo.net [207.88.14.193]
 11    55 ms    61 ms    52 ms  207.88.14.10.ptr.us.xo.net [207.88.14.10]
 12    53 ms    60 ms    57 ms  edge1.dal.ubiquityservers.com [207.88.185.110]
 13    60 ms    66 ms    65 ms  69.147.241.114.rdns.ubiquityservers.com [69.147.
241.114]

Trace complete.

Edit again: I just wanted to clarify that I'm not saying it is btcguilds fault at all lol. I re-read my edit and I realized it could be interpreted as such. My apologies if anyone understood it that way. I'm just asking if eleuthria is aware of anything. ;o) ha

from my desktop...

skip@c17-desktop:~$ traceroute uscentral.btcguild.com
traceroute to uscentral.btcguild.com (69.147.241.114), 30 hops max, 60 byte packets
  
 4  Gi0-2-4-0.austtxrdcsc-rtr2.austin.rr.com (24.27.13.38)  20.863 ms  25.198 ms  25.361 ms
 5  agg20.austtxa-cr01.texas.rr.com (66.68.2.236)  34.327 ms  34.966 ms  35.115 ms
 6  te0-12-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.56)  44.035 ms  21.949 ms  19.852 ms
 7  ae-4-0.cr0.dfw10.tbone.rr.com (66.109.6.88)  19.020 ms  21.198 ms  21.403 ms
 8  ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209)  25.402 ms ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179)  25.553 ms  29.158 ms
 9  ip65-47-204-137.z204-47-65.customer.algx.net (65.47.204.137)  29.319 ms te1-2-0d0.cir1.dallas2-tx.us.xo.net (65.47.204.5)  34.630 ms ip65-47-204-105.z204-47-65.customer.algx.net (65.47.204.105)  62.978 ms
10  207.88.15.46.ptr.us.xo.net (207.88.15.46)  33.945 ms  34.108 ms  38.790 ms
11  65.106.4.234.ptr.us.xo.net (65.106.4.234)  39.003 ms  43.816 ms  43.444 ms
12  edge1.dal.ubiquityservers.com (207.88.185.110)  24.686 ms  16.657 ms  25.423 ms
13  69.147.241.114.rdns.ubiquityservers.com (69.147.241.114)  19.190 ms  23.139 ms  23.294 ms

Lemme go hook a miner back to it.

EDIT: Strange.  Miner(Diablo) still not connecting to it but connects to deep and east.  Dang thing is practically next door isn't it?  Maybe I should just run some cat6 to it.

a few min later:

4  Gi0-2-4-0.austtxrdcsc-rtr2.austin.rr.com (24.27.13.38)  23.987 ms  24.148 ms  26.744 ms
 5  agg20.austtxa-cr01.texas.rr.com (66.68.2.236)  29.486 ms  40.763 ms  40.927 ms
 6  te0-12-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.56)  40.567 ms  23.721 ms  25.457 ms
 7  ae-4-0.cr0.dfw10.tbone.rr.com (66.109.6.88)  18.275 ms  22.275 ms  26.334 ms
 8  ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209)  26.508 ms  30.784 ms  30.942 ms
 9  ge5-0-2d0.cir1.dallas2-tx.us.xo.net (65.47.204.29)  31.101 ms ip65-47-204-105.z204-47-65.customer.algx.net (65.47.204.105)  35.063 ms ip65-47-204-141.z204-47-65.customer.algx.net (65.47.204.141)  35.234 ms
10  207.88.15.46.ptr.us.xo.net (207.88.15.46)  35.396 ms  38.586 ms  38.742 ms
11  65.106.4.234.ptr.us.xo.net (65.106.4.234)  42.684 ms  42.848 ms  42.993 ms
12  edge1.dal.ubiquityservers.com (207.88.185.110)  28.384 ms  39.366 ms  13.234 ms
13  69.147.241.114.rdns.ubiquityservers.com (69.147.241.114)  13.336 ms  17.540 ms  23.253 ms

ping summary...

--- uscentral.btcguild.com ping statistics ---
39 packets transmitted, 30 received, 23% packet loss, time 38070ms
rtt min/avg/max/mdev = 18.410/25.881/41.100/5.130 ms

went from 37% loss to 23% to now 4%...

64 bytes from 69.147.241.114.rdns.ubiquityservers.com (69.147.241.114): icmp_req=50 ttl=52 time=15.9 ms
^C
--- uscentral.btcguild.com ping statistics ---
50 packets transmitted, 48 received, 4% packet loss, time 49101ms
rtt min/avg/max/mdev = 12.755/15.516/28.078/2.900 ms


BTW, these are from a machine that is 1 switch closer to the router than all the miners are except 1 which is on the same switch as this machine.

US Central is connecting fine from central California.

Also, fixed some payouts.  A few payouts were requested from US West while the bitcoind's were being switched over.  I voided those payouts so the funds are back in your account to request again.

You could post a traceroute. It may help eleuthria if he has to call the hosting provider and prove a routing issue. No one likes to admit they have a network problem and can sometimes be difficult to prove ;o)

Tracing route to uscentral.btcguild.com [69.147.241.114]
over a maximum of 30 hops:

~
  7   120 ms   101 ms   101 ms  cr2.cgcil.ip.att.net [12.122.153.6]
  8   121 ms   101 ms   101 ms  ggr2.attga.ip.att.net [12.122.81.97]
  9   122 ms   101 ms   101 ms  206.111.2.89.ptr.us.xo.net [206.111.2.89]
 10   123 ms    99 ms   102 ms  207.88.14.193.ptr.us.xo.net [207.88.14.193]
 11   122 ms   100 ms   103 ms  207.88.14.10.ptr.us.xo.net [207.88.14.10]
 12   124 ms   101 ms   100 ms  edge1.dal.ubiquityservers.com [207.88.185.110]
 13   122 ms   101 ms   101 ms  69.147.241.114.rdns.ubiquityservers.com [69.147.
241.114]

Central is good from North Midwest.

lost route to uscentral server about 2 hours ago... just outside of Austin, TX here.

Luck is pretty simple at least how it's calculated here. Well let me clarify at least how I understand it ;o)

At difficulty 1379223 if we find a valid block in 1379223 shares we are on par with the average.

On the other hand if over 24 hours our block average rate is 1517145.3 shares we are -10% on luck and each and every miner can expect 10% less btc for that 24 hours. Of course each individual miner has their own hash fluctuations but roughly 10% less.

Same applies for if our 24 hour average is 1241300.7 each miner can expect 10% greater btc plus/minus their own hash fluctuations.

I love the word fluctuation. Is that weird? lol

Ok then, let hope for better days... 
I guess I am confused on how stales effect your payout per block found by the pool. I thought that having less stales would mean that I contributed more, which in turn would result in a greater share of the payout. Also, maybe I am confused on luck too. I was under the impression luck had to do with how fast we "the pool" solved a block. So you are saying that we had -10% luck so we should expect a 10% drop in payout. Please clarify if I am wrong when you have time. I'm sure you are busy fixing stuff and a reply can wait. Thanks again for your continued efforts.

Idles/stales are not the reason you went from 3.5 to 2.8.  LUCK is.  We were functioning at +10-20% luck for the last two days.  Last 24 hours was -10%

I'm up to almost 6% stales on the various servers I point to. (NL2 being the primary with Central/West being backup split 50/50 between all my miners) Can't seem to find one server that is not having this issue. (Disconnects/Stales)

Nothing has changed with my configurations, I was getting <1% stales about 3-4 days ago. I realize there has been growth with the pool, I'm just a little concerned. Going from 3.5+ BTC to less then 2.8 BTC in 24 hrs is starting to hit the old bitcoin wallet. (running 4.8GHash) Especially since we are not due until 4 to 5 days for another difficulty increase.

I know you'll do what you can, thanks for looking into it. I appreciate your time and effort keeping this all running.

Hi

website is down...unable to get to it..

Hi

Woooot automatic payouts. So looking forward to that. hope it gets done this weekend