Author

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

legendary
Activity: 2212
Merit: 1038
Hi tnx ppl for fast response but this problem is not because
Quote
--max-conns 8 --outgoing-conns 4
It is the same without it. Also reset does not help. This must be something else related to this specific coin because I have no problems running other coins p2pool.
Also p2protocol version changed to
Quote
VERSION = 1004
Because that's what getinfo reports


Oh, that's p2pools max connections, way to make me look foolish. Grin Your bitcoind must have its connections limited in a similar fashion.

Delete 'maxconnections=8' from bitcoin.conf or increase the number of allowable connections.



If that doesn't work then it's proof positive that I am in fact a fool.
hero member
Activity: 561
Merit: 500
kittehcoin.info
Hi tnx ppl for fast response but this problem is not because
Quote
--max-conns 8 --outgoing-conns 4
It is the same without it. Also reset does not help. This must be something else related to this specific coin because I have no problems running other coins p2pool.
Also p2protocol version changed to
Quote
VERSION = 1004
Because that's what getinfo reports
sr. member
Activity: 266
Merit: 250
Or just restart your coin daemon - p2pool will then kick in  Wink
legendary
Activity: 2212
Merit: 1038
I was building p2pool for joincoin.
https://github.com/joincoin/joincoin
Quote
from p2pool.bitcoin import networks

PARENT = networks.nets['joincoin']
SHARE_PERIOD = 5 # seconds
CHAIN_LENGTH = 24*60*60//10 # shares
REAL_CHAIN_LENGTH = 24*60*60//10 # shares
TARGET_LOOKBEHIND = 200 # shares
SPREAD = 50 # blocks
IDENTIFIER = '27392307bca64c44'.decode('hex')
PREFIX = '27392307bca64c44'.decode('hex')
P2P_PORT = 9050
MIN_TARGET = 0
MAX_TARGET = 2**256//2**20 - 1
PERSIST = False
WORKER_PORT = 9241
BOOTSTRAP_ADDRS = '194.135.90.171 194.135.92.4 194.135.94.113'.split(' ')
ANNOUNCE_CHANNEL = '#p2pool-alt'
VERSION_CHECK = lambda v: True
VERSION_WARNING = lambda v: None

Quote
import os
import platform

from twisted.internet import defer

from .. import data, helper
from p2pool.util import pack


P2P_PREFIX = 'f1b4dc9e'.decode('hex') #pchmessagestart
P2P_PORT = 17941
ADDRESS_VERSION = 43 #pubkey_address
RPC_PORT = 17942
RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'joincoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        ))

SUBSIDY_FUNC = lambda height: 2*100000000
POW_FUNC = lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data))
BLOCK_PERIOD = 45 # s
SYMBOL = 'J'
CONF_FILE_FUNC = lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'joincoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/joincoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.joincoin'), 'joincoin.conf')
BLOCK_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/block/'
ADDRESS_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/address/'
TX_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/tx/'
SANE_TARGET_RANGE = (2**256//1000000000 - 1, 2**256//1000 - 1)
DUMB_SCRYPT_DIFF = 2**16
DUST_THRESHOLD = 0.03e8

Quote
server=1
listen=1
daemon=1
rpcuser=majsta
rpcpassword=x

rpcallowip=*
rpcallowip=127.0.0.1
rpcallowip=192.168.1.99
rpcallowip=192.168.1.103
rpcallowip=192.168.1.104
rpcallowip=192.168.1.105

rpcport=17942
port=17941
rpcconnect=*
rpcconnect=127.0.0.1
rpcconnect=192.168.1.99
rpcconnect=192.168.1.103
rpcconnect=192.168.1.104
rpcconnect=192.168.1.105
algo=scrypt


addnode=24.38.16.6
addnode=194.135.90.171
addnode=194.135.92.4
addnode=194.135.94.113
addnode=gdhtrc7qoh3qowvf.onion:17941
addnode=jsghu6d5lop757ml.onion:17941
addnode=iamzedqd6kmzi3qs.onion:17941
addnode=nwjw2badoulwc4yi.onion:17941
addnode=7wc53o5c3ox62azh.onion:17941
addnode=53zy47p5wly5penk.onion:17941
addnode=5k7xsbnnw3mpotx6.onion:17941
addnode=b2mgu5dvcw3m7cxw.onion:17941


Does anyone have ideas what is going on?

You've limited your connections to 8 and like the message says all slots are being used. Either remove '--max-conns 8' and '--outgoing-conns 4' or increase the number of connections you're allowing.
hero member
Activity: 561
Merit: 500
kittehcoin.info
I was building p2pool for joincoin.
https://github.com/joincoin/joincoin
Quote
from p2pool.bitcoin import networks

PARENT = networks.nets['joincoin']
SHARE_PERIOD = 5 # seconds
CHAIN_LENGTH = 24*60*60//10 # shares
REAL_CHAIN_LENGTH = 24*60*60//10 # shares
TARGET_LOOKBEHIND = 200 # shares
SPREAD = 50 # blocks
IDENTIFIER = '27392307bca64c44'.decode('hex')
PREFIX = '27392307bca64c44'.decode('hex')
P2P_PORT = 9050
MIN_TARGET = 0
MAX_TARGET = 2**256//2**20 - 1
PERSIST = False
WORKER_PORT = 9241
BOOTSTRAP_ADDRS = '194.135.90.171 194.135.92.4 194.135.94.113'.split(' ')
ANNOUNCE_CHANNEL = '#p2pool-alt'
VERSION_CHECK = lambda v: True
VERSION_WARNING = lambda v: None

Quote
import os
import platform

from twisted.internet import defer

from .. import data, helper
from p2pool.util import pack


P2P_PREFIX = 'f1b4dc9e'.decode('hex') #pchmessagestart
P2P_PORT = 17941
ADDRESS_VERSION = 43 #pubkey_address
RPC_PORT = 17942
RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'joincoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        ))

SUBSIDY_FUNC = lambda height: 2*100000000
POW_FUNC = lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data))
BLOCK_PERIOD = 45 # s
SYMBOL = 'J'
CONF_FILE_FUNC = lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'joincoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/joincoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.joincoin'), 'joincoin.conf')
BLOCK_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/block/'
ADDRESS_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/address/'
TX_EXPLORER_URL_PREFIX = 'http://cryptexplorer.com/tx/'
SANE_TARGET_RANGE = (2**256//1000000000 - 1, 2**256//1000 - 1)
DUMB_SCRYPT_DIFF = 2**16
DUST_THRESHOLD = 0.03e8

Quote
server=1
listen=1
daemon=1
rpcuser=majsta
rpcpassword=x

rpcallowip=*
rpcallowip=127.0.0.1
rpcallowip=192.168.1.99
rpcallowip=192.168.1.103
rpcallowip=192.168.1.104
rpcallowip=192.168.1.105

rpcport=17942
port=17941
rpcconnect=*
rpcconnect=127.0.0.1
rpcconnect=192.168.1.99
rpcconnect=192.168.1.103
rpcconnect=192.168.1.104
rpcconnect=192.168.1.105
algo=scrypt


addnode=24.38.16.6
addnode=194.135.90.171
addnode=194.135.92.4
addnode=194.135.94.113
addnode=gdhtrc7qoh3qowvf.onion:17941
addnode=jsghu6d5lop757ml.onion:17941
addnode=iamzedqd6kmzi3qs.onion:17941
addnode=nwjw2badoulwc4yi.onion:17941
addnode=7wc53o5c3ox62azh.onion:17941
addnode=53zy47p5wly5penk.onion:17941
addnode=5k7xsbnnw3mpotx6.onion:17941
addnode=b2mgu5dvcw3m7cxw.onion:17941


Does anyone have ideas what is going on?
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
No problem.  I just happened to check the blocks and saw that was orphaned... and I was like, "Huh?  I swear I got BTC for that... let me check."
legendary
Activity: 1258
Merit: 1027
Not sure why your front-end is doing this windpath, but it's showing the latest block found by p2pool as orphaned:

https://i.imgur.com/HMCWsis.png

That block wasn't orphaned...

It's fixed now, thanks. It happens when I restart bitcoin and leave the node running, forgot to correct it yesterday Smiley
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Not sure why your front-end is doing this windpath, but it's showing the latest block found by p2pool as orphaned:



That block wasn't orphaned...
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
It's transaction related.
full member
Activity: 175
Merit: 100
Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
Bull.
You can do same adding
timeout=150
BUT it will NOT give you better GBT.

Hey I've been trying to optimize my bitcoind for p2pool any tips. As to settings, what kind of peers I should allow, where to find those peers, etc.
What do you think about his I been banning rbf peers kind of an actives activity.
https://www.mail-archive.com/[email protected]/msg08422.html
Like that you represent in your tag name!

I update my P2P to version 14.0-9 and bitcoin to v0.11 and my GBT is now <1s as it was before the change from v13 to v14. I have not blocked any peers as the application seems to be doing it's job since now after the initial P2P v14 was not able to block v13 peers (thanks forrestv). My GBT had been at >3s before this last update. Can't say this is a coincident or not just providing my status.
full member
Activity: 213
Merit: 100
How do you figure your sharechain was corrupted?

I'm not sure, I can only put it down to the bad peers, which I've now blocked - no problems since  Smiley

Ok so i started to block peers who are not up to date and now i am seeing a spam request of parent share over and over which will not go away.
full member
Activity: 213
Merit: 100
Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
Bull.
You can do same adding
timeout=150
BUT it will NOT give you better GBT.

Hey I've been trying to optimize my bitcoind for p2pool any tips. As to settings, what kind of peers I should allow, where to find those peers, etc.
What do you think about his I been banning rbf peers kind of an actives activity.
https://www.mail-archive.com/[email protected]/msg08422.html
Like that you represent in your tag name!
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
Bull.
You can do same adding
timeout=150
BUT it will NOT give you better GBT.
sr. member
Activity: 266
Merit: 250
How do you figure your sharechain was corrupted?

I'm not sure, I can only put it down to the bad peers, which I've now blocked - no problems since  Smiley
full member
Activity: 213
Merit: 100
yes, mainly because of a corrupted share chain (of P2Pool).
verified share can't rease, too ... in this case of many disconnected clients.

i must have deleted 3 times (in 1 week) the sharechain of P2Pool to have a standard P2Pool reaction.

probably the old v13 that it tries to inject shares ... again.

I too experienced a corrupted p2pool sharechain & had to delete/redownload a new one a few days ago. It seems like p2pool is not fully banning older v13 releases, which seems to be causing the problem. Since I started proactively banning bad peers manually the problems have all but gone, but having to constantly monitor my logs for repeat offending IP's is a real bind & very laborious.
Also, looking around the various p2pool node finder sites, there's still a multitude of v13 nodes still mining away regardless - which makes me wonder if these nodes are actually still getting paid, as there have been zero complaints here about unpaid blocks. If these outdated nodes are still getting paid, that would mean that their owners are still blissfully unaware of any required upgrade & would also explain why there are still so many older nodes humming away......

How do you figure your sharechain was corrupted?
Mine seems to be kicking peers very often. Could that traffic just be rerouted to a dead zone where we dont have to worry about them affecting the majority who actually try to keep things up to date. It also ends up sending them a share before it kicks them could that be slowing the network down.

Just in case someone wants to block these peers manually i do this on windows.
https://serverfault.com/questions/117420/windows-firewall-ip-ban
full member
Activity: 238
Merit: 100
Howto get latency of bitcoin-qt low? I am just now around 0.5s

Install bitcoin v0.11. Add to your bitcoin.conf:

maxconnections=10

then run bitcoin-qt and look connections in debug witdow. Choose IPs with lowest latencies and add them to your bitcoin.conf. Add there not more then 4 the best.

addnode=x.x.x.x
newbie
Activity: 3
Merit: 0
Hey, can anybody recommend some good nodes to use for Nicehash (Amsterdam) and Westhash (San Jose)? I'm ready to drop some rental hash on it, when the price is right.

i'm also running a node in germany; https://pascal-schwarz.ch/p2pool-node-status/
sr. member
Activity: 266
Merit: 250
yes, mainly because of a corrupted share chain (of P2Pool).
verified share can't rease, too ... in this case of many disconnected clients.

i must have deleted 3 times (in 1 week) the sharechain of P2Pool to have a standard P2Pool reaction.

probably the old v13 that it tries to inject shares ... again.

I too experienced a corrupted p2pool sharechain & had to delete/redownload a new one a few days ago. It seems like p2pool is not fully banning older v13 releases, which seems to be causing the problem. Since I started proactively banning bad peers manually the problems have all but gone, but having to constantly monitor my logs for repeat offending IP's is a real bind & very laborious.
Also, looking around the various p2pool node finder sites, there's still a multitude of v13 nodes still mining away regardless - which makes me wonder if these nodes are actually still getting paid, as there have been zero complaints here about unpaid blocks. If these outdated nodes are still getting paid, that would mean that their owners are still blissfully unaware of any required upgrade & would also explain why there are still so many older nodes humming away......
legendary
Activity: 1512
Merit: 1012
yes, mainly because of a corrupted share chain (of P2Pool).
verified share can't rease, too ... in this case of many disconnected clients.

i must have deleted 3 times (in 1 week) the sharechain of P2Pool to have a standard P2Pool reaction.

probably the old v13 that it tries to inject shares ... again.
sr. member
Activity: 266
Merit: 250
I heard blocking peers can effect your bitcoin node in a weird way. If you are using    -addnode or -connect try using defualts and see if that fixes it.Depending on your peers take off firewall as well.

Where did you hear this - can you provide a link? I've never had any issues.....


Bitcoin Core 0.11.0 released

I will not have time to test it today, but it looks like there are a lot of speed improvements for the mempool that should speed up GBT latency.

https://bitcoin.org/en/release/v0.11.0

Would be interested in hearing anybody's experience Smiley

Been running this version since it was released, so far it's proven very stable with no disconnects - although I do have quite a few bad peers blocked, weather this has something to do with it I'm not sure, but generally I'm very happy with how it performs.

EDIT: Although I am having trouble with the relaynetworkclient disconnecting - anyone else having this problem?
Jump to: