stratum is 51 seconds in the future.
better now? |
|
|
|
Hi, We have added RADS as an official payout coin on our multipool: www.zpool.caI hope you can bring good support from miners. We offer 10+ algos to mine and over 100 altcoins. Cheers! Awesome! The ANN was updated with the link! radiumd keeps using 100%+ CPU. Any idea why? Staking is not enabled. "version" : "v1.2.0.1-g32a928e", "enabled" : false, "staking" : false, I'll have to drop it from the pool if I can't get it under control. That is our fault. We had a hard fork a few days ago, which is what would be causing the issue. If you update to the latest wallet, you'll be good to go. https://github.com/tm2013/RadiumMy apologies. If you have any issues, please let me know. JJ OK thanks. |
|
|
|
Hi, We have added RADS as an official payout coin on our multipool: www.zpool.caI hope you can bring good support from miners. We offer 10+ algos to mine and over 100 altcoins. Cheers! Awesome! The ANN was updated with the link! radiumd keeps using 100%+ CPU. Any idea why? Staking is not enabled. "version" : "v1.2.0.1-g32a928e", "enabled" : false, "staking" : false, I'll have to drop it from the pool if I can't get it under control. |
|
|
|
Groestl algo was present a while ago, is it still on the book?
I was waiting for DMD to switch back to groestl then enable it again. Not sure if they ever forked yet... |
|
|
|
but zpool doesnt have the other 5 coins that is why i ask
the other coins aren't on an exchange that I use so are not enabled on zpool. I didn't realize they were all on cryptopia. I've added the whole bunch to www.zpool.ca now. nice dude are they all merged mined there yup |
|
|
|
Is there something I can do to stop getting disconnects I never had this problem before
read back. there's some in depth analysis on how deep the issue really is.. for the short term... nothing but setting up a stratum proxy to minimize the issues. I have no notice of disconnects on my multi algo mining. I have mainly been seeing and hearing about issues with SHA or Scrypt ports when it comes to disconnects. It is pretty much isolated to scrypt and sha. Not only that there are more crap coins on those ports but I think also from the vast amount of crappy ASIC devices. It rarely happens on any other port. Only step ATM to help reduce this is what JK suggested. I may have a dev willing to recode the stratum but it won't be easy or done in short order but seems work is underway. |
|
|
|
but zpool doesnt have the other 5 coins that is why i ask
the other coins aren't on an exchange that I use so are not enabled on zpool. I didn't realize they were all on cryptopia. I've added the whole bunch to www.zpool.ca now. |
|
|
|
The reject issue has been bothering me a lot recently.
IDK whats causing it; but its very recent. Within a week or two.
It's just catching erroneous data. Right now the rejects on the front end can be ignored, it's a WIP. Unless you are seeing high rejects on the miners side, you're still getting credits for all of them. Ok... good... that's very consoling info. Seeing all those red reject lines zigzagging all over my hashrate charts is disconcerting =) Myr-gr seems pretty profitable; my GTX980 keeps switching to it. I put XVG on it earlier today and AUR was added the other day too. May have given't it a bump but XVG looks like it's the bottom of the bunch right now.. |
|
|
|
The reject issue has been bothering me a lot recently.
IDK whats causing it; but its very recent. Within a week or two.
It's just catching erroneous data. Right now the rejects on the front end can be ignored, it's a WIP. Unless you are seeing high rejects on the miners side, you're still getting credits for all of them. |
|
|
|
How do I put "-f 256" into a sgminer .conf file ?
cheers
Don't have to now. I rebuilt the stratum for blakecoin with the fix in there. |
|
|
|
Hi, We've added XVG to the miners multipool: www.zpool.caCheers! We're mining on algos scrypt and lyra2rev2 and also payout in XVG on any algo. Cheers We've added XVG to the myr-gr algo now. Cheers! |
|
|
|
For miners using blakecoin there is an extra switch you should use, which will make the pool report the proper hash rate.
GPU miners please add -f 256 to your command line. There is no standard with blakecoin which is why there is a discrepancy but your shares are still accepted and valued properly.
Cheers
I was thinking of -f 256 but didn't try it....Thx crackfoo.  Yes and it is reporting mh/s it should be Gh/s. Ok, I'm going to apply a different fix. Stratum will restart in a bit Ok but I can't put it in my bat or conf file because of this... it will stick to that algo as being the highest forever. Ok, shouldn't need that now then. Hashrates look normal now. |
|
|
|
For miners using blakecoin there is an extra switch you should use, which will make the pool report the proper hash rate.
GPU miners please add -f 256 to your command line. There is no standard with blakecoin which is why there is a discrepancy but your shares are still accepted and valued properly.
Cheers
I was thinking of -f 256 but didn't try it....Thx crackfoo. Yes and it is reporting mh/s it should be Gh/s. Ok, I'm going to apply a different fix. Stratum will restart in a bit |
|
|
|
|
For miners using blakecoin there is an extra switch you should use, which will make the pool report the proper hash rate.
GPU miners please add -f 256 to your command line. There is no standard with blakecoin which is why there is a discrepancy but your shares are still accepted and valued properly.
Cheers
|
|
|
|
but zpool doesnt have the other 5 coins that is why i ask
the other coins aren't on an exchange that I use so are not enabled on zpool. |
|
|
|
Yup, I've tried manipulating those even up to the 600, it then just hangs that much longer. There were a few other timeouts I tried manipulating as well with little improvement. If only it was smart enough to identify which wallet it was that was causing the issues, and simply disconnect it... it would be so much better. To reset stratum, seems like a big hammer and IMO, was a big shortcut by the orig dev.
I doubt you could narrow it down to any particular coins wallet, as it seems it can be any wallet at any time that might either respond immediately or take a long time to return. I assume the wallet must be doing something that prevents it from processing rpc calls at the time. Calling GBT with no parameters can return a massive amount of data on the BTC wallet. Do you know if it is making a GBT call on BTC? Since this is not being mined directly, it might be possible to put an exclusion in for the BTC wallet. Yeah I can't really. I tried reducing them all to just main stream, higher diff coins and it would still happen. Stratum has to be always calling GBT on all coins all the time after each block notify. BTC isn't enabled in stratum so those calls don't get made but yes, BTC GBT spits out a lot of crap. Early on it was enabled and saw errors all the time but isn't the source of the on going issue unfortunately. |
|
|
|
Is there any reason not to add skein, the 5th Algo for DGB/MYR/AUR?
I'll be added a few more algos over the next few weeks. btw, the pool is already running of SSD's and is also distributed over 4 8-12core servers with 256GB ram. It's not the hardware. I've changed it 3 times now. The hardware investment is now 10-15k a year. I'm still looking for a dev that is willing to re-write port the stratum component to something more robust and stable. I have one prospect so far and it by no means cheap. It will be a $2-3k job and has to be done right. Trust me, nothing I hate more than seeing the stratum resets. It's also BTC out of my pocket too. My end game is to be A) The most profitable, B) Reliable, C) Stable and D) The biggest. I've got 3 out of 4 IMO, stability will come as soon as I can get it developed. Ouch. I hope you get a highly configurable stratum server for that job. It's a bit beyond something I would want to tackle at the moment. The issue I was getting involved the monitor thread. I was trying to use it to solo mine some MYR which now has the getwork protocol removed. For some reason the system thought my MYR address was not a valid MYR address, so I think I was getting this due to the stratum server not having any jobs to provide. If your stratums are resetting at the same piece of code (perhaps due to getblocktemplate rpc delays), than I suppose you could always try increasing the max job delay. It might mean the stratum clients aren't being fed with jobs to run at full whack at times, but it might be better than a reset. stratum.h #define YAAMP_MAXJOBDELAY (2*60) stratum.cpp ///////////////////////////////////////////////////////////////////////////////
void *monitor_thread(void *p)
{
while(1)
{
sleep(120);
if(g_last_broadcasted + YAAMP_MAXJOBDELAY < time(NULL))
{
stratumlog("%s dead lock, exiting...\n", g_current_algo->name);
exit(1);
}
}
}
/////////////////////////////////////////////////////////////////////////////// Yup, I've tried manipulating those even up to the 600, it then just hangs that much longer. There were a few other timeouts I tried manipulating as well with little improvement. If only it was smart enough to identify which wallet it was that was causing the issues, and simply disconnect it... it would be so much better. To reset stratum, seems like a big hammer and IMO, was a big shortcut by the orig dev. |
|
|
|
Is there any reason not to add skein, the 5th Algo for DGB/MYR/AUR?
I'll be added a few more algos over the next few weeks. btw, the pool is already running of SSD's and is also distributed over 4 8-12core servers with 256GB ram. It's not the hardware. I've changed it 3 times now. The hardware investment is now 10-15k a year. I'm still looking for a dev that is willing to re-write port the stratum component to something more robust and stable. I have one prospect so far and it by no means cheap. It will be a $2-3k job and has to be done right. Trust me, nothing I hate more than seeing the stratum resets. It's also BTC out of my pocket too. My end game is to be A) The most profitable, B) Reliable, C) Stable and D) The biggest. I've got 3 out of 4 IMO, stability will come as soon as I can get it developed. |
|
|
|
Nice to see some new algos in the pool.
Is blakecoin showing the correct hashrate? Wrong units maybe?
Yeah the units doesn't seem to be right. Working on that. |
|
|
|
bug to c11 algo maximum shares 79.3800%
Even more scary is the 5% sha256 fee and whopping 20% scrypt fee!!! Surely a development system to production system rollout error. Whoops, didn't notice that! I forked the pool software to the next version and missed the example where you can set per algo fees. https://github.com/tpruvot/yiimp/blob/next/web/serverconfig.sample.php#L73 |
|
|
|
|
Show Posts
