Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 405. (Read 903217 times)

They should be but mine3 for me wasn't. I'm now on mine1 to see how it goes.

Make sure to give mine2/3 a try.  They should be a lot better than earlier today now that the load balancer is completely disabled.

Hmm, well, I tried switching my fpga miner to deepbit and so far I've noticed no failed connect attempts when the miner asks for work. There is still are a few rejected jobs even with deepbit but no connection issues. I'm using MPBM v0.0.4alpha btw. I'd expect to have more issues with deepbit as it's further away (ie more hops, higher latency, etc) but :\ I dunno. As I type this I noticed a few failed connections so maybe in the end it's pretty much the same with all pools - ie it's the fact that I'm mining with an fpga that is causing these issues, or my internet is just shit.

Anyways, my brief visit to the Deep Bit is over; back to the Guild I go.

Another update:  Port 80 mining is enabled on both mine2.btcguild.com and mine3.btcguild.com!

The servers have been updated to reflect the changes in my previous post (responding to dlasher).

btcguild.com is now pointed only at 50.31.135.4, via port 8332.
mine1.btcguild.com is also pointed at 50.31.135.4, via port 8332.
mine2.btcguild.com is 50.31.135.5, via port 8332.
mine3.btcguild.com is 50.31.135.6, via port 8332.

Port 9332 is working as well, but may stop at some point in the future, so using 8332 is preferred.

Glad to hear about the server thing going back to how it was last year.  Also was getting some connection issues popping up about 15-20min ago.

I'm preparing to post the calculated shares for users from last night.  The rewards will show up as Difficulty = 1312154.  This is because the fee is currently hard coded.  1312154 is 1.052632x the current difficulty, which brings the reimbursement to the equivalent of current difficulty at a 0% fee.  The amount of shares you'll be credited is calculated as follows:

  The average shares you submitted per hour between 19:00 and 22:00 [the problem started ~24:00].  Multiplied by 8 [actual downtime was closer to 7.5 hrs].

Because some miners come & go, I stuck to only running the automatic reimbursement for miners who were active just before the problem happened.  If you regularly start your miners between 24:00 and 8:00 EST, but not between 19:00 and 22:00 (EST), please send me an email with your username, and I will investigate your mining patterns and run a special reimbursement on the account.

I am very sorry this happened, it was an error that the pool has never encountered before, and I have to take the hit (~360 BTC) to make things right.  I purposely reduced logging after moving to PPS because an issue requiring manual calculations based on the sharelog have never cropped up since the pool started, and performance was taking a hit keeping extensive logs.  I've extended the pool logging significantly in light of this event, thanks to the new server having significantly more storage space and processing power.


UPDATE:  The earnings have been updated for the calculation identified above.

Those entries will stick around, but some changes may be made in the next few days:

1) Removing the load balance round robin (the overhead outweighs the benefit)
2) mine1.btcguild.com will become the default (btcguild.com)
3) mine2 and mine3 will be accessible directly via 8332 (9332 will redirect to 8332 though).


The setup will be *similar* to what happened back in June - September of last year.  You can pick your BTC Guild server.  They're still in the same physical location, and using the same central database server this time, so there won't be any ugly synchronization issues.  Obviously, mine2/mine3 will be what power users want to utilize.

Planning on leaving these DNS entries active for a while? I'll toss them in a cgminer script and set it to load balance. Any others you'd want us to add?

They're located in Chicago, IL.  Colocated with ServerCentral (nLayer).

Good to see you're on the ball as usual eleuthria.

Figured it was basically an accounting error or somesuch, and you would make it right eventually, though it was a bit of a shock to see my miners chugging away without their share counts working.

btw, where are the new servers located? Spread out geographically like they used to be?

Looks like this load balancing setup just doesn't work well enough.  I'll be making some changes to the servers this afternoon after fixing the earnings from last night.  Remove the round robin, and move back to having 2 servers [primary + 2 backups].  Users will be able to manually point at any of the 3 (2 of which should be as effective as a private server due to how many users use the default).

Failed job requests jumped to 46 - 5.0% of all total job requests so far.

Whats this I get it ever once in a while.

[2/13/12 10:19:35 AM] 50.31.135.5 accepted block 4389 from Juniper (#1)
[2/13/12 10:19:52 AM] 50.31.135.5 accepted block 4390 from Juniper (#1)
[2/13/12 10:21:41 AM] ERROR: Cannot connect to 50.31.135.5: Read timed out
[2/13/12 10:21:49 AM] ERROR: Cannot connect to 50.31.135.5: Bitcoin returned an error message: >

HTTP ERROR: 503

Problem accessing /. Reason:

    Service Unavailable

---

Powered by Jetty://






















[2/13/12 10:21:49 AM] 50.31.135.5 rejected block 24 from Juniper (#1)
[2/13/12 10:22:42 AM] 50.31.135.5 accepted block 4391 from Juniper (#1)
[2/13/12 10:22:54 AM] 50.31.135.5 accepted block 4392 from Juniper (#1)

Please update your post again in a while with fresh stats.  These types of problems really shouldn't be happening especially if you're connceting directly to the IP.  Other than the obvious problems that can occur when 2 LPs hit in a short window.

Wow what a nice improvement. Perhaps there is something odd with the proxy/load balancer as when connecting directly work units are being dished out with amazing speed.

UPDATE: after restarting the miner 5 min ago a few failed job requests occured (5) in total (3.0% of total), but I guess it is normal to have a few of them once in a while, no? (network issues, etc)

Update: 10 failed job requests

For anybody that has an unusual number of idles/connection errors [not counting this morning when the servers rebooted], try the following:

Change your miner from btcguild.com:8332 to one of the following (this is the recommended order to try):

mine3.btcguild.com:8332 ([removed] by direct IP)
mine2.btcguild.com:8332 ([removed] by direct IP)

you are always a professional my friend that is why i had no fear when i saw the problem.

thanks!

Should be fixed in the next 60 seconds.  One kernel tweak didn't carry over after rebooting the servers.

BTW getting a lot of :
[2/13/12 9:40:09 AM] 50.31.135.5 accepted block 4279 from Juniper (#1)
[2/13/12 9:40:13 AM] ERROR: Cannot connect to 50.31.135.5: Read timed out
[2/13/12 9:40:49 AM] 50.31.135.5 accepted block 4280 from Juniper (#1)
[2/13/12 9:41:06 AM] 50.31.135.5 accepted block 4281 from Juniper (#1)
[2/13/12 9:41:07 AM] ERROR: Cannot connect to 50.31.135.5: Read timed out
[2/13/12 9:41:23 AM] ERROR: Cannot connect to 50.31.135.5: Read timed out

Tried diffrent IP's same thing. UserID : 17104 on your site if you need any help.