I am continuously mining for last 3 days in your pool. my round share was .89% in the evening but now I am checking its .83% why this kind of thing happening with me ?
More people is joining pool with bigger hashrate, they starting tanking your percent of shares.
I switched my miner back over Nanopool and it's running fine now, so that seems to me it may be your server. I also see that the total speed of noobpool is decreasing.
Yeah, the pool crashed for about an hour while I was asleep. But it corrected itself and has been running fine since. I just got up, so I'll look into it and see if I can find the cause.
Of course it crashed during the time when I was trying to join. At least now I know it wasn't anything I was doing wrong. I'll give it another try now.
Found the source of our crash, after a second one, it's been resolved and fixed so it won't happen again. The pool is hosted on a dedicated server at a data center, so it's a little more work to remotely connect and diagnose issues, but this one was a simple fix and I take 100% of the blame for it happening. Had I been watching the server stats better I would have caught it before it happened. But it's fixed so that it can't happen again.
It's easy to forget that Linux based servers have folders with a set amount of disk space, unlike windows machines that just use any free space in any folder that needs it. Our stats folder was set to 4gigs and when it filled up the crash occurred. It took a month to fill, but it's been fixed and set with plenty of space so that it won't fill up.
We hit a block yesterday, but with the crash and the couple hours the server was down we lost a lot of miners and a lot of hash rate, so this block is only at 26% variance, will probably be another day to hit it if we get lucky.
Kudos to setting up your own mining pool! With the current pool hashrate, a block should be hit about once every 5 days. I've moved 1 small rig (~50Mh/s) over to it for testing purposes. Good luck and keep up the good work.
Our hashrate was hovering between 5-6GH, but we hit a stubborn block, then it turned out to be an uncle so the rewards were less, then our crash.. We lost some miners over it. But we are back to near 4GH now, hopefully people will come back and new people will give us a try.
Everything is fixed and back to normal. It was only the webpage, all mining and stats were safe and still running and all work that was done while the webpage was down was not effected.
We were hacked once again, they managed to steal the block reward almost instantly. The stolen eth was sent directly to Shapeshift who were notified about the theft. If we are lucky they will be able to stop them from withdrawing the money and get it back to us. Until them I'm going to try to fund the account myself to get the payments out, but it could take me a few days.
@danx - This is very interesting and instructive. How did they accomplish this? They would need both your keystore and your password, correct? I can see an inventive hacker grabbing your keystore, but what, they could bruteforce your password? I suppose that is a failing in Ethereum since if you had enough horsepower, you could just keep trying and trying, it doesn't lock out if you fail too many times, right?
Over 9 million brute force hits in less than 3 days. But it's been patched up. No more attacks, no more vulnerabilities. Brute force won't work now. I guess they were really desperate to steal 5 eth.
Comments
ETH: Received error: {"id":3,"jsonrpc":"2.0","result":null,"error":{"code":0,"message":"Worknotready"}}
ETH: Job timeout, disconnect, retry in 20 sec...
I don't know what this is. Wondering if it's the pool or my machine. I can't process any work.
It's easy to forget that Linux based servers have folders with a set amount of disk space, unlike windows machines that just use any free space in any folder that needs it. Our stats folder was set to 4gigs and when it filled up the crash occurred. It took a month to fill, but it's been fixed and set with plenty of space so that it won't fill up.
PS finally my message came through approve... lol
7/28/2017, 7:20:18 AM 0.081