The 100% fee just sucks
Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 359. (Read 903150 times)
December 06, 2012, 06:39:57 PM
Is the PPLNS details working? It shows me 0 shares in current shift and well that is not right. I changed to PPS and the shares are counted immediatly. So I switch back to PPLNS and it is still at 0 and so are a few shifts that I know the miners were hashing away in.
The 100% fee just sucks
The 100% fee just sucks
December 06, 2012, 02:22:03 PM
24 Hour Earnings stat is back, located on the top "dashboard" bar. Currently only showing PPS earnings. Working on getting PPLNS added to the figure in the next hour.
UPDATE: PPLNS is now included in the 24 hour statistic. It looks pretty accurate from my small farm. If anybody thinks the stat looks wrong, please send me a PM with your findings so I can double check my math with yours. Remember that PPLNS is subject to variance, and I think [not positive] yesterday was ~15% below expectation after just a brief look.
UPDATE: PPLNS is now included in the 24 hour statistic. It looks pretty accurate from my small farm. If anybody thinks the stat looks wrong, please send me a PM with your findings so I can double check my math with yours. Remember that PPLNS is subject to variance, and I think [not positive] yesterday was ~15% below expectation after just a brief look.
Yep.. saw it.. thanks for not only the work but ur efford to keeps us up2date over and over again...great.job.
December 06, 2012, 12:16:00 PM
24 Hour Earnings stat is back, located on the top "dashboard" bar. Currently only showing PPS earnings. Working on getting PPLNS added to the figure in the next hour.
UPDATE: PPLNS is now included in the 24 hour statistic. It looks pretty accurate from my small farm. If anybody thinks the stat looks wrong, please send me a PM with your findings so I can double check my math with yours. Remember that PPLNS is subject to variance, and I think [not positive] yesterday was ~15% below expectation after just a brief look.
UPDATE: PPLNS is now included in the 24 hour statistic. It looks pretty accurate from my small farm. If anybody thinks the stat looks wrong, please send me a PM with your findings so I can double check my math with yours. Remember that PPLNS is subject to variance, and I think [not positive] yesterday was ~15% below expectation after just a brief look.
December 06, 2012, 12:13:23 PM
the newest cgminer sure cannot handle such server problems. 5 out of 6 of them crashed.
and this is probably why I will quit mining with gpus some day soon. just do not feel like
messing with it anymore for what it brings in.
and this is probably why I will quit mining with gpus some day soon. just do not feel like
messing with it anymore for what it brings in.
Newest cgminer (or any after 2.8.3) should be able to handle disconnects. I know some versions of the proxy may have had issues if you were connecting through that. Regardless, the issue has been fixed now, and it was mostly the side-effects of the DDoS attack.
no proxy.
newest cgminer as of last week or so. running on 3 different boxes. two instances on each box. only one survived.
i realize it is not your fault. you need to do what you have to do to run your business.
the whole mining thing just gets old after a while for the rewards. maybe diff will drop this dec. one can only hope.
December 06, 2012, 12:03:54 PM
the newest cgminer sure cannot handle such server problems. 5 out of 6 of them crashed.
and this is probably why I will quit mining with gpus some day soon. just do not feel like
messing with it anymore for what it brings in.
and this is probably why I will quit mining with gpus some day soon. just do not feel like
messing with it anymore for what it brings in.
Newest cgminer (or any after 2.8.3) should be able to handle disconnects. I know some versions of the proxy may have had issues if you were connecting through that. Regardless, the issue has been fixed now, and it was mostly the side-effects of the DDoS attack.
December 06, 2012, 12:00:27 PM
the newest cgminer sure cannot handle such server problems. 5 out of 6 of them crashed.
and this is probably why I will quit mining with gpus some day soon. just do not feel like
messing with it anymore for what it brings in.
and this is probably why I will quit mining with gpus some day soon. just do not feel like
messing with it anymore for what it brings in.
December 06, 2012, 11:50:39 AM
Thanks for all the hard work! Love the new stat layout btw
December 06, 2012, 11:08:27 AM
I'm sure you're pretty busy with everything going on, but will the port80 server be making a comeback?
Yes, the port80 server should be back by tomorrow.
Update after last night's hour of instability: The fix to the Stratum server seems to have gone in perfectly. Software has been up for about 12 hours without a single reset. I also did a quick restart to bitcoind (doesn't reset the stratum server) to help fix a potential issue with stales.
December 06, 2012, 08:18:46 AM
I'm sure you're pretty busy with everything going on, but will the port80 server be making a comeback?
December 06, 2012, 01:17:44 AM
So far so good. Sorry again for the ~1 hour of high connectivity issues. It's really tough to debug an issue like what was happening, outside of letting it happen again with extensive debug information displaying in real-time.
December 05, 2012, 11:12:26 PM
I seem to be getting server not responding while ming a lot right now. But then it seems to pick itself back up.
There have been a LOT of server restarts in the last hour trying to figure out what's been crashing it. I have a fix in place, but it turns out it completely broke slush's stratum proxy. I have a NEW fix in place that should allow Slush's proxy to connect, while still avoiding the crash issue.
December 05, 2012, 11:09:31 PM
I seem to be getting server not responding while ming a lot right now. But then it seems to pick itself back up.
December 05, 2012, 11:03:58 PM
It looks like there are some people who are either attacking the Stratum pool, or simply running a completely broken implementation of the protocol. If you're running some kind of custom Stratum miner and it broke tonight as a result of my patch, please send me an email.
EDIT: Shoot, it looks like it's slush's stratum proxy sending some kind of keep-alive message (no method, just "error": null, "id": 1, "result": null)
EDIT: Shoot, it looks like it's slush's stratum proxy sending some kind of keep-alive message (no method, just "error": null, "id": 1, "result": null)
December 05, 2012, 11:01:23 PM
Hope so. Just saw a few of my miners go back to getwork from stratum. I must say you fix stuff quick as hell!
December 05, 2012, 10:56:58 PM
New patch in place. Found the main cause of this problem.
December 05, 2012, 10:28:41 PM
Thanks again for all your hard work! No problems in the last 3 hrs for me.
December 05, 2012, 10:22:24 PM
A test patch has been deployed on the Chicago stratum server for the bug that was causing a crash. It's set to restart on failure, so worst case scenario you may lose 1 second of connectivity every few hours if it does not work. It has some extra debug lines added so if it doesn't work I can hopefully catch it on the next pass. Sorry for the downtime once again. I've known there was a small crash happening every 12+ hours last week, but thought that I had it fixed when I updated the Stratum code to support PPLNS. It just happened more often these last 24 hours now that the DE server has been merged with the Chicago servers temporarily.
December 05, 2012, 10:06:51 PM
How goes the attack. I am still noticing stratum and getwork miners having connection issues from time to time.
Alright, I loaded up the status on the Chicago stratum server and noticed it was having a "soft crash" where the pool dumped the connections and started fresh once ever few hours. Not a HUGE deal (<1 second of downtime each time it happens), but certainly not ideal. Running the Chicago stratum server in a debugger to see if I can find out what's going on next time it happens.
This must have been the problem I was experiencing. It was about once every two hours for me. All my cgiminers went thru it fine but one. Thats how I noticed it would keep saying loosing shares and locking up. Oh well. Hope its all fixed.
The bug popped up again and was caught in the debugger. I've restarted the pool with auto-restart now, while I work on a fix. Sorry for any downtime since the only way to catch it is to make sure the pool doesn't restart itself once it happens.
December 05, 2012, 09:10:06 PM
How goes the attack. I am still noticing stratum and getwork miners having connection issues from time to time.
Alright, I loaded up the status on the Chicago stratum server and noticed it was having a "soft crash" where the pool dumped the connections and started fresh once ever few hours. Not a HUGE deal (<1 second of downtime each time it happens), but certainly not ideal. Running the Chicago stratum server in a debugger to see if I can find out what's going on next time it happens.
This must have been the problem I was experiencing. It was about once every two hours for me. All my cgiminers went thru it fine but one. Thats how I noticed it would keep saying loosing shares and locking up. Oh well. Hope its all fixed.
December 05, 2012, 08:51:01 PM
How goes the attack. I am still noticing stratum and getwork miners having connection issues from time to time.
Alright, I loaded up the status on the Chicago stratum server and noticed it was having a "soft crash" where the pool dumped the connections and started fresh once ever few hours. Not a HUGE deal (<1 second of downtime each time it happens), but certainly not ideal. Running the Chicago stratum server in a debugger to see if I can find out what's going on next time it happens.
Jump to: