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

[doobeedoo]

OK i think i understand whats happened here, the payout is not going to my wallet address, that would explain why it tailed off after the version update gradually to low hash rate and then dissapeared from the stats page.

So does P2Pool take the wallet address from guiminer username field.

your problem is based on a to low hashrate i think.
p2pool s on a much higher difficulty. It takes about 40-50 min. to get a share with my ~830 MH/s. So, with your hashrate it will take about 10 hours or something.
without a share, you get no payout. And when you get a share early in one round, it could be that you also get no (or very low) payout, because it's pplns.

with low hashrates you should try a pps based node to p2pool, instead of running your own one, imho.

[rav3n_pl]

P2Pool release 3.1
....

Code:

> ---> LOST CONTACT WITH BITCOIND for 2.3 minutes! Check that it isn't frozen or dead! <---

still happening, 3-4 times per 24h

This is bitcoind issue, not p2pool error.
It should be fixed on bitcoin 0.7 release.

[rav3n_pl]

OK i think i understand whats happened here, the payout is not going to my wallet address, that would explain why it tailed off after the version update gradually to low hash rate and then dissapeared from the stats page.

So does P2Pool take the wallet address from guiminer username field.

your problem is based on a to low hashrate i think.
p2pool s on a much higher difficulty. It takes about 40-50 min. to get a share with my ~830 MH/s. So, with your hashrate it will take about 10 hours or something.
without a share, you get no payout. And when you get a share early in one round, it could be that you also get no (or very low) payout, because it's pplns.

with low hashrates you should try a pps based node to p2pool, instead of running your own one, imho.

On 170MH/s it tiakes 3-4 hrs to make a share on p2pool.
Hashrate reporten on p2pool is calcuated basing on diff1 shares send to it. So it can be different form miner stats.
If you run own p2pool no need to add wallet adress on miner config.

BTW: 75% nodes updated to v3
6% still on v2 18% on v1

[Peterae]

your problem is based on a to low hashrate i think.
p2pool s on a much higher difficulty. It takes about 40-50 min. to get a share with my ~830 MH/s. So, with your hashrate it will take about 10 hours or something.
without a share, you get no payout. And when you get a share early in one round, it could be that you also get no (or very low) payout, because it's pplns.

with low hash rates you should try a pps based node to p2pool, instead of running your own one, imho.

I was getting shares and payouts up until i upgraded to the newer version 2 days ago, i have currently been running since this morning and am not showing on the stats page at all, and have not received a share of the last payout, i was getting shares of payout on very short 1 hour or so crunches before.

[sharky112065]

disk I/O related

the same time run second p2pool node for LTC mining without any frozen

Which is why I said it is bitcoind causing the issue. LTC does not use bitcoind (I do not mine LTC, so have no knowledge of what ?...d it is using).

[rav3n_pl]

your problem is based on a to low hashrate i think.
p2pool s on a much higher difficulty. It takes about 40-50 min. to get a share with my ~830 MH/s. So, with your hashrate it will take about 10 hours or something.
without a share, you get no payout. And when you get a share early in one round, it could be that you also get no (or very low) payout, because it's pplns.

with low hash rates you should try a pps based node to p2pool, instead of running your own one, imho.

I was getting shares and payouts up until i upgraded to the newer version 2 days ago, i have currently been running since this morning and am not showing on the stats page at all, and have not received a share of the last payout, i was getting shares of payout on very short 1 hour or so crunches before.

Did you copy data directory from older version?
If not, P2pool might get new adress for payouts and you lost all previous stats.
Sometimes I not get share all 24hours.... and sometimes 4 in a hour.

[Subo1977]

your problem is based on a to low hashrate i think.
p2pool s on a much higher difficulty. It takes about 40-50 min. to get a share with my ~830 MH/s. So, with your hashrate it will take about 10 hours or something.
without a share, you get no payout. And when you get a share early in one round, it could be that you also get no (or very low) payout, because it's pplns.

with low hash rates you should try a pps based node to p2pool, instead of running your own one, imho.

I was getting shares and payouts up until i upgraded to the newer version 2 days ago, i have currently been running since this morning and am not showing on the stats page at all, and have not received a share of the last payout, i was getting shares of payout on very short 1 hour or so crunches before.

Did you copy data directory from older version?
If not, P2pool might get new adress for payouts and you lost all previous stats.
Sometimes I not get share all 24hours.... and sometimes 4 in a hour.

You kan make a Test and Point Your Miner to my node:  http://p2pool-cologne.dyndns.org:9332 0% fee
Set YOUR BTC Adress as Username

[Smoovious]

Hi All!
I wrote a utility for remote monitoring of p2pool working. Download it here.

is the highlighting, user-defined?

cuz, if I tried to use that, with the colors your screenshot currently shows, I'd have to rip my eyes out.

-- Smoov

[Peterae]

Did you copy data directory from older version?
If not, P2pool might get new adress for payouts and you lost all previous stats.
Sometimes I not get share all 24hours.... and sometimes 4 in a hour.

Every time there was Bitcoins found i was getting a payout, no matter how long it took the pool to find the bitcoins.
I extracted the p2pool executable on to a directory on my desktop, when i upgraded i deleted old folder and replaced with new extracted folder and ran it as before.
It's the 32bit version of p2pool.

My new HD7850 has just arrived, looks like i need a new psu to run it

[Peterae]

You kan make a Test and Point Your Miner to my node:  http://p2pool-cologne.dyndns.org:9332 0% fee
Set YOUR BTC Adress as Username

Thanks i will try that when i get home.

[rav3n_pl]

Every time there was Bitcoins found i was getting a payout, no matter how long it took the pool to find the bitcoins.
I extracted the p2pool executable on to a directory on my desktop, when i upgraded i deleted old folder and replaced with new extracted folder and ran it as before.
It's the 32bit version of p2pool.

To preserve old graphs, payout adress and sharechain you have 2 ways to update:
- overwrite new files in same directory
- copy data folder from old direcotry to new (you might wat to skip log file)

If you unzip new package and run it P2pool can sometimes choose different payout adress and you need "earn" new shares to payout. You also lose all previous stats and pool need download and verify current sharechain.

[eightbitbandit]

Did the latest update up the ram requirement significantly? I've had oom-killer kill the python process twice in 24hrs. I restarted it again this morning and it's already back up to 350mb. This box only has 1gb total, but it's had no problem running p2pool for weeks uninterrupted before. I finally just put an entry in crontab to restart the thing every 6 hrs.

[alpet]

is the highlighting, user-defined?

cuz, if I tried to use that, with the colors your screenshot currently shows, I'd have to rip my eyes out.

-- Smoov

Now colors are fixed. In the next version they will change from a script Lua.

[edited]
I upload it here.

[Subo1977]

Did the latest update up the ram requirement significantly? I've had oom-killer kill the python process twice in 24hrs. I restarted it again this morning and it's already back up to 350mb. This box only has 1gb total, but it's had no problem running p2pool for weeks uninterrupted before. I finally just put an entry in crontab to restart the thing every 6 hrs.

on my Ubuntu-Server with 4GB Ram  bitcoind use 2.6% and Pyhthon 2.5% Memory

[eightbitbandit]

Did the latest update up the ram requirement significantly? I've had oom-killer kill the python process twice in 24hrs. I restarted it again this morning and it's already back up to 350mb. This box only has 1gb total, but it's had no problem running p2pool for weeks uninterrupted before. I finally just put an entry in crontab to restart the thing every 6 hrs.

on my Ubuntu-Server with 4GB Ram  bitcoind use 2.6% and Pyhthon 2.5% Memory

Odd. Our bitcoind's are only off by about 20mb, but my p2pool is using around 200mb more. I'm using the latest git pulls of both (as of yesterday anyway).

This is a Fedora 17 32bit box, if that matters.

[Subo1977]

Did the latest update up the ram requirement significantly? I've had oom-killer kill the python process twice in 24hrs. I restarted it again this morning and it's already back up to 350mb. This box only has 1gb total, but it's had no problem running p2pool for weeks uninterrupted before. I finally just put an entry in crontab to restart the thing every 6 hrs.

on my Ubuntu-Server with 4GB Ram  bitcoind use 2.6% and Pyhthon 2.5% Memory

Odd. Our bitcoind's are only off by about 20mb, but my p2pool is using around 200mb more. I'm using the latest git pulls of both (as of yesterday anyway).

This is a Fedora 17 32bit box, if that matters.

Did you patch the Fedora yesterday?

[eightbitbandit]

Did the latest update up the ram requirement significantly? I've had oom-killer kill the python process twice in 24hrs. I restarted it again this morning and it's already back up to 350mb. This box only has 1gb total, but it's had no problem running p2pool for weeks uninterrupted before. I finally just put an entry in crontab to restart the thing every 6 hrs.

on my Ubuntu-Server with 4GB Ram  bitcoind use 2.6% and Pyhthon 2.5% Memory

Odd. Our bitcoind's are only off by about 20mb, but my p2pool is using around 200mb more. I'm using the latest git pulls of both (as of yesterday anyway).

This is a Fedora 17 32bit box, if that matters.

Did you patch the Fedora yesterday?

I actually just did a few mins ago, but I haven't rebooted to apply the new kernel yet. According to my yum.log, my last python update was on June 03, to 2.7.3-3. Most of the stuff it pulled down today involved dhclient, perl, and the kernel.

[Subo1977]

Did the latest update up the ram requirement significantly? I've had oom-killer kill the python process twice in 24hrs. I restarted it again this morning and it's already back up to 350mb. This box only has 1gb total, but it's had no problem running p2pool for weeks uninterrupted before. I finally just put an entry in crontab to restart the thing every 6 hrs.

on my Ubuntu-Server with 4GB Ram  bitcoind use 2.6% and Pyhthon 2.5% Memory

Odd. Our bitcoind's are only off by about 20mb, but my p2pool is using around 200mb more. I'm using the latest git pulls of both (as of yesterday anyway).

This is a Fedora 17 32bit box, if that matters.

Did you patch the Fedora yesterday?

I actually just did a few mins ago, but I haven't rebooted to apply the new kernel yet. According to my yum.log, my last python update was on June 03, to 2.7.3-3. Most of the stuff it pulled down today involved dhclient, perl, and the kernel.

maybe 1 GB of RAM is to small. you need to have your own node? you can also use a public node, for example my :-) as Your runs normal.

[eightbitbandit]

maybe 1 GB of RAM is to small. you need to have your own node? you can also use a public node, for example my :-) as Your runs normal.

Eh, I dunno, like I said, it's been running fine for weeks. And no, I don't need to, but it sure is fun to  I've got other machines laying around here if I have to switch, but this one was my lowest power one so I figured I'd give it a shot first.

[Subo1977]

maybe 1 GB of RAM is to small. you need to have your own node? you can also use a public node, for example my :-) as Your runs normal.

Eh, I dunno, like I said, it's been running fine for weeks. And no, I don't need to, but it sure is fun to  I've got other machines laying around here if I have to switch, but this one was my lowest power one so I figured I'd give it a shot first.

That's my opinion. Running your own node is usually fun.
Unfortunately, the setup is not trivial, so I made my node public to support the P2pool idea.