[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers

[Sitarow]

Seems like I am getting 3.5% Dupe shares on stratum? Any ideas?

Yeah I'm seeing some issues like that too. Some stats after 3.5 hours:
Speed 5,072.51 MH/s - Accepted 14109 (99.19%) - 15 Stale / 99 Dupe

I am testing the Windows proxy and find that pointing a new system at existing workers (that has already been on the list) at the proxy systems will not connect.

However when I use a miner / password combo that is working on another system then "new" system starts crunching away.

Presently I am using 1 miner account per gpu on a given system.

I notice that submitted shares on the online webpage not updating with submitted shares.


Edited: for clarification

[1713532676]

1713532676

[eleuthria]

Seems like I am getting 3.5% Dupe shares on stratum? Any ideas?

Yeah I'm seeing some issues like that too. Some stats after 3.5 hours:
Speed 5,072.51 MH/s - Accepted 14109 (99.19%) - 15 Stale / 99 Dupe

I am testing the Windows client and find that adding some username/password systems will not work.

When I use a miner / password combo that works on another system then all works well.

I am giving 1 miner per gpu on system.

Also I  notice the submitted shares on the webpage not updating.

If you try to connect to the new pool before a worker was made/renamed, it will never "re-authorize" to see if you eventually made that worker.  This will be changed later on, though it's not high on the list since workers should have been made -before- trying to connect with them.

The submitted shares update on the web page if you go back to the https://www.btcguild.com/stratum_beta.php page.  They update roughly every 50 seconds at the moment (will be every 10 seconds after the next restart).

[Sitarow]

Seems like I am getting 3.5% Dupe shares on stratum? Any ideas?

Yeah I'm seeing some issues like that too. Some stats after 3.5 hours:
Speed 5,072.51 MH/s - Accepted 14109 (99.19%) - 15 Stale / 99 Dupe

I am testing the Windows client and find that adding some username/password systems will not work.

When I use a miner / password combo that works on another system then all works well.

I am giving 1 miner per gpu on system.

Also I  notice the submitted shares on the webpage not updating.

If you try to connect to the new pool before a worker was made/renamed, it will never "re-authorize" to see if you eventually made that worker.  This will be changed later on, though it's not high on the list since workers should have been made -before- trying to connect with them.

The submitted shares update on the web page if you go back to the https://www.btcguild.com/stratum_beta.php page.  They update roughly every 50 seconds at the moment (will be every 10 seconds after the next restart).

Yes I am using the workers that were previously made

[BitMinerN8]

I'm looking into the dupe "issue".  Right now I have a feeling it's cgminer pushing shares twice for some reason.  I've noticed in earlier versions, cgminer sometimes had problems when things happened too fast (like saying "pool not providing work fast enough" when connecting to a pool with a <10ms latency).

FYI - For the Stratum testing, I'm using 3 rigs:
RIG
#1 - Pi with bfgminer 2.7.5 (4 BFL)
#2 - BAMT with cgminer 2.5.0 (2 GPU, 6950/5850, 1 BFL)
#3 - Win 7 x64 with cgminer 2.7.5 (1 GPU, 5870) - Running the Stratum Proxy

Current Stats: (after 3:52 hours)
RIG
#1 - 11 Stale / 61 Dupe
#2 - 4 Stale / 35 Dupe
#3 - 0 Stale / 3 Dupe

[eleuthria]

If you're experiencing dupes, please restart your proxy and have it output to a file.  On linux, this can be done by running the proxy with:

./mining_proxy.py 2>&1 | tee log.txt


Please let it run until you see a few duplicates reported, then send me a PM with your log (pastebin.org works well).  Luckily, if it's just mining software or proxy submitting a second time, it shouldn't be a problem (you aren't losing speed as a result of it).

[doublec]

Please let it run until you see a few duplicates reported, then send me a PM with your log (pastebin.org works well).  Luckily, if it's just mining software or proxy submitting a second time, it shouldn't be a problem (you aren't losing speed as a result of it).

The times I've seen this have been when the miner thinks the pool took to long in responding to a share submission and so sends it again.

[eleuthria]

Please let it run until you see a few duplicates reported, then send me a PM with your log (pastebin.org works well).  Luckily, if it's just mining software or proxy submitting a second time, it shouldn't be a problem (you aren't losing speed as a result of it).

The times I've seen this have been when the miner thinks the pool took to long in responding to a share submission and so sends it again.

Yes, that would be the normal case.  But I'm seeing consistent pool responses in less than 50ms from the time I send them (on my connection).  Hopefully some logs will shed light on the issue.

[iCEBREAKER]

Firewall is off.

Proxy is up (ran as Administrator), getting templates, and listening on port 8332.

CGMiner won't connect.  I've tried network IP, computer name, computer name with full domain, and even 127.0.0.1.

   {
      "url" : "http://10.10.XX.YY:8332",
      "user" : "icebreaker_NN",
      "pass" : "Z"
   },

What am I doing wrong?   

[eleuthria]

What am I doing wrong?  

Worker names are case sensitive in the pool currently.  I think thats your problem.  Copy it _exactly_ as it appears on the My Workers page.

[meebs]

What am I doing wrong?  

Worker names are case sensitive in the pool currently.  I think thats your problem.  Copy it _exactly_ as it appears on the My Workers page.

When connecting "normally" case doesnt matter for the worker name, for the stratum it seemed to suddenly matter (or maybe running as admin is needed).

Either way, i couldnt get it working at first either but after reading this post I was able to.. woot!

[eleuthria]

During testing, I would appreciate having miners keep logs of their miner output and/or proxy output to help debug problems.

I've experienced dupe problems with bfgminer on my FPGAs for months, on multiple pools, but it seems more pronounced with the proxy.  Other users with GPUs are seeing the same:

[2012-09-13 19:22:20] Accepted b4af7a23.6a019d65 GPU 1
[2012-09-13 19:23:20] Rejected b4af7a23.6a019d65 GPU 1

[2012-09-13 19:12:38] Accepted ff6aafd5.497364a1 ZTX 9
[2012-09-13 19:12:42] Rejected ff6aafd5.497364a1 ZTX 9
 [2012-09-13 19:34:54] Accepted 30f0b4fb.d177554c ZTX 3
 [2012-09-13 19:34:57] Rejected 30f0b4fb.d177554c ZTX 3
 [2012-09-13 19:34:59] Accepted 55ead1ab.d8efaa87 ZTX 9
 [2012-09-13 19:35:04] Rejected 55ead1ab.d8efaa87 ZTX 9


In these cases, it's apparent cgminer already submitted the share, so it is a real duplicate.  With added logging to the proxy, I've watched the work requests, and have not caught a situation where the proxy is sending duplicate getworks.  This isn't wasting hash power as far as I've been able to identify from the logs I've been given so far.

[eleuthria]

Update pushed to the stratum pool requiring its first restart of the day.  List of changes:


1) Worker names are no longer case sensitive
2) Shares flush every 10 seconds instead of every 50 seconds (with a 2nd flush 10 seconds after those 50)
3) Fixed a potential duplicate work bug [do not believe this is the cause of earlier problems]
4) Fixed potential exploit that would allow multiple share submissions without being caught as duplicates
5) Added some special logging on my end to monitor upstream block pushes.

[BitMinerN8]

I'm getting this when starting the proxy on Win7 x64: (first two lines in the log)

Code:

C:\stratum-proxy\mining_proxy.exe\twisted\internet\win32eventreactor.py:64: UserWarning: Reliable disconnection notification requires pywin32 215 or later
C:\stratum-proxy\mining_proxy.exe\twisted\web\util.py:372: DeprecationWarning: Passing filenames or file objects to XMLFile is deprecated since Twisted 12.1.  P
ass a FilePath instead.

Everything seems to be working fine, I just noticed it when the proxy started with no miners pointed at it, sitting idle. I did try to resolve it by installing Python 2.7.3 and PyWin32-217, but it didn't seem to help. I don't know if it just can't find pywin32 in the environment variables or what.

[eleuthria]

I'm getting this when starting the proxy on Win7 x64: (first two lines in the log)

Code:

C:\stratum-proxy\mining_proxy.exe\twisted\internet\win32eventreactor.py:64: UserWarning: Reliable disconnection notification requires pywin32 215 or later
C:\stratum-proxy\mining_proxy.exe\twisted\web\util.py:372: DeprecationWarning: Passing filenames or file objects to XMLFile is deprecated since Twisted 12.1.  P
ass a FilePath instead.

Everything seems to be working fine, I just noticed it when the proxy started with no miners pointed at it, sitting idle. I did try to resolve it by installing Python 2.7.3 and PyWin32-217, but it didn't seem to help. I don't know if it just can't find pywin32 in the environment variables or what.

I saw a connection timeout on the poold, how long were you leaving it idle?  Could be your router dropped the connection silently during the idle time.

In other news....WE FOUND A BLOCK WITH THE STRATUM POOL!

[BitMinerN8]

I'm getting this when starting the proxy on Win7 x64: (first two lines in the log)

Code:

C:\stratum-proxy\mining_proxy.exe\twisted\internet\win32eventreactor.py:64: UserWarning: Reliable disconnection notification requires pywin32 215 or later
C:\stratum-proxy\mining_proxy.exe\twisted\web\util.py:372: DeprecationWarning: Passing filenames or file objects to XMLFile is deprecated since Twisted 12.1.  P
ass a FilePath instead.

Everything seems to be working fine, I just noticed it when the proxy started with no miners pointed at it, sitting idle. I did try to resolve it by installing Python 2.7.3 and PyWin32-217, but it didn't seem to help. I don't know if it just can't find pywin32 in the environment variables or what.

I saw a connection timeout on the poold, how long were you leaving it idle?  Could be your router dropped the connection silently during the idle time.

In other news....WE FOUND A BLOCK WITH THE STRATUM POOL!

It was only idle for about 5 min while I was adjusting pool files on the BAMT rigs. Those two lines of text appear on launch.

Grats on the block!  

This is bad ass, to think that now I can have another proxy running as a failover pool pointing out the wi-fi hotspot as a backup. Nice...  

[iCEBREAKER]

What am I doing wrong?  

Worker names are case sensitive in the pool currently.  I think thats your problem.  Copy it _exactly_ as it appears on the My Workers page.

I swear on the St. Satoshi memorial that the problem wasn't case sensitivity.  Anyhoo, it seems to magically have started working.   

Ragepost of Bill O'Reilly "freaking thing sucks" meme posting averted.   

[BitMinerN8]

What am I doing wrong?  

Worker names are case sensitive in the pool currently.  I think thats your problem.  Copy it _exactly_ as it appears on the My Workers page.

I swear on the St. Satoshi memorial that the problem wasn't case sensitivity.  Anyhoo, it seems to magically have started working.   

Ragepost of Bill O'Reilly "freaking thing sucks" meme posting averted.   

"do it live!"

[vphen]

with Stratum , than before, I got less Stale, but more Dupe

Accepted (%)   Stale/Dupe/Other
218638 (99.42%)   40 / 1230 / 0

[Joshwaa]

I was at 4.5% Dupe now at about .4% for stale and dupe.  Did you fix something on your end?  Only thing I did was move the proxy to a faster computer. 

Question.  I have a friend with 2.5GHash who has his rig here at my location. He should run thru my proxy not start another on the same network, correct?

I do not understand the whole thing yet but seems like worker name and pass are just passed thru the proxy. So should be ok.

[eleuthria]

I was at 4.5% Dupe now at about .4% for stale and dupe.  Did you fix something on your end?  Only thing I did was move the proxy to a faster computer. 

Question.  I have a friend with 2.5GHash who has his rig here at my location. He should run thru my proxy not start another on the same network, correct?

I do not understand the whole thing yet but seems like worker name and pass are just passed thru the proxy. So should be ok.

Your friend can send work through your proxy, yes.  The proxy will relay it to the proper worker.  I did make one change about dupes that may have been due to how the proxy incremented the work.

As for other dupes, so far I have yet to see a case of a dupe that wasn't a resubmission.  Unfortunately, WHY shares are being resubmitted is a mystery.  In every case so far, it has been the fault of cgminer.  You can view in the logs that it sent in the share and it was accepted, and then it was sent again sometime later and rejected (because it was already submitted).