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

[mdude77]

Just flipped back to the old software after encountering a crash on the server end.

HellDriverUK:  That still makes no sense that you're submitting a few shares and it quits.  It's not like the servers send different information after a few shares.  I need pastebin log files to have any chance at figuring out what is going wrong on your end.

I'm having a weird problem.  Suddenly the API is telling me my cube is running at 24GH/s instead of 38GH/s.  When I check my stratum proxy, I usually see shares submitted with something like [100ms] in them.  Now I'm seeing values in the 10s of thousands, averaging in high 60s.

I'm going to try resetting things...

M

[1714105879]

1714105879

[1714105879]

1714105879

[1714105879]

1714105879

[1714105879]

1714105879

[1714105879]

1714105879

[mdude77]

Just flipped back to the old software after encountering a crash on the server end.

HellDriverUK:  That still makes no sense that you're submitting a few shares and it quits.  It's not like the servers send different information after a few shares.  I need pastebin log files to have any chance at figuring out what is going wrong on your end.

I'm having a weird problem.  Suddenly the API is telling me my cube is running at 24GH/s instead of 38GH/s.  When I check my stratum proxy, I usually see shares submitted with something like [100ms] in them.  Now I'm seeing values in the 10s of thousands, averaging in high 60s.

I'm going to try resetting things...

M

I run two stratum proxies on different machines as failure.  I switched to the backup, and the values are still way too high, but are lower.  I tried restarting the proxy on the first machine and it's not connecting.  It's pointing to the backup gf server.

M

[eleuthria]

Just flipped back to the old software after encountering a crash on the server end.

HellDriverUK:  That still makes no sense that you're submitting a few shares and it quits.  It's not like the servers send different information after a few shares.  I need pastebin log files to have any chance at figuring out what is going wrong on your end.

I'm having a weird problem.  Suddenly the API is telling me my cube is running at 24GH/s instead of 38GH/s.  When I check my stratum proxy, I usually see shares submitted with something like [100ms] in them.  Now I'm seeing values in the 10s of thousands, averaging in high 60s.

I'm going to try resetting things...

M

I run two stratum proxies on different machines as failure.  I switched to the backup, and the values are still way too high, but are lower.  I tried restarting the proxy on the first machine and it's not connecting.  It's pointing to the backup gf server.

M

I'm unable to duplicate any of this.  I'm pointing a stratum proxy at the only server running the new backend and getting 78ms-100ms responses, which is the same as my ping to that server.

[mdude77]

Just flipped back to the old software after encountering a crash on the server end.

HellDriverUK:  That still makes no sense that you're submitting a few shares and it quits.  It's not like the servers send different information after a few shares.  I need pastebin log files to have any chance at figuring out what is going wrong on your end.

I'm having a weird problem.  Suddenly the API is telling me my cube is running at 24GH/s instead of 38GH/s.  When I check my stratum proxy, I usually see shares submitted with something like [100ms] in them.  Now I'm seeing values in the 10s of thousands, averaging in high 60s.

I'm going to try resetting things...

M

I run two stratum proxies on different machines as failure.  I switched to the backup, and the values are still way too high, but are lower.  I tried restarting the proxy on the first machine and it's not connecting.  It's pointing to the backup gf server.

M

I changed my proxy to point to stratum.btcguild.com and it's doing the same thing.  Hanging on authentication.

I reset my cube, but the API is still reporting 22GH/s instead of 38GH/s.

M

[eleuthria]

PM me the worker name you're using....because I'm completely unable to duplicate anything you're saying.  It's working the same as it has all week...because NOTHING has changed on that server all week.

[Trongersoll]

Just flipped back to the old software after encountering a crash on the server end.

HellDriverUK:  That still makes no sense that you're submitting a few shares and it quits.  It's not like the servers send different information after a few shares.  I need pastebin log files to have any chance at figuring out what is going wrong on your end.

I'm having a weird problem.  Suddenly the API is telling me my cube is running at 24GH/s instead of 38GH/s.  When I check my stratum proxy, I usually see shares submitted with something like [100ms] in them.  Now I'm seeing values in the 10s of thousands, averaging in high 60s.

I'm going to try resetting things...

M

I guess this is a me too post. My Bitfury rig which should be doing 230 Gh/s is showing 130 Gh/s on the site it even shows a drop on the graph pages. The Bitfury interface still shows a Noncerate of 230. I could understand the site showing a little lower, but not this low.

[eleuthria]

Try resetting your stats if your speed is showing up very low.  I know Bitfury is one of the many ASICs that is complete garbage in its firmware, which means it's not good at handling server disconnects.  There have been a few server restarts over the last few hours (switching to new software, new software crashing and restarting, and then switching back to the old software after it had crashed).

[Trongersoll]

Try resetting your stats if your speed is showing up very low.  I know Bitfury is one of the many ASICs that is complete garbage in its firmware, which means it's not good at handling server disconnects.  There have been a few server restarts over the last few hours (switching to new software, new software crashing and restarting, and then switching back to the old software after it had crashed).

on the site, my hashrate is now rising. it is 166 and climbing. maybe i had trouble during one of the restarts. I've don nothing on my end, just watching.

[mdude77]

Try resetting your stats if your speed is showing up very low.  I know Bitfury is one of the many ASICs that is complete garbage in its firmware, which means it's not good at handling server disconnects.  There have been a few server restarts over the last few hours (switching to new software, new software crashing and restarting, and then switching back to the old software after it had crashed).

I've been running fine at 38GH/s, give or take a few, for about 2 weeks now.  Suddenly recently it dipped to 23.  According to my logs it started dipping around 4:18 ET, which I think is -4 UTC right now.  At 4:41 it stabilized at 23.

My cube still reports normal 38GH/s.

PM sent with username.

M

[mdude77]

Try resetting your stats if your speed is showing up very low.  I know Bitfury is one of the many ASICs that is complete garbage in its firmware, which means it's not good at handling server disconnects.  There have been a few server restarts over the last few hours (switching to new software, new software crashing and restarting, and then switching back to the old software after it had crashed).

I've been running fine at 38GH/s, give or take a few, for about 2 weeks now.  Suddenly recently it dipped to 23.  According to my logs it started dipping around 4:18 ET, which I think is -4 UTC right now.  At 4:41 it stabilized at 23.

My cube still reports normal 38GH/s.

PM sent with username.

M

According to the PPLNS stats, my hashrate decrease isn't just visual.  I'm usually around 24k per shift.

14166   0.00074%   17,018   2014-01-20 04:32 PM
14165   0.00105%   24,384   2014-01-20 03:46 PM
14164   0.00106%   24,512   2014-01-20 02:59 PM
14163   0.00106%   24,576   2014-01-20 02:14 PM

M

[eleuthria]

I know it's not just visual, but your hash rate is PROBABLY recovered by now, the problem is BTC Guild uses a 1 hour window, and if your'e not mining for part of that window due to shitty hardware/software, your hash rate will show up as bad for an hour, even if it's CURRENTLY hashing at normal rates.

Stratum proxies, Bitfury, and KNC Jupiters are all known to have EXTREMELY bad reactions to server restarts/disconnects.  There's nothing a pool can do on their end to fix shitty software/firmware.  I can't leave the servers running on the same outdated software for the next 2 years just because a few pieces of hardware react poorly.

[mdude77]

I know it's not just visual, but your hash rate is PROBABLY recovered by now, the problem is BTC Guild uses a 1 hour window, and if your'e not mining for part of that window due to shitty hardware/software, your hash rate will show up as bad for an hour, even if it's CURRENTLY hashing at normal rates.

Stratum proxies, Bitfury, and KNC Jupiters are all known to have EXTREMELY bad reactions to server restarts/disconnects.  There's nothing a pool can do on their end to fix shitty software/firmware.  I can't leave the servers running on the same outdated software for the next 2 years just because a few pieces of hardware react poorly.

What about being able to restart?  I'm not able to authenticate to backup server or US, but I can authenticate fine on the EU server.

Hash rate is down 21 now, since I can authenticate to EU I've switched my cube to point there, let's see if hashrate recovers.

M

[eleuthria]

Your problem, based on your logs, is something completely out of my control.  As far as I can tell, you can't even connect to stratum.btcguild.com:3333, period, let alone authenticate.

[mdude77]

Your problem, based on your logs, is something completely out of my control.  As far as I can tell, you can't even connect to stratum.btcguild.com:3333, period, let alone authenticate.

It worked fine (aside from hash decrease) until I restarted it.  Now I can connect to EU just fine.

I think others reported problems as well.

I have 3 rigs pointing to a scrypt server and they are running fine.

I'll try resetting my DSL...

M

[eleuthria]

Your problem, based on your logs, is something completely out of my control.  As far as I can tell, you can't even connect to stratum.btcguild.com:3333, period, let alone authenticate.

It worked fine (aside from hash decrease) until I restarted it.  Now I can connect to EU just fine.

I think others reported problems as well.

I have 3 rigs pointing to a scrypt server and they are running fine.

I'll try resetting my DSL...

M

Alright, I think I've been able to duplicate the issue, time to run some packet capture to see what the hell the stratum proxy is doing that is non-standard.  Next time you supply logs, please dont' use '-q'.  Either leave that off or use '-v' so it actually outputs information.

[mdude77]

Your problem, based on your logs, is something completely out of my control.  As far as I can tell, you can't even connect to stratum.btcguild.com:3333, period, let alone authenticate.

It worked fine (aside from hash decrease) until I restarted it.  Now I can connect to EU just fine.

I think others reported problems as well.

I have 3 rigs pointing to a scrypt server and they are running fine.

I'll try resetting my DSL...

M

Alright, I think I've been able to duplicate the issue, time to run some packet capture to see what the hell the stratum proxy is doing that is non-standard.  Next time you supply logs, please dont' use '-q'.  Either leave that off or use '-v' so it actually outputs information.

Not sure if it was my inet reset or if you fixed something.  Proxies are connecting just fine now to backup server, and [ms] values are in their normal range again.  Now I need a few minutes to see if the hashrate comes up.

I use -q on the proxy because the output looks better for normal use.  I'll remember to remove it if debugging in the future.

M

[mdude77]

Your problem, based on your logs, is something completely out of my control.  As far as I can tell, you can't even connect to stratum.btcguild.com:3333, period, let alone authenticate.

It worked fine (aside from hash decrease) until I restarted it.  Now I can connect to EU just fine.

I think others reported problems as well.

I have 3 rigs pointing to a scrypt server and they are running fine.

I'll try resetting my DSL...

M

Alright, I think I've been able to duplicate the issue, time to run some packet capture to see what the hell the stratum proxy is doing that is non-standard.  Next time you supply logs, please dont' use '-q'.  Either leave that off or use '-v' so it actually outputs information.

Not sure if it was my inet reset or if you fixed something.  Proxies are connecting just fine now to backup server, and [ms] values are in their normal range again.  Now I need a few minutes to see if the hashrate comes up.

I use -q on the proxy because the output looks better for normal use.  I'll remember to remove it if debugging in the future.

M

Hashrate is climbing, looks encouraging.

I'd love to not use the stratum proxy.  Seems to be the only game in town.  I have on my to do list making my own... but haven't made the time to do it yet, and I don't know how successful I'll be.

M

[Trongersoll]

I reset the stats. now the hashrate is floating between 166 - 177. Something isn't right. Whether it is wonky hardware on our end, or problem on the server side, there is a problem. If i had to guess, i'd guess a marginal timing problem.

[mdbssm]

Try resetting your stats if your speed is showing up very low.  I know Bitfury is one of the many ASICs that is complete garbage in its firmware, which means it's not good at handling server disconnects.  There have been a few server restarts over the last few hours (switching to new software, new software crashing and restarting, and then switching back to the old software after it had crashed).

on the site, my hashrate is now rising. it is 166 and climbing. maybe i had trouble during one of the restarts. I've don nothing on my end, just watching.

2 of my BF rigs dropped offline this afternoon as well. Could not re-connect to US stratum server. After rebooting / restarting stratum proxy etc I was finally able to get connected to the EU server.

[os2sam]

Anyone else noticing cgminer 3.10.0 crashing when connecting to BTCGuild?  Runs fine on Eligius and p2pool, but as soon as it connects to Guild it just quits.

It's self-compiled on Debian, running 2x Nanofury and 1x Bitburner Fury.

My guess is you messed up your argument on the worker name/port or something similar.  Works fine on bfgminer 3.9 and 3.10 here.

It gets a few shares then craps out.  cgminer.conf hasn't changed in....oh...about 3 months. It's CGminer, not bfgminer, too (only using cg because bfg doesn't support the Bitburner). So, I think your guess is wrong.

I'm pointing out the issue in case it's something with the new servers?  Nothing's changed here.

Trying to get a working version of cgminer 3.10 working, but since cgminer likes to fuck with drivers and make itself incompatible with bfgminer it's taking a long time.  I'm not seeing anybody else complaining about a similar issue though...I'm still thinking it's a config problem.

Absolutely nothing has changed on the validation server in the last week.  Any connection attempts have been connecting to the validation server all week.  Additionally, the communication between the server and client is identical to what it used to be.

I updated my CGMiner 3.8.4 to 3.10.0 and it seems to be working fine here for over an hour now.

Win Vista w/Jalapeno and 49 BE's.