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

ThiagoCMC

legendary

Activity: 1204

Merit: 1000

฿itcoin: Currency of Resistance!

I'll try P2Pool for Bitcoin and Litecoin at the same machine but:

> Last, forward port 9333 through your firewall to the host running p2pool! (Oh, and join #p2pool on freenode!)

Litecoin already listen @ 9333... So as P2Pool...

What is the best workaround?!

Move litecoin to 10333 or P2Pool to 10333, for example?!

wachtwoord

legendary

Activity: 2324

Merit: 1125

Quote from: wachtwoord on February 02, 2012, 02:00:19 PM

Okay these are the result for running today for 11 hours at 251 Mhash

My miner reports: [251.34 Mhash/sec] [249 Accepted] [1 Rejected] [RPC (+LP)]

p2pool reports:

2012-02-02 18:55:01.238000 Pool: 157GH/s in 17350 shares (17354/17354 verified)
Recent: 0.13% >203MH/s Shares: 6 (0 orphan, 0 dead) Peers: 10 (0 incoming)
2012-02-02 18:55:01.238000 Average time between blocks: 0.41 days
2012-02-02 18:55:01.238000 Pool stales: 9% Own: 20±20% Own efficiency: 88±21%

This seems rather contradictionary to me:

Miner reports: 0.4% stales (1 in 250)
p2pool reports 0% stales (0 in 6)
p2pool reports 20±20% (where does this number come from)

Also, why does it recognize only 6 of 249 submitted shares?

Can someone explain all this to me?

Quote from: Vanderbleek on February 02, 2012, 02:02:11 PM

Quote from: Qoheleth on February 02, 2012, 01:55:05 PM

Haven't received a payout for two days. Is this just another block drought or is something wrong with my setup?
I'm seeing 156GH/s so I'm not on the split chain.

Since the transactions count as mined, you need 120 confirms for them to show up -- could that be why you're not seeing them?

Thanks for that explanation. Anyone for the other questions I posted? I had similar results today (5 shares, 0orphan 0 dead but 22±22% own stales reported)

waspoza

hero member

Activity: 602

Merit: 508

Firstbits: 1waspoza

Quote from: forrestv on February 03, 2012, 09:16:53 AM

Quote from: waspoza on February 03, 2012, 07:04:03 AM

Yea looks like my client is bugged. Pool hashrate went to zero, local hashrate is good. Strange.

Have you upgraded to the latest version? There was a problem that caused this that was fixed two weeks ago.

Ok, pulled newest version from git, and looks good now. Thanks.

Gabi

legendary

Activity: 1148

Merit: 1008

If you want to walk on water, get out of the boat

175ghash/s now, good job guys!

forrestv

hero member

Activity: 516

Merit: 643

Quote from: waspoza on February 03, 2012, 07:04:03 AM

Yea looks like my client is bugged. Pool hashrate went to zero, local hashrate is good. Strange.

Have you upgraded to the latest version? There was a problem that caused this that was fixed two weeks ago.

waspoza

hero member

Activity: 602

Merit: 508

Firstbits: 1waspoza

Yea looks like my client is bugged. Pool hashrate went to zero, local hashrate is good. Strange.

Qoheleth

legendary

Activity: 960

Merit: 1028

Spurn wild goose chases. Seek that which endures.

Quote from: waspoza on February 03, 2012, 05:31:50 AM

Does really pool hash rate dropped that much or its only me?

I'm seeing 153GH/s total network power on my client

waspoza

hero member

Activity: 602

Merit: 508

Firstbits: 1waspoza

Does really pool hash rate dropped that much or its only me?

spiccioli

legendary

Activity: 1378

Merit: 1003

nec sine labore

Quote from: eja on February 02, 2012, 07:42:20 PM

Normally you will see 'LONGPOLL requested work restart..' every couple of seconds with p2pool. If you're not seeing that, it might be this long polling issue. I'd try with just one pool configured.

Second thing I'd look at is if the host running your p2pool daemon is not too overloaded.

eja,

I see them and, no, the host with p2pool is a 3GhZ PentiumD/HT pc with xubuntu running just p2pool and bitcoind.

regards.

spiccioli.

spiccioli

legendary

Activity: 1378

Merit: 1003

nec sine labore

Quote from: thirdlight on February 03, 2012, 03:55:18 AM

spiccioli, try cgminer with only 1 thread, it's

Code:

"gpu-threads": "1"

in the config file.

Let us know if it makes a difference.

thirdlight,

with latest cgminer (2.2.1) using dynamic intensity forces a single therad per GPU, so I've set it to dynamic right now, let's see what happens.

regards.

spiccioli.

spiccioli

legendary

Activity: 1378

Merit: 1003

nec sine labore

Quote from: Red Emerald on February 02, 2012, 07:23:44 PM

Quote from: spiccioli on February 02, 2012, 07:16:11 PM

Any idea?

What version of p2pool are you running? That looks like miner output. What does your p2pool output look like?

As has been said many times, stales in p2pool are higher than a traditional pool

Red Emerald,

that is p2pool (I'm using latest) log file filtered for "GOT SHARE" lines.

I uderstad higher, but here they're mostly dead and it seems other people on p2pool have a few dead shares even with thousands good ones received.

Look, I've just restarted p2pool

Code:

08:59:19.034126 Average time between blocks: 0.40 days
08:59:19.034604 Pool stales: 10% Own: 67±33% Own efficiency: 37±37%
08:59:20.354290 New work for worker! Difficulty: 331.665349 Payout if block: 0.046013 BTC Total block value: 50.001500 BTC including 21 transactions
08:59:22.043901 Pool: 162GH/s in 17341 shares (17345/17345 verified) Recent: 0.13% >217MH/s Shares: 2 (0 orphan, 2 dead) Peers: 10
08:59:22.044154 Average time between blocks: 0.40 days
08:59:22.044419 Pool stales: 10% Own: 67±33% Own efficiency: 37±37%

and I already have 2 deads.

spiccioli.

thirdlight

sr. member

Activity: 445

Merit: 250

spiccioli, try cgminer with only 1 thread, it's

Code:

"gpu-threads": "1"

in the config file.

Let us know if it makes a difference.

eja

newbie

Activity: 39

Merit: 0

Quote from: spiccioli on February 02, 2012, 07:16:11 PM

Quote from: spiccioli on February 02, 2012, 05:09:40 AM

Well, I've restarted p2pool this morning at 0900 GMT+1, tomorrow I'll let you know what numbers I see.

regards.

spiccioli

Here we are, 20 hours later,

Code:

09:35:21.192503 GOT SHARE! cccccc 2a50469e prev ee4e3887 age 28.24s DEAD ON ARRIVAL
10:51:29.609170 GOT SHARE! cccccc ae20489a prev f5036a0c age 22.39s DEAD ON ARRIVAL
11:00:45.274799 GOT SHARE! cccccc 7ae24ef4 prev b1d8d61a age 20.28s DEAD ON ARRIVAL
11:30:42.989054 GOT SHARE! cccccc 1fb89a27 prev 0af6c699 age 29.78s DEAD ON ARRIVAL
11:38:33.196739 GOT SHARE! cccccc 2ffce415 prev 2c561f75 age 20.60s DEAD ON ARRIVAL
12:20:52.215387 GOT SHARE! cccccc 2deeb628 prev 21ff2b7b age 13.81s DEAD ON ARRIVAL
13:40:47.230481 GOT SHARE! cccccc 1aef7202 prev 1c4d5fe3 age 20.82s
14:27:05.064232 GOT SHARE! cccccc 61749cce prev fc90b812 age 23.00s DEAD ON ARRIVAL
14:54:32.934686 GOT SHARE! cccccc bf2761d7 prev 36614893 age 23.06s
15:13:35.412215 GOT SHARE! cccccc 7981f9dc prev eab26f20 age 20.23s DEAD ON ARRIVAL
15:19:06.171630 GOT SHARE! cccccc f46aa885 prev f98f68d2 age 21.07s DEAD ON ARRIVAL
16:28:33.961269 GOT SHARE! cccccc a9dbaaf4 prev 4f3bac03 age 22.01s DEAD ON ARRIVAL
16:43:18.028367 GOT SHARE! cccccc b2ab8707 prev 881e93ba age 21.55s DEAD ON ARRIVAL
16:48:31.739828 GOT SHARE! cccccc 3231a5e2 prev 08075e20 age 34.50s DEAD ON ARRIVAL
17:11:56.867175 GOT SHARE! cccccc fd25a9bd prev 69d47462 age 26.91s DEAD ON ARRIVAL
17:26:35.194804 GOT SHARE! cccccc 640e9ebd prev 5c2e2221 age 11.85s
17:35:39.829151 GOT SHARE! cccccc 582b0db9 prev f452f2f8 age 16.75s
17:41:35.629520 GOT SHARE! cccccc bd41d585 prev 32818a48 age 33.79s DEAD ON ARRIVAL
17:48:58.909271 GOT SHARE! cccccc ee2d6b93 prev 47bb9cfa age 9.51s
19:13:12.722993 GOT SHARE! cccccc 8ef4140e prev a402ee4a age 11.58s DEAD ON ARRIVAL
19:13:50.677687 GOT SHARE! cccccc f09c4eab prev d0613a01 age 28.44s DEAD ON ARRIVAL
19:15:47.942192 GOT SHARE! cccccc f81a2d80 prev 59599851 age 16.00s DEAD ON ARRIVAL

something is wrong, isn't it? most are dead, and what does that "age" field really mean?

I'm using latest cgminer 2.2.1 on my miner, with I 7 (intensity) and just p2pool, I have a failover pool, to be honest, but with

Code:

"failover-only" : true

inside cgminer.conf.

Any idea?

best regards.

spiccioli.

Your dead share rates seems rather excessive, I haven't had any dead shares myself for two weeks almost (I've only got fairly slow miner though).
I've had bad experience with mixing traditional pool and p2pool with cgminer. Not sure what the logic behind it is, but in my case it ended up using long polling connection to traditional pool while doing work for p2pool. Since the polling cycle on p2pool is a lot faster than normal pools this leads to (possibly very) high stale/dead shares.
Normally you will see 'LONGPOLL requested work restart..' every couple of seconds with p2pool. If you're not seeing that, it might be this long polling issue. I'd try with just one pool configured.
Second thing I'd look at is if the host running your p2pool daemon is not too overloaded.

Red Emerald

hero member

Activity: 742

Merit: 500

Quote from: spiccioli on February 02, 2012, 07:16:11 PM

Any idea?

What version of p2pool are you running? That looks like miner output. What does your p2pool output look like?

As has been said many times, stales in p2pool are higher than a traditional pool

spiccioli

legendary

Activity: 1378

Merit: 1003

nec sine labore

Quote from: spiccioli on February 02, 2012, 05:09:40 AM

Well, I've restarted p2pool this morning at 0900 GMT+1, tomorrow I'll let you know what numbers I see.

regards.

spiccioli

Here we are, 20 hours later,

Code:

09:35:21.192503 GOT SHARE! cccccc 2a50469e prev ee4e3887 age 28.24s DEAD ON ARRIVAL
10:51:29.609170 GOT SHARE! cccccc ae20489a prev f5036a0c age 22.39s DEAD ON ARRIVAL
11:00:45.274799 GOT SHARE! cccccc 7ae24ef4 prev b1d8d61a age 20.28s DEAD ON ARRIVAL
11:30:42.989054 GOT SHARE! cccccc 1fb89a27 prev 0af6c699 age 29.78s DEAD ON ARRIVAL
11:38:33.196739 GOT SHARE! cccccc 2ffce415 prev 2c561f75 age 20.60s DEAD ON ARRIVAL
12:20:52.215387 GOT SHARE! cccccc 2deeb628 prev 21ff2b7b age 13.81s DEAD ON ARRIVAL
13:40:47.230481 GOT SHARE! cccccc 1aef7202 prev 1c4d5fe3 age 20.82s
14:27:05.064232 GOT SHARE! cccccc 61749cce prev fc90b812 age 23.00s DEAD ON ARRIVAL
14:54:32.934686 GOT SHARE! cccccc bf2761d7 prev 36614893 age 23.06s
15:13:35.412215 GOT SHARE! cccccc 7981f9dc prev eab26f20 age 20.23s DEAD ON ARRIVAL
15:19:06.171630 GOT SHARE! cccccc f46aa885 prev f98f68d2 age 21.07s DEAD ON ARRIVAL
16:28:33.961269 GOT SHARE! cccccc a9dbaaf4 prev 4f3bac03 age 22.01s DEAD ON ARRIVAL
16:43:18.028367 GOT SHARE! cccccc b2ab8707 prev 881e93ba age 21.55s DEAD ON ARRIVAL
16:48:31.739828 GOT SHARE! cccccc 3231a5e2 prev 08075e20 age 34.50s DEAD ON ARRIVAL
17:11:56.867175 GOT SHARE! cccccc fd25a9bd prev 69d47462 age 26.91s DEAD ON ARRIVAL
17:26:35.194804 GOT SHARE! cccccc 640e9ebd prev 5c2e2221 age 11.85s
17:35:39.829151 GOT SHARE! cccccc 582b0db9 prev f452f2f8 age 16.75s
17:41:35.629520 GOT SHARE! cccccc bd41d585 prev 32818a48 age 33.79s DEAD ON ARRIVAL
17:48:58.909271 GOT SHARE! cccccc ee2d6b93 prev 47bb9cfa age 9.51s
19:13:12.722993 GOT SHARE! cccccc 8ef4140e prev a402ee4a age 11.58s DEAD ON ARRIVAL
19:13:50.677687 GOT SHARE! cccccc f09c4eab prev d0613a01 age 28.44s DEAD ON ARRIVAL
19:15:47.942192 GOT SHARE! cccccc f81a2d80 prev 59599851 age 16.00s DEAD ON ARRIVAL

something is wrong, isn't it? most are dead, and what does that "age" field really mean?

I'm using latest cgminer 2.2.1 on my miner, with I 7 (intensity) and just p2pool, I have a failover pool, to be honest, but with

Code:

"failover-only" : true

inside cgminer.conf.

Any idea?

best regards.

spiccioli.

Drsmite

newbie

Activity: 20

Merit: 0

Quote from: forrestv on February 01, 2012, 10:31:19 PM

Quote from: Drsmite on February 01, 2012, 08:08:43 PM

I am running the latest stable version of BTCMiner (https://bitcointalksearch.org/topic/btcminer-open-source-bitcoin-miner-for-ztex-fpga-boards-215-mhs-on-lx150-40047) pointed at P2Pool. After a few hours of running (I haven't been around when it fails) it throws an invalid length string exception and shuts down. After this happens whenever I try to restart the miner it seems to be ineffective and constantly reports that it detects a new block via long polling. To resolve it I have to kill and restart bitcoind, P2Pool, and BTCMiner. Is there anyone experiencing a similar error in their miners and odd P2Pool behavior?

BTCMiner's exact exception would be helpful in determining the problem - can you pastebin it somewhere? I can't test it as I have no FPGA miner..

Here is the last segment of BTCMiner's output:

Code:

ztex_ufm1_15d2-04A32E1A6F: f=204.00MHz,  errorRate=0.00%,  maxErrorRate=0.54%,  hash rate: 204.0MH/s,  submitted 0 new nonces,  submitted hash rate 198.5MH/s
New block detected by long polling
New block detected by long polling
ztex_ufm1_15d2-04A32E1A6F: f=204.00MHz,  errorRate=0.00%,  maxErrorRate=0.54%,  hash rate: 204.0MH/s,  submitted 4 new nonces,  submitted hash rate 199.1MH/s
New block detected by long polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
ztex_ufm1_15d2-04A32E1A6F: f=204.00MHz,  errorRate=0.23%,  maxErrorRate=0.54%,  hash rate: 203.5MH/s,  submitted 0 new nonces,  submitted hash rate 199.0MH/s
New block detected by long polling
Exception in thread "Thread-0" java.lang.NumberFormatException: Invalid length of string
	at BTCMiner.hexStrToData(BTCMiner.java:695)
	at NewBlockMonitor.run(BTCMiner.java:159)
ztex_ufm1_15d2-04A32E1A6F: Error: Invalid length of string: Disabling device

The new block detected message is pretty much constant at all times.

Edit for relevant sections from the BTCMiner code:

Line 159

Code:

BTCMiner.hexStrToData(BTCMiner.jsonParse(BTCMiner.bitcoinRequest(this, BTCMiner.longPollURL, BTCMiner.longPollUser, BTCMiner.longPollPassw, "getwork", ""), "data"), dataBuf);

Line 693-699

Code:

public static void hexStrToData( String str, byte[] buf ) throws NumberFormatException {
	if ( str.length()	    throw new NumberFormatException("Invalid length of string");
	for ( int i=0; i	    buf[i] = (byte) Integer.parseInt( str.substring(i*2,i*2+2), 16);
	}
    }

JSON Parse method

Code:

 public static String jsonParse (String response, String parameter) throws ParserException {
	int lp = parameter.length();
	int i = 0;
	while ( i+lp	    i++;
	i+=lp;
	if ( i>=response.length() )
	    throw new ParserException( "jsonParse: Parameter `"+parameter+"' not found" );
	while ( i	    i++;
	i+=1;
	while ( i	    i++;
	if ( i>=response.length() )
	    throw new ParserException( "jsonParse: Value expected after `"+parameter+"'" );
	int j=i;
	if ( i	    i+=1;
	    j=i;
	    while ( j		j++;
	    if ( j>=response.length() )
		throw new ParserException( "jsonParse: No closing `\"' found for value of paramter `"+parameter+"'" );
	}
	else { 
	    while ( j		j++;
	}
	return response.substring(i,j);
    }

Bitcoin request call

Code:

public static String bitcoinRequest( MsgObj msgObj, String url, String user, String passw, String request, String params) throws MalformedURLException, IOException {
	bcid += 1;
	return httpGet( msgObj, url, user, passw, "{\"jsonrpc\":\"1.0\",\"id\":" + bcid + ",\"method\":\""+ request + "\",\"params\":["+ (params.equals("") ? "" : ("\""+params+"\"")) + "]}" );
    }

The source is available here http://www.ztex.de/btcminer/ and I am running release 120126
It appears the getwork call to P2Pool is returning fewer bytes than expected.

someone703

full member

Activity: 928

Merit: 101

Quote from: ?? on ??

Sorry, P2Pool has been updated and I missed that part of the instructions. Here is the new step 10.

10. Extract p2pool from ~~p2pool_win32_1685a89.zip~~ p2pool_win32_592ceea.zip.

All this means is unzip the P2Pool file that you've downloaded so that you can run P2Pool.

You should try cgminer, ask Rassah. Wink

Edit: Updated again with the new P2Pool file.

Haha, no problem. Earlier in that post you did link the right zip file I believe. I got P2Pool running and connected just fine. Saw that it had some 155 Ghash/s or so in the messages that scroll by in the command prompt.

Also, I saw mention of updating Git Head or something. What's that? Is that necessary?

And yeah, I've had several people tell me to get cgminer cause GUIMiner is old... Is there no way of using GUIMiner with P2Pool since I've already got it set up at the moment?

Qoheleth

legendary

Activity: 960

Merit: 1028

Spurn wild goose chases. Seek that which endures.

Quote from: cheat_2_win on February 02, 2012, 02:18:28 PM

Quote from: Qoheleth on February 02, 2012, 01:55:05 PM

Haven't received a payout for two days. Is this just another block drought or is something wrong with my setup?
I'm seeing 156GH/s so I'm not on the split chain.

If you check your address at blockexplorer.com, you will see if you have received any payout. If it shows balance in your p2pool address, then just wait from 120 confirmations. Otherwise Huh

Nah, I'm looking at blockexplorer directly and the last Generation was Block 164634 two days ago.

cheat_2_win

full member

Activity: 215

Merit: 100

Quote from: Qoheleth on February 02, 2012, 01:55:05 PM

Haven't received a payout for two days. Is this just another block drought or is something wrong with my setup?
I'm seeing 156GH/s so I'm not on the split chain.

If you check your address at blockexplorer.com, you will see if you have received any payout. If it shows balance in your p2pool address, then just wait from 120 confirmations. Otherwise Huh

Vanderbleek

sr. member

Activity: 518

Merit: 250

Quote from: Qoheleth on February 02, 2012, 01:55:05 PM

Haven't received a payout for two days. Is this just another block drought or is something wrong with my setup?
I'm seeing 156GH/s so I'm not on the split chain.

Since the transactions count as mined, you need 120 confirms for them to show up -- could that be why you're not seeing them?

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