Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 8. (Read 379084 times)
September 30, 2011, 06:10:41 AM
Am I the only one having connection problems? (I'm able to mine in Slush's pool)
September 29, 2011, 12:25:18 AM
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
September 28, 2011, 10:25:56 AM
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!
September 28, 2011, 09:52:26 AM
My bad, was adding invalid characters.
September 28, 2011, 09:50:50 AM
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...
September 28, 2011, 09:45:51 AM
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.
September 28, 2011, 08:02:33 AM
The pool payout stats on https://www.btcguild.com/blocks.php haven't been updated in nearly 3 weeks.
September 28, 2011, 06:24:29 AM
New workers cannot be added. Just saying.
September 27, 2011, 03:13:05 PM
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.
September 27, 2011, 02:53:08 PM
There's a small cosmetic bug with the confirmation e-mails. The "
" from the HTML part is removed instead of being replaced with a space or a line break, resulting in e-mails like the following:
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.
" from the HTML part is removed instead of being replaced with a space or a line break, resulting in e-mails like the following:
Quote
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.
September 27, 2011, 02:14:14 PM
There's a small cosmetic bug with the confirmation e-mails. The "
" from the HTML part is removed instead of being replaced with a space or a line break, resulting in e-mails like the following:
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.
" from the HTML part is removed instead of being replaced with a space or a line break, resulting in e-mails like the following:
Quote
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.
September 26, 2011, 01:13:37 PM
Safe to say Diablo's a dick, then!
September 26, 2011, 12:47:58 PM
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.
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.
September 25, 2011, 07:29:52 PM
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.
September 25, 2011, 07:13:02 PM
Long story short, I was trying to change our cert so it would work on PPS as well as Proportional, but I'm not using a self-signed cert, and it costs more to add a wildcard subdomain to our cert. Botched my explanation of why I revoked/rekeyed the cert (its been a long day). The old server did not have the re-issued SSL cert, since we were moving to a different server. I didn't expect the move to take as long as it did, ideally nobody would have received any messages about an invalid/revoked certificate.
September 25, 2011, 06:38:51 PM
Server is being moved if you're seeing the security certificate revoked message. Revoked our old SSL cert since we're changing IPs. Should be back up and running shortly.
Why would you do that? A cert is attached to a domain name not an IP and can move to a new IP easily. September 25, 2011, 04:09:54 PM
Server is being moved if you're seeing the security certificate revoked message. Revoked our old SSL cert trying to setup a wildcard subdomain so PPS pool could use the same cert. Should be back up and running shortly.
September 22, 2011, 09:57:33 AM
This weekend I will be moving the website to a different server again, changing it from a 2 gig VPS to a dedicated server. I do not know when it will happen exactly (most likely Saturday evening, PDT). Similar to the last move, the pools still be working as usual. The only part going down is the website frontend, meaning you wont be able to access your stats / payouts until the move is complete (1~2 hours).
The move is for two main purposes: 1) Speeding up the website in general, especially when a long round is calculated/sync'd. 2) Making some DB schema changes to eventually allow merging the PPS option into the main pool, rather than running it as a separate pool.
The move is for two main purposes: 1) Speeding up the website in general, especially when a long round is calculated/sync'd. 2) Making some DB schema changes to eventually allow merging the PPS option into the main pool, rather than running it as a separate pool.
September 20, 2011, 07:01:02 AM
Geez!
You might wish to remember who the moderator is for this part of the forum.
theymos has zero problems with how I moderate this board. If you have a problem with me having a problem with the pool I use having a problem with their security in the face of recent security problems then bring the problem up with theymos, and he will probably have a problem with you. Problem?
Just wondering, who has had their password hash's stolen? BTCguild or bitcointalk?
September 19, 2011, 10:41:02 PM
Not responding on web or mining ports. My traffic stops after this hop: hetzner-ic-134650-ffm-b2.c.telia.net [213.248.92.82]
Watched the new Two and a Half Men and it's back up. Woohoo!
Watched the new Two and a Half Men and it's back up. Woohoo!
Jump to: