all my workers on the account detail are red though they show a hash rate weird...
Yep, missed that last night. I'll have it working shortly.
UPDATE: Added some load balancing to up site/pool performance.
Topic: Old simplecoin thread - page 22. (Read 99808 times)
Yep, missed that last night. I'll have it working shortly.
UPDATE: Added some load balancing to up site/pool performance.
Asus has a pretty good rma process. it tends to be pretty fast when i've done mobos...
all my workers on the account detail are red though they show a hash rate weird...
About to try out nginx web server. The pool will be up but the website may be unreachable for a few.
UPDATE: Unrelated pool trouble.... looks like a network issue at the datacenter.
UPDATE #2: back up. couldn't reach any of my sites there for a minute.
UPDATE #3: Round shares & estimates showing 0, working on making that stat less resource intensive.
UPDATE #4: Everything's happy again. Network issues may have only been on my end, as I don't see a real drop in anyone else's hashrates.
UPDATE: Unrelated pool trouble.... looks like a network issue at the datacenter.
UPDATE #2: back up. couldn't reach any of my sites there for a minute.
UPDATE #3: Round shares & estimates showing 0, working on making that stat less resource intensive.
UPDATE #4: Everything's happy again. Network issues may have only been on my end, as I don't see a real drop in anyone else's hashrates.
Yeah! Then when switching a few things around, one of my 1 month old 5770s decided to stop working! So, I lose a little there, and cuts my gain down! I'm still trying to get the new cards dialed in. And, I guess I'll have to send the 5770 out to RMA! How is ASUS's RMA process anyway?
It's looking like no 5830s for me tonight! 
They'll probably be here tomorrow!
They'll probably be here tomorrow!Looks like somebody's cards came in
keep up the work man looking good.
Hey! It's cool that the top 30 hashrates doesn't show inactive people anymore, but it looks awkward for the Onion winners to be below the Top 30 most shares.
Working on it
I've pretty much rewritten about 50% of the back-end in the past few days. While the site looks mostly the same, the operation behind the scenes is vastly improved.
Hey! It's cool that the top 30 hashrates doesn't show inactive people anymore, but it looks awkward for the Onion winners to be below the Top 30 most shares.
SC - my stats haven't updated at all since this morning. I can't tell if all my miners are still hashing, etc.
edit: nvm, I see it. fixing.update: fixed. hashrates look lower than they should due to running out of order to force update.
SC - my stats haven't updated at all since this morning. I can't tell if all my miners are still hashing, etc.
edit: nvm, I see it. fixing.update: fixed. hashrates look lower than they should due to running out of order to force update.
SC - my stats haven't updated at all since this morning. I can't tell if all my miners are still hashing, etc.
Which stats on which page? I see you hashing at 1.5 gh currently.
SC - my stats haven't updated at all since this morning. I can't tell if all my miners are still hashing, etc.
Warning: mysql_fetch_object(): supplied argument is not a valid MySQL result resource in /var/www/includes/requiredFunctions.php on line 243 Notice: Trying to get property of non-object in /var/www/stats.php on line 133
In pool stats.
In pool stats.
Thanks, I just saw that too.
The new .24 bitcoin client just crashed and was unrecoverable, I reverted to the stable one we've had up for weeks.
Even the failsafes managed to fail....
Sorry for the brief downtime, should be back to smooth now.
Also, stats caching is changing to dynamic as opposed to just timed. Which means you'll be more likely to get updated site stats than ones previously cached.
Warning: mysql_fetch_object(): supplied argument is not a valid MySQL result resource in /var/www/includes/requiredFunctions.php on line 243 Notice: Trying to get property of non-object in /var/www/stats.php on line 133
In pool stats.
In pool stats.
The site is showing current difficulty where the current block should be displayed.
Oops. Nice catch.
The site is showing current difficulty where the current block should be displayed.
It's looking like no 5830s for me tonight! They'll probably be here tomorrow!
They'll probably be here tomorrow!
About to break the site for a few minutes. If you get issues all over the place, I'm still working on it.
UPDATE: Site speed update done. Live stats are up, but to protect the server there is a 5 second wait required between them being refreshed.
UPDATE: Site speed update done. Live stats are up, but to protect the server there is a 5 second wait required between them being refreshed.
Added new caching methods to speed up shared data. The site should be a bit more responsive now.
Jump to: