i have several workers at same & other add's but they are at different worker diff's which i normally see.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 172. (Read 2591920 times)
June 26, 2015, 10:11:11 PM
i'm seeing this, lots of blanks, the blank space are normally where it says new work for worker ! diff xxx share diff xxx & block value but in my case only 1 worker shows up n the rest are blank. getting shares though.
i have several workers at same & other add's but they are at different worker diff's which i normally see.
i have several workers at same & other add's but they are at different worker diff's which i normally see.
June 26, 2015, 09:30:05 PM
My man is back. Thx for update. Is that the same as the 3 files pushed recently at git?
There have been a lot of changes since 13.4, but the most important one is BIP66 compatibility, which was what the most recent changes consisted of. Most other things were minor internal cleanups, but a few external pull requests were merged that might be useful, namely midnightmagic's dynamic address cycling support.
By the way, I'm not sure if you're doing this, but don't just try to manually pull the changed files. Either use git and "git pull" or download a fresh tarball. Doing it manually is dangerous.
thx. looks like it's downloading shares, seems to be working. I'll let it run & see how it goes.
June 26, 2015, 09:15:29 PM
My man is back. Thx for update. Is that the same as the 3 files pushed recently at git?
There have been a lot of changes since 13.4, but the most important one is BIP66 compatibility, which was what the most recent changes consisted of. Most other things were minor internal cleanups, but a few external pull requests were merged that might be useful, namely midnightmagic's dynamic address cycling support.
By the way, I'm not sure if you're doing this, but don't just try to manually pull the changed files. Either use git and "git pull" or download a fresh tarball. Doing it manually is dangerous.
June 26, 2015, 09:05:23 PM
P2Pool release 14.0 - commit hash: f2660428263d4249d9b224b7f7260d8ff5da1e88
HARDFORK - Upgrade URGENTLY required in the next 24 hours.
Windows binary: http://u.forre.st/u/dosjhkch/p2pool_win32_14.0.zip
Windows binary signature: http://u.forre.st/u/mvuofxtx/p2pool_win32_14.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/14.0
Source tarball: https://github.com/forrestv/p2pool/tarball/14.0
Changes:
* BIP66/block version 3 compatibility
* Requires Bitcoin >=0.10.0 (due to BIP66 compatibility)
BIP66 will take effect in about 2.5 days and in order for P2Pool to continue working without producing blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP66 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.
So, please upgrade to 14.0 now and tell everyone else to also.
My man is back. Thx for update. Is that the same as the 3 files pushed recently at git?HARDFORK - Upgrade URGENTLY required in the next 24 hours.
Windows binary: http://u.forre.st/u/dosjhkch/p2pool_win32_14.0.zip
Windows binary signature: http://u.forre.st/u/mvuofxtx/p2pool_win32_14.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/14.0
Source tarball: https://github.com/forrestv/p2pool/tarball/14.0
Changes:
* BIP66/block version 3 compatibility
* Requires Bitcoin >=0.10.0 (due to BIP66 compatibility)
BIP66 will take effect in about 2.5 days and in order for P2Pool to continue working without producing blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP66 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.
So, please upgrade to 14.0 now and tell everyone else to also.
I'm seeing a bunch of errors ? it just keeps on scrolling . . .
2015-06-27 10:22:41.259000 > web_root.putChild('rate', WebInterface(lambda:
p2pool_data.get_pool_attempts_per_second(node.tracker, node.best_share_var.value
, decent_height())/(1-p2pool_data.get_average_stale_prop(node.tracker, node.best
_share_var.value, decent_height()))))
2015-06-27 10:22:41.259000 > File "R:\p2pool\forrestv-p2pool-fad1e1c\p2pool\da
ta.py", line 882, in get_pool_attempts_per_second
2015-06-27 10:22:41.259000 > assert dist >= 2
2015-06-27 10:22:41.259000 > exceptions.AssertionError:
2015-06-27 10:22:41.933000 > Error in DeferredResource handler:
2015-06-27 10:22:41.933000 > Traceback (most recent call last):
2015-06-27 10:22:41.933000 > File "R:\p2pool\forrestv-p2pool-fad1e1c\p2pool\ut
il\deferred_resource.py", line 24, in render
2015-06-27 10:22:41.933000 > defer.maybeDeferred(resource.Resource.render, s
elf, request).addCallbacks(finish, finish_error)
2015-06-27 10:22:41.933000 > File "C:\Python27\lib\site-packages\twisted\inter
net\defer.py", line 140, in maybeDeferred
2015-06-27 10:22:41.933000 > result = f(*args, **kw)
2015-06-27 10:22:41.934000 > File "C:\Python27\lib\site-packages\twisted\web\r
esource.py", line 250, in render
2015-06-27 10:22:41.934000 > return m(request)
2015-06-27 10:22:41.934000 > File "C:\Python27\lib\site-packages\twisted\inter
net\defer.py", line 1253, in unwindGenerator
2015-06-27 10:22:41.934000 > return _inlineCallbacks(None, gen, Deferred())
2015-06-27 10:22:41.934000 > ---
2015-06-27 10:22:41.934000 > File "C:\Python27\lib\site-packages\twisted\inter
net\defer.py", line 1107, in _inlineCallbacks
2015-06-27 10:22:41.934000 > result = g.send(result)
2015-06-27 10:22:41.934000 > File "R:\p2pool\forrestv-p2pool-fad1e1c\p2pool\we
b.py", line 198, in render_GET
2015-06-27 10:22:41.935000 > res = yield self.func(*self.args)
2015-06-27 10:22:41.935000 > File "R:\p2pool\forrestv-p2pool-fad1e1c\p2pool\we
b.py", line 203, in
2015-06-27 10:22:41.935000 > web_root.putChild('rate', WebInterface(lambda:
p2pool_data.get_pool_attempts_per_second(node.tracker, node.best_share_var.value
, decent_height())/(1-p2pool_data.get_average_stale_prop(node.tracker, node.best
_share_var.value, decent_height()))))
2015-06-27 10:22:41.935000 > File "R:\p2pool\forrestv-p2pool-fad1e1c\p2pool\da
ta.py", line 882, in get_pool_attempts_per_second
2015-06-27 10:22:41.935000 > assert dist >= 2
2015-06-27 10:22:41.935000 > exceptions.AssertionError:
June 26, 2015, 08:49:46 PM
P2Pool release 14.0 - commit hash: f2660428263d4249d9b224b7f7260d8ff5da1e88
HARDFORK - Upgrade URGENTLY required in the next 24 hours.
Windows binary: http://u.forre.st/u/dosjhkch/p2pool_win32_14.0.zip
Windows binary signature: http://u.forre.st/u/mvuofxtx/p2pool_win32_14.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/14.0
Source tarball: https://github.com/forrestv/p2pool/tarball/14.0
Changes:
* BIP66/block version 3 compatibility
* Requires Bitcoin >=0.10.0 (due to BIP66 compatibility)
BIP66 will take effect in about 2.5 days and in order for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP66 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.
So, please upgrade to 14.0 now and tell everyone else to also.
HARDFORK - Upgrade URGENTLY required in the next 24 hours.
Windows binary: http://u.forre.st/u/dosjhkch/p2pool_win32_14.0.zip
Windows binary signature: http://u.forre.st/u/mvuofxtx/p2pool_win32_14.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/14.0
Source tarball: https://github.com/forrestv/p2pool/tarball/14.0
Changes:
* BIP66/block version 3 compatibility
* Requires Bitcoin >=0.10.0 (due to BIP66 compatibility)
BIP66 will take effect in about 2.5 days and in order for P2Pool to continue working without producing invalid blocks, everyone needs to upgrade. At 50% of our hashrate upgrading, P2Pool instances will start displaying a warning saying that an upgrade is required. Reaching that point as quickly as possible is very important. And then, at 95%, users that have not upgraded will be excluded. If non-upgraded users aren't excluded before BIP66 takes effect, P2Pool users will be subject to paying other users for invalid work - effectively a withholding attack.
So, please upgrade to 14.0 now and tell everyone else to also.
June 26, 2015, 05:21:40 PM
Only forrestv can do it.
June 26, 2015, 02:38:14 PM
I saw this error on my node:
(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
(...)
Error messages on daemon indicates some problems on daemon, not P2Pool.(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
(...)
P2Pool is merely showing this in log.
daemon was ok, even after a restart msg was still there but after i restarted p2p then all is good.
June 26, 2015, 02:36:42 PM
I saw this error on my node:
(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
Edit: my node is 104.131.12.128:9332 if anyone wants to see the error...
Edit 2: here's the snippet from the p2pool log:
Here's what the bitcoin log shows:
Not a lot of help there...
From bitcoind:
Edit 3: and now it's gone. Last occurrence was:
(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
Edit: my node is 104.131.12.128:9332 if anyone wants to see the error...
Edit 2: here's the snippet from the p2pool log:
Code:
2015-06-26 09:58:14.329592 P2Pool: 17376 shares in chain (17380 verified/17380 total) Peers: 41 (34 incoming)
2015-06-26 09:58:14.329634 Local: 2680GH/s in last 10.0 minutes Local dead on arrival: ~6.4% (4-9%) Expected time to share: 1.4 hours
2015-06-26 09:58:14.329676 Shares: 1048 (85 orphan, 68 dead) Stale rate: ~14.6% (12-17%) Efficiency: ~96.1% (93-99%) Current payout: (0.0000)=0.0000 BTC
2015-06-26 09:58:14.329724 Pool: 1259TH/s Stale rate: 11.1% Expected time to block: 2.0 days
2015-06-26 09:58:15.623680 Peer sent entire transaction 1170fcf19ad833fb8f237004c0efc59e46697dab9b81850478d4fa6f8ae18575 that was already received
2015-06-26 09:58:16.125142 Peer sent entire transaction 0b7dbeb74599087db6b263919499c71cf05da374b7d809a47585ce2c5f4f0dd2 that was already received
2015-06-26 09:58:17.291632 Peer sent entire transaction ea49a8b720dd2b4eea58f9eaff5b58fd780f5375b6de3ed6e328557658ffc71b that was already received
2015-06-26 09:58:17.333289 > ########################################
2015-06-26 09:58:17.333419 > >>> Warning: (from bitcoind) EXCEPTION: St12out_of_range
2015-06-26 09:58:17.333473 > CInv::GetCommand() : type=513 unknown type
2015-06-26 09:58:17.333520 > bitcoin in ProcessMessages()
2015-06-26 09:58:17.333567 >
2015-06-26 09:58:17.333620 > ########################################
Here's what the bitcoin log shows:
Code:
2015-06-26 13:58:02 socket recv error Connection reset by peer (104)
2015-06-26 13:58:03 CreateNewBlock(): total size 749911
2015-06-26 13:58:21 CreateNewBlock(): total size 749862
2015-06-26 13:58:38 CreateNewBlock(): total size 749950
2015-06-26 13:58:38 receive version message: : version 40000, blocks=0, us=104.131.12.128:8333, peer=122431
2015-06-26 13:58:38 Added time data, samples 200, offset -40 (+0 minutes)
2015-06-26 13:58:55 CreateNewBlock(): total size 749874
Not a lot of help there...
From bitcoind:
Code:
miner@devildog:~/bitcoin-0.10.2/src$ ./bitcoin-cli getinfo
{
"version" : 100200,
"protocolversion" : 70002,
"blocks" : 362645,
"timeoffset" : 0,
"connections" : 97,
"proxy" : "",
"difficulty" : 49692386354.89383698,
"testnet" : false,
"relayfee" : 0.00001000,
"errors" : "EXCEPTION: St12out_of_range \nCInv::GetCommand() : type=513 unknown type \nbitcoin in ProcessMessages() \n"
}
Edit 3: and now it's gone. Last occurrence was:
Code:
2015-06-26 10:31:37.606884 > ########################################
2015-06-26 10:31:37.607046 > >>> Warning: (from bitcoind) EXCEPTION: St12out_of_range
2015-06-26 10:31:37.607101 > CInv::GetCommand() : type=513 unknown type
2015-06-26 10:31:37.607148 > bitcoin in ProcessMessages()
2015-06-26 10:31:37.607226 >
2015-06-26 10:31:37.607282 > ########################################
same here, saw that & i went to update the 2 files that was pushed out abt 14 hrs ago or so, restarted bitcoind & p2p then it's all good now.
June 26, 2015, 02:03:09 PM
June 26, 2015, 01:54:37 PM
I saw this error on my node:
(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
(...)
Error messages on daemon indicates some problems on daemon, not P2Pool.(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
(...)
P2Pool is merely showing this in log.
June 26, 2015, 01:28:23 PM
I saw this error on my node:
(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
(...)
Error messages on daemon indicates some problems on daemon, not P2Pool.(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
(...)
P2Pool is merely showing this in log.
June 26, 2015, 01:22:42 PM
how is the mining lately ?
i don't see too many blocks solved by p2pool but curious if many are mining ?
We're currently in a little streak of bad luck but the past few weeks leading up have been pretty good. Still, total luck has been around or over 100 for the past couple months. Seems we are hovering consistently between 260-280 miners for a while now, but there have been several new faces coming into the thread working on new nodes which has been good. i don't see too many blocks solved by p2pool but curious if many are mining ?
June 26, 2015, 11:17:30 AM
how is the mining lately ?
i don't see too many blocks solved by p2pool but curious if many are mining ?
i don't see too many blocks solved by p2pool but curious if many are mining ?
June 26, 2015, 08:50:55 AM
I saw this error on my node:
(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
Edit: my node is 104.131.12.128:9332 if anyone wants to see the error...
Edit 2: here's the snippet from the p2pool log:
Here's what the bitcoin log shows:
Not a lot of help there...
From bitcoind:
Edit 3: and now it's gone. Last occurrence was:
(from bitcoind) EXCEPTION: St12out_of_range CInv::GetCommand() : type=513 unknown type bitcoin in ProcessMessages()
First time I've seen this... Anyone have any ideas?
Edit: my node is 104.131.12.128:9332 if anyone wants to see the error...
Edit 2: here's the snippet from the p2pool log:
Code:
2015-06-26 09:58:14.329592 P2Pool: 17376 shares in chain (17380 verified/17380 total) Peers: 41 (34 incoming)
2015-06-26 09:58:14.329634 Local: 2680GH/s in last 10.0 minutes Local dead on arrival: ~6.4% (4-9%) Expected time to share: 1.4 hours
2015-06-26 09:58:14.329676 Shares: 1048 (85 orphan, 68 dead) Stale rate: ~14.6% (12-17%) Efficiency: ~96.1% (93-99%) Current payout: (0.0000)=0.0000 BTC
2015-06-26 09:58:14.329724 Pool: 1259TH/s Stale rate: 11.1% Expected time to block: 2.0 days
2015-06-26 09:58:15.623680 Peer sent entire transaction 1170fcf19ad833fb8f237004c0efc59e46697dab9b81850478d4fa6f8ae18575 that was already received
2015-06-26 09:58:16.125142 Peer sent entire transaction 0b7dbeb74599087db6b263919499c71cf05da374b7d809a47585ce2c5f4f0dd2 that was already received
2015-06-26 09:58:17.291632 Peer sent entire transaction ea49a8b720dd2b4eea58f9eaff5b58fd780f5375b6de3ed6e328557658ffc71b that was already received
2015-06-26 09:58:17.333289 > ########################################
2015-06-26 09:58:17.333419 > >>> Warning: (from bitcoind) EXCEPTION: St12out_of_range
2015-06-26 09:58:17.333473 > CInv::GetCommand() : type=513 unknown type
2015-06-26 09:58:17.333520 > bitcoin in ProcessMessages()
2015-06-26 09:58:17.333567 >
2015-06-26 09:58:17.333620 > ########################################
2015-06-26 09:58:14.329634 Local: 2680GH/s in last 10.0 minutes Local dead on arrival: ~6.4% (4-9%) Expected time to share: 1.4 hours
2015-06-26 09:58:14.329676 Shares: 1048 (85 orphan, 68 dead) Stale rate: ~14.6% (12-17%) Efficiency: ~96.1% (93-99%) Current payout: (0.0000)=0.0000 BTC
2015-06-26 09:58:14.329724 Pool: 1259TH/s Stale rate: 11.1% Expected time to block: 2.0 days
2015-06-26 09:58:15.623680 Peer sent entire transaction 1170fcf19ad833fb8f237004c0efc59e46697dab9b81850478d4fa6f8ae18575 that was already received
2015-06-26 09:58:16.125142 Peer sent entire transaction 0b7dbeb74599087db6b263919499c71cf05da374b7d809a47585ce2c5f4f0dd2 that was already received
2015-06-26 09:58:17.291632 Peer sent entire transaction ea49a8b720dd2b4eea58f9eaff5b58fd780f5375b6de3ed6e328557658ffc71b that was already received
2015-06-26 09:58:17.333289 > ########################################
2015-06-26 09:58:17.333419 > >>> Warning: (from bitcoind) EXCEPTION: St12out_of_range
2015-06-26 09:58:17.333473 > CInv::GetCommand() : type=513 unknown type
2015-06-26 09:58:17.333520 > bitcoin in ProcessMessages()
2015-06-26 09:58:17.333567 >
2015-06-26 09:58:17.333620 > ########################################
Here's what the bitcoin log shows:
Code:
2015-06-26 13:58:02 socket recv error Connection reset by peer (104)
2015-06-26 13:58:03 CreateNewBlock(): total size 749911
2015-06-26 13:58:21 CreateNewBlock(): total size 749862
2015-06-26 13:58:38 CreateNewBlock(): total size 749950
2015-06-26 13:58:38 receive version message: : version 40000, blocks=0, us=104.131.12.128:8333, peer=122431
2015-06-26 13:58:38 Added time data, samples 200, offset -40 (+0 minutes)
2015-06-26 13:58:55 CreateNewBlock(): total size 749874
2015-06-26 13:58:03 CreateNewBlock(): total size 749911
2015-06-26 13:58:21 CreateNewBlock(): total size 749862
2015-06-26 13:58:38 CreateNewBlock(): total size 749950
2015-06-26 13:58:38 receive version message: : version 40000, blocks=0, us=104.131.12.128:8333, peer=122431
2015-06-26 13:58:38 Added time data, samples 200, offset -40 (+0 minutes)
2015-06-26 13:58:55 CreateNewBlock(): total size 749874
Not a lot of help there...
From bitcoind:
Code:
miner@devildog:~/bitcoin-0.10.2/src$ ./bitcoin-cli getinfo
{
"version" : 100200,
"protocolversion" : 70002,
"blocks" : 362645,
"timeoffset" : 0,
"connections" : 97,
"proxy" : "",
"difficulty" : 49692386354.89383698,
"testnet" : false,
"relayfee" : 0.00001000,
"errors" : "EXCEPTION: St12out_of_range \nCInv::GetCommand() : type=513 unknown type \nbitcoin in ProcessMessages() \n"
}
{
"version" : 100200,
"protocolversion" : 70002,
"blocks" : 362645,
"timeoffset" : 0,
"connections" : 97,
"proxy" : "",
"difficulty" : 49692386354.89383698,
"testnet" : false,
"relayfee" : 0.00001000,
"errors" : "EXCEPTION: St12out_of_range \nCInv::GetCommand() : type=513 unknown type \nbitcoin in ProcessMessages() \n"
}
Edit 3: and now it's gone. Last occurrence was:
Code:
2015-06-26 10:31:37.606884 > ########################################
2015-06-26 10:31:37.607046 > >>> Warning: (from bitcoind) EXCEPTION: St12out_of_range
2015-06-26 10:31:37.607101 > CInv::GetCommand() : type=513 unknown type
2015-06-26 10:31:37.607148 > bitcoin in ProcessMessages()
2015-06-26 10:31:37.607226 >
2015-06-26 10:31:37.607282 > ########################################
2015-06-26 10:31:37.607046 > >>> Warning: (from bitcoind) EXCEPTION: St12out_of_range
2015-06-26 10:31:37.607101 > CInv::GetCommand() : type=513 unknown type
2015-06-26 10:31:37.607148 > bitcoin in ProcessMessages()
2015-06-26 10:31:37.607226 >
2015-06-26 10:31:37.607282 > ########################################
June 26, 2015, 06:16:23 AM
Is it possible to compile the newest updates to p2pool for windows? Is there a way i could do this myself? Any input would be appreciated.
Maybe this setup guide will help you out?
Thanks bro but i was looking on a how to to compile forestv github. I have p2pool running i just wanted to learn to compile the latest version.
For MS Windows, I'm thinking there should be a tool out there to do this for you man. I'm sorry I can't tell you what that is exactly >.>
June 26, 2015, 05:01:00 AM
Is it possible to compile the newest updates to p2pool for windows? Is there a way i could do this myself? Any input would be appreciated.
Maybe this setup guide will help you out?
Thanks bro but i was looking on a how to to compile forestv github. I have p2pool running i just wanted to learn to compile the latest version.
June 26, 2015, 02:27:28 AM
June 25, 2015, 05:30:01 PM
Is it possible to compile the newest updates to p2pool for windows? Is there a way i could do this myself? Any input would be appreciated.
Maybe this setup guide will help you out?
June 25, 2015, 06:56:04 AM
I did compile current git.
Look @ my OneDrive.
Thank you Look @ my OneDrive.
June 25, 2015, 05:12:43 AM
I did compile current git.
Look @ my OneDrive.
Look @ my OneDrive.
Jump to: