Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 641. (Read 2591920 times)
September 20, 2012, 10:06:31 AM
what version of bitcoin and p2pool are you running. There was a bug that caused this in an earlier version when bitcoind would stop responding to p2pool.
September 20, 2012, 09:18:51 AM
Hardware failure then. Overheating or something.
September 20, 2012, 08:50:13 AM
They are your miners?
one at local host (127.0.0.1) same PC as p2poolone at LAN same private IP net
one at WAN directed to assigned by router IP
Quote
okayIt looks like bad miner config for me
all config, all miners are identicalQuote
It may be also connections form far away and ping kill all joy.
LAN <1msWAN <10ms
no lost packets
September 20, 2012, 05:50:40 AM
They are your miners? It looks like bad miner config for me.
It may be also connections form far away and ping kill all joy.
It may be also connections form far away and ping kill all joy.
September 20, 2012, 02:44:13 AM
Could someone help me please with following problem?
LAN and WAN miners have problem with p2pool - some time after start mining (with <1% DOA) DOA is go to 100%.
local host miner working with no problem, <1% DOA
can you give me some ideas?
LAN and WAN miners have problem with p2pool - some time after start mining (with <1% DOA) DOA is go to 100%.
local host miner working with no problem, <1% DOA
can you give me some ideas?
September 19, 2012, 02:22:28 AM
What link?
I'm a windows guy.
https://github.com/forrestv/p2pool/zipball/master
That's what gave me 'forrestv-p2pool-4.0-0-g2adf77e.zip'
Now when I go there I get 'forrestv-p2pool-5.0-2-gb1e5a50'.
Upgrading...
M
https://bitcointalksearch.org/topic/m.231846
September 18, 2012, 04:14:07 PM
What link?
I'm a windows guy.
https://github.com/forrestv/p2pool/zipball/master
That's what gave me 'forrestv-p2pool-4.0-0-g2adf77e.zip'
Now when I go there I get 'forrestv-p2pool-5.0-2-gb1e5a50'.
Upgrading...
M
September 18, 2012, 01:29:32 PM
kjj: No, not really; you'll eventually start getting spammed warnings about needing to upgrade to v5 when 50% of everyone else upgrades to v5, but there's nothing essential there as long as you are actually running Bitcoin 0.7.0.
September 18, 2012, 12:36:26 PM
P2Pool release 5.0 tag: 5.0 hash: 11b050873e2a77869fdf4f86d2a9cb14e6dd2966
Windows binary: http://u.forre.st/u/tskucpih/p2pool_win32_5.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/5.0
Source tarball: https://github.com/forrestv/p2pool/tarball/5.0
Changes:
* This release requires users to upgrade to Bitcoin 0.7.0 in order to support BIP 0034 (block versioning). (It increments the share version to 5 in order to do this.)
* BIP 0022 (getblocktemplate) support
Sorry about the confusion with versions 4 and 5. Version 4 was the first to support BIP 0034 and getblocktemplate, but now version 5 requires a bitcoind that supports BIP 0034 (Bitcoin 0.7). Neither of those two versions were actual announced releases (until now).
Windows binary: http://u.forre.st/u/tskucpih/p2pool_win32_5.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/5.0
Source tarball: https://github.com/forrestv/p2pool/tarball/5.0
Changes:
* This release requires users to upgrade to Bitcoin 0.7.0 in order to support BIP 0034 (block versioning). (It increments the share version to 5 in order to do this.)
* BIP 0022 (getblocktemplate) support
Sorry about the confusion with versions 4 and 5. Version 4 was the first to support BIP 0034 and getblocktemplate, but now version 5 requires a bitcoind that supports BIP 0034 (Bitcoin 0.7). Neither of those two versions were actual announced releases (until now).
Doh! Is there any compelling need to switch to version 5 of p2pool? I just rolled out my stuff using version 4 and bitcoind-0.7.0 yesterday.
September 18, 2012, 11:09:28 AM
P2Pool release 5.0 tag: 5.0 hash: 11b050873e2a77869fdf4f86d2a9cb14e6dd2966
Windows binary: http://u.forre.st/u/tskucpih/p2pool_win32_5.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/5.0
Source tarball: https://github.com/forrestv/p2pool/tarball/5.0
Changes:
* This release requires users to upgrade to Bitcoin 0.7.0 in order to support BIP 0034 (block versioning). (It increments the share version to 5 in order to do this.)
* BIP 0022 (getblocktemplate) support
Sorry about the confusion with versions 4 and 5. Version 4 was the first to support BIP 0034 and getblocktemplate, but now version 5 requires a bitcoind that supports BIP 0034 (Bitcoin 0.7). Neither of those two versions were actual announced releases (until now).
Windows binary: http://u.forre.st/u/tskucpih/p2pool_win32_5.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/5.0
Source tarball: https://github.com/forrestv/p2pool/tarball/5.0
Changes:
* This release requires users to upgrade to Bitcoin 0.7.0 in order to support BIP 0034 (block versioning). (It increments the share version to 5 in order to do this.)
* BIP 0022 (getblocktemplate) support
Sorry about the confusion with versions 4 and 5. Version 4 was the first to support BIP 0034 and getblocktemplate, but now version 5 requires a bitcoind that supports BIP 0034 (Bitcoin 0.7). Neither of those two versions were actual announced releases (until now).
September 18, 2012, 07:19:32 AM
If I read all properly, the current share chain version (desired) is v4, p2pool version is v5.
Desired share chain v5 is testing version afik.
I have no idea, why forrestv jumped in p2pool version from v3 (chain v3) to v5 (chain v4).
Maybe share chain v4 is just test run for final v5?
Desired share chain v5 is testing version afik.
I have no idea, why forrestv jumped in p2pool version from v3 (chain v3) to v5 (chain v4).
Maybe share chain v4 is just test run for final v5?
As you can see from the OP, the current p2pool release is 3.1, with desired share version 3,
which is still the largest part in current p2pool network.
It is not compatible with Bitcoin v0.7.
The desired share version jumped from 3 to 4 about three weeks ago, and was tagged as p2pool version 4.0.
It is not announced (updated in OP) yet, but everyone pulled from the git repository in the past three weeks use this version,
with different further changes. It is the second largest part in current p2pool network.
It is compatible with Bitcoin v0.7.
September 18, 2012, 07:14:44 AM
An update to p2pool.info is uploading now that works with the final version of bitcoind 0.7. Note, as a side effect, I have stopped displaying subsidies. The new version of bitcoind makes is way to painful to look at the details of every transaction in a block (which is required for looking for subsidies), so I removed that functionality.
Since the age of regular subsidies appears to be long past, I guess that no one will care that this functionality is gone, but I thought I would mention it in case anyone noticed and wondered what was going on.
Since the age of regular subsidies appears to be long past, I guess that no one will care that this functionality is gone, but I thought I would mention it in case anyone noticed and wondered what was going on.
September 18, 2012, 06:47:54 AM
If I read all properly, the current share chain version (desired) is v4, p2pool version is v5.
Desired share chain v5 is testing version afik.
I have no idea, why forrestv jumped in p2pool version from v3 (chain v3) to v5 (chain v4).
Maybe share chain v4 is just test run for final v5?
Desired share chain v5 is testing version afik.
I have no idea, why forrestv jumped in p2pool version from v3 (chain v3) to v5 (chain v4).
Maybe share chain v4 is just test run for final v5?
September 18, 2012, 06:33:25 AM
Then it is all good. I menat v5 on stats page Not watching version number that it reports in log.
Not watching version number that it reports in log.oh, by "increasing v5" i meant the desired-versions-stats. my stats page and log still says 4.0-2-g11b0508.
What forrestv increased is desired share version,
which you can see the proportion in the "Desired versions" graph, or in a share you produced.
The version in the stats page is p2pool version.
September 18, 2012, 06:14:12 AM
Then it is all good. I menat v5 on stats page Not watching version number that it reports in log.
Not watching version number that it reports in log.oh, by "increasing v5" i meant the desired-versions-stats. my stats page and log still says 4.0-2-g11b0508.
September 18, 2012, 05:40:10 AM
did one more git pull 2 minutes ago, but it's saying "Already up-to-date.". my node still says Version: 4.0-2-g11b0508.
however, i can see v5 increasing in the stats.
btw, my bitcoind is showing version 70003, protocolversion 60002 and walletversion 60000.
Then it is all good. I menat v5 on stats page however, i can see v5 increasing in the stats.
btw, my bitcoind is showing version 70003, protocolversion 60002 and walletversion 60000.
Not watching version number that it reports in log. September 18, 2012, 04:49:47 AM
Odd, my node still sayin "5.0", git pulled today.
Anyway, complied last p2pool commit on win32 including LTC this time (finally get mingw working)
http://sdrv.ms/Swy8w9
If anyone intrested
Will compile win64 version later today.
Anyway, complied last p2pool commit on win32 including LTC this time (finally get mingw working)
http://sdrv.ms/Swy8w9
If anyone intrested
Will compile win64 version later today.
I pulled the latest via link and got forrestv-p2pool-4.0-0-g2adf77e.
M
Code:
git clone https://github.com/forrestv/p2pool.git
Then every week or soCode:
cd ~/p2pool
git pull
And your node is always up to date.git pull
did one more git pull 2 minutes ago, but it's saying "Already up-to-date.". my node still says Version: 4.0-2-g11b0508.
however, i can see v5 increasing in the stats.
btw, my bitcoind is showing version 70003, protocolversion 60002 and walletversion 60000.
September 18, 2012, 04:34:07 AM
Odd, my node still sayin "5.0", git pulled today.
Anyway, complied last p2pool commit on win32 including LTC this time (finally get mingw working)
http://sdrv.ms/Swy8w9
If anyone intrested
Will compile win64 version later today.
Anyway, complied last p2pool commit on win32 including LTC this time (finally get mingw working)
http://sdrv.ms/Swy8w9
If anyone intrested
Will compile win64 version later today.
I pulled the latest via link and got forrestv-p2pool-4.0-0-g2adf77e.
M
Code:
git clone https://github.com/forrestv/p2pool.git
Then every week or soCode:
cd ~/p2pool
git pull
And your node is always up to date.git pull
September 18, 2012, 04:26:00 AM
Code:
/home/xx/p2pool/p2pool/util/pack.py:186: DeprecationWarning: object.__new__() takes no parameters
return Type.__new__(cls, bits, endianness)
2012-09-18 10:23:49.927295 p2pool (version 4.0-2-g11b0508)
During every startup now. return Type.__new__(cls, bits, endianness)
2012-09-18 10:23:49.927295 p2pool (version 4.0-2-g11b0508)
September 18, 2012, 04:20:16 AM
Odd, my node still sayin "5.0", git pulled today.
Anyway, complied last p2pool commit on win32 including LTC this time (finally get mingw working)
http://sdrv.ms/Swy8w9
If anyone intrested
Will compile win64 version later today.
Anyway, complied last p2pool commit on win32 including LTC this time (finally get mingw working)
http://sdrv.ms/Swy8w9
If anyone intrested
Will compile win64 version later today.
I pulled the latest via link and got forrestv-p2pool-4.0-0-g2adf77e.
M
Jump to: