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

[TinyBBC]

I am very sad, every time I see less and less the p2pool's hashrate proportion of the whole network

[norgan]

is there any way to store stats in a db or even flat file so that when you restart a node you don't loose the share, uptime and hashing stats of the pool?

I imagine we could pull the json feeds into a db table then make the front end pull those stats from there but hoping there is a simpler way.

[windpath]

is there any way to store stats in a db or even flat file so that when you restart a node you don't loose the share, uptime and hashing stats of the pool?

I imagine we could pull the json feeds into a db table then make the front end pull those stats from there but hoping there is a simpler way.

Uptime needs to reset when you restart the node, that's a basic principle of "uptime", you have to be "up" the whole time...

I have not gotten to setting up MySQL yet, and all the data you want exists; my node displays data from 4 sources; Network data from P2Pool and Bitcoind, Recent P2Pool blocks from BlockChain.info, and miner shares from P2Pool's log file.

Node stats page: http://mining.coincadence.com/

Individual miner stats page: http://mining.coincadence.com/miner.php?id=19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj

There is still lots of work to do, but I'll take progress over perfection

[norgan]

is there any way to store stats in a db or even flat file so that when you restart a node you don't loose the share, uptime and hashing stats of the pool?

I imagine we could pull the json feeds into a db table then make the front end pull those stats from there but hoping there is a simpler way.

Uptime needs to reset when you restart the node, that's a basic principle of "uptime", you have to be "up" the whole time...

I have not gotten to setting up MySQL yet, and all the data you want exists; my node displays data from 4 sources; Network data from P2Pool and Bitcoind, Recent P2Pool blocks from BlockChain.info, and miner shares from P2Pool's log file.

Node stats page: http://mining.coincadence.com/

Individual miner stats page: http://mining.coincadence.com/miner.php?id=19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj

There is still lots of work to do, but I'll take progress over perfection

ok sure uptime maybe not but if you run another instance of p2pool up along side and it comes up immediately then your stats still reset and your uptime is still 100%. mainly though the shares, efficiency etc is what I want to keep. I was also looking to the server stats and considering presenting server uptime as well as node uptime to show users that the server has been 100% available and it was only the node that was restarted.
how did you get that nice smooth looking graph? keen to make mine a bit nicer.

[windpath]

is there any way to store stats in a db or even flat file so that when you restart a node you don't loose the share, uptime and hashing stats of the pool?

I imagine we could pull the json feeds into a db table then make the front end pull those stats from there but hoping there is a simpler way.

Uptime needs to reset when you restart the node, that's a basic principle of "uptime", you have to be "up" the whole time...

I have not gotten to setting up MySQL yet, and all the data you want exists; my node displays data from 4 sources; Network data from P2Pool and Bitcoind, Recent P2Pool blocks from BlockChain.info, and miner shares from P2Pool's log file.

Node stats page: http://mining.coincadence.com/

Individual miner stats page: http://mining.coincadence.com/miner.php?id=19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj

There is still lots of work to do, but I'll take progress over perfection

ok sure uptime maybe not but if you run another instance of p2pool up along side and it comes up immediately then your stats still reset and your uptime is still 100%. mainly though the shares, efficiency etc is what I want to keep. I was also looking to the server stats and considering presenting server uptime as well as node uptime to show users that the server has been 100% available and it was only the node that was restarted.
how did you get that nice smooth looking graph? keen to make mine a bit nicer.

Agreed on the uptime points, but whenever I kill my existing node process (having started a new instance of P2Pool first) it still takes a minute for my miners to connect on the new process, your right, it would be great to figure out a way to persist incoming hash power across instances of P2Pool on the same server.

The main graph is from the "Node Status" front end:

Live: http://mining.coincadence.com:9332/static/node-status/

Source: https://github.com/johndoe75/p2pool-node-status

The "miner stats" graph, which includes expected payout was put together by jonnybravo0311

Edit:

I keep the 3 major open source front ends live on my server (unedited), both as a reference for my development and a way for existing P2Pool miners to see a confirmation of what they are familiar with.

Default front end: http://mining.coincadence.com:9332/static/original/
Source: https://github.com/forrestv/p2pool/tree/master/web-static

Node Status front end: http://mining.coincadence.com:9332/static/node-status/
Source: https://github.com/johndoe75/p2pool-node-status

Extended front end: http://mining.coincadence.com:9332/static/extended/
Source: https://github.com/hardcpp/P2PoolExtendedFrontEnd

They are all publicly available in the footer link....

[norgan]

Agreed on the uptime points, but whenever I kill my existing node process (having started a new instance of P2Pool first) it still takes a minute for my miners to connect on the new process, your right, it would be great to figure out a way to persist incoming hash power across instances of P2Pool on the same server.

The main graph is from the "Node Status" front end:

Live: http://mining.coincadence.com:9332/static/node-status/

Source: https://github.com/johndoe75/p2pool-node-status

The "miner stats" graph, which includes expected payout was put together by jonnybravo0311

Edit:

I keep the 3 major open source front ends live on my server (unedited), both as a reference for my development and a way for existing P2Pool miners to see a confirmation of what they are familiar with.

Default front end: http://mining.coincadence.com:9332/static/original/
Source: https://github.com/forrestv/p2pool/tree/master/web-static

Node Status front end: http://mining.coincadence.com:9332/static/node-status/
Source: https://github.com/johndoe75/p2pool-node-status

Extended front end: http://mining.coincadence.com:9332/static/extended/
Source: https://github.com/hardcpp/P2PoolExtendedFrontEnd

They are all publicly available in the footer link....

great thanks. I saw the extended and default front end but not the node status stuff. will check it out.

[bitpop]

is there any way to store stats in a db or even flat file so that when you restart a node you don't loose the share, uptime and hashing stats of the pool?

I imagine we could pull the json feeds into a db table then make the front end pull those stats from there but hoping there is a simpler way.

There's already a db afaik
Maybe your directory isn't writable

[norgan]

is there any way to store stats in a db or even flat file so that when you restart a node you don't loose the share, uptime and hashing stats of the pool?

I imagine we could pull the json feeds into a db table then make the front end pull those stats from there but hoping there is a simpler way.

There's already a db afaik
Maybe your directory isn't writable

what directory?

"p2pool folder"/data? it is writable and there is data in it but it still seems to reset after you restart the node.

[rav3n_pl]

Uptime and share count are cleared when u reset. Hashing data (graphs) are stored, shares too.

[norgan]

Uptime and share count are cleared when u reset. Hashing data (graphs) are stored, shares too.

thanks for clarifying!

[norgan]

right, now the https://github.com/johndoe75/p2pool-node-status runs fine on the node but won't display anything when run from an external web server even when the url is entered in the Config file.

Has anyone run this on a separate web server successfully? anything special you had to do?

[andmax]

If anyone is thinking of buying a Antminer S2 from Bitmain in the next couple of weeks I have a couple of US$400 off vouchers I can donate, you need an account with Bitmain so I can transfer them over.

Andrew 

[windpath]

right, now the https://github.com/johndoe75/p2pool-node-status runs fine on the node but won't display anything when run from an external web server even when the url is entered in the Config file.

Has anyone run this on a separate web server successfully? anything special you had to do?

Look for:

Code:

var api_url= "";

in index.html and try setting that...

[norgan]

right, now the https://github.com/johndoe75/p2pool-node-status runs fine on the node but won't display anything when run from an external web server even when the url is entered in the Config file.

Has anyone run this on a separate web server successfully? anything special you had to do?

Look for:

Code:

var api_url= "";

in index.html and try setting that...

Yeah I found and set that still no luck unfortunately

[norgan]

so how do you know if your node solved a block? I got an initial dump of alt coins when I first set up the merged mining and not anything since. I've been told that those don't pay unless you hit a block and you are effectively solo mining on them.
So does that mean I actually solved a block? and how the hell do you read the blockchain to figure it out?

[bitpop]

so how do you know if your node solved a block? I got an initial dump of alt coins when I first set up the merged mining and not anything since. I've been told that those don't pay unless you hit a block and you are effectively solo mining on them.
So does that mean I actually solved a block? and how the hell do you read the blockchain to figure it out?

I just query that wallet once in a while

[norgan]

so how do you know if your node solved a block? I got an initial dump of alt coins when I first set up the merged mining and not anything since. I've been told that those don't pay unless you hit a block and you are effectively solo mining on them.
So does that mean I actually solved a block? and how the hell do you read the blockchain to figure it out?

I just query that wallet once in a while

the wallet specified in the -a argument?

[bitpop]

so how do you know if your node solved a block? I got an initial dump of alt coins when I first set up the merged mining and not anything since. I've been told that those don't pay unless you hit a block and you are effectively solo mining on them.
So does that mean I actually solved a block? and how the hell do you read the blockchain to figure it out?

I just query that wallet once in a while

the wallet specified in the -a argument?

No like the nmc wallet to see if the balance increased

Or parse the log files

[norgan]

so how do you know if your node solved a block? I got an initial dump of alt coins when I first set up the merged mining and not anything since. I've been told that those don't pay unless you hit a block and you are effectively solo mining on them.
So does that mean I actually solved a block? and how the hell do you read the blockchain to figure it out?

I just query that wallet once in a while

the wallet specified in the -a argument?

No like the nmc wallet to see if the balance increased

Or parse the log files

right! well in that case I must have hit a block only days after running up my p2pool node since I have a payout in all my merged wallets. I wasn't sure at that stage as I thought it was just pay per share type payment. that's pretty cool on only 36gh/s

[bitpop]

so how do you know if your node solved a block? I got an initial dump of alt coins when I first set up the merged mining and not anything since. I've been told that those don't pay unless you hit a block and you are effectively solo mining on them.
So does that mean I actually solved a block? and how the hell do you read the blockchain to figure it out?

I just query that wallet once in a while

the wallet specified in the -a argument?

No like the nmc wallet to see if the balance increased

Or parse the log files

right! well in that case I must have hit a block only days after running up my p2pool node since I have a payout in all my merged wallets. I wasn't sure at that stage as I thought it was just pay per share type payment. that's pretty cool on only 36gh/s

All your coins got a block? I'm not aware that the merged coins were merged mined across each other. As in you find a good hash but it can apply to more than one coin. I guess it can though. I'm guessing you hit an nmc and since it's the hardest it counted for all of them.

Open their qt you should see your block plus transaction fees

Yup you're solo mining, the coins are easier than Bitcoin but great luck on 36 ghs