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

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: PatMan on February 10, 2013, 08:14:21 AM

On other pools I can mine with stratum @ 1100% + efficiency, but stratum here is @ 350% on a good day, with constant stratum disconnects/restarts.

Please do not place any value whatsoever on the efficiency figure as it's virtually meaningless with stratum, and expected to be lower with frequent block updates of p2pool - and does NOT correlate with luck, performance, payment, value, btc, or anything.

If you do get disconnects and restarts, though, that is a totally different issue.

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Ed

member

Activity: 69

Merit: 10

Quote from: forrestv on February 06, 2013, 06:16:43 PM

P2Pool release 11.2 ....

thank you

can someone explain, why 7 days luck chart trend was broken?
last time it happened when block value is halved

lenny_

legendary

Activity: 1036

Merit: 1000

DARKNETMARKETS.COM

Thanks. I tried it, working very well - but ONLY with getwork.
When this bug with Stratum will be finally fixed? I cannot connect my Stratum Mining Proxy to any p2pool.
AFAIR Slush said that's bug in p2pool, not in his proxy.

Ztex BTCMiner reporting when connected to Stratum Mining Proxy:

Code:

ztex_ufm1_15y1-04A3461AD9-4: Using LongPolling URL http://localhost:4617/lp
ztex_ufm1_15y1-04A3461AD9-4: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-3: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-2: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s
ztex_ufm1_15y1-04A3461AD9-1: Error: jsonParse: Parameter `data' not found: Disabling URL http://localhost:4617 for 60s

Stratum Mining Proxy reporting when connected to p2pool-cologne.dyndns.org:9332:

Code:

$ python ~/stratum-mining-proxy/mining_proxy.py -gp 4617 -sp 4618 -rt -oh localhost -o p2pool-cologne.dyndns.org -p 9332
2013-02-10 08:09:05,284 INFO proxy jobs. # Using C extension for midstate speedup. Good!
2013-02-10 08:09:05,939 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
  File "/home/pioruns/stratum-mining-proxy/mining_proxy.py", line 154, in main
    new_host = (yield utils.detect_stratum(args.host, args.port))
  File "/usr/local/lib/python2.6/dist-packages/Twisted-12.2.0-py2.6-linux-x86_64.egg/twisted/internet/defer.py", line 1045, in _inlineCallbacks
    result = g.send(result)
  File "/home/pioruns/stratum-mining-proxy/mining_libs/utils.py", line 69, in detect_stratum
    header = f.response_headers.get('x-stratum', None)[0]
TypeError: 'NoneType' object is unsubscriptable
2013-02-10 08:09:05,943 WARNING proxy mining_proxy.main # Stratum proxy version: 1.3.0
2013-02-10 08:09:05,944 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at p2pool-cologne.dyndns.org:9332
2013-02-10 08:09:06,056 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-02-10 08:09:06,057 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at p2pool-cologne.dyndns.org:9332
2013-02-10 08:09:06,058 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-02-10 08:09:06,141 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2013-02-10 08:09:06,142 WARNING proxy mining_proxy.main # LISTENING FOR MINERS ON http://localhost:4617 (getwork) and stratum+tcp://0.0.0.0:4618 (stratum)
2013-02-10 08:09:06,143 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2013-02-10 08:09:06,146 INFO proxy client_service.handle_event # Setting new difficulty: 1.25145617624
2013-02-10 08:09:06,213 INFO proxy client_service.handle_event # New job 325955743810929301480796180155202751669 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:26,362 INFO proxy client_service.handle_event # Setting new difficulty: 1.18215669878
2013-02-10 08:09:26,799 INFO proxy client_service.handle_event # New job 269997156551243822103854752532703491497 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:34,703 INFO proxy client_service.handle_event # Setting new difficulty: 1.09734043353
2013-02-10 08:09:34,968 INFO proxy client_service.handle_event # New job 73858452078503214942533707870333976939 for prevhash d9371e22, clean_jobs=True
^[OH^[OH2013-02-10 08:09:54,593 INFO proxy client_service.handle_event # Setting new difficulty: 1.09616051031
2013-02-10 08:09:54,670 INFO proxy client_service.handle_event # New job 321835293524890064476778311031875755101 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:09:56,307 INFO proxy client_service.handle_event # Setting new difficulty: 1.03434332373
2013-02-10 08:09:56,416 INFO proxy client_service.handle_event # New job 273423769805879948480669006224757885078 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:00,896 INFO proxy client_service.handle_event # Setting new difficulty: 1.06754432673
2013-02-10 08:10:01,047 INFO proxy client_service.handle_event # New job 81720095736822856709879056879847550243 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:05,357 INFO proxy client_service.handle_event # Setting new difficulty: 1.07267594408
2013-02-10 08:10:05,627 INFO proxy client_service.handle_event # New job 236633676678111076937776131695314696685 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:11,155 INFO proxy client_service.handle_event # Setting new difficulty: 1.10580012625
2013-02-10 08:10:11,309 INFO proxy client_service.handle_event # New job 126088639858383928803852013588898765095 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,094 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,171 INFO proxy client_service.handle_event # New job 338531295106564500565665242810625478384 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,218 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,285 INFO proxy client_service.handle_event # New job 98321113877270917104872120611515544998 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,332 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,366 INFO proxy client_service.handle_event # New job 240149389807169797691884903318242084252 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:16,429 INFO proxy client_service.handle_event # Setting new difficulty: 1.08505565922
2013-02-10 08:10:16,479 INFO proxy client_service.handle_event # New job 119193302466034592597267511360171587748 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:17,982 WARNING proxy getwork_listener.render_POST # Worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo' subscribed for LP
2013-02-10 08:10:24,659 INFO proxy client_service.handle_event # Setting new difficulty: 1.00851885059
2013-02-10 08:10:24,728 INFO proxy client_service.handle_event # New job 172222459887028084567777385883242931397 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:24,729 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo'
2013-02-10 08:10:24,730 INFO proxy jobs.extranonce2_padding # Extranonce size mismatch. Please report this error to pool operator!
2013-02-10 08:10:24,768 WARNING proxy getwork_listener.render_POST # Worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo' subscribed for LP
2013-02-10 08:10:33,666 INFO proxy client_service.handle_event # Setting new difficulty: 0.999984741211
2013-02-10 08:10:34,198 INFO proxy client_service.handle_event # New job 83422292320684236540679450563292946587 for prevhash d9371e22, clean_jobs=True
2013-02-10 08:10:34,199 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker '15Um8SwbDpNMvnp8zKCHzx6mpS6p8AWAAo'
2013-02-10 08:10:34,200 INFO proxy jobs.extranonce2_padding # Extranonce size mismatch. Please report this error to pool operator!

Result - cannot mine on stratum protocol at all. I reported this problem here #4319.

Subo1977

sr. member

Activity: 344

Merit: 250

Flixxo - Watch, Share, Earn!

Quote from: lenny_ on February 09, 2013, 10:38:37 PM

Can somebody give me node addresses, which are stable 24/7 on good internet and fast server? I would like to give it a try with Stratum miner.
http://nodes.p2pmine.com/ doesn't seem to be working.

http://p2pool-cologne.dyndns.org:9332

lenny_

legendary

Activity: 1036

Merit: 1000

DARKNETMARKETS.COM

Can somebody give me node addresses, which are stable 24/7 on good internet and fast server? I would like to give it a try with Stratum miner.
http://nodes.p2pmine.com/ doesn't seem to be working.

forrestv

hero member

Activity: 516

Merit: 643

P2Pool release 11.2 hash: 6ff320bf4ddfc735ea34ad30e0eab954f9bbaa69

Windows binary: http://u.forre.st/u/rliakpxs/p2pool_win32_11.2.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/11.2
Source tarball: https://github.com/forrestv/p2pool/tarball/11.2

Changes:
* Fixed a major memory leak of peer objects, as far as I know the cause of all P2Pool memory issues recently. Found by Prattler, whose donation address is 18uyCqDvP6VQUeyTuA5s6x1Ft8x8om767J:

Quote

[19:39:11] Memory leak solved!

[19:39:12] https://github.com/forrestv/p2pool/pull/81
[19:41:44] donations accepted at 18uyCqDvP6VQUeyTuA5s6x1Ft8x8om767J - I spent many hours tracking it down

* Fixed a minor memory leak of peer objects

neosniperkiller

newbie

Activity: 8

Merit: 0

Quote from: mdude77 on January 30, 2013, 05:20:02 PM

At 21.4mh, it's going to take a LONG time to find a share. If you check the p2pool output, it'll tell you the average time it'll take. Wildly guessing, maybe 1/2 a day.

M

Thanks for the info, I just saw the mentioning of TIME TO SHARE in the same block of text that keeps on reappearing in the terminal.
Indeed it takes some time +- 10.5 hours... nvidia laptop gpu...

Quote from: twmz

There are two different kinds of shares. Your miner reports finding pseudo shares that are typically difficulty 1. P2Pool's console output is reporting real shares that are difficulty in the hundreds. Most pseudo shares are not real shares. As someone else mentioned, the p2pool console output also includes a line that estimates how long (on average) it will take to find a real share based on your recent hashrate. For the record, you are wasting time mining with only 21.4 MH/s or at least wasting electricity and money even if you are doing this just for fun. It will take you an insane amount of time to find a share and your earnings will not outweigh the costs of your mining.

Alt-coin merged mining is not pooled. When you find an entire block based on your own mining effort, that payment will appear in your alt coin client just as if you were solo mining that alt-coin.

Thanks for the more detailed information!
I know about the loss of costs, but I did this to test the p2pool to see if it actually runs on my local network.

twmz

hero member

Activity: 737

Merit: 500

Quote from: neosniperkiller on January 30, 2013, 03:02:33 PM

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0000 BTC"

...

Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?

There are two different kinds of shares. Your miner reports finding pseudo shares that are typically difficulty 1. P2Pool's console output is reporting real shares that are difficulty in the hundreds. Most pseudo shares are not real shares. As someone else mentioned, the p2pool console output also includes a line that estimates how long (on average) it will take to find a real share based on your recent hashrate. For the record, you are wasting time mining with only 21.4 MH/s or at least wasting electricity and money even if you are doing this just for fun. It will take you an insane amount of time to find a share and your earnings will not outweigh the costs of your mining.

Quote from: neosniperkiller on January 30, 2013, 03:02:33 PM

Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.

Alt-coin merged mining is not pooled. When you find an entire block based on your own mining effort, that payment will appear in your alt coin client just as if you were solo mining that alt-coin.

mdude77

legendary

Activity: 1540

Merit: 1001

At 21.4mh, it's going to take a LONG time to find a share. If you check the p2pool output, it'll tell you the average time it'll take. Wildly guessing, maybe 1/2 a day.

M

Quote from: neosniperkiller on January 30, 2013, 03:02:33 PM

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0000 BTC"

== phoenix

Now I tried to mine on it using phoenix and it can connect to the p2pool.
But somehow when phoenix says "result accepted", nothing is displayed in the p2pool concerning that result.

== bfgminer

Second try was with bfgminer, see stats below, but still nothing changed at the p2pool overview.

[2013-01-30 20:41:44] Started at [2013-01-30 20:29:46]
[2013-01-30 20:41:44] Pool: http://192.168.1.4:9332
[2013-01-30 20:41:44] Runtime: 0 hrs : 11 mins : 55 secs
[2013-01-30 20:41:44] Average hashrate: 21.4 Megahash/s
[2013-01-30 20:41:44] Solved blocks: 0
[2013-01-30 20:41:44] Best share difficulty: 1
[2013-01-30 20:41:44] Queued work requests: 82
[2013-01-30 20:41:44] Share submissions: 5
[2013-01-30 20:41:44] Accepted shares: 5
[2013-01-30 20:41:44] Rejected shares: 0
[2013-01-30 20:41:44] Accepted difficulty shares: 5
[2013-01-30 20:41:44] Rejected difficulty shares: 0
[2013-01-30 20:41:44] Reject ratio: 0.0%
[2013-01-30 20:41:44] Hardware errors: 0
[2013-01-30 20:41:44] Efficiency (accepted shares * difficulty / 2 KB): 0.01
[2013-01-30 20:41:44] Utility (accepted shares / min): 0.42/min

[2013-01-30 20:41:44] Discarded work due to new blocks: 197
[2013-01-30 20:41:44] Stale submissions discarded due to new blocks: 0
[2013-01-30 20:41:44] Unable to get work from server occasions: 0
[2013-01-30 20:41:44] Work items generated locally: 431
[2013-01-30 20:41:44] Submitting work remotely delay occasions: 0
[2013-01-30 20:41:44] New blocks detected on network: 1

Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?
Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.

neosniperkiller

newbie

Activity: 8

Merit: 0

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0000 BTC"

== phoenix

Now I tried to mine on it using phoenix and it can connect to the p2pool.
But somehow when phoenix says "result accepted", nothing is displayed in the p2pool concerning that result.

== bfgminer

Second try was with bfgminer, see stats below, but still nothing changed at the p2pool overview.

[2013-01-30 20:41:44] Started at [2013-01-30 20:29:46]
[2013-01-30 20:41:44] Pool: http://192.168.1.4:9332
[2013-01-30 20:41:44] Runtime: 0 hrs : 11 mins : 55 secs
[2013-01-30 20:41:44] Average hashrate: 21.4 Megahash/s
[2013-01-30 20:41:44] Solved blocks: 0
[2013-01-30 20:41:44] Best share difficulty: 1
[2013-01-30 20:41:44] Queued work requests: 82
[2013-01-30 20:41:44] Share submissions: 5
[2013-01-30 20:41:44] Accepted shares: 5
[2013-01-30 20:41:44] Rejected shares: 0
[2013-01-30 20:41:44] Accepted difficulty shares: 5
[2013-01-30 20:41:44] Rejected difficulty shares: 0
[2013-01-30 20:41:44] Reject ratio: 0.0%
[2013-01-30 20:41:44] Hardware errors: 0
[2013-01-30 20:41:44] Efficiency (accepted shares * difficulty / 2 KB): 0.01
[2013-01-30 20:41:44] Utility (accepted shares / min): 0.42/min

[2013-01-30 20:41:44] Discarded work due to new blocks: 197
[2013-01-30 20:41:44] Stale submissions discarded due to new blocks: 0
[2013-01-30 20:41:44] Unable to get work from server occasions: 0
[2013-01-30 20:41:44] Work items generated locally: 431
[2013-01-30 20:41:44] Submitting work remotely delay occasions: 0
[2013-01-30 20:41:44] New blocks detected on network: 1

Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?
Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.

lenny_

legendary

Activity: 1036

Merit: 1000

DARKNETMARKETS.COM

Quote from: forrestv on January 28, 2013, 11:52:11 AM

Lenny, simply upgrading to the most recent commit in git will help. I think that 11.1-6-g19bf4ea solves the leak.

Indeed, it holds for 382 MB for whole day and even decreasing over time. Thank you forrestv!

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: K1773R on January 29, 2013, 03:22:32 AM

Quote from: rav3n_pl on January 29, 2013, 03:08:23 AM

Also I still thinks, that txes should be sent on demand, not to all connected nodes. "Peer sent entire transaction..." is seen too many times in log...

on demand -> ask if he knows the TX, if he says no send the TX to him.

I think about:
- received new share -> check txes it contains
- have all tx -> noop
- not have some txes -> ask for them node that send share
- node not send back tx in 2-5 sec -> check local bitcoin again -> ask another node/s if need

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: rav3n_pl on January 29, 2013, 03:08:23 AM

Quote from: forrestv on January 25, 2013, 03:37:28 PM

I believe the memory leak is fixed in git. Can everyone who can pull and notify me if memory is still leaking?

Version: 11.1-6-g19bf4ea
Ubuntu 64bit 4GB
When I run it on "old" sharechain (over 24hrs offline) it bumps to about 520MB
When I delete share chain and allow to re download, it walks to about 300MB and holds there.

There is still something wrong in chain handling imo (maybe txes are not cleared?).
Maybe add a check - if node starts over 12hrs after last share in chain delete it completely and redownload?

Also I still thinks, that txes should be sent on demand, not to all connected nodes. "Peer sent entire transaction..." is seen too many times in log...

on demand -> ask if he knows the TX, if he says no send the TX to him.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: forrestv on January 25, 2013, 03:37:28 PM

I believe the memory leak is fixed in git. Can everyone who can pull and notify me if memory is still leaking?

Version: 11.1-6-g19bf4ea
Ubuntu 64bit 4GB
When I run it on "old" sharechain (over 24hrs offline) it bumps to about 520MB
When I delete share chain and allow to re download, it walks to about 300MB and holds there.

There is still something wrong in chain handling imo (maybe txes are not cleared?).
Maybe add a check - if node starts over 12hrs after last share in chain delete it completely and redownload?

Also I still thinks, that txes should be sent on demand, not to all connected nodes. "Peer sent entire transaction..." is seen too many times in log...

Rogue Star

member

Activity: 89

Merit: 10

Quote from: forrestv on January 28, 2013, 11:52:11 AM

Lenny, simply upgrading to the most recent commit in git will help. I think that 11.1-6-g19bf4ea solves the leak.

I'm still seeing the leak on my node on the latest code, so you might want to check that out when you get a chance. Another odd thing I noticed on the stats page is it is showing solved blocks >24 hours old

cabin

sr. member

Activity: 604

Merit: 250

Ok thanks that makes sense. No I don't see it often at all.. maybe just a few times right after I start p2pool.

Quote from: forrestv on January 28, 2013, 11:52:11 AM

Quote from: lenny_ on January 27, 2013, 08:44:29 PM

forrestv, what I can do for you to help debugging?

Lenny, simply upgrading to the most recent commit in git will help. I think that 11.1-6-g19bf4ea solves the leak.

Quote from: cabin on January 28, 2013, 09:16:40 AM

Regarding this message: Punishing share for 'not all txs present'!

Does this mean that nodes that don't include all transactions will have their shares punished and therefore more likely to be orphaned?

No, the "not all txs present" punishment is for when a share isn't accompanied by all the transactions it says it contains (as opposed to all the transactions it could possibly contain). Are you seeing it a lot? That message should be very rare.

forrestv

hero member

Activity: 516

Merit: 643

Quote from: lenny_ on January 27, 2013, 08:44:29 PM

forrestv, what I can do for you to help debugging?

Lenny, simply upgrading to the most recent commit in git will help. I think that 11.1-6-g19bf4ea solves the leak.

Quote from: cabin on January 28, 2013, 09:16:40 AM

Regarding this message: Punishing share for 'not all txs present'!

Does this mean that nodes that don't include all transactions will have their shares punished and therefore more likely to be orphaned?

No, the "not all txs present" punishment is for when a share isn't accompanied by all the transactions it says it contains (as opposed to all the transactions it could possibly contain). Are you seeing it a lot? That message should be very rare.

cabin

sr. member

Activity: 604

Merit: 250

Regarding this message: Punishing share for 'not all txs present'!

Does this mean that nodes that don't include all transactions will have their shares punished and therefore more likely to be orphaned?

twmz

hero member

Activity: 737

Merit: 500

FYI, I broke something with one of the servers that sit behind p2pool.info this weekend and the result was it was mis-reporting some blocks as orphaned (that weren't really orphaned). It's being fixed now...

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