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

gyverlb

hero member

Activity: 896

Merit: 1000

Quote from: lenny_ on May 15, 2013, 07:21:50 PM

Code:

2013-05-16 01:21:45.157251 Worker xxx submitted share with hash > target:
2013-05-16 01:21:45.157521     Hash:   29ce8ec59713ce17ce3eff6d5c1c7a739c899eb0d00d262954c94b999fc0c4c1
2013-05-16 01:21:45.157684     Target: 366ac93b2b0cc6000000000000000000000000000000000000000000
2013-05-16 01:21:45.351318 Worker xxx submitted share with hash > target:
2013-05-16 01:21:45.351516     Hash:   8b5a09376fa6abcc7264fd3a78824904931bef81283a7018e98d287f83c6a6b6
2013-05-16 01:21:45.351679     Target: 366ac93b2b0cc6000000000000000000000000000000000000000000
2013-05-16 01:21:45.586972 Worker xxx submitted share with hash > target:
2013-05-16 01:21:45.587226     Hash:   5d60d0ec5860697a415cb3fed8bbc89b8a0e0679df59ceae01361a25a78364d
2013-05-16 01:21:45.588938     Target: 366ac93b2b0cc6000000000000000000000000000000000000000000

I tried to connect Blade Erupter 13GH/s to p2pool directly by typing localhost:9332 in it's settings.
That's what I am getting on p2pool log.
How to fix it?

The log itself is harmless and may mean that the Erupter doesn't support dynamic difficulty (surprising) or that it is overclocked too much and output errors (more likely given the very high values of the hash in your log).

If it's an hardware problem, cool the blade more or slow it down.
If it's variable difficulty support missing or buggy and the rate of share submission puts too much load on your p2pool node, you could try using slush's stratum proxy between the blade and the node to lower the load on it.

lenny_

legendary

Activity: 1036

Merit: 1000

DARKNETMARKETS.COM

Code:

2013-05-16 01:21:45.157251 Worker xxx submitted share with hash > target:
2013-05-16 01:21:45.157521     Hash:   29ce8ec59713ce17ce3eff6d5c1c7a739c899eb0d00d262954c94b999fc0c4c1
2013-05-16 01:21:45.157684     Target: 366ac93b2b0cc6000000000000000000000000000000000000000000
2013-05-16 01:21:45.351318 Worker xxx submitted share with hash > target:
2013-05-16 01:21:45.351516     Hash:   8b5a09376fa6abcc7264fd3a78824904931bef81283a7018e98d287f83c6a6b6
2013-05-16 01:21:45.351679     Target: 366ac93b2b0cc6000000000000000000000000000000000000000000
2013-05-16 01:21:45.586972 Worker xxx submitted share with hash > target:
2013-05-16 01:21:45.587226     Hash:   5d60d0ec5860697a415cb3fed8bbc89b8a0e0679df59ceae01361a25a78364d
2013-05-16 01:21:45.588938     Target: 366ac93b2b0cc6000000000000000000000000000000000000000000

I tried to connect Blade Erupter 13GH/s to p2pool directly by typing localhost:9332 in it's settings.
That's what I am getting on p2pool log.
How to fix it?

gyverlb

hero member

Activity: 896

Merit: 1000

Quote from: labsbitforum on May 15, 2013, 04:16:11 PM

Update. I think I figured out what was going on. I had limited the connections on bitcoin-qt.exe to 6 to keep latencies low. I think what was happening is the 6 connection were getting taken up before I started P2Pool. Strange as I've never had the problem before. I loosened the connections to 10 and started P2Pool right after the bitcoin client loaded. Prior to that I always let the bitcoin client load and get all caught up prior to starting P2Pool. Its working now. Posting back in case this trips someone else up.

I was about to reply to your previous message with this suggestion.

For reference, I had to configure some of my *coind with 20 connections to make sure P2Pool can connect, I had problems with some alt-coins at 10 and 15.

labsbitforum

member

Activity: 99

Merit: 10

Quote from: labsbitforum on May 15, 2013, 01:11:02 PM

Been running P2Pool for weeks now. On version 11.4. Last night windows update ran and now I cant get P2Pool to start. I just sits at

Quote

Testing bitcoind P2P connection to '127.0.0.1:8333' ...

Tried these so far and nothing:
Turned off windows firewall
rolled back windows updates

Any ideas what might be up? It seemed like bitcoin-qt.exe went too fast catching up on the 50 blocks it missed. I watched it take a minute or two to get through the first 5 missed blocks and then it jumped to caught up right away. I had another bitcoin-qt.exe on a separate computer catching up as well and that one took several more minutes to finish getting the 50 missed blocks since 3am when they all rebooted. Any ideas on what to check next?

Update. I think I figured out what was going on. I had limited the connections on bitcoin-qt.exe to 6 to keep latencies low. I think what was happening is the 6 connection were getting taken up before I started P2Pool. Strange as I've never had the problem before. I loosened the connections to 10 and started P2Pool right after the bitcoin client loaded. Prior to that I always let the bitcoin client load and get all caught up prior to starting P2Pool. Its working now. Posting back in case this trips someone else up.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: hendo420 on May 15, 2013, 03:06:42 PM

I apologize if this has been asked before, if there is an answer somewhere in the 200+ pages please link me.

How do i get this to work with scrypt coins? I can easily get it working with bitcoin but not litecoin or any other variation.

I believe it's in the readme. I found compiling the latest get to be difficult for litecoin, but if you don't need/want that, the executable works just fine.

M

hendo420

sr. member

Activity: 420

Merit: 250

I apologize if this has been asked before, if there is an answer somewhere in the 200+ pages please link me.

How do i get this to work with scrypt coins? I can easily get it working with bitcoin but not litecoin or any other variation.

labsbitforum

member

Activity: 99

Merit: 10

Been running P2Pool for weeks now. On version 11.4. Last night windows update ran and now I cant get P2Pool to start. I just sits at

Quote

Testing bitcoind P2P connection to '127.0.0.1:8333' ...

Tried these so far and nothing:
Turned off windows firewall
rolled back windows updates

Any ideas what might be up? It seemed like bitcoin-qt.exe went too fast catching up on the 50 blocks it missed. I watched it take a minute or two to get through the first 5 missed blocks and then it jumped to caught up right away. I had another bitcoin-qt.exe on a separate computer catching up as well and that one took several more minutes to finish getting the 50 missed blocks since 3am when they all rebooted. Any ideas on what to check next?

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: GrapeApe on May 14, 2013, 01:44:47 PM

I've never gotten one of these before.

[2013-05-14 08:57:17] Accepted 000055bf Diff 196K/1 GPU 0 pool 0

Just means your share has a high difficulty.
On p2pool that's the same as a normal required difficulty share in terms of payment.
Though the information is useful to show you that indeed that share is high enough for the share chain.

The only pool that this makes a difference is the OzCoin Pay on Target pool.
e.g. [2013-05-13 01:44:55] Accepted 0000103e Diff 1.03M/256 BAJ 0 pool 0
That was worth $10

But on another pool:
[2013-05-04 02:24:44] Accepted 00000222 Diff 7.86M/12 BAJ 0 pool 2
that was worth ... 1 share Sad

GrapeApe

sr. member

Activity: 476

Merit: 250

I've never gotten one of these before.

[2013-05-14 08:57:17] Accepted 000055bf Diff 196K/1 GPU 0 pool 0

mokahless

sr. member

Activity: 471

Merit: 256

Is anyone else getting errors like:

Quote

2013-05-13 22:24:44.834000 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind

in the new 11.4 and are stuck with p2pool not accepting any shares?

as in:

Quote

2013-05-13 22:27:02.755000 Local: 0H/s in last 0.0 seconds Local dead on arrival: ?? ? Expected time to sh
are: ?? ?
2013-05-13 22:27:02.755000 Shares: 0 (0 orphan, 0 dead) Stale rate: ?? ? Efficiency: ?? ? Current payout: 0
.0000 BTC

I'm testing again by copying over all my old data to the the data dir in the new p2pool folder but I'm not sure. I'm also going to try running it for longer.

FYI: windows pre-compiled, doing merged mining with namecoind and I am also continually getting:

Quote

2013-05-13 22:27:05.797000 Processing 23 shares from 71.39.52.34:9335...
2013-05-13 22:27:13.082000 > Error while processing Event callbacks:
2013-05-13 22:27:13.082000 > Traceback (most recent call last):
2013-05-13 22:27:13.082000 > File "p2pool\node.pyc", line 289, in set_best_share

with a whole bunch of lines listed as per the last line.

Edit: watching it. The graph shows my hashrate and that seems to be working fine. Still no shares (0, 0 orphan, 0 dead) and I got a few "punishing share for block-stale detected". Not sure what those are. Also got some "twisted.internet.connectionlost" and something about being disconnected locally. My "dead" on the graph spiked once to 100% for 1 tick. Other oddities include only one incoming peer, when I limited to 8/8. 11.1 immediately connected to at least 3-4 and eventually to 8.

Edit, Edit: So I do have a number under "payout if block were found NOW" so I am thinking everything is working fine, regardless of these weird errors. I understand there are to be errors normally but I was worried since there were errors I was not getting in 11.1

GrapeApe

sr. member

Activity: 476

Merit: 250

"so you've never downloaded the complete share chain?

unless your p2pool is on a ramdrive and not backed up, you shouldnt be downloading the entire share chain every time you restart (unless it's been ~2 days since you last ran it)"

Yep every time I restart p2p it downloads the shares. I am just running p2p through the ubuntu terminal using "python run_p2p.py" command. I am new to mining and ubuntu so if I'm doing something wrong let me know.

I get an error when I try to make install. So I’ve just been inputting my parameters into the terminal and running python run_p2p.py.This is all very new to me. I have the dependencies.But yes I do download the share chain every time I start p2p.

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: GrapeApe on May 11, 2013, 03:19:51 PM

Quote from: rav3n_pl on May 11, 2013, 03:14:45 PM

Quote from: GrapeApe on May 11, 2013, 03:09:27 PM

I've been getting this today "GOT INCOMPLETE BLOCK FROM PEER"
Any clues???

It is normal and harmless when you restart node and download share chain.

I've done that a few times and my miner keeps telling me lost connection at " blah blah" when p2p hangs before it tells me got incomplete block.

p2p freezes says processing shares from blah blah, my cpu spikes to 100% (python), a minute or two later the incomplete message and then my miner is disconnected.

so you've never downloaded the complete share chain?

unless your p2pool is on a ramdrive and not backed up, you shouldnt be downloading the entire share chain every time you restart (unless it's been ~2 days since you last ran it)

GrapeApe

sr. member

Activity: 476

Merit: 250

Quote from: rav3n_pl on May 11, 2013, 03:14:45 PM

Quote from: GrapeApe on May 11, 2013, 03:09:27 PM

I've been getting this today "GOT INCOMPLETE BLOCK FROM PEER"
Any clues???

It is normal and harmless when you restart node and download share chain.

I've done that a few times and my miner keeps telling me lost connection at " blah blah" when p2p hangs before it tells me got incomplete block.

p2p freezes says processing shares from blah blah, my cpu spikes to 100% (python), a minute or two later the incomplete message and then my miner is disconnected.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: GrapeApe on May 10, 2013, 03:37:17 PM

Now that it's been brought up (by me). What are the shares.xx files?

This is our share chain.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: GrapeApe on May 11, 2013, 03:09:27 PM

I've been getting this today "GOT INCOMPLETE BLOCK FROM PEER"
Any clues???

It is normal and harmless when you restart node and download share chain.

GrapeApe

sr. member

Activity: 476

Merit: 250

I've been getting this today "GOT INCOMPLETE BLOCK FROM PEER"
Any clues???

GrapeApe

sr. member

Activity: 476

Merit: 250

I screwed up somehow. I had everything running great and started messing around and somehow now when I start p2pool it doesn’t load the shares it says 0 shares verified. In the data/bitcoin folder the shares.xx files are missing (I'm sure I'm at fault here) and when I download a new copy of p2p no new ones are created when I start it.
I just said in a previous post if it isn’t broke don’t fix it.

NEVERMIND: It seems to have worked itself out.I'm turning everything on and leaving it alone.....

EDIT:
Now that it's been brought up (by me). What are the shares.xx files?

hexed

newbie

Activity: 44

Merit: 0

Quote from: GrapeApe on May 09, 2013, 11:18:46 PM

Quote from: hexed on May 09, 2013, 04:52:11 PM

Sorry if this has been explained before but many people in the past couple of pages have been saying they are getting 200..400..600MHash/s. Is that correct? I thought mining with a single video card would be producing KHash/s and not MHash/s like bitcoin.

Currently I have:

AMD 7970: ~600KHash/s
AMD 7870: ~350KHash/s
AMD 5870: ~350KHash/s.

Technically I am running ~1.3MHash/s now.. so I doubt someone with a AMD 7770 is getting 200MHash/s but maybe I am totally missing out. Moved from bitcoin mining to Litecoin yesterday. Started with notroll pool but realized they have major issues paying out but in less than a day I got 2 LTC which seems about right.

..and of course after checking the litecoin calculator I come up with ~470 LTC a day if you ran 200MHash/s.. so I'm 99.9999% sure everyone else is misspeaking.

I am p2pool mining BTC with an AMD 7770 and I am getting 220 MHash/s. I was getting 200 I got 20 more after a few tweaks in cgminer. I am also curious about what other people are getting with this card and what they are doing for said results.

Well don't I feel like an idiot. My bad, I forgot that P2Pool allows all the different cryptocurrencies. I am mining LTC and seems that everyone else is talking about BTC. I followed this link directly from a Litecoin pool comparison chart.

...carry on

gyverlb

hero member

Activity: 896

Merit: 1000

Quote from: forrestv on May 09, 2013, 12:37:19 PM

What kind of "latency issues" were you having? High "Bitcoin Getwork Latency" or low efficiency? The former doesn't matter too much.

In my experience, "Bitcoin Getwork Latency" starts to impact efficiency negatively when it reaches the [0.10s, 0.20s] range and things start to get ugly above that.

microxp

newbie

Activity: 24

Merit: 0

hi forrestv:
what do you think of the problems mentioned in this topic: https://forum.litecoin.net/index.php/topic,3193.0.html
when using popool for ltc mining,the payout rises at first,and when the payout for one miner reaches the standard level for the miner's hashrate ,the payout begin to drop very fast!
it seems the pool rate,the Share difficulty and the local rate haven't changes so much, why?
It seems it's very easy for a new worker to find the Shares when he first join the pool and begin to work,but with the time passes by,it will become more and more difficult to find the shares,In this progress,the worker's hash rate and the pool rate haven't changed so obviously ! I think this can't be simply caused by the "lucky",do u think so?

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