Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 498. (Read 2591928 times)
August 06, 2013, 07:39:26 PM
At 800mhash, you should expect to find one share every 24hrs or so... then with a 1% fee, you'd expect to get credited with a share every 100 days
August 06, 2013, 07:16:43 PM
And your fee is by randomly taking shares, which might need more time to actually find one.
August 06, 2013, 07:12:38 PM
He's hitting it with about 800MH/s.
At the current difficulty, he's not hitting anything with 800MH/s. Hell, he's not even grazing it which should explain why his payout is zero. 
August 06, 2013, 07:07:50 PM
I'm not too concerned yet so I figured I would post here instead of making a new thread. I've finally gotten around to setting up my p2pool node again, this time in linux. Been running my SC (60GH/s) on it for a few days now and have a 1% fee.
So, as expected, I get the payout to my address that I choose with my SC and it takes off 1% and that payout goes to the default p2pool address. Everything's shiny, right?
Well, a bit over 24-hours ago, the payout to my default address suddenly went from something like 1.5mbtc to 0BTC and has stayed there ever since. The address I use with my SC is working fine - two payouts since. But zero payout for the default address. So the fee is not working? That doesn't seem to be the issue. 1 hour after the payout to default address dropped to 0BTC, my friend started mining at my pool. He's hitting it with about 800MH/s. It's been over 24 hours and two payouts later and his payout graph is still 0BTC and he's not received anything to his wallet. I threw my SC on his address an hour ago for about 60 seconds then took it off. It didn't change his payout from 0. His address doesn't show up under the active users section of p2pool.info at the moment.
I am using 13.2 on xubuntu in a VM with bitcoind on the same machine. Nice low getblock latency and my efficiency is over 100%. I've tried restarting both bitcoind and the p2pool node. No change.
If this doesn't change by tomorrow, I'm going to start worrying. What are your thoughts on this?
So, as expected, I get the payout to my address that I choose with my SC and it takes off 1% and that payout goes to the default p2pool address. Everything's shiny, right?
Well, a bit over 24-hours ago, the payout to my default address suddenly went from something like 1.5mbtc to 0BTC and has stayed there ever since. The address I use with my SC is working fine - two payouts since. But zero payout for the default address. So the fee is not working? That doesn't seem to be the issue. 1 hour after the payout to default address dropped to 0BTC, my friend started mining at my pool. He's hitting it with about 800MH/s. It's been over 24 hours and two payouts later and his payout graph is still 0BTC and he's not received anything to his wallet. I threw my SC on his address an hour ago for about 60 seconds then took it off. It didn't change his payout from 0. His address doesn't show up under the active users section of p2pool.info at the moment.
I am using 13.2 on xubuntu in a VM with bitcoind on the same machine. Nice low getblock latency and my efficiency is over 100%. I've tried restarting both bitcoind and the p2pool node. No change.
If this doesn't change by tomorrow, I'm going to start worrying. What are your thoughts on this?
August 05, 2013, 06:04:15 AM
Adding BTCMiners with a twist
Hostname: BTCMiners.net
Port: 9332
Username: BitcoinAddress+Difficulty (Difficulty is usually between 2 through 32)
Password: Anything
Our pool is a normal P2Pool node however we have a fun addition to it! Use your forum name as your username+difficulty, once a block is found and that address is paid out, you will be thrown into a lottery of other miners to win the POOL'S pot it made during it's last round. 100MH/s? 50GH/s? The more hashing we have the bigger the pot! If the pool wins the round share it is applied to the second bonus, the monthly round bonus!
In addition to the round share bonus, there will be a monthly bonus!
For each round share bonus you're entered into, you'll gain +1 extra entry per round share towards the monthly round bonus. The pool will keep 10% of the monthly round bonus to continue pool efforts.
also his fee is set to 2%, stay away as usual. run your own node...Hostname: BTCMiners.net
Port: 9332
Username: BitcoinAddress+Difficulty (Difficulty is usually between 2 through 32)
Password: Anything
Our pool is a normal P2Pool node however we have a fun addition to it! Use your forum name as your username+difficulty, once a block is found and that address is paid out, you will be thrown into a lottery of other miners to win the POOL'S pot it made during it's last round. 100MH/s? 50GH/s? The more hashing we have the bigger the pot! If the pool wins the round share it is applied to the second bonus, the monthly round bonus!
In addition to the round share bonus, there will be a monthly bonus!
For each round share bonus you're entered into, you'll gain +1 extra entry per round share towards the monthly round bonus. The pool will keep 10% of the monthly round bonus to continue pool efforts.
The 2% Fee is now taken away so that normal miners can mine free of charge.
Stay away? You have equal share to win the pot. But I suppose you're just into Bitcoins for the money to be made, not the fun to be had as well.
How would you pay people who use a username? Oh they only get the contest.
I'd message them via the forums for their BTC Address. Yes, if you mine at my pool you either get 98% of what you mine (2% goes to the pool's monthly pot for bonuses). Or you can join the round share drawing and be entered however many times you're in the drawings throughout the month for the end of month pot.
People with less than 25GH/s should enjoy this sort of thing. It's a HUGE possible payout depending on how many are mining. I know with a Jalapeno you're lucky to get a few bucks a day, why not try to double or triple the odds?
August 05, 2013, 01:46:44 AM
How would you pay people who use a username? Oh they only get the contest.
August 05, 2013, 01:19:15 AM
Adding BTCMiners with a twist
Hostname: BTCMiners.net
Port: 9332
Username: BitcoinAddress+Difficulty (Difficulty is usually between 2 through 32)
Password: Anything
Our pool is a normal P2Pool node however we have a fun addition to it! Use your forum name as your username+difficulty, once a block is found and that address is paid out, you will be thrown into a lottery of other miners to win the POOL'S pot it made during it's last round. 100MH/s? 50GH/s? The more hashing we have the bigger the pot! If the pool wins the round share it is applied to the second bonus, the monthly round bonus!
In addition to the round share bonus, there will be a monthly bonus!
For each round share bonus you're entered into, you'll gain +1 extra entry per round share towards the monthly round bonus. The pool will keep 10% of the monthly round bonus to continue pool efforts.
also his fee is set to 2%, stay away as usual. run your own node... Hostname: BTCMiners.net
Port: 9332
Username: BitcoinAddress+Difficulty (Difficulty is usually between 2 through 32)
Password: Anything
Our pool is a normal P2Pool node however we have a fun addition to it! Use your forum name as your username+difficulty, once a block is found and that address is paid out, you will be thrown into a lottery of other miners to win the POOL'S pot it made during it's last round. 100MH/s? 50GH/s? The more hashing we have the bigger the pot! If the pool wins the round share it is applied to the second bonus, the monthly round bonus!
In addition to the round share bonus, there will be a monthly bonus!
For each round share bonus you're entered into, you'll gain +1 extra entry per round share towards the monthly round bonus. The pool will keep 10% of the monthly round bonus to continue pool efforts.
August 04, 2013, 07:20:46 PM
Adding BTCMiners with a twist
Hostname: BTCMiners.net
Port: 9332
Username: BitcoinAddress+Difficulty (Difficulty is usually between 2 through 32)
Password: Anything
Our pool is a normal P2Pool node however we have a fun addition to it! Use your forum name as your username+difficulty, once a block is found and that address is paid out, you will be thrown into a lottery of other miners to win the POOL'S pot it made during it's last round. 100MH/s? 50GH/s? The more hashing we have the bigger the pot! If the pool wins the round share it is applied to the second bonus, the monthly round bonus! (The pool's 2% fee is included in the monthly round share to encourage use of the bonus program! )
In addition to the round share bonus, there will be a monthly bonus!
For each round share bonus you're entered into, you'll gain +1 extra entry per round share towards the monthly round bonus. The pool will keep 10% of the monthly round bonus to continue pool efforts.
Hostname: BTCMiners.net
Port: 9332
Username: BitcoinAddress+Difficulty (Difficulty is usually between 2 through 32)
Password: Anything
Our pool is a normal P2Pool node however we have a fun addition to it! Use your forum name as your username+difficulty, once a block is found and that address is paid out, you will be thrown into a lottery of other miners to win the POOL'S pot it made during it's last round. 100MH/s? 50GH/s? The more hashing we have the bigger the pot! If the pool wins the round share it is applied to the second bonus, the monthly round bonus! (The pool's 2% fee is included in the monthly round share to encourage use of the bonus program! )
In addition to the round share bonus, there will be a monthly bonus!
For each round share bonus you're entered into, you'll gain +1 extra entry per round share towards the monthly round bonus. The pool will keep 10% of the monthly round bonus to continue pool efforts.
August 02, 2013, 02:48:25 PM
Wouldn't an increase in dead shares from high bitcoind getblocktemplate latency only occur after a new block is found? (I guess the 'obvious' correlation being that if one of those dead shares is a block, then it'll probably be orphaned)
I'd think most dead share problems are latency related... some possibly from hardware (maybe a crappy switch, router, wireless extender, or something).. but I didn't get many dead shares at 185ms latency even with the 10s shares or w/e, so even less now. locally I'll get about 0.5% DOA, to server it's 2-4% (unless it's being DDoS'ed)
oh, i did a symlink to the log file again at nogleg.com/log, times are in US CST (UTC−05:00)... nothing private (like miner IPs) is shown there anyway. so if you ever wanted to see what the p2pool log looks like, there you go. it gets cleaned fairly often
I'd think most dead share problems are latency related... some possibly from hardware (maybe a crappy switch, router, wireless extender, or something).. but I didn't get many dead shares at 185ms latency even with the 10s shares or w/e, so even less now. locally I'll get about 0.5% DOA, to server it's 2-4% (unless it's being DDoS'ed)
oh, i did a symlink to the log file again at nogleg.com/log, times are in US CST (UTC−05:00)... nothing private (like miner IPs) is shown there anyway. so if you ever wanted to see what the p2pool log looks like, there you go. it gets cleaned fairly often
August 01, 2013, 08:07:46 AM
Win7 64, i5, 16GB, p2pool and bitcoind is running from ramdisk. At the moment I try to optimize bitcoind, the getblocktemplate latency is to high and thats why I have many Dead shares. But it looks better and better
I tried optimising mine, but ended up making it worse. Now I just have bitcoind affinity to one CPU with "Above Normal" priority, and run_p2pool.exe to the other core with same priority. Seems to be working OK considering it's a dual core 1.1GHz. No other tweaks, I removed the custom block size and min/max transmittal settings. Now it's up and down between 0.1 and 0.3s.
It's running on Windows 7 x64, 4GB RAM, 250GB Samsung 840 SSD.
I'm setting up another machine, which is an i3-2110 with 4GB RAM and 32GB SSD running Ubuntu 13.04, so I can return the Celeron to it's HTPC duties (it's in a fancy HTPC case).
August 01, 2013, 07:06:06 AM
If someone want to test p2pool with your ASIC befor making an own node, my public node is in my sig (100mbit)
Win7 64, i5, 16GB, p2pool and bitcoind is running from ramdisk. At the moment I try to optimize bitcoind, the getblocktemplate latency is to high and thats why I have many Dead shares. But it looks better and better
August 01, 2013, 05:55:26 AM
If someone want to test p2pool with your ASIC befor making an own node, my public node is in my sig (100mbit)
Your little node is pretty impressive - those Avalons are certainly quick. What are you running your node on?
My node is at http://847pool.no-ip.biz:9332/static/ - much less impressive, though it is only running on a Celeron 847 machine, and I only have a few GPUs and 3 Block Erupters mining.
August 01, 2013, 02:46:49 AM
You need to run a proxy on STRATUM p2pool LTC
No you don't.
To connect with the striatum is not possible.
Yes, it is.
August 01, 2013, 01:41:28 AM
You need to run a proxy on STRATUM p2pool LTC, tell me what to do. That's after the launch.
To connect with the striatum is not possible.
To connect with the striatum is not possible.
Quote
python mining_proxy.py --pow-algo scrypt --host 127.0.0.1 --port 9327 --stratum-port 3333 --getwork-port 9999 --no-midstate --real-target --custom-user pool --custom-password x --verbose
2013-07-31 21:44:08,350 DEBUG stats logger.get_logger # Logging initialized
2013-07-31 21:44:08,360 DEBUG protocol logger.get_logger # Logging initialized
2013-07-31 21:44:08,360 DEBUG socket_transport logger.get_logger # Logging initialized
2013-07-31 21:44:08,415 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,415 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,433 WARNING proxy jobs. # C extension for midstate not available. Using default implementation instead.
2013-07-31 21:44:08,433 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,434 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,435 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,435 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,436 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,436 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,438 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
File "mining_proxy.py", line 155, in main
new_host = (yield utils.detect_stratum(args.host, args.port))
AttributeError: 'module' object has no attribute '_parse'
2013-07-31 21:44:08,439 INFO proxy mining_proxy.main # Stratum proxy version: 1.3.0
2013-07-31 21:44:08,439 INFO proxy mining_proxy.main # Trying to connect to Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:08,440 INFO proxy mining_proxy.main # Setting PoW algo: scrypt
2013-07-31 21:44:08,441 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-31 21:44:08,441 DEBUG protocol protocol.connectionMade # Connected 127.0.0.1
2013-07-31 21:44:08,441 DEBUG protocol protocol.connectionMade # Resuming connection: []
2013-07-31 21:44:08,441 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:08,441 INFO proxy mining_proxy.on_connect # Authorizing custom user pool, password x
2013-07-31 21:44:08,442 DEBUG protocol protocol.writeJsonRequest # < {"params": ["pool", "x"], "id": 1, "method": "mining.authorize"}
2013-07-31 21:44:08,442 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-31 21:44:08,442 DEBUG protocol protocol.writeJsonRequest # < {"params": [], "id": 2, "method": "mining.subscribe"}
2013-07-31 21:44:08,461 DEBUG protocol protocol.lineReceived # > {u'result': None, u'jsonrpc': u'2.0', u'id': 1, u'error': None}
2013-07-31 21:44:08,461 DEBUG protocol protocol.lineReceived # > {u'result': [[u'mining.notify', u'ae6812eb4cd7735a302a8a9dd95cf71f'], u'', 2], u'jsonrpc': u'2.0', u'id': 2, u'error': None}
2013-07-31 21:44:08,464 INFO proxy mining_proxy.main # -----------------------------------------------------------------------
2013-07-31 21:44:08,464 INFO proxy mining_proxy.main # PROXY IS LISTENING ON ALL IPs ON PORT 3333 (stratum) AND 9999 (getwork)
2013-07-31 21:44:08,464 INFO proxy mining_proxy.main # -----------------------------------------------------------------------
2013-07-31 21:44:08,465 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'params': [14.52613027417101], u'method': u'mining.set_difficulty', u'id': 940918514}
2013-07-31 21:44:08,465 INFO proxy client_service.handle_event # Setting new difficulty: 14.5261302742
2013-07-31 21:44:08,465 DEBUG protocol protocol.writeJsonResponse # < {"error": null, "id": 940918514, "result": null}
/usr/lib/python2.6/site-packages/stratum-0.2.13-py2.6.egg/stratum/protocol.py:201: DeprecationWarning: Returning a value other than None from stratum.protocol.ClientProtocol.dataReceived is deprecated since Twisted 11.0.0.
return self.lineLengthExceeded(self._buffer)
2013-07-31 21:44:08,489 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:08,489 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-31 21:44:08,489 DEBUG socket_transport socket_transport.clientConnectionLost # [Failure instance: Traceback (failure with no frames): : Connection to the other side was lost in a non-clean fashion.
]
2013-07-31 21:44:11,332 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-31 21:44:11,332 DEBUG protocol protocol.connectionMade # Connected 127.0.0.1
2013-07-31 21:44:11,332 DEBUG protocol protocol.connectionMade # Resuming connection: []
2013-07-31 21:44:11,332 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:11,333 INFO proxy mining_proxy.on_connect # Authorizing custom user pool, password x
2013-07-31 21:44:11,333 DEBUG protocol protocol.writeJsonRequest # < {"params": ["pool", "x"], "id": 1, "method": "mining.authorize"}
2013-07-31 21:44:11,333 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-31 21:44:11,333 DEBUG protocol protocol.writeJsonRequest # < {"params": [], "id": 2, "method": "mining.subscribe"}
2013-07-31 21:44:11,337 DEBUG protocol protocol.lineReceived # > {u'result': None, u'jsonrpc': u'2.0', u'id': 1, u'error': None}
2013-07-31 21:44:11,338 DEBUG protocol protocol.lineReceived # > {u'result': [[u'mining.notify', u'ae6812eb4cd7735a302a8a9dd95cf71f'], u'', 2], u'jsonrpc': u'2.0', u'id': 2, u'error': None}
2013-07-31 21:44:11,338 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'params': [14.52613027417101], u'method': u'mining.set_difficulty', u'id': 512789334}
2013-07-31 21:44:11,339 INFO proxy client_service.handle_event # Setting new difficulty: 14.5261302742
2013-07-31 21:44:11,339 DEBUG protocol protocol.writeJsonResponse # < {"error": null, "id": 512789334, "result": null}
2013-07-31 21:44:11,340 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:11,340 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-31 21:44:11,340 DEBUG socket_transport socket_transport.clientConnectionLost # [Failure instance: Traceback (failure with no frames): : Connection to the other side was lost in a non-clean fashion.
2013-07-31 21:44:08,350 DEBUG stats logger.get_logger # Logging initialized
2013-07-31 21:44:08,360 DEBUG protocol logger.get_logger # Logging initialized
2013-07-31 21:44:08,360 DEBUG socket_transport logger.get_logger # Logging initialized
2013-07-31 21:44:08,415 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,415 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,433 WARNING proxy jobs. # C extension for midstate not available. Using default implementation instead.
2013-07-31 21:44:08,433 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,434 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,435 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,435 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,436 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,436 DEBUG proxy logger.get_logger # Logging initialized
2013-07-31 21:44:08,438 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
File "mining_proxy.py", line 155, in main
new_host = (yield utils.detect_stratum(args.host, args.port))
AttributeError: 'module' object has no attribute '_parse'
2013-07-31 21:44:08,439 INFO proxy mining_proxy.main # Stratum proxy version: 1.3.0
2013-07-31 21:44:08,439 INFO proxy mining_proxy.main # Trying to connect to Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:08,440 INFO proxy mining_proxy.main # Setting PoW algo: scrypt
2013-07-31 21:44:08,441 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-31 21:44:08,441 DEBUG protocol protocol.connectionMade # Connected 127.0.0.1
2013-07-31 21:44:08,441 DEBUG protocol protocol.connectionMade # Resuming connection: []
2013-07-31 21:44:08,441 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:08,441 INFO proxy mining_proxy.on_connect # Authorizing custom user pool, password x
2013-07-31 21:44:08,442 DEBUG protocol protocol.writeJsonRequest # < {"params": ["pool", "x"], "id": 1, "method": "mining.authorize"}
2013-07-31 21:44:08,442 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-31 21:44:08,442 DEBUG protocol protocol.writeJsonRequest # < {"params": [], "id": 2, "method": "mining.subscribe"}
2013-07-31 21:44:08,461 DEBUG protocol protocol.lineReceived # > {u'result': None, u'jsonrpc': u'2.0', u'id': 1, u'error': None}
2013-07-31 21:44:08,461 DEBUG protocol protocol.lineReceived # > {u'result': [[u'mining.notify', u'ae6812eb4cd7735a302a8a9dd95cf71f'], u'', 2], u'jsonrpc': u'2.0', u'id': 2, u'error': None}
2013-07-31 21:44:08,464 INFO proxy mining_proxy.main # -----------------------------------------------------------------------
2013-07-31 21:44:08,464 INFO proxy mining_proxy.main # PROXY IS LISTENING ON ALL IPs ON PORT 3333 (stratum) AND 9999 (getwork)
2013-07-31 21:44:08,464 INFO proxy mining_proxy.main # -----------------------------------------------------------------------
2013-07-31 21:44:08,465 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'params': [14.52613027417101], u'method': u'mining.set_difficulty', u'id': 940918514}
2013-07-31 21:44:08,465 INFO proxy client_service.handle_event # Setting new difficulty: 14.5261302742
2013-07-31 21:44:08,465 DEBUG protocol protocol.writeJsonResponse # < {"error": null, "id": 940918514, "result": null}
/usr/lib/python2.6/site-packages/stratum-0.2.13-py2.6.egg/stratum/protocol.py:201: DeprecationWarning: Returning a value other than None from stratum.protocol.ClientProtocol.dataReceived is deprecated since Twisted 11.0.0.
return self.lineLengthExceeded(self._buffer)
2013-07-31 21:44:08,489 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:08,489 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-31 21:44:08,489 DEBUG socket_transport socket_transport.clientConnectionLost # [Failure instance: Traceback (failure with no frames): : Connection to the other side was lost in a non-clean fashion.
]
2013-07-31 21:44:11,332 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-31 21:44:11,332 DEBUG protocol protocol.connectionMade # Connected 127.0.0.1
2013-07-31 21:44:11,332 DEBUG protocol protocol.connectionMade # Resuming connection: []
2013-07-31 21:44:11,332 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:11,333 INFO proxy mining_proxy.on_connect # Authorizing custom user pool, password x
2013-07-31 21:44:11,333 DEBUG protocol protocol.writeJsonRequest # < {"params": ["pool", "x"], "id": 1, "method": "mining.authorize"}
2013-07-31 21:44:11,333 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-31 21:44:11,333 DEBUG protocol protocol.writeJsonRequest # < {"params": [], "id": 2, "method": "mining.subscribe"}
2013-07-31 21:44:11,337 DEBUG protocol protocol.lineReceived # > {u'result': None, u'jsonrpc': u'2.0', u'id': 1, u'error': None}
2013-07-31 21:44:11,338 DEBUG protocol protocol.lineReceived # > {u'result': [[u'mining.notify', u'ae6812eb4cd7735a302a8a9dd95cf71f'], u'', 2], u'jsonrpc': u'2.0', u'id': 2, u'error': None}
2013-07-31 21:44:11,338 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'params': [14.52613027417101], u'method': u'mining.set_difficulty', u'id': 512789334}
2013-07-31 21:44:11,339 INFO proxy client_service.handle_event # Setting new difficulty: 14.5261302742
2013-07-31 21:44:11,339 DEBUG protocol protocol.writeJsonResponse # < {"error": null, "id": 512789334, "result": null}
2013-07-31 21:44:11,340 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at 127.0.0.1:9327
2013-07-31 21:44:11,340 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-31 21:44:11,340 DEBUG socket_transport socket_transport.clientConnectionLost # [Failure instance: Traceback (failure with no frames): : Connection to the other side was lost in a non-clean fashion.
Is it ok to run cgminer using the --balance command with P2Pool + one non p2pool?
Trying to even out payouts a little more using this method, but it looks like P2Pool may be large enough to get rid of that serious variance here soon
I wouldn't recommend it; p2pool basically uses its own separate block chain for shares. According to the third line in the cgminer readme:Trying to even out payouts a little more using this method, but it looks like P2Pool may be large enough to get rid of that serious variance here soon
Quote
Do not use on multiple block chains at the same time!
Is it ok to run cgminer using the --balance command with P2Pool + one non p2pool?
Trying to even out payouts a little more using this method, but it looks like P2Pool may be large enough to get rid of that serious variance here soon
Trying to even out payouts a little more using this method, but it looks like P2Pool may be large enough to get rid of that serious variance here soon
Wow, 3.75 TH/s at the moment. Good job p2pool!
yeah, i like that too, thats because of 13.2 which is fully ASIC combatible. I hope everyone is running p2pool with a minimum of --give-author 0.1, Better 0.5! Forrest did a good job with version 13.2!I run 2 Avalons on my public node very stable. ava.0 is a original batch#2 which is restarting from time to time but without huge hashrate impact and ava.1 is simply connected to a notebook.
If someone want to test p2pool with your ASIC befor making an own node, my public node is in my sig (100mbit)
Wow, 3.75 TH/s at the moment. Good job p2pool!
someone decided to DDoS my server, so my 3ghash mining operation was offline for a few minutes, before redirecting to another pool
the network is saved
the network is saved
We nailed the problem. 
We are prepping a completely virtual environment that will allow us to spin up multiple loadbalanced p2p nodes depending on load.
The problem was caused by virtual clock drift. The system time was drifting approximately 5 minutes every hour which caused an automatic re sync of the time. The time re sync appeared as a total drop in the charts when actually no drops were occurring. We have corrected the time drift issue and are no longer seeing the drops.
Thanks for all your suggestions.
EMBTCII
We are prepping a completely virtual environment that will allow us to spin up multiple loadbalanced p2p nodes depending on load.
The problem was caused by virtual clock drift. The system time was drifting approximately 5 minutes every hour which caused an automatic re sync of the time. The time re sync appeared as a total drop in the charts when actually no drops were occurring. We have corrected the time drift issue and are no longer seeing the drops.
Thanks for all your suggestions.
EMBTCII
Jump to: