Deal worked with Totmacher12000 for a V1000.  Payment received, and PSU will be shipped on Monday.

Thanks!

Fuse

bumpiddy bump?

would like to know if xfx stepped up and fixed their issues in the past few months or not ;]

Grats, totmacher.

I wanted to ask the active miners what they think about something.  It seems that unless we get more dedicated miners, we're going to have roughly the same group of people on the jackpot list every week.  Should I set the rule that if you win one week, you can't win the next week?  You could of course win the week after that though.

Pretty straight forward change... any ideas/concerns?

2nd Jackpot

Alrighty folks, here's the info:

There were 444 total rounds for the week.  To be eligible for this jackpot, you would have needed to submit shares to 75% of those rounds, equaling 333 rounds.  There were 15 people, including myself, who qualified for the jackpot.  This was out of 195 miners who mined on the pool this week.  The qualifying miners are as follows:

AFKMPEG
elloi
flywin
jebshka
johndec
kubur
mevecco
Namamonkee
ny2cafuse (not eligible of course)
TagCoinDaddy
TagThePinkPanther
totmacher12000
vesperwillow
wujizhu
zybqe177

This week's jackpot was a double jackpot purse carried over from last week due to the server issues we were having.  This week's and last week's total fees and donations equal roughly 175TAG.  I'm putting up 25TAG to round it out to 200TAG.  So half of that, the total jackpot purse, is 100TAG.  This might seem low compared to the first jackpot, and the fact that we've grown substantially.  However, the first jackpot covered 2 weeks of mining with a higher donation percentage from our early adopters and myself, and a 50TAG pay in by me to pad the wallet for the first couple weeks.  So going forward we should roughly be around a 100TAG jackpot payout.  If we are short, I will pay in to round it up to 100TAG, and if it is higher, I will leave it as is.

This week's winners are as follows:

1st place - totmacher12000  50TAG  - 2d12793fa014b7762c2d6792df5ff8853528ec9990a2d83fe8326361c4677e5a
2nd place - AFKMPEG           30TAG  - c12cca6f7061ac1bee8a68e6d9d211a4712fa747029b47b345b771822e88381e
3rd place - kubur                 20TAG  - 812c8df8d7f4a053698a4f4b17260057ce903bc7b18ebccb4e4d08b79ea09bc6


Payments will be sent shortly, and TXID numbers will be posted above.

Congratulations, miners!  Good luck to everyone next week!

-Fuse

Damn, Vesper... I'm going to have to start paying you for all this schooling.  U of Vesper.

Thanks, mate!

Ok here's the skinny on what was happening:

Bad news... the mysql slave server at some point lost connection to the master which threw it out of replication.  So the front-end knew that it had written block, share and payment data to the master database, but when it went to read the info from the slave it wasn't synced.  Thus the missing block confirms, finders, etc.

Good news... nothing was lost during this time, and the time earlier today.  All the data was properly written to the DB.  I was able to shut down the slave and kick the reads back over to the master without any downtime.  Also, I've been monitoring the resource usage on the master DB, and it looks good.  I think with the live data turned off, we'll be ok just running the master for now.  Looking back now, the upgraded server we had before probably would have been fine had I known about the live stats being the issue.  Either way though, we're still churning out blocks, and the pool is working properly now.

So crisis averted... again.

-Fuse

Confirmed your order.  I will ship this out in the mail tomorrow, as your my only sale in the last couple days.

Thanks,

Fuse

you posted

Test will this thing let me even post?!!!