[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 52.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: leri4 on May 01, 2017, 06:32:41 PM

After syncing sharechain:

Code:

 raise jsonrpc.Error_for_code(-12345)(u'p2pool is not connected to any peers')

Looking at my logs, I see a bunch of messages like these:

Code:

2017-05-01 20:55:07.290038 Incoming connection from peer 109.87.83.144:49400 established. p2pool version: 3200 '15.0-41-g1f5448b-dirty'
2017-05-01 21:41:39.181375 Bad peer banned: ('109.87.83.144', 49400)
2017-05-01 21:41:39.182193 Lost peer 109.87.83.144:49400 - Connection was aborted locally, using.
2017-05-01 22:42:15.000639 Incoming connection from peer 109.87.83.144:52714 established. p2pool version: 3200 '15.0-41-g1f5448b-dirty'
2017-05-01 22:45:07.558142 Lost peer 109.87.83.144:52714 - Connection was closed cleanly.
2017-05-01 23:06:50.094427 Incoming connection from peer 109.87.83.144:53776 established. p2pool version: 3200 '16.0-4-gde1be30-dirty'
2017-05-01 23:06:50.945576 Sending 361 shares to 109.87.83.144:53776
2017-05-01 23:06:55.109767 Sending 124 shares to 109.87.83.144:53776
2017-05-01 23:07:07.602339 Sending 459 shares to 109.87.83.144:53776
2017-05-01 23:07:21.591850 Sending 104 shares to 109.87.83.144:53776
2017-05-01 23:07:24.495455 Sending 147 shares to 109.87.83.144:53776
2017-05-01 23:07:34.857315 Sending 223 shares to 109.87.83.144:53776
2017-05-01 23:07:39.886468 Sending 220 shares to 109.87.83.144:53776
2017-05-01 23:08:16.104214 Sending 396 shares to 109.87.83.144:53776
2017-05-01 23:08:40.337457 Sending 51 shares to 109.87.83.144:53776
2017-05-01 23:09:30.850726 Sending 409 shares to 109.87.83.144:53776
2017-05-01 23:10:06.623567 Sending 264 shares to 109.87.83.144:53776
2017-05-01 23:10:33.138572 Sending 453 shares to 109.87.83.144:53776
2017-05-01 23:11:06.481957 Sending 253 shares to 109.87.83.144:53776
2017-05-01 23:11:44.957750 Sending 297 shares to 109.87.83.144:53776
2017-05-01 23:12:01.389848 Sending 270 shares to 109.87.83.144:53776
2017-05-01 23:12:10.298115 Sending 64 shares to 109.87.83.144:53776
2017-05-01 23:12:26.135477 Sending 3 shares to 109.87.83.144:53776
2017-05-01 23:12:26.986912 Sending 227 shares to 109.87.83.144:53776
2017-05-01 23:12:36.100733 Sending 294 shares to 109.87.83.144:53776
2017-05-01 23:13:18.806125 Sending 329 shares to 109.87.83.144:53776
2017-05-01 23:13:33.780652 Sending 333 shares to 109.87.83.144:53776
2017-05-01 23:14:24.745534 Bad peer banned: ('109.87.83.144', 53776)
2017-05-01 23:14:24.746185 Lost peer 109.87.83.144:53776 - Connection was aborted locally, using.
2017-05-02 08:06:50.092776 Incoming connection from peer 109.87.83.144:37942 established. p2pool version: 3200 '16.0-4-gde1be30-dirty'
2017-05-02 08:06:53.226807 Sending 183 shares to 109.87.83.144:37942
2017-05-02 08:06:56.293072 Sending 281 shares to 109.87.83.144:37942
2017-05-02 08:07:04.028620 Sending 369 shares to 109.87.83.144:37942
2017-05-02 08:07:07.735216 Sending 482 shares to 109.87.83.144:37942
2017-05-02 08:07:10.878189 Sending 95 shares to 109.87.83.144:37942
2017-05-02 08:07:16.028535 Sending 164 shares to 109.87.83.144:37942

I'm looking into the cause. I'll probably add some debugging messages to the code running on my nodes to give more information on why my nodes are banning yours. I'm going to need to go offline in a bit, so I might not get it ready tonight. Can you PM me your email address or send an email to "j AT toom PERIOD im" so I can let you know when I have new code running and when you should try to reconnect?

sawa, same for you: send me an email with your full logs? The "Missing ... for broadcast" messages are some new messages that I added while figuring out the transaction broadcast bug mentioned here. This message still gets printed out sometimes when a node just starts up, but probably is not related to the problem that's preventing your node from staying connected. I'm not seeing any "Bad peer banned" messages when grepping my logs for your IP address, but maybe your node is banning me?

sawa

legendary

Activity: 1308

Merit: 1011

Quote from: jtoomim on May 02, 2017, 05:06:29 PM

If anyone is planning on running a stable, long-term node on my fork, please let me know your IP and I'll include it as a seed.

I'm thinking of starting a long-term node crypto.office-on-the.net
P2P_PORT = 9335
WORKER_PORT = 9334

But there is a problem. After some time there is such error:

Code:

2017-05-03 04:20:25.016218 Missing 28 of 1074 transactions for broadcast
2017-05-03 04:20:25.016333 Scheduling another broadcast attempt in 8 seconds
2017-05-03 04:20:25.019103 Missing 28 of 1074 transactions for broadcast
2017-05-03 04:20:25.019200 Scheduling another broadcast attempt in 8 seconds
2017-05-03 04:20:25.021319 Missing 28 of 1074 transactions for broadcast
2017-05-03 04:20:25.021428 Scheduling another broadcast attempt in 8 seconds
2017-05-03 04:20:25.023668 Missing 28 of 1074 transactions for broadcast
2017-05-03 04:20:25.023775 Scheduling another broadcast attempt in 8 seconds

And the node stops accepting work.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: windpath on May 02, 2017, 09:48:30 AM

Quote from: tubexc on May 02, 2017, 09:39:53 AM

What is jtoomim fork Hashrate Roll Eyes

Where can i find it Huh

http://ml.toom.im:9334/static/

Actually, http://ml.toom.im:9332 is a better choice. The :9334 node has more different users on it right now so it's running a bit more slowly at handing out new work.

The current hashrate on the fork is around 7 PH/s. Of that, around 1.2 PH/s is from my facility, and will be on 24/7 as baseline hashrate. A lot of the rest is currently rented hashrate, and will be coming and going depending on the Nicehash rental rates.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: tubexc on May 02, 2017, 01:39:17 PM

I think if there are no issues with invalid shares in the new version one should do a progressive migration to this new version and not a split Roll Eyes

When I created the new share chain, I mined for several days in a fashion that would have paid out everybody on the mainnet sharechain had a block been found. I think it's fair for the inverse when people migrate to my share chain. Edit: It's also fair because after you switch, the mainnet chain will continue mining based on your shares for a while, ramping down at the same rate that jtoomimfork ramps up.

~~Note that the old mainnet p2pool's hashrate has fallen significantly, and will experience far fewer blocks than my fork will. My fork is still in the late testing stages, though.~~ No, it hasn't. It looks like hashrate was added to the new fork, not moved from the old fork. My mistake.

I will release code soon-ish that will automatically find a few peers (using DNS seeds) to make it easier to join my fork. However, I want to do some performance testing with an artificially linked node graph/chain, so it will probably be a couple days before that is out. If anyone is planning on running a stable, long-term node on my fork, please let me know your IP and I'll include it as a seed.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: kavjlaeg on May 02, 2017, 04:02:32 PM

I strictly ask do fork on port 9334.

I do not support this. The :9334 node is just ONE of the three nodes I run. ml.toom.im:9332 and ml.toom.im:9336 are also on the fork. We are only using 9334 for that node because we have one global IP and multiple nodes on our LAN.

Nodes on the old share chain and the new share chain will refuse to connect to each other. I made sure of this in the code and tested it several times.

You can identify whether a node is running my code by looking at the protocol version that the node reports (≥3200 for my fork, 1600 or 1700 for the forrestv fork), or by looking at the share versions on the chain (16/17 for forrestv, ≥32 for jtoomim).

kavjlaeg

newbie

Activity: 66

Merit: 0

Global pool rate: 7.12 PH/s (DOA 392.59 TH/s / 5.51%)

tubexc

hero member

Activity: 496

Merit: 500

Quote from: kavjlaeg on May 02, 2017, 04:02:32 PM

Please.
I strictly ask do fork on port 9334.

ps
classic port=9332
fork port =9334

Who want's to mine on a forked node with only 200TH/s and not in the main p2pool sharechain Huh

kavjlaeg

newbie

Activity: 66

Merit: 0

Please.
I strictly ask do fork on port 9334.

ps
classic port=9332
fork port =9334

tubexc

hero member

Activity: 496

Merit: 500

I think if there are no issues with invalid shares in the new version one should do a progressive migration to this new version and not a split Roll Eyes

kavjlaeg

newbie

Activity: 66

Merit: 0

Hello, add p2p node

classic p2pool http://low-doa.mine.nu:9332/static/
hardforked p2pool http://low-doa.mine.nu:9334/static/

Location Russia, Moscow city, installed and configured by sawa.

------------------
CPU: i7 7700k 4.2 GHz
RAM: 16GB DDR4
HDD: 2x PCI-E NVMe SSD
Pipe: 50m/50m optic cable

tubexc

hero member

Activity: 496

Merit: 500

Ha Ok thanks windpath
It's a 1.43885715 BTC taxes block Grin

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: tubexc on May 02, 2017, 09:39:53 AM

Quote from: whortonda on May 02, 2017, 08:40:42 AM

jtoomim fork found a block: https://blockchain.info/block/00000000000000000218556606adced3948eccd7703411117304211f7ed83fe3
998kB / 13.93885715 BTC

Yay!

What is jtoomim fork Hashrate Roll Eyes

Where can i find it Huh

http://ml.toom.im:9334/static/

tubexc

hero member

Activity: 496

Merit: 500

Quote from: whortonda on May 02, 2017, 08:40:42 AM

jtoomim fork found a block: https://blockchain.info/block/00000000000000000218556606adced3948eccd7703411117304211f7ed83fe3
998kB / 13.93885715 BTC

Yay!

What is jtoomim fork Hashrate Roll Eyes

Where can i find it Huh

whortonda

newbie

Activity: 24

Merit: 0

jtoomim fork found a block: https://blockchain.info/block/00000000000000000218556606adced3948eccd7703411117304211f7ed83fe3
998kB / 13.93885715 BTC

Yay!

windpath

legendary

Activity: 1258

Merit: 1027

When advertising nodes I think it's very important to differentiate between what share chain you are running on very clearly.

The two I am currently aware of are

- MainNet
- Jtoomim fork

The two share chains are not compatible with each other, so if you explicitly set a -n to an incompatible node you will not submit valid work...

If both share chains survive for a while I will update p2pool.org to track stats for both, currently it's only for MainNet (the long standing main implemtation by Forrest).

leri4

newbie

Activity: 6

Merit: 0

Quote from: whortonda on May 01, 2017, 02:53:56 PM

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)

whortonda

newbie

Activity: 24

Merit: 0

Greetings p2poolers,

I'm the owner of the "1Hinen" address. I began renting hashpower to mine on p2pool about a month ago and noticed the smaller block sizes, and came across the discussion here after some Googling on the subject.

@jtoomim, I have switched my node to your fork. I just finished downloading the sharechain and it looks like everything is working well. You can expect anywhere from 0-10Ph of rented hashpower from me depending on rental prices.

Please let me know if I can do anything else to help you test your fork (or if I'm doing anything that's not helpful). Thank you for your work on this. Looking forward to finding a fat 1MB block with you.

--Darren

----------------------------------------------------------------------------------

Node: whortonda.noip.me
Worker port: 3000
P2P port: 9333
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 16.04 LTS

I am using a non-standard miner port to avoid conflict with litecoind.
Anyone is welcome to mine to my node, but I can't guarantee 100% stability.

windpath

legendary

Activity: 1258

Merit: 1027

Your both absolutely right! Will edit now so it's correct, was on my cell phone and could not search the source so went from memory (or lack there of...)

in2tactics

hero member

Activity: 578

Merit: 501

Personally speaking, I have always found the "+" option to be the most useful as it forces p2pool to give a miner the specified work difficulty.

frodocooper

sr. member

Activity: 351

Merit: 410

Quote from: windpath on April 29, 2017, 10:37:32 AM

...

There are 2 other difficulty settings configurable by the miner:

Share difficulty: sets the actual difficulty for a miners shares. This was implemented for large miners who wanted to set share difficulty HIGHER than P2Pools actual difficulty. If set to lower than share difficulty it is ignored. It is set by adding a "+" to the end of your address followed by the difficulty number.

Sudo share difficulty: sets a sudo difficulty so your miners will submit work more often than they would at the actual difficulty. This is useful to smooth out your hash rate graph on the node. It is set by adding a "/" at the end of the miner address followed by the desired sudo difficulty.

You can set both or either one.

Regardless of your settings shares will only be accepted if they meet the minimum P2Pool difficulty.

Hmm, I was under the impression that it was the other way around, i.e.:
- adding a "/" followed by the desired difficulty level to the end of the Bitcoin address would tell the miner to submit only shares above the stated "/" difficulty level, and
- adding a "+" to the end of the Bitcoin address tells the P2Pool node to always give the miner work with the stated "+" difficulty level.

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 52. (Read 2591916 times)