[~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More

[BkkCoins]

Ah, understand. I thought to mention startcom issues wildcard certs for a reasonable price. It's the same as a single domain cert ($60). I think that is more than GoDaddy's single cert price though but they have an unusual policy of issuing any number of certs for you for the one price. I don't think any other CA offers that. I realize that doesn't help now you've got new ones but just something to file away for future needs.

[eleuthria]

For the last few hours, 40% of the pool has been running on PoolServerJ.  I've been comparing the share acceptance rate/reject reasons between PSJ and Pushpool for these last few hours, and have found significantly better performance on the PoolServerJ side.

The number of stale share submissions on the PSJ side are ~80% lower than the pushpool side.  This afternoon I will be rolling out a second PSJ server, and move the pool over to 80% PSJ and 20% pushpool, monitoring the stats closely before completely phasing out pushpool from the servers.

[terrytibbs]

Safe to say Diablo's a dick, then!

[ancow]

There's a small cosmetic bug with the confirmation e-mails. The "<br />" from the HTML part is removed instead of being replaced with a space or a line break, resulting in e-mails like the following:

Your confirmed rewards of XXXXX have been sent to your wallet (YYYYY).The transaction ID was: ZZZZZZZThe payout may show up instantly, or it may take a few hours depending on the time it takes to confirm.

While that isn't a problem for the payout confirmation, it caused me to copy&paste the wrong verification token when trying to verify my e-mail address until I noticed this.

[eleuthria]

There's a small cosmetic bug with the confirmation e-mails. The "<br />" from the HTML part is removed instead of being replaced with a space or a line break, resulting in e-mails like the following:

Your confirmed rewards of XXXXX have been sent to your wallet (YYYYY).The transaction ID was: ZZZZZZZThe payout may show up instantly, or it may take a few hours depending on the time it takes to confirm.

While that isn't a problem for the payout confirmation, it caused me to copy&paste the wrong verification token when trying to verify my e-mail address until I noticed this.

Is this recent (we did move servers over the weekend).  The emails are sent with both plaintext and HTML versions.  It looks to me like your email client is displaying the HTML version, but stripping HTML tags for "security".  Every email I've received to date has properly displayed the line breaks.

[ancow]

Is this recent (we did move servers over the weekend).  The emails are sent with both plaintext and HTML versions.  It looks to me like your email client is displaying the HTML version, but stripping HTML tags for "security".  Every email I've received to date has properly displayed the line breaks.

Nope, not that recent. It's happened ever since I joined (beginning of the month; same username as here, so you can look it up). My client displays the plaintext version sent with each message (for security, I'm kinda paranoid about HTML e-mails). When I select the HTML version, everything is fine.

To me it looks like whatever software you're using to create the emails simply uses the HTML version to create the plaintext version from it and simply strips out the HTML tags...

Anyway, this should be *really* easy for you to verify (just change e-mail addresses/request a payout for your own account and look at the plaintext version; any decent mail client should let you look at the source). It's pretty obvious once you know where to look and easy to miss if you just skim over it.

[AniceInovation]

New workers cannot be added. Just saying.

[kjj]

The pool payout stats on https://www.btcguild.com/blocks.php haven't been updated in nearly 3 weeks.

[eleuthria]

New workers cannot be added. Just saying.

I need more information.  I just made a worker and everything worked just fine.

The pool payout stats on https://www.btcguild.com/blocks.php haven't been updated in nearly 3 weeks.

Fixed, didn't have the script added to cron ever since the previous server move.

[ancow]

The pool payout stats on https://www.btcguild.com/blocks.php haven't been updated in nearly 3 weeks.

Fixed, didn't have the script added to cron ever since the previous server move.

While you're fixing stuff, the confirmation counts are pretty jumbled up again...

[AniceInovation]

My bad, was adding invalid characters.

[eleuthria]

The pool payout stats on https://www.btcguild.com/blocks.php haven't been updated in nearly 3 weeks.

Fixed, didn't have the script added to cron ever since the previous server move.

While you're fixing stuff, the confirmation counts are pretty jumbled up again...

Ah, missed that one.  Guess now it's time to explain what happened (it has been corrected):

As I mentioned in other threads/earlier in this one, BTC Guild has been moving from pushpool to PoolServerJ, putting lots of stress on it by redirecting some loadbalance nodes.  As of Sunday evening, the entire pool was shifted to PoolServerJ.  We've gone from 10 pushpool+bitcoind instances to 1 PoolServerJ with 3 bitcoind instances.  We update confirmations by polling a list of recent transactions from bitcoind and updating the confirmations based on the bitcoind output. 

Since we're now only using 3 bitcoind instances, its possible that the list of recent transactions is pushing out blocks that aren't yet at 120 confirms.  I've increased how many transactions get pulled, so it shouldn't happen again!

[infofront]

For the last two days, the miners on one of my machines fail, with the word "Killed" at the end of the command line. I'm running 5850s on linuxcoin, using phoenix with phatk, and I was running for weeks on end with no failures previously. Does anyone know what the problem might be and/or how to correct it? Thanks

[bz]

Am I the only one having connection problems? (I'm able to mine in Slush's pool)

[sadpandatech]

Am I the only one having connection problems? (I'm able to mine in Slush's pool)

down for me as well....


API; Failed to connect to Eleuthria Games database. Please try again later.

Website; Failed to connect to BTC Guild database. Please try again later.

Stopped accepting shares at 6:43:01 AM EST and last update to DB on shares was 4 minutes later.
Possibly some unforseen needed tweek with the changes they made recently.

[phorensic]

Yeah down for me too.  E will get it fixed fast cuz he is made of awesome.

[eleuthria]

Sorry for the downtime.  A script that has been running seemingly flawlessly for the past few months had an unforeseen side effect on the database server.  The script that was backing up the DB and uploading it to a remote server was not properly deleting the backup after they were successfully transferred.  Last night the hard drive on the DB server became completely full, and it ended up killing the database.

I've fixed the script, and I am sorry for the downtime that happened while I was asleep. 

[sadpandatech]

Sorry for the downtime.  A script that has been running seemingly flawlessly for the past few months had an unforeseen side effect on the database server.  The script that was backing up the DB and uploading it to a remote server was not properly deleting the backup after they were successfully transferred.  Last night the hard drive on the DB server became completely full, and it ended up killing the database.

I've fixed the script, and I am sorry for the downtime that happened while I was asleep. 

As previously stated, you are awesome. And you even spelled 'unforeseen' correctly. ;p

[eleuthria]

Feature/Update:  Worker stats and API are now pulled live, rather than on a one minute cache.  They should never be behind by more than 10 seconds (due to work being logged to the DB in batches).
Bugfix:  Line breaks are now properly being added on plain-text versions of emails.

[AniceInovation]

Could you check if the "Reset miner" and "Reset all miners" is working ok?
Since the update i press them and the miners never get to 0 like before.