I like Terracoins!  14aBCjYpwCp9ZvWsLGYNKttV4riBSPD7VX Thanks! |
|
|
|
Thanks for posting a link to the windows client. I've fired it up and now synchronizing with the network. bYUjjGvCK9fYE1tg8uVB53Wd1cHfdj99Q9 |
|
|
|
|
I'm in!
13RsUgqfKWhutg3YwZFuWDPgMktzdAZXLb
Thanks!
|
|
|
|
|
Probably it's own network. I was poking around myself a couple days ago to see if it would work with PPCoin.
|
|
|
|
Now everyone can add his server.
Just click on "Add server" and enter address,location and type (BTC/LTC).
Best!
I've been trying but it doesn't seem to work. |
|
|
|
I'm rebuilding my p2pool node due to a hardware failure. Running the latest version as of 15 minutes ago from the GIT and I get the following: 2012-11-30 08:31:23.335637 > Traceback (most recent call last):
2012-11-30 08:31:23.336126 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:23.336928 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:25.159341 > in download_shares:
2012-11-30 08:31:25.159967 > Traceback (most recent call last):
2012-11-30 08:31:25.160453 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:25.161314 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:28.133602 > in download_shares:
2012-11-30 08:31:28.134254 > Traceback (most recent call last):
2012-11-30 08:31:28.134743 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:28.135574 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:28.166702 P2Pool: 0 shares in chain (0 verified/4565 total) Peers: 6 (0 incoming)
2012-11-30 08:31:28.167326 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2012-11-30 08:31:30.027398 > in download_shares:
2012-11-30 08:31:30.028164 > Traceback (most recent call last):
2012-11-30 08:31:30.028618 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:30.029446 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:31.816948 > in download_shares:
2012-11-30 08:31:31.817605 > Traceback (most recent call last):
2012-11-30 08:31:31.818093 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:31.818912 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:34.376080 > in download_shares:
2012-11-30 08:31:34.376732 > Traceback (most recent call last):
2012-11-30 08:31:34.377251 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:34.378040 Requesting parent share b68a0d0b from 75.12.89.18:9333
Not sure if it's worth worrying about or not but posting just in case. I got this too on a fresh install and fresh git this morning. Did it eventually get all the shares and recover? I'm still getting them after 10 minutes. I ended up shutting down the pool, waiting about 15 minutes and starting up again. The message hasn't come back yet and it's been running for almost 2 days now. |
|
|
|
I'm rebuilding my p2pool node due to a hardware failure. Running the latest version as of 15 minutes ago from the GIT and I get the following: 2012-11-30 08:31:23.335637 > Traceback (most recent call last):
2012-11-30 08:31:23.336126 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:23.336928 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:25.159341 > in download_shares:
2012-11-30 08:31:25.159967 > Traceback (most recent call last):
2012-11-30 08:31:25.160453 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:25.161314 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:28.133602 > in download_shares:
2012-11-30 08:31:28.134254 > Traceback (most recent call last):
2012-11-30 08:31:28.134743 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:28.135574 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:28.166702 P2Pool: 0 shares in chain (0 verified/4565 total) Peers: 6 (0 incoming)
2012-11-30 08:31:28.167326 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2012-11-30 08:31:30.027398 > in download_shares:
2012-11-30 08:31:30.028164 > Traceback (most recent call last):
2012-11-30 08:31:30.028618 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:30.029446 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:31.816948 > in download_shares:
2012-11-30 08:31:31.817605 > Traceback (most recent call last):
2012-11-30 08:31:31.818093 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:31.818912 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:34.376080 > in download_shares:
2012-11-30 08:31:34.376732 > Traceback (most recent call last):
2012-11-30 08:31:34.377251 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:34.378040 Requesting parent share b68a0d0b from 75.12.89.18:9333
Not sure if it's worth worrying about or not but posting just in case. |
|
|
|
PNPBKMJU5Yb9ETQtJotqrJEZxrrvwoZfVb I'm in! |
|
|
|
|
I've setup a node and have it running... seems the "main program processor" stalls almost every minute...
|
|
|
|
Apparently most pools listed in the OP are coming up as 'offline' even though I know some are online.
I'd be interested in seeing what results someone else gets with Red Emerald's Status script.
Here's what I get: {'btc': [{'avg': 0.15731461048126222,
'fee': '0.3',
'uptime': '270151.51699995995',
'url': 'http://p2pool.hopto.org:9332/'},
{'avg': 0.16363060474395752,
'fee': '100.0',
'uptime': '91566.21904587746',
'url': 'http://p2pmining.com:9332/'},
{'avg': 0.2398826837539673,
'fee': '0.5',
'uptime': '763525.3071889877',
'url': 'http://109.74.195.142:9332/'},
{'avg': 0.2880192995071411,
'fee': '0.5',
'uptime': '769027.4405620098',
'url': 'http://p2pool.stitthappens.com:8336/'},
{'avg': 0.346216607093811,
'fee': '0.5',
'uptime': '383904.9463469982',
'url': 'http://p2pool.soon.it:9332/'},
{'avg': 0.47736568450927735,
'fee': '0.0',
'uptime': '841356.9259998798',
'url': 'http://bitpoppool.geekgalaxy.com:9332/'}],
'ltc': [{'avg': 0.25075981616973875,
'fee': '1.0',
'uptime': '769048.9110291004',
'url': 'http://p2pool.stitthappens.com:10336/'}],
'offline': ['http://bitcoinp2pool.zapto.org:9332/',
'http://litecoinp2pool.zapto.org:9327/',
'http://blockexplorer.funkymonkey.org:9335/',
'http://litep2pool.sytes.net:9327/',
'http://p2pool.tgservers.com:9332/',
'http://thirdlight.dynalias.com:9332/',
'http://82.165.39.91:9332/',
'http://195.234.11.101:9332/'],
'unknown': []}
|
|
|
|
|
Or just point them to a 0 fee p2pool node already running using your own payout address...
|
|
|
|
|
Ya, I did another 'git pull' and got more updates. Restarted and it's working again.
|
|
|
|
forestv: 0.11.1 - accessing page /peer_addresses returns: Request did not return a string Request: <GET /peer_addresses HTTP/1.1> Resource: <p2pool.web.WebInterface instance at 0xbfdb1ac> Value: u' .. ip addresses.... |
|
|
|
|
I had someone mine for like 5 minutes a few weeks ago but other than that no one has been here from what I've seen.
|
|
|
|
|
It could be...
I was running GG on a linux box with a gig of ram but GG quickly exceeded that causing the box to swap non-stop.
I switched to a Windows box with 12gigs of ram but since GG runs as a 32-bit process it can't exceed 2 gigs of ram. Once GG got to 2 gigs it crashed and it won't come back. I think the downloaded block chain is now corrupted.
At this point the only way you're going to run is on a 64-bit client.
At some point bitcoin and the other chains will grow to this same size and will have the same problems. I'm hoping someone comes up with a fix for GG that can be applied to the rest.
|
|
|
|
|
Show Posts
