Search content
Sort by
Showing 6 of 6 results by leri4
Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
My NTP is working any ideas?
Try setting the clock in BIOS and system UTC + 0
Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
Node IP: whortonda.noip.me (default ports)
Connected to: ml.toom.im:9333
To connect to me: run_p2pool.py -n whortonda.noip.me:9333
CPU: Core i7-6800K @ 3.4GHz
RAM: 32GB
Pipe: 100m/20m cable
Using: Python 2.7 / Ubuntu
Node IP: 109.87.83.144 (default ports)
Connected to: 208.84.223.121:9335
To connect to me: run_p2pool.py -n 109.87.83.144:9333
CPU: i5 4690 3.5 GHz
RAM: 16GB
Pipe: 100m/100m cable
Using: Python 2.7 /PyPy 5.1.2/ Ubuntu
After syncing sharechain:
Code:
raise jsonrpc.Error_for_code(-12345)(u'p2pool is not connected to any peers')
Code:
2017-05-02 09:14:23.415915 P2Pool: 16885 shares in chain (8245 verified/16886 total) Peers: 3 (0 incoming)
2017-05-02 09:14:23.416102 Local: 10064GH/s in last 4.1 minutes Local dead on arrival: ~27.8% (12-51%) Expected time to share: 20.2 minutes
2017-05-02 09:14:23.416245 Shares: 1 (0 orphan, 1 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-81%) Current payout: (0.0000)=0.0000 BTC
2017-05-02 09:14:23.416403 Pool: 9005TH/s Stale rate: 0.8% Expected time to block: 2.9 days
2017-05-02 09:14:23.419608 Peer sent entire transaction b703f925cfeccb47fa4cd4957ebb8d8efb7fcac6d2a59ca58b69741dd7635b0d that was already received
2017-05-02 09:14:23.425375 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.425646 Transaction 3062050f02b1ec30d1a0f14e4fe539ae40917ed8f84f995184dda9e098c3d03d rescued from peer latency cache!
2017-05-02 09:14:23.427743 Peer sent entire transaction fcafe2636e858ae28bffd87102a54544ad4f2195fda2f75f95f0565a0d622ae5 that was already received
2017-05-02 09:14:23.436750 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.437028 Peer sent entire transaction a2bdb9f1f914e7ce2cc4c354f1ebb804832a269e9b4170d214b3dd9557a62a67 that was already received
2017-05-02 09:14:23.442954 Peer sent entire transaction 080667f400e06ddc8b24c1be9cc18c50e9ed07ff97f08a0edbe18aae809a30c8 that was already received
2017-05-02 09:14:23.450137 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.450335 Peer sent entire transaction ac171faed3f3d58b10ee64c87db758c393b65c877f783ac9eb6973fd6d446eea that was already received
2017-05-02 09:14:24.211989 Processing 32 shares from 74.66.86.127:9333...
2017-05-02 09:14:24.592938 ... done processing 32 shares. New: 32 Have: 16918/~17280
2017-05-02 09:14:24.593267 Requesting parent share 3c2dc9ea from 208.84.223.121:9335
2017-05-02 09:14:24.600174 GOT SHARE! 18gMRtpHR9iCQBHtJWyCktTYqrrTQ48RMT 5ae39c4e prev e9a5a8b5 age 50.06s
2017-05-02 09:14:24.612468 Warning: Previous share's timestamp is 3603 seconds old.
2017-05-02 09:14:24.612675 Make sure your system clock is accurate, and ensure that you're connected to decent peers.
2017-05-02 09:14:24.612826 If your clock is more than 300 seconds behind, it can result in orphaned shares.
2017-05-02 09:14:24.612970 (It's also possible that this share is just taking a long time to mine.)
2017-05-02 09:14:24.629463 Generating a share with 96944 bytes (3005 new) and 104 transactions (9 new)
2017-05-02 09:14:24.631907 New work for 18gMRtpHR9iCQBHtJWyCktTYqrrTQ48RMT! Diff: 32000.00 Share diff: 1744307.93 Block value: 12.81 BTC (104 tx, 97 kB)
2017-05-02 09:14:24.784342 Lost peer 74.66.86.127:9333 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:24.848019 Lost peer 208.84.223.121:9333 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:24.912460 Lost peer 208.84.223.121:9335 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:53.425500 P2Pool: 16918 shares in chain (8278 verified/16919 total) Peers: 0 (0 incoming)
2017-05-02 09:14:23.416102 Local: 10064GH/s in last 4.1 minutes Local dead on arrival: ~27.8% (12-51%) Expected time to share: 20.2 minutes
2017-05-02 09:14:23.416245 Shares: 1 (0 orphan, 1 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-81%) Current payout: (0.0000)=0.0000 BTC
2017-05-02 09:14:23.416403 Pool: 9005TH/s Stale rate: 0.8% Expected time to block: 2.9 days
2017-05-02 09:14:23.419608 Peer sent entire transaction b703f925cfeccb47fa4cd4957ebb8d8efb7fcac6d2a59ca58b69741dd7635b0d that was already received
2017-05-02 09:14:23.425375 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.425646 Transaction 3062050f02b1ec30d1a0f14e4fe539ae40917ed8f84f995184dda9e098c3d03d rescued from peer latency cache!
2017-05-02 09:14:23.427743 Peer sent entire transaction fcafe2636e858ae28bffd87102a54544ad4f2195fda2f75f95f0565a0d622ae5 that was already received
2017-05-02 09:14:23.436750 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.437028 Peer sent entire transaction a2bdb9f1f914e7ce2cc4c354f1ebb804832a269e9b4170d214b3dd9557a62a67 that was already received
2017-05-02 09:14:23.442954 Peer sent entire transaction 080667f400e06ddc8b24c1be9cc18c50e9ed07ff97f08a0edbe18aae809a30c8 that was already received
2017-05-02 09:14:23.450137 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.450335 Peer sent entire transaction ac171faed3f3d58b10ee64c87db758c393b65c877f783ac9eb6973fd6d446eea that was already received
2017-05-02 09:14:24.211989 Processing 32 shares from 74.66.86.127:9333...
2017-05-02 09:14:24.592938 ... done processing 32 shares. New: 32 Have: 16918/~17280
2017-05-02 09:14:24.593267 Requesting parent share 3c2dc9ea from 208.84.223.121:9335
2017-05-02 09:14:24.600174 GOT SHARE! 18gMRtpHR9iCQBHtJWyCktTYqrrTQ48RMT 5ae39c4e prev e9a5a8b5 age 50.06s
2017-05-02 09:14:24.612468 Warning: Previous share's timestamp is 3603 seconds old.
2017-05-02 09:14:24.612675 Make sure your system clock is accurate, and ensure that you're connected to decent peers.
2017-05-02 09:14:24.612826 If your clock is more than 300 seconds behind, it can result in orphaned shares.
2017-05-02 09:14:24.612970 (It's also possible that this share is just taking a long time to mine.)
2017-05-02 09:14:24.629463 Generating a share with 96944 bytes (3005 new) and 104 transactions (9 new)
2017-05-02 09:14:24.631907 New work for 18gMRtpHR9iCQBHtJWyCktTYqrrTQ48RMT! Diff: 32000.00 Share diff: 1744307.93 Block value: 12.81 BTC (104 tx, 97 kB)
2017-05-02 09:14:24.784342 Lost peer 74.66.86.127:9333 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:24.848019 Lost peer 208.84.223.121:9333 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:24.912460 Lost peer 208.84.223.121:9335 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:53.425500 P2Pool: 16918 shares in chain (8278 verified/16919 total) Peers: 0 (0 incoming)
Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
I already have a simple Debian based step-by-step that can be included if you want. I use it whenever I do a fresh install for my p2pool node. It includes installing all required packages, compiling bitcoind to include options for --disable-wallet and --without-gui, creating a bootstrap file the official way using linearize, creating a simple script for starting p2pool with options such as a manually specified payout address, and configuring some basic options for bitcoin.conf.
With regard to OS consideration, I have the following to say: CentOS... Meh, Ubuntu... Yuck, Windows... Crazy, and Debian... Winner!
With regard to OS consideration, I have the following to say: CentOS... Meh, Ubuntu... Yuck, Windows... Crazy, and Debian... Winner!
Also like Debian, but I could not adjust. Where can I see your instructions to try again.
Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
IMHO to help p2pool scale there should be one or several simple but useful HOWTOs on p2pool node deployment, and these HOWTOs should be constantly kept up-to-date by their maintainers. So every newcomer will be able to deploy a p2pool node completely by himself.
Just my two cents.
I completely agree, for example, it took me more than a month to configure the node.Just my two cents.
Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
I wanted to try to connect to your node http://ml.toom.im:9334/, but unfortunately for some reason it did not work.
If you want to view the stats, use http://. If you want to actually mine to it, you need to use stratum+tcp://ml.toom.im:9334. Does that help?Unfortunately not, if I connected the miner directly, there is no connection, but if I connect through the ckproxy, the miner is connected and after a minute goes into reboot, and so constantly. I see it in the first.
http://uploads.ru/w3xzr.jpg
Re: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
If you want to watch the mining on my new fork, the nodes running the new fork are these:
http://ml.toom.im:9332/
http://ml.toom.im:9334/
http://ml.toom.im:9336/
http://ml.toom.im:9332/
http://ml.toom.im:9334/
http://ml.toom.im:9336/
First of all, thank you very much for your work. I wanted to try to connect to your node http://ml.toom.im:9334/, but unfortunately for some reason it did not work. I will wait for the completed code.