[ANN][POOL] ipoMiner - Profitable multipool targeting new coins + merged mining!

[precrime3]

Im getting some BS error.... "error 47 from memcached.... SERVER HAS FAILED AND IS DISABLE UNTIL TIMED RETRY"

[anyone4u]

Im getting some BS error.... "error 47 from memcached.... SERVER HAS FAILED AND IS DISABLE UNTIL TIMED RETRY"

yes server has failed, too many ppl on pool, was on 4127mhash I think when I looked be4 refreshing page then server failed. We need to lock this thread or stop new miners coming on because its hurting us all as shown by above.

also was updated yesterday but too many ppl joining

Mar 21 8:20 PM Due to a problem with a stratum server process becoming unstable at our higher hashrates today, we have implemented a load balanced stratum architecture. Tomorrow we will be performing some maintenance to upgrade our server hardware and begin to prepare to add an EU stratum endpoint. There may be a short period of downtime lasting for 30-45 minutes around approximately 3-4pm EST (7-8pm GMT).
already crashed agian

[hashmasterz91]

Im getting some BS error.... "error 47 from memcached.... SERVER HAS FAILED AND IS DISABLE UNTIL TIMED RETRY"

I have the exact same error in cgminer. Only just started happening within the last 20 minutes or so.

[anyone4u]

Im getting some BS error.... "error 47 from memcached.... SERVER HAS FAILED AND IS DISABLE UNTIL TIMED RETRY"

I have the exact same error in cgminer. Only just started happening within the last 20 minutes or so.

If you look at official page, no one is mining because too many ppl joined and crashed it. I suggest op lock the pool so no new ppl can join it or else same will keep happening.

[precrime3]

Yeah that makes sense xD

[ipominer]

Sorry about the issues currently! The hashrate estimate displayed currently on the site is wrong, as the statistics caching job is quite behind. We're working on it.

[RentaMouse]

This isnt related to the current hashrate, quite the opposite, but there appear to be a lot of recent reports of something diverting miners' hash power to 206.223.224.225 (I see MultiPool has added an announcement about it)

Apparently your miner will display the above IP instead of the server you expect so quite easy to spot, consensus seems to be that it is some sort of malware but not yet identified.

[schnauzr]

Sorry about the issues currently! The hashrate estimate displayed currently on the site is wrong, as the statistics caching job is quite behind. We're working on it.

I'm also getting this error constantly - [23:16:42] Lost 10 shares due to stratum disconnect on Pool 0 - where the number of shares varies every time it disconnects.  Is the pool just being overloaded and can't cope?  Anyone else getting these errors?  Happening on both my rigs, Windows and Linux.

[precrime3]

Yup me too. What happened to that code that ran 20-30 gh/s? This is only like 4.... Still a great pool, just wished I could mine on it.

[anyone4u]

Yup me too. What happened to that code that ran 20-30 gh/s? This is only like 4.... Still a great pool, just wished I could mine on it.

I click page and it was up a sec, I click login
"405 Not Allowed
nginx/1.2.1"

I then click refresh

We are currently seeing 30Gh/s+ of illegitimate hashrate on our stratum servers, and have taken them down for maintenance to evaluate the situation.

So scammers have ruined the day again. Why can't they just go to hell already?

[ipominer]

For the past ~7 hours we've been seeing 40-60 Gh/s of hashrate pointed at our stratum, which is overloading it in what appears to be some kind of strange DDOS. However, we aren't solving blocks at the rate that would indicate that we should be.

Part of the issue has also been that stratum-mining blocks on database calls, so I've been working with Ahmed Bodi (the stratum-mining maintainer) on tuning the stratum server as best as we can currently.

We've been actively working on this, and I'll post more details as we have them. The website/frontend is not being updated because the jobs to handle the calculations are being blocked by constant large writes to the shares table.

(As a side note, we have temporarily increased the starting variable difficulty to 1024 to give the database server a fighting chance whenever we have to restart stratum because it becomes unresponsive. After restarting the stratum process recently, within a minute there had been more than 80k 1024 shares submitted!)

[ratty]

Dumb question, but aren't they logged in when submitting shares? If it's all the same account submitting the bad shares, you could just block that account. Or does stratum work by allowing work to be requested before asking for worker user/pass ?

[PDcologne]

is the pool down? i am getting constant disconnects and losing shares....

any idea on when it will be up and running again - ?

[ipominer]

They are rotating through existing users, which is why you see insane hashrates for your workers if you've looked at the site after I've managed to get the jobs to run the frontend statistics calculations to access the database long enough to update. We are actively working on identifying the sources and implementing a way to block it.

[MrJoshwaa]

I mined for about 6hrs today on your pool.

My account shows zero balance, is it likely some sort of balance may show up? or has the ddos made my afternoons mining redundant?

Thanks

[roadies]

I mined for about 6hrs today on your pool.

My account shows zero balance, is it likely some sort of balance may show up? or has the ddos made my afternoons mining redundant?

Thanks

Did you check your unconfirmed balance too? I have quite a few coin locked up as unconfirmed from today's mining. You might too.

[MrJoshwaa]

No mate, not even a singe satoshi lol

Its very wierd indeed

[Charloz24]

I'm getting no hashrate displayed at all??? On my 2 worker

[Gamer67]

So despite the blurb in the OP this pool suffers from the same sort of problems as other multipools ?

[ipominer]

We have been back up and running since approximately 6:30AM EST, although we have only just now completed getting the remainder of the background processing jobs caught up.

All background/processing jobs have been re-enabled now. The site and pool should be 100% operatational at this time.

The short explanation is that it appears we were under an attack due to an exploitable flaw in stratum-mining, where fake shares can be submitted and they are treated as valid. We were seeing around 100,000 difficulty 1024 shares submitted per minute -- which is roughly equivalent to a 40Gh/s pool. We were on a bit of a wild goose chase for a while, as WafflePool was having issues with "hash redirection" that initially seemed like they might be related (https://bitcointalk.org/index.php?topic=433634.msg5853318#msg5853318).

However, that was not the case, and eventually we narrowed the source of the problem down to stratum-mining, and began working on a fix. We ultimately switched our servers to use the same stratum server version that Multipool.us uses, which is unaffected by the exploit.

As soon as we switched over to that stratum code version, the excessive shares instantly stopped.

Please note that ECC blocks mined overnight between block #29,962 and #30,599 will have to be manually processed, and will be credited later today. We've been up working on this all night, so that will most likely begin to happen after 8pm EST. We found approximately 33 blocks during that block range that will require manual processing.

Blocks prior to #29,962 and after #30,599 are unaffected and have all been paid normally.

Also, we have had to disable variable difficulty with the new stratum code. We've temporarily set worker difficulty to a static 128 for everyone, and will be adding the difficulty setting control back onto the site later today.