Quote from: rjk
It does, just start a new instance in another command window with your desired arguments. They will be forwarded to the running bitcoind and the values returned to you.
Then it is cool. Works great.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 787. (Read 2591971 times)
February 10, 2012, 06:15:57 PM
Then it is cool. Works great.
February 10, 2012, 05:59:09 PM
I've been playing around with making a p2pool recent stats page. It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:
http://btcstats.net/p2pool/
Hmm nice.http://btcstats.net/p2pool/
- Includes Recent pool hash rate and stale rate
- Recent blocks are shown on the chart as vertical lines so that you can "see" variance
- Recent blocks are also listed in a table with links to the details
I presume the lack of history can be overcome with help from forrestv?
February 10, 2012, 04:26:31 PM
Ente: Here's a version with the submitold commit reverted: https://github.com/forrestv/p2pool/tarball/nosubmitold
Do you think you could test it to see if it fixes the problem?
EDIT: Also, does GUIMiner have any log files? There should be an additional message after the "Unexpected error" lines, but it's not there. Maybe it's appearing on the terminal or something?
Do you think you could test it to see if it fixes the problem?
EDIT: Also, does GUIMiner have any log files? There should be an additional message after the "Unexpected error" lines, but it's not there. Maybe it's appearing on the terminal or something?
February 10, 2012, 04:15:03 PM
Ah, thanks, that gave me enough information to find the (likely) problem - this commit: https://github.com/forrestv/p2pool/commit/d39081784f6 !
GUIminer doesn't use a real JSON parser, and that additional field might be confusing it.. Which backend are you using?
By the way, those releases are really old. There have been some important fixes since then.. Most people just use something recent from git master. I might get back into the habit of making releases soon, though.
GUIminer doesn't use a real JSON parser, and that additional field might be confusing it.. Which backend are you using?
By the way, those releases are really old. There have been some important fixes since then.. Most people just use something recent from git master. I might get back into the habit of making releases soon, though.
Guiminer 2011-06-14
with poclbm "-f 100 -w 128 -v"
I see no obvious way to find out poclbm's version. If you wish to know that I have a second look.
edit:
Oh, I assumed both gid and the tar'ed version would be the same.. Good to know, I'll get the gid version then!
Maybe drop a note on that on the downloadpage? ;-)
Thank you for your help and all the time and energy you put in this!
Ente
February 10, 2012, 04:09:48 PM
Do you run P2Pool on each individual rig? If so, any reason why?
Yep, every rig has its own p2pool node.
My friend prefers to not be dependent on one machine's p2pool.
Talking about statistics: the probability that one p2pool from any of the rigs crashes is higher than if there is just one, (locally) centralized p2pool where all rigs connect to.. I'll talk him out of that next week :-)
I rolled back to 0.8.1 and that miner works now again.
The guiminer log only said "unexpected error" too.
I will have a second look next week, and maybe switch to cgminer etc anyway, and hopefully to one p2pool node where all rigs connect to too.
Ente
February 10, 2012, 04:05:25 PM
After rebooting all rigs, now all (0.8.1) p2pool instances seem to give/get work to guiminer. The rig with 0.8.3 is the only one with "unexpected error" with guiminer.
All 8 rigs have the same versions, configs, tools, everything is identical (except 0.8.1/0.8.3)
All 8 rigs have the same versions, configs, tools, everything is identical (except 0.8.1/0.8.3)
Ah, thanks, that gave me enough information to find the (likely) problem - this commit: https://github.com/forrestv/p2pool/commit/d39081784f6 !
GUIminer doesn't use a real JSON parser, and that additional field might be confusing it.. Which backend are you using?
By the way, those releases are really old. There have been some important fixes since then.. Most people just use something recent from git master. I might get back into the habit of making releases soon, though.
February 10, 2012, 03:53:08 PM
I've been playing around with making a p2pool recent stats page. It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:
http://btcstats.net/p2pool/
http://btcstats.net/p2pool/
- Includes Recent pool hash rate and stale rate
- Recent blocks are shown on the chart as vertical lines so that you can "see" variance
- Recent blocks are also listed in a table with links to the details
That's really cool. Can we integrate a luck graph into there too'?
February 10, 2012, 03:51:32 PM
Quote from: Syke
Here's a great command to list found blocks:
Code:
bitcoind listtransactions
It would be cool if bitcoind had a side-channel interface so that queries could be made while it was running.
Probably via http or ssh.
February 10, 2012, 03:49:00 PM
Quote from: Syke
Here's a great command to list found blocks:
Code:
bitcoind listtransactions
It would be cool if bitcoind had a side-channel interface so that queries could be made while it was running.
Probably via http or ssh.
February 10, 2012, 03:36:45 PM
Quote from: forrestv
P2Pool should listen on port 9332 on all interfaces. Is this a problem..? You mentioned just needing to connect external miners, which many people already do.
It's not a problem for me now, I modified main.py. I tried to add the diff to an issue for p2pool on github. I'm pretty sure that my diff got garbled on github. sorryboutthat I'm not githubish yet.
I have tested it and it does work.
February 10, 2012, 03:28:54 PM
Still using GuiMiner, it throws:
Any ideas?
Quote
2012-02-10 17:50:49: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:49, long poll: new block 000004f709b08c9c
2012-02-10 17:50:53: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:53, Unexpected error:
2012-02-10 17:51:03: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:03, Unexpected error:
2012-02-10 17:51:09: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:09, Unexpected error:
2012-02-10 17:51:10: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:10, long poll: new block 000004f709b08c9c
2012-02-10 17:51:16: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:16, long poll: new block 000004f709b08c9c
2012-02-10 17:51:18: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:18, long poll: new block 000004f709b08c9c
2012-02-10 17:50:53: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:53, Unexpected error:
2012-02-10 17:51:03: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:03, Unexpected error:
2012-02-10 17:51:09: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:09, Unexpected error:
2012-02-10 17:51:10: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:10, long poll: new block 000004f709b08c9c
2012-02-10 17:51:16: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:16, long poll: new block 000004f709b08c9c
2012-02-10 17:51:18: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:18, long poll: new block 000004f709b08c9c
Any ideas?
Do all of the rigs have identical configurations? It looks like you're using poclbm as the backend.. Maybe try downloading the newest version of poclbm from https://github.com/m0mchil/poclbm/downloads and dropping it into GUIMiner's directory?
Now thats strange..
After rebooting all rigs, now all (0.8.1) p2pool instances seem to give/get work to guiminer. The rig with 0.8.3 is the only one with "unexpected error" with guiminer.
All 8 rigs have the same versions, configs, tools, everything is identical (except 0.8.1/0.8.3)
I try to get more info from poclbm/guiminer..
Ente
February 10, 2012, 03:23:56 PM
Here's a great command to list found blocks:
Code:
bitcoind listtransactions
For Linux and/or bash users: here's a bash function I wrote yesterday -- it omits the txid lines from listtransactions, but more important (to me) it adds a human-readable time to the time of each one:
Code:
btx () {
bitcoind listtransactions $* | while read name colon value
do
if [ $colon ] ; then
if [ $name != '"txid"' ] ; then # omit txid line
if [ $name = '"time"' ] ; then # provide a readable version of time
echo '"time"' : $value = `date -d "1970-01-01 $value seconds UTC" +"%Y-%m-%d %T %z"`
else
echo "$name : $value"
fi
fi
else
echo $name
fi
done
}
Thus, this...
Code:
"txid" : "aca39f64e4f71f984b9693fe1dbd6dc9361162d94db10b1b814121cf3da44a9f",
"time" : 1328894325
is replaced by....
Code:
"time" : 1328894325 = 2012-02-10 09:18:45 -0800
(The UTC offset is specific to your local system's time zone setting.)
February 10, 2012, 02:57:41 PM
This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.
+1
p2pool claims to be totally transparent. Users having full control (as in opposite to big mining pools).
Yet we don't even know for sure when / what was found.
Here's a great command to list found blocks:
Code:
bitcoind listtransactions
+1
February 10, 2012, 02:53:23 PM
This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.
+1
p2pool claims to be totally transparent. Users having full control (as in opposite to big mining pools).
Yet we don't even know for sure when / what was found.
Here's a great command to list found blocks:
Code:
bitcoind listtransactions
February 10, 2012, 01:33:01 PM
Still using GuiMiner, it throws:
Any ideas?
Quote
2012-02-10 17:50:49: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:49, long poll: new block 000004f709b08c9c
2012-02-10 17:50:53: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:53, Unexpected error:
2012-02-10 17:51:03: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:03, Unexpected error:
2012-02-10 17:51:09: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:09, Unexpected error:
2012-02-10 17:51:10: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:10, long poll: new block 000004f709b08c9c
2012-02-10 17:51:16: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:16, long poll: new block 000004f709b08c9c
2012-02-10 17:51:18: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:18, long poll: new block 000004f709b08c9c
2012-02-10 17:50:53: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:53, Unexpected error:
2012-02-10 17:51:03: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:03, Unexpected error:
2012-02-10 17:51:09: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:09, Unexpected error:
2012-02-10 17:51:10: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:10, long poll: new block 000004f709b08c9c
2012-02-10 17:51:16: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:16, long poll: new block 000004f709b08c9c
2012-02-10 17:51:18: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:18, long poll: new block 000004f709b08c9c
Any ideas?
Do all of the rigs have identical configurations? It looks like you're using poclbm as the backend.. Maybe try downloading the newest version of poclbm from https://github.com/m0mchil/poclbm/downloads and dropping it into GUIMiner's directory?
February 10, 2012, 01:27:10 PM
I've been meaning to ask for a while... how are version numbers generated? Do they encode any information of interest to a user?
They are git commit hashes. You can look at the source code for your version by going to https://github.com/forrestv/p2pool/tree/053d7ca or you can see changes I've committed since your version, by going to https://github.com/forrestv/p2pool/compare/053d7ca...master .
I'm sorry my sentence keeps coming up, I was answering a previous message from piuk with a link to blockchain.info which had a wrong block listed and just the day before p2pool log file was found by me to contain out-of-date (and as such "misleading" as in "misleading to a user" of p2pool) informations (they clearly are not misleading to their author or to someone who digs into the source code and understands its inner workings).
I also did not check that blockexplorer link because I thought that grepping p2pool log file was the surest way to know what was going on and in case of troubles (blocks being lost and share numbers swinging a lot were yesterday "problems" I was trying to go after) looking up an address to see if it got its payment is not a good idea IMHO since on a lost block every address should not receive any payment.
So I was trying to express the idea that there is not a "place" which lists blocks found and found but rejected by the network as it happens with other pools which often have such a "place".
Maybe my sentence sounds to english speaking peoples in way that is too harsh or just stronger than it was meant to be, my apologies if this is the case.
I also did not check that blockexplorer link because I thought that grepping p2pool log file was the surest way to know what was going on and in case of troubles (blocks being lost and share numbers swinging a lot were yesterday "problems" I was trying to go after) looking up an address to see if it got its payment is not a good idea IMHO since on a lost block every address should not receive any payment.
So I was trying to express the idea that there is not a "place" which lists blocks found and found but rejected by the network as it happens with other pools which often have such a "place".
Maybe my sentence sounds to english speaking peoples in way that is too harsh or just stronger than it was meant to be, my apologies if this is the case.
Ah, sorry, I guess I didn't understand then. The best way to see invalid blocks is to see if any of the blocks mentioned in your log aren't present on Block Explorer. Just looking at Block Explorer only tells you confirmed blocks, and only looking at your log can sometimes tell you old blocks and sometimes not tell you about new blocks, due to them being stale on P2Pool.
It wasn't too harsh!
February 10, 2012, 01:16:19 PM
do you know whether blocks found but later rejected by bitcoin network can be listed?
You mean, "Invalid Blocks"?No, my page doesn't include those. There's not a convenient centralized place to get a list of those that I can pull from.
February 10, 2012, 01:11:54 PM
I've been playing around with making a p2pool recent stats page. It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:
http://btcstats.net/p2pool/
http://btcstats.net/p2pool/
- Includes Recent pool hash rate and stale rate
- Recent blocks are shown on the chart as vertical lines so that you can "see" variance
- Recent blocks are also listed in a table with links to the details
Very nice twmz,
do you know whether blocks found but later rejected by bitcoin network can be listed?
spiccioli
You mean, "Invalid Blocks"?
Yes, blocks found by pool but then rejected by bitcoin network.
spiccioli
February 10, 2012, 12:56:59 PM
I've been playing around with making a p2pool recent stats page. It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:
http://btcstats.net/p2pool/
http://btcstats.net/p2pool/
- Includes Recent pool hash rate and stale rate
- Recent blocks are shown on the chart as vertical lines so that you can "see" variance
- Recent blocks are also listed in a table with links to the details
Very nice twmz,
do you know whether blocks found but later rejected by bitcoin network can be listed?
spiccioli
You mean, "Invalid Blocks"?
February 10, 2012, 12:53:12 PM
I've been playing around with making a p2pool recent stats page. It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:
http://btcstats.net/p2pool/
http://btcstats.net/p2pool/
- Includes Recent pool hash rate and stale rate
- Recent blocks are shown on the chart as vertical lines so that you can "see" variance
- Recent blocks are also listed in a table with links to the details
Very nice twmz,
do you know whether blocks found but later rejected by bitcoin network can be listed?
spiccioli
Jump to: