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

[eleuthria]

I believe I've got the problem figured out.  Once again the slush stratum proxy never fails to disappoint in its ordering/formatting of his own damn protocol.  Restarting with a fix in place.


mdude77:  Can you try restarting pointing at the stratum.btcguild.com:3333 address?

[1714257949]

1714257949

[1714257949]

1714257949

[1714257949]

1714257949

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

back down to 140. This is frustrating I'd hate to be Eleuthria right now. What i don't get is why the pool's over all hashrate hasn't dropped. Why only a few of us seem to be affected.

[mdude77]

I believe I've got the problem figured out.  Once again the slush stratum proxy never fails to disappoint in its ordering/formatting of his own damn protocol.  Restarting with a fix in place.


mdude77:  Can you try restarting pointing at the stratum.btcguild.com:3333 address?

Both backup and stratum.btcguild.com are working fine for me now.

My hashrate is still climbing, up to 26 now.  It was down to 18 when I reset my internet connection.

M

[eleuthria]

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.

back down to 140. This is frustrating I'd hate to be Eleuthria right now. What i don't get is why the pool's over all hashrate hasn't dropped. Why only a of us seem to be affected.

Only a few people are affected because it's only affecting fringe cases where the stratum commands are being sent in awkward ways that normal mining software doesn't do.  The problem mdude77 was having was related to how the stratum proxy sends it's auth+subscribe requests (it sends them in one packet), ONLY when using the '-cu' argument.

[mdude77]

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.

back down to 140. This is frustrating I'd hate to be Eleuthria right now. What i don't get is why the pool's over all hashrate hasn't dropped. Why only a of us seem to be affected.

Only a few people are affected because it's only affecting fringe cases where the stratum commands are being sent in awkward ways that normal mining software doesn't do.  The problem mdude77 was having was related to how the stratum proxy sends it's auth+subscribe requests (it sends them in one packet), ONLY when using the '-cu' argument.

lol.  good catch.  it was always unclear exactly when you use custom user and when you don't.  I had to play with it for an hour or more initially before I found a combination that worked here.

M

[Trongersoll]

I'm still having issues. I tried hitting the restart proxy button on the bitfury screen. it didn't make any difference. I'll let things run for a day incase it manages to fix itself. I need to shut it down tomorrow to add a couple of more cards so it will get a reboot then if all else fails.

[mdbssm]

I'm still having issues. I tried hitting the restart proxy button on the bitfury screen. it didn't make any difference. I'll let things run for a day incase it manages to fix itself. I need to shut it down tomorrow to add a couple of more cards so it will get a reboot then if all else fails.

For my BF rigs, I need to restart the proxy, then stop the miner, wait 30 secs, then restart the miner.

ssh in and look at the error rates coming each chip from the /run/shm/.stat.log file. If the errors are high from the beginning, they don't seem to settle down as the hashrate ramps up. In that case, start and stop the miner again until you get a clean startup.

[mdude77]

I'm still having issues. I tried hitting the restart proxy button on the bitfury screen. it didn't make any difference. I'll let things run for a day incase it manages to fix itself. I need to shut it down tomorrow to add a couple of more cards so it will get a reboot then if all else fails.

Everything looks normal now on my side, except the hash rate peaked ~30GH/s and won't go any higher.  In fact it looks like it's decreasing again.

I'm afraid something is still amiss.

M

[Trongersoll]

I'm still having issues. I tried hitting the restart proxy button on the bitfury screen. it didn't make any difference. I'll let things run for a day incase it manages to fix itself. I need to shut it down tomorrow to add a couple of more cards so it will get a reboot then if all else fails.

Everything looks normal now on my side, except the hash rate peaked ~30GH/s and won't go any higher.  In fact it looks like it's decreasing again.

I'm afraid something is still amiss.

M

Looks like i'm back where i belong as well. Maybe it was the chicken that i sacrificed. 

[eleuthria]

I'm still having issues. I tried hitting the restart proxy button on the bitfury screen. it didn't make any difference. I'll let things run for a day incase it manages to fix itself. I need to shut it down tomorrow to add a couple of more cards so it will get a reboot then if all else fails.

Everything looks normal now on my side, except the hash rate peaked ~30GH/s and won't go any higher.  In fact it looks like it's decreasing again.

I'm afraid something is still amiss.

M

You should've clicked reset stats so it had a proper average window instead of including the downtime/outages.  I'm looking at your account now and it's almost at 37 GH/s.

[mdude77]

I'm still having issues. I tried hitting the restart proxy button on the bitfury screen. it didn't make any difference. I'll let things run for a day incase it manages to fix itself. I need to shut it down tomorrow to add a couple of more cards so it will get a reboot then if all else fails.

Everything looks normal now on my side, except the hash rate peaked ~30GH/s and won't go any higher.  In fact it looks like it's decreasing again.

I'm afraid something is still amiss.

M

You should've clicked reset stats so it had a proper average window instead of including the downtime/outages.  I'm looking at your account now and it's almost at 37 GH/s.

Affirmative, at 37 now.  So the downtime was caused by my side, and I just happened to run into the authentication issue when I restarted the proxies?

Thanks for good work.

M

[spazzcat]

I had my two cubes drop in the last hour, the only thing that seem to fix them was powering them off???

14169   ---   11,664   In Progress
14168   0.00016%   3,806   2014-01-20 06:03 PM
14167   0.00016%   3,710   2014-01-20 05:17 PM
14166   0.00139%   32,034   2014-01-20 04:32 PM
14165   0.00196%   45,362   2014-01-20 03:46 PM
14164   0.00211%   48,808   2014-01-20 02:59 PM

[eleuthria]

I had my two cubes drop in the last hour, the only thing that seem to fix them was powering them off???

14169   ---   11,664   In Progress
14168   0.00016%   3,806   2014-01-20 06:03 PM
14167   0.00016%   3,710   2014-01-20 05:17 PM
14166   0.00139%   32,034   2014-01-20 04:32 PM
14165   0.00196%   45,362   2014-01-20 03:46 PM
14164   0.00211%   48,808   2014-01-20 02:59 PM

There's nothing a pool can do when it comes to poor hardware design.  Most ASICs are simply designed poorly, they're hacked together in a way that "works" and immediately shipped.  As a result, there have ALWAYS been problems with just about every ASIC hardware manufacturer where they randomly screw up when a server disconnect occurs.  Normally they work fine, but sometimes they just die and require a power cycle.

This is the one nice thing about ASICs which use USB, they're controlled by decent (and update-able) software that can normally get them to behave properly and handle things like disconnects without dying.

[Billbags]

How are you connecting your cubes to the pool. I now use Slushs stratum proxy pointed at BTC guild and it is really stable.

[eleuthria]

How are you connecting your cubes to the pool. I now use Slushs stratum proxy pointed at BTC guild and it is really stable.

That's how most do it.  The issues today only affecting 2 of the 4 public servers, so many users did not experience any disconnect/outage at all.

[eleuthria]

Alright, everything is rolled back to the old software.  There's a definite bug in this new setup where it will occasionally stop accepting new connections.  I thought that was fixed after the patch this morning, but it just showed up again.

I won't be touching the pool software for the next week while doing a line-by-line review to try to figure out what is causing this to happen.

[Soros Shorts]

Had to restart the stratum proxies of *all* my BitFury rigs because the hashrate dropped to 50% or less. May have something to with the way the BitFury software splits work up across all the configured pools.

If this keeps up I am going to remove all backup pools and mine solely against the private IP.

[opentoe]

Just wanted to thank the forum-goers today.  This outage lasted a lot longer than I would've liked (well, hard to have any outage that is shorter than 0 minutes), and lasted longer than my original projections due to just how long the resync took.

However, for the first time in quite a while, the thread remained clear of useless posts, no demands, no crying foul.  Even my email inbox was *mostly* empty during this event.  The ability to concentrate solely on the task at hand (and providing updates) really made it easier to focus than having to pull double-duty as public relations.

Now to compensate us some dividends. Even my car insurance company does that.

[jesse11]

Yeah, my Cubes really took a hit, there running 94-97% on my end. Down 90%  I'll move them till the problem is fixed.

[eleuthria]

Yeah, my Cubes really took a hit, there running 94-97% on my end. Down 90%  I'll move them till the problem is fixed.

All problems are fixed now, every BTC Guild server (including validation server) has been reverted to the same software it was using for the last year.