I'm trying to set up P2Pool for an altcoin, but it is hanging at: Testing bitcoind P2P connection to '127.0.0.1:19323' What would cause this? I can see the node on the daemon. {
"addr" : "127.0.0.1:51311",
"services" : "00000000",
"lastsend" : 0,
"lastrecv" : 1367878607,
"conntime" : 1367878607,
"version" : 0,
"subver" : "",
"inbound" : true,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
Setting the magic numbers in p2pool/bitcoin/networks.py incorrectly. |
|
|
|
For the first time in a month of mining on p2pool, the page is saying "Payout if a block were found now: 0 BTC". This is in spite of the hashrate being shown normal and DOAs/orphans next to nonexistent. And about an hour ago it was showing a non-zero payment. I restarted the entire btc, p2pool, bfgminer ensemble but it's still showing 0. Why does this happen?
Do you have any peer connections? ...I have them right now. And my payout's back to normal. I'm not sure about before. If it happens again, I'll check. Do you have a pretty low hash rate? If you don't get a share every 24 hours, your payout will drop to zero at times. Wow, I didn't know that existed. That makes something I'm trying to do a lot easier.
Yep, useful. What time period are those stats over? In particular I mean the miner_hash_rates and miner_dead_hash_rates. I need them over a reasonably short period for alarming to be able to react if a miner goes away. def get_local_stats():
...
lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...
SHARE_PERIOD=10, # seconds for BTC... So... I would guess that it's a 10 sec resolution? No, one hour (3600 seconds). |
|
|
|
Some kind of DOS attack?
Got three "GOT INCOMPLETE BLOCK FROM PEER" messages and then p2pool stopped. Peer IP is 192.203.228.65
Now just got another one.
What do you mean by "p2pool stopped"? |
|
|
|
forrestv: you may want to update the subject of the thread, the pool seems to stabilize at more than 650GH/s now.
Good point. Used 700GH/s, as it is now  |
|
|
|
I contacted him. Thanks for the tip! |
|
|
|
That's a bug in the block explorer you're using. There is no way for a Litecoin transaction to pay Bitcoin addreses - the network ID isn't even encoded in the block. All addresses in a block are just 160-bit hashes, without any identifying information. You mean, it's a bug of explorer.litecoin.net? If so, then why is that block listed in the p2pool history? And why haven't I got any reward from it? It's a real Litecoin-P2Pool block, but the Litecoin explorer is displaying Litecoin addresses as Bitcoin addresses for some reason. It appears to have been orphaned, so you didn't get a payout. The explorer displaying Bitcoin addresses and the block being orphaned might have some common cause, however.. |
|
|
|
That's a bug in the block explorer you're using. There is no way for a Litecoin transaction to pay Bitcoin addreses - the network ID isn't even encoded in the block. All addresses in a block are just 160-bit hashes, without any identifying information. |
|
|
|
What is the definitive way to see when a non orphaned block has been generated by p2pool?
|
|
|
|
Hi i just checked md5 and sh1 for windows zip and run_p2pool.exe and they are not as in decryption any suggestion why ?
Can I use this save ? or is there back door or virus ?
That hash in the release post is a Git commit hash. If you want to ensure the safety of the Windows binary, use GPG to validate it with the separate signature file. If you want to validate the source code, it's a bit harder - use git to download it from Github and compare the commit hash, or check the release tag, which is signed. |
|
|
|
HELP: I was a previous user of p2pool with no problems for months; i used it on bitcoin as well as litecoin and terracoin; I did afresh re-install of windows re-downloaded and set-up my coins and p2pool etc. P2pool launches with no error and connects to the network. When i launch my miner to connect it connects and finds the p2pool network but results in this error and no shares are submitted. please help!!!  Thank you for the help!! [/quote Using the latest release will fix this. |
|
|
|
My miners are using the noob/sauce user & password but I did use the -a option to set the address to my bitcoinspinner wallet.
Hm. Litecoin mining? |
|
|
|
I think I'm mining. My miners look like they are mining. Fans are spinning high and the room is getting warm. Yet the top graph is flat at zero even on the hour view. Is this supposed to be the case?
Local rate on main page also says 0. What is happening to the MH/s that my miners are claiming?
If your miners have a Bitcoin address username, this will happen. Those graphs and numbers are for the main address, which defaults to one requested from bitcoind and can be set with the -a option on P2Pool. Letting P2Pool manage the payout address is the recommended course. However, your local rate and current payout should show up under the "Miners" header on the graphs page. |
|
|
|
|
I emailed him earlier today and was refunded within hours. Yay!
|
|
|
|
|
I just pushed a commit that should fix the traceback. All it does is ignore the extra argument cgminer provides to mining.subscribe (which is cgminer's version).
|
|
|
|
submitblock is relatively new in bitcoind. In litecoind it's done with getblocktemplate, passing the first argument (mode) as submit, and the second argument (data) as the hex data of the full block.
That means there really is a compatibility problem between latest p2pool (11.2, possibly earlier) and any version of litecoind. Maybe users should be adviced not to update to latest p2pool with litecoin. If everyone updates... litecoin p2pool stops getting any blocks :-( P2Pool also submits blocks over the P2P connection, so even if everyone upgraded, there wouldn't be any problem. I'll either fix this in P2Pool or submit a pull request to the Litecoin project to add submitblock. |
|
|
|
|
Aseras/Subo1977: Are you using P2Pool 11.2 (the current newest version)? It fixed a memory leak that caused similar problems.
|
|
|
|
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. 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. |
|
|
|
|
Show Posts
