Topic: [ANN][TAG] TAGMining.Com is now the official pool of Tagcoin! - page 40. (Read 45656 times)

Great news Fuse!  My miners are back there hard at work.

Pool mining has been resumed, and the pool is ready to rock again!

First of all I want to sincerely apologize for the downtime.  I realize that I probably lost some miners to this issue, but I'm hoping that with time we will be able to get back on top.  I want to thank those of you that come back and mine with the pool.  Thanks for everyone's support through the downtime.  For the record, I received many offers for help- servers, cash for new equipment, coding... it was an overwhelming feeling of community.  Although I didn't take anyone up on their offers, I wanted to thank those of you that had my back over the last two days.

That being said... we're ready to rock.

We are now running a Mysql load-balancing setup to handle additional loads.  If things get crazy in the future, I can easily spin up another server or two or three and throw them into the mix on the fly.  In addition to this, I have upgraded MPOS again.  It contains new code for DB cleanup, as well as a few extra backend updates that will speed things up a little and make things more secure.  One thing in particular is the addition of a password and pin lockout on 3 failed attempts.

There will be some things that will need to be changed aesthetically, but as far as the framework goes, we should be solid.  I will be making some front-end website changes over the next few days, so if you see something by Saturday that I haven't fixed on the site, let me know.  I'm sure there will be things I forget, so don't hesitate to shout at me.

I have noticed the liquid assets are different from the old server to the new one.  Don't worry, it is showing as less on the new server, so your balances and payouts will be correct.  The only thing it effects is me knowing exactly how much is in the jackpot pool when we run the next jackpot, which will be next Saturday.  This weeks earnings will carry over to next week and a larger jackpot will be held.

If for any reason there are any issues mining or getting payouts, LET ME KNOW ASAP... either by PM or reply in this thread.

Thank you again to everyone, and thanks for being awesome!

-Fuse

Yes thank you for all your hard work! It is greatly appreciated 

Awesome news! I've been redoing cable bundles here, and am going to find some food. This is nice to hear now that I'm ready to relax a little Thanks for the hard work.

Update on progress:

• Front end work completed.
• DB and wallet transferred to new server.
• Tested site functionality(looking good!).
• Changed DNS records, and I'm just waiting for the change to take effect.

I think we will be back up tonight .  Little later than I had hoped, but things should be much better now.  I'll post an update when things are back to business.

-Fuse

Fuse,

Don't stress about it... I went over the HashFaster and have also been mining some other coin as well... when the pool is back up I have 3Mh/s that I will put into the pool.

Update on progress:

• Database cluster has been created and configured.
• Front end work has started, and should be complete in the next few hours.
• Existing blocks on old pool server have been confirmed, and the database is ready to be moved.

The front end connection to the DB cluster is taking a little longer than expected.  One of the php-mysql libraries is being stubborn, and I'm currently trying to trace the issue.

As a reminder, please do a manual cashout on the pool if you have a balance.

Updates to continue as the day goes on.

-Fuse

Sounds like you're the man.

If I can help let me know. I wasn't sure if an extra physical server would help or not, which is why I asked.

Threw my spare miners at DGC. Mine, chomp, hash, mine, chomp, hash.. lol

I had one that matched the main server, but bringing it online wouldn't solve the current issue with Mysql.  I think it's an issue with clearing out the old share archive in Mysql, which at this point the server couldn't keep up with.  Besides a backup server, the other option is to lock out the 85MH user, and continue mining on the pool at a lower load, but that still wouldn't solve the load problems later on.

So I am rebuilding from scratch and updating MPOS, as the new version has some code pertaining to how to handle the added archive cleanup load.  Between this and the mysql load balancing, I think that should solve the issue.  I think a realistic ETA would be tomorrow afternoon.  I will be pulling an all nighter and taking tomorrow off from work to handle this.

In the meantime, payouts will still occur.  I believe this is the most responsible thing to do at this point so miners' money isn't tied up on a downed server.  The action plan I outlined, while creating additional mining downtime, should enable a smoother transition to a new server.

-Fuse

Subscribed. Do you need a second/backup server?

Mining is currently disabled on the pool.

Something is happening with the db where mysql is ramping up to 80-90% CPU usage and bogging everything down.  Even with the server upgrade to try to limp along, we got to a point of sluggishness we were at before.  I am shutting down the stratum service so I can work on the pool.  The front end is still running, as is payouts, both manual and automatic.  I want to make sure everyone is able to get their coins.  This is the most important thing to me right now.

My plan of action is as follows:

• Setup new server cluster with Mysql load balancing.  The old pool will run in this mining disabled payout mode until I get the new pool up and running.
• Transfer the database over to the new pool DB so we can keep our stats, and there are no issues with readding accounts and miners.
• Shut down the old pool and transfer the pool wallet over to the new pool.
• Change the DNS records to point to the new pool.

I will update this thread as progress occurs.  If you have balances on the pool, please do a manual payout to insure you don't have funds just sitting around.

Thanks for your patience and understanding in this matter,

Fuse

*EDIT- This week's jackpot will be suspended until I can get the pool up and running again.  The balance will be carried over to the next jackpot.

Pool was brought down, upgraded and brought back up.  Total downtime was about 3-4 minutes.

Doubled the CPU cores and quadrupled the memory.  Let's see if that helps for now.  I will be spinning up the load balancing servers ASAP and testing things out.

Thanks,

Fuse

To answer your question honestly... yes, we are struggling.  For some reason, the Mysql writes are pegging the CPU usage.  I will be bringing the pool down today to upgrade to a higher tier server.  This will be the band-aid for now.  I'm going to spin up a load balancing server cluster or look at a dedicated server.  I might also try to just load balance the Mysql server to get things evened out.  Either way, there will be an end result that makes everything work the way it should.

I sincerely apologize for the lag, guys and gals.  Server downtime incoming.

-Fuse

Weird, back to 200 odd all of a sudden...  And it's not an Australian thing as tagmining.com is the only site I was getting really bad lag 

John,

I am in the same position... query times of 50,000ms or more. I am back and throwing a solid 2Mh/s at the pool... I am dreading my power bill... hope my estimates are right!!!

Edit - make that 86,000ms...

Maybe I broke the interwebz again    but the querytimes are reallllly bad for me ATM.  25,000 + MS. Other US based sites are OK, not great, but OK. I'm getting < 200 MS from the tag pps pool.  Is the server struggling with the extra load?

We're back up on the front-end.  Thanks for your patience.

-Fuse

Not panicking because I know your doing your best to correct the issue thanks! 

DONT PANIC!

I am working on the frontend.  It will be back shortly, mining is still running, as is auto-payouts.

I will update when the front end is back up.

Can I adopt your son?  My daughter is 3... she better be making profitable trades on exchanges when she's 14 or I did something wrong lol.