Bitcoin Forum
March 19, 2024, 08:17:42 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 [21] 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 ... 425 »
  Print  
Author Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers  (Read 902898 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Olly_K
Sr. Member
****
Offline Offline

Activity: 361
Merit: 250


View Profile
February 13, 2012, 02:19:32 PM
 #401

That makes me feel a lot better. I left my workers mining in hopes the shares were being counted. Glad to know all those shares will get paid! This is why I stick with this pool. Thanks eleuthria!

agreed Smiley
1710836262
Hero Member
*
Offline Offline

Posts: 1710836262

View Profile Personal Message (Offline)

Ignore
1710836262
Reply with quote  #2

1710836262
Report to moderator
1710836262
Hero Member
*
Offline Offline

Posts: 1710836262

View Profile Personal Message (Offline)

Ignore
1710836262
Reply with quote  #2

1710836262
Report to moderator
1710836262
Hero Member
*
Offline Offline

Posts: 1710836262

View Profile Personal Message (Offline)

Ignore
1710836262
Reply with quote  #2

1710836262
Report to moderator
Even if you use Bitcoin through Tor, the way transactions are handled by the network makes anonymity difficult to achieve. Do not expect your transactions to be anonymous unless you really know what you're doing.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1710836262
Hero Member
*
Offline Offline

Posts: 1710836262

View Profile Personal Message (Offline)

Ignore
1710836262
Reply with quote  #2

1710836262
Report to moderator
1710836262
Hero Member
*
Offline Offline

Posts: 1710836262

View Profile Personal Message (Offline)

Ignore
1710836262
Reply with quote  #2

1710836262
Report to moderator
eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 13, 2012, 02:30:41 PM
 #402

That makes me feel a lot better. I left my workers mining in hopes the shares were being counted. Glad to know all those shares will get paid! This is why I stick with this pool. Thanks eleuthria!

I'm going to have to do some work to calculate payout miners for some of that time.  It won't be 100% perfect, but anybody that is a dedicated miner should come out AHEAD of their normal 24 hour earnings.  I've made changes to the server logs now that we're on a stronger server [with significantly more HDD space], so if it happens again I can do a complete recalculation for the entire period with exact payment to the share.

Current plan is the following, unless I can pull some extra information from the partial logs:
  1) Calculate the average shares per hour submitted by each miner for the 3 hours before the problem.  Multiple that hourly average by 8 (downtime was very close to 8 hours).
  2) Take the shares submitted by each miner during that 8 hour time frame the previous day.

  Whichever number is LARGER, will be added to your earnings, at a 0% fee.

RIP BTC Guild, April 2011 - June 2015
allinvain
Legendary
*
Offline Offline

Activity: 3080
Merit: 1080



View Profile WWW
February 13, 2012, 02:32:14 PM
 #403

I noticed an unsually high number of failed job requests this morning. Were you doing something with the servers 5 - 10 min ago?

Joshwaa
Hero Member
*****
Offline Offline

Activity: 497
Merit: 500



View Profile
February 13, 2012, 02:32:49 PM
 #404

That makes me feel a lot better. I left my workers mining in hopes the shares were being counted. Glad to know all those shares will get paid! This is why I stick with this pool. Thanks eleuthria!

I'm going to have to do some work to calculate payout miners for some of that time.  It won't be 100% perfect, but anybody that is a dedicated miner should be directly on track with their normal 24 hour earnings.  I've made changes to the server logs now that we're on a stronger server [with significantly more HDD space], so if it happens again I can do a complete recalculation for the entire period with exact payment to the share.

Current plan is the following, unless I can pull some extra information from the partial logs:
  1) Calculate the average shares per hour submitted by each miner for the 3 hours before the problem.  Multiple that hourly average by 8 (downtime was very close to 8 hours).
  2) Take the shares submitted by each miner during that 8 hour time frame the previous day.

  Whichever number is LARGER, will be added to your earnings, at a 0% fee.

You Rock thanks again!

Like what I said : 1JosHWaA2GywdZo9pmGLNJ5XSt8j7nzNiF
Don't like what I said : 1FuckU1u89U9nBKQu4rCHz16uF4RhpSTV
Joshwaa
Hero Member
*****
Offline Offline

Activity: 497
Merit: 500



View Profile
February 13, 2012, 02:42:16 PM
 #405

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.

Like what I said : 1JosHWaA2GywdZo9pmGLNJ5XSt8j7nzNiF
Don't like what I said : 1FuckU1u89U9nBKQu4rCHz16uF4RhpSTV
eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 13, 2012, 02:55:15 PM
 #406

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.

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

RIP BTC Guild, April 2011 - June 2015
cablepair
Hero Member
*****
Offline Offline

Activity: 896
Merit: 1000


Buy this account on March-2019. New Owner here!!


View Profile WWW
February 13, 2012, 03:15:25 PM
 #407

That makes me feel a lot better. I left my workers mining in hopes the shares were being counted. Glad to know all those shares will get paid! This is why I stick with this pool. Thanks eleuthria!

I'm going to have to do some work to calculate payout miners for some of that time.  It won't be 100% perfect, but anybody that is a dedicated miner should come out AHEAD of their normal 24 hour earnings.  I've made changes to the server logs now that we're on a stronger server [with significantly more HDD space], so if it happens again I can do a complete recalculation for the entire period with exact payment to the share.

Current plan is the following, unless I can pull some extra information from the partial logs:
  1) Calculate the average shares per hour submitted by each miner for the 3 hours before the problem.  Multiple that hourly average by 8 (downtime was very close to 8 hours).
  2) Take the shares submitted by each miner during that 8 hour time frame the previous day.

  Whichever number is LARGER, will be added to your earnings, at a 0% fee.

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

thanks!
eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 13, 2012, 03:18:22 PM
Last edit: August 11, 2012, 11:01:39 PM by eleuthria
 #408

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)

RIP BTC Guild, April 2011 - June 2015
allinvain
Legendary
*
Offline Offline

Activity: 3080
Merit: 1080



View Profile WWW
February 13, 2012, 03:33:01 PM
Last edit: February 13, 2012, 04:02:41 PM by allinvain
 #409

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

eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 13, 2012, 03:59:42 PM
 #410

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)

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.

RIP BTC Guild, April 2011 - June 2015
Joshwaa
Hero Member
*****
Offline Offline

Activity: 497
Merit: 500



View Profile
February 13, 2012, 04:21:42 PM
 #411

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: <html
>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 503 Service Unavailable</title>
</head>
<body>
<h2>HTTP ERROR: 503</h2>
<p>Problem accessing /. Reason:
<pre>    Service Unavailable</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>




















</body>
</html>
[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)

Like what I said : 1JosHWaA2GywdZo9pmGLNJ5XSt8j7nzNiF
Don't like what I said : 1FuckU1u89U9nBKQu4rCHz16uF4RhpSTV
allinvain
Legendary
*
Offline Offline

Activity: 3080
Merit: 1080



View Profile WWW
February 13, 2012, 04:37:52 PM
 #412

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

eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 13, 2012, 04:43:55 PM
 #413

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).

RIP BTC Guild, April 2011 - June 2015
CyberPhunk
Full Member
***
Offline Offline

Activity: 124
Merit: 100


View Profile
February 13, 2012, 05:22:10 PM
 #414

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. Wink

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

List of client download mirrors / Older Catalyst drivers/SDK
13dRbbqBpfZEmZiXXdLM4NKNoJYsgHbuFJ  <- might as well, in case someone feels generous. Wink
eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 13, 2012, 05:26:06 PM
 #415

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. Wink

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

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

RIP BTC Guild, April 2011 - June 2015
dlasher
Sr. Member
****
Offline Offline

Activity: 467
Merit: 250



View Profile WWW
February 14, 2012, 12:03:28 AM
 #416

mine3.btcguild.com:9332 (50.31.135.6 by direct IP)
mine2.btcguild.com:9332 (50.31.135.5 by direct IP)
mine1.btcguild.com:9332 (50.31.135.4 by direct IP)

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?
eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 14, 2012, 01:06:05 AM
 #417

mine3.btcguild.com:9332 (50.31.135.6 by direct IP)
mine2.btcguild.com:9332 (50.31.135.5 by direct IP)
mine1.btcguild.com:9332 (50.31.135.4 by direct IP)

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?


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.

RIP BTC Guild, April 2011 - June 2015
eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 14, 2012, 01:19:20 AM
 #418

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.

RIP BTC Guild, April 2011 - June 2015
Joshwaa
Hero Member
*****
Offline Offline

Activity: 497
Merit: 500



View Profile
February 14, 2012, 01:26:15 AM
 #419

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.

Like what I said : 1JosHWaA2GywdZo9pmGLNJ5XSt8j7nzNiF
Don't like what I said : 1FuckU1u89U9nBKQu4rCHz16uF4RhpSTV
eleuthria (OP)
Legendary
*
Offline Offline

Activity: 1750
Merit: 1007



View Profile
February 14, 2012, 01:49:04 AM
Last edit: February 14, 2012, 02:33:54 AM by eleuthria
 #420

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.

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.

RIP BTC Guild, April 2011 - June 2015
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 [21] 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 ... 425 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!