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

wachtwoord

legendary

Activity: 2324

Merit: 1125

Thanks, nice work.

But how do you know you found it?

Ente

legendary

Activity: 2126

Merit: 1001

Quote from: Ente on February 11, 2012, 06:42:22 AM

It gets more and more strange..

Rig "Miner04" uses forrestv-p2pool-0.8.4-1-gadba786
Rig "Miner03" uses forrestv-p2pool-release-0.8.1-0-gc7feb00

Rig "Miner04" uses Guiminer v2011-06-14
Rig "Miner03" uses Guiminer v2011-06-14

Guiminer "Miner03" --> p2pool "Miner03": finds "minerblocks" and "shareblocks"
Guiminer "Miner04" --> p2pool "Miner04": drops "unexpected error:" in guiminer
Guiminer "Miner03" --> p2pool "Miner04": finds "minerblocks" with 100% in (), finds "shareblocks"
Guiminer "Miner04" --> p2pool "Miner03": finds "minerblocks" with 50% in (), finds no "shareblocks"

So obviously its some problem on Guiminer's (or poclbm) side on "Miner04".

In Guiminer you see for example:

Quote

Accepted: 471 (256)
Stale: 0 (0)

I didnt find out what the number in () means, yet.

All other rigs are like "Miner03" and behave well.

Bah, I'm losing my patience with this windows stuff..

Ente

edits underlined

Ok, its quite clear now that its a problem on the Guiminer (or poclbm) side.
Will try to solve that and update all p2pool instances to the "forrestv-p2pool-0.8.4-1-gadba786" version too.

Thank you for your help!

Ente

jothan

full member

Activity: 184

Merit: 100

Feel the coffee, be the coffee.

Yay, I found my first block ever, just now, while participating in P2Pool. It took over 2 months at ~1710 Mhash/s.

Glad to see my mining rig can actually mine a full block Tongue

https://blockchain.info/block-index/867562/0000000000000943404156a9980c3c6e49b0f3c712a4c4673a6e8890edf9c13c

forrestv

hero member

Activity: 516

Merit: 643

Quote from: Red Emerald on February 11, 2012, 12:36:09 PM

I wanted to setup a backup pool and so I installed everything on a debian server. If I specify all of the command line options, it starts fine. But "--help" gives an error.

Fixed, thanks for pointing that out.

Red Emerald

hero member

Activity: 742

Merit: 500

So I have p2pool running on an ubuntu server with python 2.7.

I wanted to setup a backup pool and so I installed everything on a debian server. If I specify all of the command line options, it starts fine. But "--help" gives an error.

Code:

[user@p2pool p2pool]$ ./run_p2pool.py --help
Install SciPy for more accurate confidence intervals!
/home/user/src/p2pool/p2pool/util/pack.py:191: DeprecationWarning: object.__new__() takes no parameters
  return Type.__new__(cls, bits, endianness)
Traceback (most recent call last):
  File "./run_p2pool.py", line 5, in 
    main.run()
  File "/home/user/src/p2pool/p2pool/main.py", line 1041, in run
    args = parser.parse_args()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1698, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1730, in parse_known_args
    return self._parse_known_args(args, namespace)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1932, in _parse_known_args
    start_index = consume_optional(start_index)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1872, in consume_optional
    take_action(action, args, option_string)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1800, in take_action
    action(self, namespace, argument_values, option_string)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1023, in __call__
    parser.print_help()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 2319, in print_help
    self._print_message(self.format_help(), file)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 2293, in format_help
    return formatter.format_help()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 314, in format_help
    help = self._root_section.format_help()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 244, in format_help
    func(*args)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 365, in _format_usage
    assert ' '.join(opt_parts) == opt_usage
AssertionError
[user@p2pool p2pool]$ python -V
Python 2.6.6
[user@p2pool p2pool]$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 6.0.4 (squeeze)
Release:        6.0.4
Codename:       squeeze

thirdlight

sr. member

Activity: 445

Merit: 250

Quote from: cabin on February 11, 2012, 07:48:59 AM

I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?

"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,

I see this at the bottom of the table on this page.

I thought it was someone who had specified a bad address with the "-a" option. But that was just a guess. Smart people will help...

twmz

hero member

Activity: 737

Merit: 500

Quote from: Tittiez on February 11, 2012, 11:37:16 AM

I meant at least in our prospective. My payouts show as "Mined" in the bitcoin client.

Yes, but that is just a "bug" in the bitcoin client. The actual generation transaction does include your address. The client just doesn't show it to you.

Tittiez

hero member

Activity: 686

Merit: 500

Quote from: kano on February 11, 2012, 10:39:09 AM

Quote from: Tittiez on February 11, 2012, 09:39:24 AM

Quote from: cabin on February 11, 2012, 07:48:59 AM

I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?

"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

Ummmm? Eh?
It goes to all the N addresses listed in the share chain - the coinbase txn lists all those addresses.

Aside ... so as mentioned above ... could someone stop every block from being accepted by putting crap addresses in the share chain?
Hope that problem doesn't exist or has been already dealt with if it did exist.

I meant at least in our prospective. My payouts show as "Mined" in the bitcoin client.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Tittiez on February 11, 2012, 09:39:24 AM

Quote from: cabin on February 11, 2012, 07:48:59 AM

I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?

"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

Ummmm? Eh?
It goes to all the N addresses listed in the share chain - the coinbase txn lists all those addresses.

Aside ... so as mentioned above ... could someone stop every block from being accepted by putting crap addresses in the share chain?
Hope that problem doesn't exist or has been already dealt with if it did exist.

cabin

sr. member

Activity: 604

Merit: 250

Well actually each p2p block has hundreds of payout addresses, but you're right it is solo mining. My concern was if one funny payout address could drastically slow down confirmation of a found block and therefore result in a p2pool block being orphaned. For example if only 5% of the network supported P2SH addresses, and the p2pool payout list includes a P2SH-style address, then p2pool blocks would be very slow to transmit through the network.

I suspect it is nothing to worry about and that I'm missing something.. but I just wanted to bring up the possibility in case it is a potential bug/problem.

Quote from: Tittiez on February 11, 2012, 09:39:24 AM

Quote from: cabin on February 11, 2012, 07:48:59 AM

I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?

"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

wachtwoord

legendary

Activity: 2324

Merit: 1125

You can also specify a bitcoin address which is not part of the wallet of the bitcoind (or bitcoin-qt) which is currently running. I set it up this way after I got advise in the IRC channel that this is more secure (which I agree with).

Tittiez

hero member

Activity: 686

Merit: 500

Quote from: cabin on February 11, 2012, 07:48:59 AM

I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?

"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

cabin

sr. member

Activity: 604

Merit: 250

I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?

"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,

Ente

legendary

Activity: 2126

Merit: 1001

It gets more and more strange..

Rig "Miner04" uses forrestv-p2pool-0.8.4-1-gadba786
Rig "Miner03" uses forrestv-p2pool-release-0.8.1-0-gc7feb00

Rig "Miner04" uses Guiminer v2011-06-14
Rig "Miner03" uses Guiminer v2011-06-14

Guiminer "Miner03" --> p2pool "Miner03": finds "minerblocks" and "shareblocks"
Guiminer "Miner04" --> p2pool "Miner04": drops "unexpected error:" in guiminer
Guiminer "Miner03" --> p2pool "Miner04": finds "minerblocks" with 100% in (), finds "shareblocks"
Guiminer "Miner04" --> p2pool "Miner03": finds "minerblocks" with 50% in (), finds no "shareblocks"

So obviously its some problem on Guiminer's (or poclbm) side on "Miner04".

In Guiminer you see for example:

Quote

Accepted: 471 (256)
Stale: 0 (0)

I didnt find out what the number in () means, yet.

All other rigs are like "Miner03" and behave well.

Bah, I'm losing my patience with this windows stuff..

Ente

edits underlined

Ente

legendary

Activity: 2126

Merit: 1001

Quote from: forrestv on 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?

Good morning,

I tested the "new old" version you linked. It works, connects faster and all, but the (guiminer) error still persists.
Still, the guiminer "console" says "unexpected error:", and thats all it says in its logfile too (in guiminer.log and guiminer.exe.log).

I'll experiment a bit with connecting (different) guiminer instances to (different) p2pool nodes to find out which one causes trouble here..

Ente

twmz

hero member

Activity: 737

Merit: 500

Ok, historical data from forrest is loaded. It's interesting to see how quickly things have grown relative to how long the pool floated steadily at around 10-15 GH/s.

Quote from: twmz on February 10, 2012, 12:33:27 PM

http://btcstats.net/p2pool/

Includes Recent pool hash rate and ~~stale rate~~ active users
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

miscreanity

legendary

Activity: 1316

Merit: 1005

Quote from: ThiagoCMC on February 11, 2012, 12:42:09 AM

Code:

~/p2pool/run_p2pool.py --version
becb233

The current git pull is:
aa520c1

ThiagoCMC

legendary

Activity: 1204

Merit: 1000

฿itcoin: Currency of Resistance!

Upgrading P2Pool node...

Guys, when is the best time to upgrade P2Pool node?

I mean, is there any announcements of new P2Pool versions?! If yes, where?!

Now I have:

Code:

~/p2pool/run_p2pool.py --version
becb233

But, is this the version you guys are using?!

Thanks!
Thiago

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

No hurry

Was just thinking out loud - but you already had thought of it anyway.

twmz

hero member

Activity: 737

Merit: 500

Quote from: kano on February 10, 2012, 05:59:09 PM

Hmm nice.
I presume the lack of history can be overcome with help from forrestv?

Yes, he gave me a database of old hashrate stats. I just have to spend time getting it into my database. We don't have old state rate data. I'm not sure if stale rate over time is all that interesting though, so maybe it isn't important and should be replaced with something like # of active users over time.

I also want to look at luck, but I will admit that I don't yet know how I am going to calculate that with only the information I have. But forrest's graph does it using this same data, so I probably just need to chat with him more and see what approach he is using.

I really need to also get a real backend for it because right now it is using the rrd files that the standard p2pool uses. I'd like to move this to a real database on my web host instead of using the rrd files.

But tomorrow is my wife's birthday, so I don't know how much time I can reasonably spend on this over the weekend. I'll probably squeeze a few hours in.

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