I had to do a git pull in p2pool folder and recompiled bitcoind from source to fix your problem.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 744. (Read 2591916 times)
March 18, 2012, 08:54:28 PM
March 18, 2012, 06:28:10 PM
Question for all of you - hoping for some help with this one.
Server keeps starting up, seeing shares, then crashing with this error:
Anyone had anything similar?
Currently in the middle of redownloading bitcoin 0.60 rc4 + blockchain + p2pool to see if I can fix it.
Server keeps starting up, seeing shares, then crashing with this error:
Anyone had anything similar?
Currently in the middle of redownloading bitcoin 0.60 rc4 + blockchain + p2pool to see if I can fix it.
March 18, 2012, 01:04:36 PM
Just got my Linux server setup.
March 18, 2012, 12:45:52 AM
I've used pypy for a couple of days, it works ok, I don't see a big difference in CPU usage compared to python, but it has a problem: it is not compatible with pygame so you cannot show/generate graphs.
Bummer about both. I don't use the graphs so hadn't noticed that pygame wasn't compatible. But if it doesn't offer any significant CPU efficiency gain, it's probably irrelevant.
March 17, 2012, 09:15:44 PM
I just upgraded to 6.0 rc4 and the most recent version of p2pool as shown on the first post, and am having issues. The error log is here: http://pastebin.com/3nga0nSB
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Seems your p2pool version is not current, so perhaps the first posting links to an obsolete build. Try to look a few pages back to get the link to a current p2pool build.
Dia
The error messages you see are coming from bitcoin, not from p2pool. Go make sure you actually have the latest version of bitcoin. Based on what others have reported, it seems that the bitcoin installer often does not actually update old versions. Maybe try the .zip file instead, or try uninstalling the old version first.
March 17, 2012, 08:42:01 PM
I just upgraded to 6.0 rc4 and the most recent version of p2pool as shown on the first post, and am having issues. The error log is here: http://pastebin.com/3nga0nSB
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Seems your p2pool version is not current, so perhaps the first posting links to an obsolete build. Try to look a few pages back to get the link to a current p2pool build.
Dia
The error messages you see are coming from bitcoin, not from p2pool. Go make sure you actually have the latest version of bitcoin. Based on what others have reported, it seems that the bitcoin installer often does not actually update old versions. Maybe try the .zip file instead, or try uninstalling the old version first.
March 17, 2012, 08:17:26 PM
To anyone using my pool, I'm installing a Linux P2Pool currently and will have everything automatically changed over as long as you are using the domain name.
You won't have to change anything, as I will leave the other server up for as long as I can (so far the server has been online since 1/9/2012 10:11 AM EST since a reboot) that way your hash/s (shares) wont get messed up.
[Edit]: Currently downloading the blocks, shouldn't be too much longer.
You won't have to change anything, as I will leave the other server up for as long as I can (so far the server has been online since 1/9/2012 10:11 AM EST since a reboot) that way your hash/s (shares) wont get messed up.
[Edit]: Currently downloading the blocks, shouldn't be too much longer.
March 17, 2012, 08:09:02 PM
I just upgraded to 6.0 rc4 and the most recent version of p2pool as shown on the first post, and am having issues. The error log is here: http://pastebin.com/3nga0nSB
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Seems your p2pool version is not current, so perhaps the first posting links to an obsolete build. Try to look a few pages back to get the link to a current p2pool build.
Dia
The error messages you see are coming from bitcoin, not from p2pool. Go make sure you actually have the latest version of bitcoin. Based on what others have reported, it seems that the bitcoin installer often does not actually update old versions. Maybe try the .zip file instead, or try uninstalling the old version first.
March 17, 2012, 08:08:18 PM
I just upgraded to 6.0 rc4 and the most recent version of p2pool as shown on the first post, and am having issues. The error log is here: http://pastebin.com/3nga0nSB
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Seems your p2pool version is not current, so perhaps the first posting links to an obsolete build. Try to look a few pages back to get the link to a current p2pool build.
Dia
Well you are right, my displayed version number is 1f87c32, too ... so that is okay. I use 0.6 RC4 on Win7, which works for me.
What seems weird is your error message "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.". Are you sure your BC client is the 0.6 RC4? Are any errors in the debug.log of the BC client shown? Did you change the bitcoin.conf?
Dia
March 17, 2012, 07:31:00 PM
I just upgraded to 6.0 rc4 and the most recent version of p2pool as shown on the first post, and am having issues. The error log is here: http://pastebin.com/3nga0nSB
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Seems your p2pool version is not current, so perhaps the first posting links to an obsolete build. Try to look a few pages back to get the link to a current p2pool build.
Dia
March 17, 2012, 07:18:25 PM
I just upgraded to 6.0 rc4 and the most recent version of p2pool as shown on the first post, and am having issues. The error log is here: http://pastebin.com/3nga0nSB
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Seems your p2pool version is not current, so perhaps the first posting links to an obsolete build. Try to look a few pages back to get the link to a current p2pool build.
Dia
March 17, 2012, 03:41:56 PM
I just upgraded to 6.0 rc4 and the most recent version of p2pool as shown on the first post, and am having issues. The error log is here: http://pastebin.com/3nga0nSB
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
Log was expanding rapidly, so I shut the node down.
Running on Server 2008 R2.
March 17, 2012, 02:17:52 PM
Are there known problems with the current p2pool build and the 0.6 RC4 build of the client? I got no share for quite some time, can be bad luck or an undiscovered problem.
I'll let it mine for some time and will report back ...
Dia
I have 0.6 RC4 and i find shares so it work fine I'll let it mine for some time and will report back ...
Dia
March 17, 2012, 12:44:34 PM
p2pool tries to use git to get its version number - no harm done if it can't.
I think you can look at '/path/to/p2pool/.git/ORIG_HEAD' to get the current version and then you don't need to use git.Hmm:
Code:
cat .git/ORIG_HEAD
72d960a1000cb9ac97dc2eb3be33ace29f28dfd5
72d960a1000cb9ac97dc2eb3be33ace29f28dfd5
whereas p2pool does:
Code:
git describe --always --dirty
0.9.2-59-g6b4c15a
0.9.2-59-g6b4c15a
Nope, you can't...
Code:
$ cat .git/HEAD
ref: refs/heads/master
$ cat .git/refs/heads/master
6b4c15aeae4604ef3c536ea2cc695ae2be160914
$ git describe --always --dirty
0.9.2-59-g6b4c15a
ref: refs/heads/master
$ cat .git/refs/heads/master
6b4c15aeae4604ef3c536ea2cc695ae2be160914
$ git describe --always --dirty
0.9.2-59-g6b4c15a
March 17, 2012, 12:31:00 PM
p2pool tries to use git to get its version number - no harm done if it can't.
I think you can look at '/path/to/p2pool/.git/ORIG_HEAD' to get the current version and then you don't need to use git.Hmm:
Code:
cat .git/ORIG_HEAD
72d960a1000cb9ac97dc2eb3be33ace29f28dfd5
72d960a1000cb9ac97dc2eb3be33ace29f28dfd5
whereas p2pool does:
Code:
git describe --always --dirty
0.9.2-59-g6b4c15a
0.9.2-59-g6b4c15a
Nope, you can't...
March 17, 2012, 12:23:33 PM
p2pool tries to use git to get its version number - no harm done if it can't.
I think you can look at '/path/to/p2pool/.git/ORIG_HEAD' to get the current version and then you don't need to use git. March 17, 2012, 12:10:36 PM
p2pool tries to use git to get its version number - no harm done if it can't.
March 17, 2012, 12:02:44 PM
I just downloaded the latest code from github.
This is what happens when I start p2pool:
http://dl.dropbox.com/u/34410241/gitnotfound.png
Windows complains about an unknown "git" command.
This is what happens when I start p2pool:
http://dl.dropbox.com/u/34410241/gitnotfound.png
Windows complains about an unknown "git" command.
March 17, 2012, 11:38:44 AM
Strange problem with my P2Pool node.
Everything was running fine, hashrate about 1600Mh/s (600Mh/s of my own hashpower + 1Gh/s of unknown other miners I assume).
I go away for two hours, come back and it takes 20 minutes (!!!) to establish a remote desktop connection to my server. Finally get on and the p2pool window is scrolling so fast I can't read anything, whole system is almost completely unresponsive. Memory usage is about 140MB and CPU Usage is 100%.
Hard reboot vpn, find that bitcoind now refuses to connect.
Have now switched over to 0.5.3.1 and reinstalled everything and p2pool is working again, stable with 2% CPU load and 105MB of memory in use.
Any thoughts?
Everything was running fine, hashrate about 1600Mh/s (600Mh/s of my own hashpower + 1Gh/s of unknown other miners I assume).
I go away for two hours, come back and it takes 20 minutes (!!!) to establish a remote desktop connection to my server. Finally get on and the p2pool window is scrolling so fast I can't read anything, whole system is almost completely unresponsive. Memory usage is about 140MB and CPU Usage is 100%.
Hard reboot vpn, find that bitcoind now refuses to connect.
Have now switched over to 0.5.3.1 and reinstalled everything and p2pool is working again, stable with 2% CPU load and 105MB of memory in use.
Any thoughts?
What does the p2pool log say for the time that it was broken? Hard to diagnose without knowing that. The log is kept in the data/bitcoin/log file under the folder where p2pool is installed, so you can go back and look at it after the fact if you didn't delete it when you reinstalled p2pool.
March 17, 2012, 11:26:41 AM
Are there known problems with the current p2pool build and the 0.6 RC4 build of the client? I got no share for quite some time, can be bad luck or an undiscovered problem.
I'll let it mine for some time and will report back ...
Dia
I'll let it mine for some time and will report back ...
Dia
Running RC4 without problems for 8+ hours. Everything looks normal.
Still no share, what is your hash-rate?
Dia
Dia, I had a day like that the other day. Ended up with a few big gaps with no shares. Try a reboot, and a git pull on p2pool. I just updated bitcoind to rc4 myself yesterday, everything seems pretty normal. With 2.3GH/s I get about .40 payout.
--edit---
Oops, sorry I actually am using rc3 in linux.
Jump to: