Greetings - we have revived p2pool-maza.
We have posted our p2pool modifications here on bitbin
Our announcement in the maza thread is here on BCT
peers may connect to: p2pool.maza.club:14476 or p2pool-2.maza.club:14476
The network seems to be working well, but we would like to see some additional peers to ensure the sharechain is working well for everyone. Our antminer S1 units are performing well on this network.
ShastaFarEye Prospectors maintain 2 nodes through our mazaclub, and we have one additional peer. We will post the full code fork on github shortly.
We have even noted an ad from our other peer on the network here on BCT
We invite Treasure Quarry to connect to the network and reopen a node. We'd be stoked to see you back on mazacoin!
Do not hesitate to contact [email protected] if you need assistance - mazaclub is committed to the success of p2pool-maza! Maza Means Money!
Topic: Mazacoin p2pool closed. (Read 3239 times)
I really want to see P2Pool get MZC going. I'm using 11.4. I am not willing to change my software version right now. Not being stubborn, it just took so ling to get running stable I dont want to risk it.
Is there some setting somewhere that will keep my server from banning yours for that lame reason? Like a whitelist?
Add my server to your bootstrap
mining.pool2p.com
Also, anyone else making a mazacoin node do the same.
I've added your server to the bootstrap line and given the pool a quick restart but still not connecting to you. Can I just check, did you mean to say you are not using 11.4 or you are using 11.4? Is there some setting somewhere that will keep my server from banning yours for that lame reason? Like a whitelist?
Add my server to your bootstrap
mining.pool2p.com
Also, anyone else making a mazacoin node do the same.
Quote
If we connect up together then we can hopefully get that "Expected time to block" down to nice levels.
I am putting some hashing power into MZC now, join in, hope to see some coin!I have ONE simple question.
I pointed my single erupter here and now when we hit a block the payout has me at 300+ coin payout.
Along with the rest of the miners here too.
How are you going to meet those payouts?
Just wondering,, I really like P2P pools and want to support but this basic issue bothers me.
I pointed my single erupter here and now when we hit a block the payout has me at 300+ coin payout.
Along with the rest of the miners here too.
How are you going to meet those payouts?
Just wondering,, I really like P2P pools and want to support but this basic issue bothers me.
Whatever your payout is supposed to be based on the shares you have submitted, you'll get it in the coinbase generation section of the block itself. The pool doesn't pay you anything directly, your payment will be built into the block itself.
I have ONE simple question.
I pointed my single erupter here and now when we hit a block the payout has me at 300+ coin payout.
Along with the rest of the miners here too.
How are you going to meet those payouts?
Just wondering,, I really like P2P pools and want to support but this basic issue bothers me.
I pointed my single erupter here and now when we hit a block the payout has me at 300+ coin payout.
Along with the rest of the miners here too.
How are you going to meet those payouts?
Just wondering,, I really like P2P pools and want to support but this basic issue bothers me.
I really want to see P2Pool get MZC going. I'm using 11.4. I am not willing to change my software version right now. Not being stubborn, it just took so ling to get running stable I dont want to risk it.
Is there some setting somewhere that will keep my server from banning yours for that lame reason? Like a whitelist?
Add my server to your bootstrap
mining.pool2p.com
Also, anyone else making a mazacoin node do the same.
Is there some setting somewhere that will keep my server from banning yours for that lame reason? Like a whitelist?
Add my server to your bootstrap
mining.pool2p.com
Also, anyone else making a mazacoin node do the same.
Quote
If we connect up together then we can hopefully get that "Expected time to block" down to nice levels.
I am putting some hashing power into MZC now, join in, hope to see some coin!
There hasn't been much hashing at the pool which is why the expected time to block is so long at the moment.
I think that the peer too old message is probably because I'm using p2pool version 11.4-31 . The latest p2pool wasn't changing its share difficulty for some reason when the hashrate increased, so I changed things back to reliable old 11.4-31 (which has also served me well for most of my other p2pools).
I've updated my March 6th post with the version number . You can download p2pool 11.4 from https://github.com/forrestv/p2pool/releases/tag/11.4 which will probably work in connecting up with mine. If we connect up together then we can hopefully get that "Expected time to block" down to nice levels.
I think that the peer too old message is probably because I'm using p2pool version 11.4-31 . The latest p2pool wasn't changing its share difficulty for some reason when the hashrate increased, so I changed things back to reliable old 11.4-31 (which has also served me well for most of my other p2pools).
I've updated my March 6th post with the version number . You can download p2pool 11.4 from https://github.com/forrestv/p2pool/releases/tag/11.4 which will probably work in connecting up with mine. If we connect up together then we can hopefully get that "Expected time to block" down to nice levels.
I set up MZC on my p2pool server and at first I connected to you but after a while I got this...
So I went from one connection to zero, is that because of the version of p2pool you are using?
Also, why is the expected time to block nearly infinity? I believe that may discourage others from joining in. Your thoughts?
Code:
2014-04-01 06:58:18.347000 Peer 198.105.222.218:43423 misbehaving, will drop and ban. Reason: peer too old
So I went from one connection to zero, is that because of the version of p2pool you are using?
Also, why is the expected time to block nearly infinity? I believe that may discourage others from joining in. Your thoughts?
sorry but you lost any cred with me now supporting this scam coin.
Share difficulty was getting stuck at a low value on p2pool version 13.4, resulting in lots of DOAs so I've gone back to an old faithful version of p2pool - version 11.4.31. Share difficulty is now adapting nicely to increases or decreases in hashrate. Yay!
I'd like to mine p2pool but it looks like this is the only functioning node right now, and I don't have enough hashpower to hope to find a block any time in the near future. Jumping back on the pool I was on before but will come back if there are some more nodes up and running soon...
I'm using version 13.4-16-g5ee3172-dirty from https://github.com/forrestv/p2pool .
I don't think the bad peer banned lines should cause any trouble. It seems a bit odd that 54.201.164.152:35163 is connecting though as I would have expected connected peers to have port 14476
You're connecting to me which is good ( 198.105.222.218:14476 )
Unfortunately you don't seem to be picking up the shares from me though
The only time I've known something like this there was something in the other person's sharechain which prevented the pickup of the sharechain from me (something like a fork in the p2pool sharechain).
Can you try stopping p2pool then deleting your /data/mazacoin directory (this will delete the 2 shares in your sharechain) then starting p2pool again.
I don't think the bad peer banned lines should cause any trouble. It seems a bit odd that 54.201.164.152:35163 is connecting though as I would have expected connected peers to have port 14476
You're connecting to me which is good ( 198.105.222.218:14476 )
Unfortunately you don't seem to be picking up the shares from me though
The only time I've known something like this there was something in the other person's sharechain which prevented the pickup of the sharechain from me (something like a fork in the p2pool sharechain).
Can you try stopping p2pool then deleting your /data/mazacoin directory (this will delete the 2 shares in your sharechain) then starting p2pool again.
I restarted and here is the log:
I will try re-cloning the p2pool from github. Which repository are you using?
Code:
2014-03-11 19:24:14.227041 p2pool (version 13.3-247-g2ffa4af-dirty)
2014-03-11 19:24:14.227174
2014-03-11 19:24:14.227276 Testing bitcoind RPC connection to 'http://127.0.0.1:12832/' with username 'mazacoinrpc'...
2014-03-11 19:24:14.252417 ...success!
2014-03-11 19:24:14.252619 Current block hash: 9fcae840d5a59552e97d1633764888dd7a83976a373c58d375
2014-03-11 19:24:14.252753 Current block height: 23771
2014-03-11 19:24:14.252869
2014-03-11 19:24:14.252969 Testing bitcoind P2P connection to '127.0.0.1:12835'...
2014-03-11 19:24:14.356868 ...success!
2014-03-11 19:24:14.357020
2014-03-11 19:24:14.357094 Determining payout address...
2014-03-11 19:24:14.419560 Loaded cached address: MC6zvyNdZ9qVbCQ3tUGDM8DHvU7aKyG3Hg...
2014-03-11 19:24:14.424291 ...success! Payout address: MC6zvyNdZ9qVbCQ3tUGDM8DHvU7aKyG3Hg
2014-03-11 19:24:14.424418
2014-03-11 19:24:14.424504 Loading shares...
2014-03-11 19:24:14.428802 ...done loading 2 shares (2 verified)!
2014-03-11 19:24:14.428915
2014-03-11 19:24:14.429002 Initializing work...
2014-03-11 19:24:14.463648 ...success!
2014-03-11 19:24:14.463785
2014-03-11 19:24:14.463869 Joining p2pool network using port 14476...
2014-03-11 19:24:14.543428 ...success!
2014-03-11 19:24:14.543598
2014-03-11 19:24:14.543934 Listening for workers on '' port 14477...
2014-03-11 19:24:14.742550 ...success!
2014-03-11 19:24:14.742750
2014-03-11 19:24:14.742843 Started successfully!
2014-03-11 19:24:14.742936 Go to http://127.0.0.1:14477/ to view graphs and statistics!
2014-03-11 19:24:14.743042 Donating 0.0% of work towards P2Pool's development. Please donate to encourage further development of P2Pool!
2014-03-11 19:24:14.743138
2014-03-11 19:24:14.758764 Peer 192.241.184.189:56197 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:14.758977 Bad peer banned: ('192.241.184.189', 56197)
2014-03-11 19:24:14.759576 Peer 192.241.184.189:14476 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:14.759705 Bad peer banned: (u'192.241.184.189', 14476)
2014-03-11 19:24:17.434883 Outgoing connection to peer 198.105.222.218:14476 established. p2pool version: 1300 '13.4-16-g5ee3172-dirty'
2014-03-11 19:24:17.441818 Sending 1 shares to 198.105.222.218:14476
2014-03-11 19:24:17.483721 Peer sent entire transaction 9cd927b1f45fbae5531e35af2c5fc127ccbb2265c04832ce1ba937b21a93eda7 that was already received
2014-03-11 19:24:17.743573 P2Pool: 2 shares in chain (2 verified/3 total) Peers: 1 (0 incoming)
2014-03-11 19:24:17.743712 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:24:18.595520 Sending 1 shares to 198.105.222.218:14476
2014-03-11 19:24:22.997509 Peer 127.0.0.1:58056 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:22.997807 Bad peer banned: ('127.0.0.1', 58056)
2014-03-11 19:24:22.998741 Peer 0.0.0.0:14476 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:22.998926 Bad peer banned: (u'0.0.0.0', 14476)
2014-03-11 19:24:26.939935 Incoming connection to peer 54.201.164.152:35163 established. p2pool version: 1300 'unknown 7032706f6f6c'
2014-03-11 19:24:27.258990 Sending 1 shares to 54.201.164.152:35163
2014-03-11 19:24:27.261750 Peer sent entire transaction 9cd927b1f45fbae5531e35af2c5fc127ccbb2265c04832ce1ba937b21a93eda7 that was already received
2014-03-11 19:24:27.444993 Sending 1 shares to 54.201.164.152:35163
2014-03-11 19:24:29.746273 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:24:29.746440 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:24:44.748152 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:24:44.748356 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:24:59.750010 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:24:59.750217 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:25:14.752814 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:25:14.753278 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:25:17.753932 P2Pool: 2 shares in chain (2 verified/5 total) Peers: 2 (1 incoming)
2014-03-11 19:25:17.754169 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
The only thing that jumps out to me is the "Bad peer banned" lines.2014-03-11 19:24:14.227174
2014-03-11 19:24:14.227276 Testing bitcoind RPC connection to 'http://127.0.0.1:12832/' with username 'mazacoinrpc'...
2014-03-11 19:24:14.252417 ...success!
2014-03-11 19:24:14.252619 Current block hash: 9fcae840d5a59552e97d1633764888dd7a83976a373c58d375
2014-03-11 19:24:14.252753 Current block height: 23771
2014-03-11 19:24:14.252869
2014-03-11 19:24:14.252969 Testing bitcoind P2P connection to '127.0.0.1:12835'...
2014-03-11 19:24:14.356868 ...success!
2014-03-11 19:24:14.357020
2014-03-11 19:24:14.357094 Determining payout address...
2014-03-11 19:24:14.419560 Loaded cached address: MC6zvyNdZ9qVbCQ3tUGDM8DHvU7aKyG3Hg...
2014-03-11 19:24:14.424291 ...success! Payout address: MC6zvyNdZ9qVbCQ3tUGDM8DHvU7aKyG3Hg
2014-03-11 19:24:14.424418
2014-03-11 19:24:14.424504 Loading shares...
2014-03-11 19:24:14.428802 ...done loading 2 shares (2 verified)!
2014-03-11 19:24:14.428915
2014-03-11 19:24:14.429002 Initializing work...
2014-03-11 19:24:14.463648 ...success!
2014-03-11 19:24:14.463785
2014-03-11 19:24:14.463869 Joining p2pool network using port 14476...
2014-03-11 19:24:14.543428 ...success!
2014-03-11 19:24:14.543598
2014-03-11 19:24:14.543934 Listening for workers on '' port 14477...
2014-03-11 19:24:14.742550 ...success!
2014-03-11 19:24:14.742750
2014-03-11 19:24:14.742843 Started successfully!
2014-03-11 19:24:14.742936 Go to http://127.0.0.1:14477/ to view graphs and statistics!
2014-03-11 19:24:14.743042 Donating 0.0% of work towards P2Pool's development. Please donate to encourage further development of P2Pool!
2014-03-11 19:24:14.743138
2014-03-11 19:24:14.758764 Peer 192.241.184.189:56197 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:14.758977 Bad peer banned: ('192.241.184.189', 56197)
2014-03-11 19:24:14.759576 Peer 192.241.184.189:14476 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:14.759705 Bad peer banned: (u'192.241.184.189', 14476)
2014-03-11 19:24:17.434883 Outgoing connection to peer 198.105.222.218:14476 established. p2pool version: 1300 '13.4-16-g5ee3172-dirty'
2014-03-11 19:24:17.441818 Sending 1 shares to 198.105.222.218:14476
2014-03-11 19:24:17.483721 Peer sent entire transaction 9cd927b1f45fbae5531e35af2c5fc127ccbb2265c04832ce1ba937b21a93eda7 that was already received
2014-03-11 19:24:17.743573 P2Pool: 2 shares in chain (2 verified/3 total) Peers: 1 (0 incoming)
2014-03-11 19:24:17.743712 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:24:18.595520 Sending 1 shares to 198.105.222.218:14476
2014-03-11 19:24:22.997509 Peer 127.0.0.1:58056 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:22.997807 Bad peer banned: ('127.0.0.1', 58056)
2014-03-11 19:24:22.998741 Peer 0.0.0.0:14476 misbehaving, will drop and ban. Reason: was connected to self
2014-03-11 19:24:22.998926 Bad peer banned: (u'0.0.0.0', 14476)
2014-03-11 19:24:26.939935 Incoming connection to peer 54.201.164.152:35163 established. p2pool version: 1300 'unknown 7032706f6f6c'
2014-03-11 19:24:27.258990 Sending 1 shares to 54.201.164.152:35163
2014-03-11 19:24:27.261750 Peer sent entire transaction 9cd927b1f45fbae5531e35af2c5fc127ccbb2265c04832ce1ba937b21a93eda7 that was already received
2014-03-11 19:24:27.444993 Sending 1 shares to 54.201.164.152:35163
2014-03-11 19:24:29.746273 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:24:29.746440 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:24:44.748152 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:24:44.748356 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:24:59.750010 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:24:59.750217 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:25:14.752814 P2Pool: 2 shares in chain (2 verified/4 total) Peers: 2 (1 incoming)
2014-03-11 19:25:14.753278 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-03-11 19:25:17.753932 P2Pool: 2 shares in chain (2 verified/5 total) Peers: 2 (1 incoming)
2014-03-11 19:25:17.754169 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
I will try re-cloning the p2pool from github. Which repository are you using?
...Apart from a couple of adjustments to get the "Expected time to share" and "Share difficulty" to display more accurately (which I can post if you're interested)...
Hi, thanks for sharing your p2pool code!
I just started up a server and am not getting the stats api to work (pool hash rates, etc).
http://192.241.184.189:14477/static/
I noticed they work on your site and was wondering if the other "adjustments" you made fix that?
For example,
http://mazacoin.treasurequarry.com:14477/global_stats yours returns data
http://192.241.184.189:14477/global_stats mine returns null
I can't say for sure but you likely need some minimum amount of hashing history before they populate.
Can you try stopping your p2pool, then restarting and copy the output of the log file at data/mazacoin/log from when it restarts? It should show it loading shares after connecting to my pool.
Also are there any errors showing in the log?
The other adjustments that I had mentioned were simply to display the time to share and share difficulty more accurately. I'll post them later but without them you should still get stats showing.
...Apart from a couple of adjustments to get the "Expected time to share" and "Share difficulty" to display more accurately (which I can post if you're interested)...
Hi, thanks for sharing your p2pool code!
I just started up a server and am not getting the stats api to work (pool hash rates, etc).
http://192.241.184.189:14477/static/
I noticed they work on your site and was wondering if the other "adjustments" you made fix that?
For example,
http://mazacoin.treasurequarry.com:14477/global_stats yours returns data
http://192.241.184.189:14477/global_stats mine returns null
I can't say for sure but you likely need some minimum amount of hashing history before they populate.
...Apart from a couple of adjustments to get the "Expected time to share" and "Share difficulty" to display more accurately (which I can post if you're interested)...
Hi, thanks for sharing your p2pool code!
I just started up a server and am not getting the stats api to work (pool hash rates, etc).
http://192.241.184.189:14477/static/
I noticed they work on your site and was wondering if the other "adjustments" you made fix that?
For example,
http://mazacoin.treasurequarry.com:14477/global_stats yours returns data
http://192.241.184.189:14477/global_stats mine returns null
I've just patched and recompiled the mazacoind daemon using a suggestion from arch at http://cryptominers.freeforums.org/post232.html#p232
This has very significantly sped up mazacoind responses to requests. I'm hoping this may also result in a nice improvement in general performance of the pool.
This has very significantly sped up mazacoind responses to requests. I'm hoping this may also result in a nice improvement in general performance of the pool.
I am having trouble getting my erupter blades connected. Can anybody tell me the appropriate command line code? Thank you.
Are those the ones that can only accept DIFF 1 work? If so, add /1 after your payment address, but you'll have lots of network traffic to the pool. Best to run a local stratum proxy if that's possible, or a local p2pool node on your own computer.
I am having trouble getting my erupter blades connected. Can anybody tell me the appropriate command line code? Thank you.
No problem, roy7, and I don't mind it going into the github. I was just a bit put off by rav3n_pl's shouting. I've used similar settings for months on some of my other p2pools with great success and happy miners.
On a totally unrelated note, could miner MFiqFUxwFVNdKfGJQsYPNd9zL74iip6pby PM me as whatever you're settings or software you're using for mining seems to have been causing some problems. I've reluctantly had to ban you meanwhile. If you can PM me with what details of program you're using to mine and your command line or settings you're using then maybe we can figure out what's causing the problems.
On a totally unrelated note, could miner MFiqFUxwFVNdKfGJQsYPNd9zL74iip6pby PM me as whatever you're settings or software you're using for mining seems to have been causing some problems. I've reluctantly had to ban you meanwhile. If you can PM me with what details of program you're using to mine and your command line or settings you're using then maybe we can figure out what's causing the problems.
Sorry for rocking the boat. I'd asked rav3n to review and add to his repo if he wanted, since I use it for other coins already and figured it'd be convenient if he dropped it into the github. 
Jump to: