Topic: [1423GH] ABCPool PPS - Proxy Pool For High & Steady Mining Rewards - page 37. (Read 151781 times)
January 17, 2012, 05:02:30 PM
Looks like whitelisting may have begun; a good chunk of my miners at my primary location are back, but alternate locations (and thus IPs) still showing down.
January 17, 2012, 03:00:08 PM
Thanks for the update - on back-up pools for now...
January 17, 2012, 01:08:25 PM
Looking into it.
UPDATE: It's official, ABCPool is playing with the big boys now: We are being DDOS'ed! We're now going to do some emergency whitelisting on the network perimeter and then figure out a more permanent solution. The pool will most likely be unavailable for a few hours; keep an eye on the forum for updates.
UPDATE: It's official, ABCPool is playing with the big boys now: We are being DDOS'ed! We're now going to do some emergency whitelisting on the network perimeter and then figure out a more permanent solution. The pool will most likely be unavailable for a few hours; keep an eye on the forum for updates.
January 17, 2012, 12:54:13 PM
January 17, 2012, 12:51:23 PM
Looks like it's offline again.
January 17, 2012, 10:42:52 AM
Hi miners,
16:00 UTC: Problems at our hosting provider caused ABCPool to be offline for now. Cause is yet unknown, but i'm inclined to guess that the pool will be back online in half an hour.
Sorry for the inconvenience!
UPDATE 17:00 UTC: pool is back online. The bare metal on which the server was hosted gave up. Data is unaffected, all shares have been counted. Please check your miners to make sure they have reconnected.
Thanks for your patience while we resolved this. Happy hashing again everyone!
16:00 UTC: Problems at our hosting provider caused ABCPool to be offline for now. Cause is yet unknown, but i'm inclined to guess that the pool will be back online in half an hour.
Sorry for the inconvenience!
UPDATE 17:00 UTC: pool is back online. The bare metal on which the server was hosted gave up. Data is unaffected, all shares have been counted. Please check your miners to make sure they have reconnected.
Thanks for your patience while we resolved this. Happy hashing again everyone!
January 13, 2012, 08:54:25 PM
I believe it's to get their stale count down at the cost of extremely poor efficiency. Dunno if that debate was ever really resolved to anyones satisfaction circa Bitcoin Pool.
January 13, 2012, 08:20:12 PM
I've looked through our source code, and at some point we switched to shorter timeouts for the longpolls. They're now every 120 seconds, which means that that timeout is indeed what diablominer is reporting. Therefore what you see is expected behavior
Why would you want to make such short LP timeouts ?It should be more than 600 seconds (or longer) for best efficiency.
January 13, 2012, 04:07:05 PM
DiabloMiner output goes like this:
I've looked through our source code, and at some point we switched to shorter timeouts for the longpolls. They're now every 120 seconds, which means that that timeout is indeed what diablominer is reporting. Therefore what you see is expected behavior. Code:
[1/13/12 3:30:40 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
[1/13/12 3:32:41 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
While the negative part of this effect will be between 0.00% and 0.02% in wasted GPU cycles (depending on your latency), the positive effect more than compensates that because of the faster longpoll-handling whenever a new block is reported.
January 13, 2012, 03:41:12 PM
DiabloMiner output goes like this:
2 x RAdeon HD6950 Linux Mint x64 Debian Edition
Code:
[1/13/12 3:29:20 PM] pool.ABCPool.co accepted block 616 from Cayman (#1)
[1/13/12 3:29:25 PM] pool.ABCPool.co accepted block 617 from Cayman (#1)
[1/13/12 3:29:29 PM] pool.ABCPool.co accepted block 618 from Cayman (#1)
[1/13/12 3:29:31 PM] pool.ABCPool.co accepted block 619 from Cayman (#1)
[1/13/12 3:29:48 PM] pool.ABCPool.co accepted block 620 from Cayman (#1)
[1/13/12 3:29:49 PM] pool.ABCPool.co accepted block 621 from Cayman (#1)
[1/13/12 3:29:52 PM] pool.ABCPool.co accepted block 622 from Cayman (#2)
[1/13/12 3:29:53 PM] pool.ABCPool.co accepted block 623 from Cayman (#1)
[1/13/12 3:29:53 PM] pool.ABCPool.co accepted block 624 from Cayman (#1)
[1/13/12 3:29:55 PM] pool.ABCPool.co accepted block 625 from Cayman (#2)
[1/13/12 3:29:59 PM] pool.ABCPool.co accepted block 626 from Cayman (#1)
[1/13/12 3:30:02 PM] pool.ABCPool.co accepted block 627 from Cayman (#1)
[1/13/12 3:30:05 PM] pool.ABCPool.co accepted block 628 from Cayman (#1)
[1/13/12 3:30:10 PM] pool.ABCPool.co accepted block 629 from Cayman (#2)
[1/13/12 3:30:10 PM] pool.ABCPool.co accepted block 630 from Cayman (#2)
[1/13/12 3:30:19 PM] pool.ABCPool.co accepted block 631 from Cayman (#1)
[1/13/12 3:30:23 PM] pool.ABCPool.co accepted block 632 from Cayman (#1)
[1/13/12 3:30:24 PM] pool.ABCPool.co accepted block 633 from Cayman (#2)
[1/13/12 3:30:25 PM] pool.ABCPool.co accepted block 634 from Cayman (#2)
[1/13/12 3:30:29 PM] pool.ABCPool.co accepted block 635 from Cayman (#1)
[1/13/12 3:30:40 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
[1/13/12 3:30:52 PM] pool.ABCPool.co accepted block 636 from Cayman (#2)
[1/13/12 3:30:52 PM] pool.ABCPool.co accepted block 637 from Cayman (#2)
[1/13/12 3:30:55 PM] pool.ABCPool.co accepted block 638 from Cayman (#1)
[1/13/12 3:31:16 PM] pool.ABCPool.co accepted block 639 from Cayman (#1)
[1/13/12 3:31:29 PM] pool.ABCPool.co accepted block 640 from Cayman (#1)
[1/13/12 3:31:30 PM] pool.ABCPool.co accepted block 641 from Cayman (#2)
[1/13/12 3:31:41 PM] pool.ABCPool.co accepted block 642 from Cayman (#2)
[1/13/12 3:31:44 PM] pool.ABCPool.co accepted block 643 from Cayman (#2)
[1/13/12 3:31:51 PM] pool.ABCPool.co accepted block 644 from Cayman (#1)
[1/13/12 3:32:01 PM] pool.ABCPool.co accepted block 645 from Cayman (#2)
[1/13/12 3:32:05 PM] pool.ABCPool.co accepted block 646 from Cayman (#1)
[1/13/12 3:32:08 PM] pool.ABCPool.co accepted block 647 from Cayman (#2)
[1/13/12 3:32:15 PM] pool.ABCPool.co accepted block 648 from Cayman (#2)
[1/13/12 3:32:16 PM] pool.ABCPool.co accepted block 649 from Cayman (#1)
[1/13/12 3:32:21 PM] pool.ABCPool.co accepted block 650 from Cayman (#2)
[1/13/12 3:32:21 PM] pool.ABCPool.co accepted block 651 from Cayman (#1)
[1/13/12 3:32:22 PM] pool.ABCPool.co accepted block 652 from Cayman (#1)
[1/13/12 3:32:26 PM] pool.ABCPool.co accepted block 653 from Cayman (#2)
[1/13/12 3:32:39 PM] pool.ABCPool.co accepted block 654 from Cayman (#2)
[1/13/12 3:32:40 PM] pool.ABCPool.co accepted block 655 from Cayman (#2)
[1/13/12 3:32:41 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
[1/13/12 3:32:41 PM] pool.ABCPool.co accepted block 656 from Cayman (#2)
[1/13/12 3:32:51 PM] pool.ABCPool.co accepted block 657 from Cayman (#2)
[1/13/12 3:32:52 PM] pool.ABCPool.co accepted block 658 from Cayman (#1)
[1/13/12 3:33:05 PM] pool.ABCPool.co accepted block 659 from Cayman (#2)
[1/13/12 3:33:10 PM] pool.ABCPool.co accepted block 660 from Cayman (#1)
[1/13/12 3:33:18 PM] pool.ABCPool.co accepted block 661 from Cayman (#1)
[1/13/12 3:33:18 PM] pool.ABCPool.co accepted block 662 from Cayman (#1)
[1/13/12 3:33:18 PM] pool.ABCPool.co accepted block 663 from Cayman (#1)
[1/13/12 3:33:36 PM] pool.ABCPool.co accepted block 664 from Cayman (#2)
[1/13/12 3:33:47 PM] pool.ABCPool.co accepted block 665 from Cayman (#2)
[1/13/12 3:34:03 PM] pool.ABCPool.co accepted block 666 from Cayman (#1)
[1/13/12 3:34:12 PM] pool.ABCPool.co accepted block 667 from Cayman (#2)
[1/13/12 3:34:13 PM] pool.ABCPool.co accepted block 668 from Cayman (#1)
[1/13/12 3:34:13 PM] pool.ABCPool.co accepted block 669 from Cayman (#2)
[1/13/12 3:34:22 PM] pool.ABCPool.co accepted block 670 from Cayman (#1)
[1/13/12 3:34:31 PM] pool.ABCPool.co accepted block 671 from Cayman (#1)
2 x RAdeon HD6950 Linux Mint x64 Debian Edition
January 13, 2012, 02:59:12 PM
Well, I am getting that error like every minute. I have no idea if its hurting the production if at all. Is there a parameter to pass on to DiabloMiner to adjust this?
As far as i'm aware there's no parameter to hide the message in Diablominer. Why don't you PM me the log output and I'll take a look at it. Please also include your GPU/worker configuration. January 13, 2012, 02:51:11 PM
Well, I am getting that error like every minute. I have no idea if its hurting the production if at all. Is there a parameter to pass on to DiabloMiner to adjust this?
January 13, 2012, 01:17:01 PM
I am getting sporadic (about 1 out of 15 blocks) errors:
ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
I am directly connected to high bandwidth internet using DiabloMiner. What could be wrong?
Hi 99Percent,ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
I am directly connected to high bandwidth internet using DiabloMiner. What could be wrong?
That error message indicates that the long poll connection was terminated. ABCPool releases those connections on purpose for performance reasons.
The message should occur ca. every 10 minutes, and only when a new block was not found within that time. In those cases it is innocent and you may ignore it. Diablominer will immediately reconnect after the connection has been released.
hope this helps,
MC
January 13, 2012, 01:09:13 PM
I am getting sporadic (about 1 out of 15 blocks) errors:
ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
I am directly connected to high bandwidth internet using DiabloMiner. What could be wrong?
ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
I am directly connected to high bandwidth internet using DiabloMiner. What could be wrong?
January 13, 2012, 12:40:43 AM
n
Interesting theory!
Came across it today and felt it possibly related to wat was being mention above.
Interesting theory!
January 12, 2012, 09:04:10 PM
Interesting theory!
January 12, 2012, 06:06:04 PM
Transparency needed?/avoided?
https://bitcointalksearch.org/topic/m.658974
https://bitcointalksearch.org/topic/m.658974
January 12, 2012, 04:52:42 PM
With a 4% fee it would be in ABC's interest to atleast offer the same features that can be found at a 0% fee pool.
Features such as email and sms notifications of miner failure, payout, account changes, block being solved. Block stats can be found on nearly all mining pools.
Features such as email and sms notifications of miner failure, payout, account changes, block being solved. Block stats can be found on nearly all mining pools.
January 12, 2012, 12:12:25 PM
Assuming they're not doing anything underhanded (which I don't think they are, since, well, I get paid what I expect), the "allure" of "seeing the blocks you've found" is simply that: something to look at and "brag" about.
Kinda cool? Sure. What *MOST* people in a pure PPS pool are looking for? I sort of doubt it.
Kinda cool? Sure. What *MOST* people in a pure PPS pool are looking for? I sort of doubt it.
I think my key point is more about transparency then fun charts and graphs to look at. While abcpool.co is fairly stable, their lack of details regarding the pool doesn't inspire confidence. Nor does their new marketing strategy around their fees.
January 12, 2012, 10:57:36 AM
Assuming they're not doing anything underhanded (which I don't think they are, since, well, I get paid what I expect), the "allure" of "seeing the blocks you've found" is simply that: something to look at and "brag" about.
Kinda cool? Sure. What *MOST* people in a pure PPS pool are looking for? I sort of doubt it.
Kinda cool? Sure. What *MOST* people in a pure PPS pool are looking for? I sort of doubt it.
Jump to: