 Show Posts
|
|
Pages: « 1 [2]
|
|
Congrats on the block on jtoomimnet, way to stick it out! =] . But I have a question for anyone that could answer. How would one know if the p2pool network is getting attacked? It seems at times, over 100GH,while being only a 200-300GH network currently, can come jump on the p2pool LTC network and global rejection rates seems to spike. Rejections 30-40%, sometimes even 50% on some of the bigger nodes it seems. It could just be going crazy watching the networks numbers and trying to figure out whats going on. I know it would take someone with 50% or so of our hashrate to preform an attack. They would just submit mass invalid shares purposefully, correct?
|
|
|
|
|
and thanks to all that contribute with different p2pool forks as well. Its all good work.
|
|
|
|
Kiefff, it looks like you have a lot of different mining addresses on the same node. Most of the work that p2pool needs to do is per worker address, not per worker. If you have 1000 miners all sharing the same worker address, that's less work for p2pool than 10 miners each with a different address. If you can change the miners to all use the same worker address, you should be able to handle the load just fine. That might not be an option, though.
I also notice that you seem to have enabled incoming p2p connections (e.g. by forwarding a port on your router) a few days ago, and you're now getting about 2x as many connections. Each connection increases the CPU load on your node, so if you have a slow CPU, you may be better off limiting your node to e.g. 5 connections total.
Pypy will probably also help as long as you have enough RAM. It looks like you're currently using about 1.8 GB of RAM on CPython, so that might increase to 4 GB if you switch to Pypy.
My p2pool modifications would probably help too, but I haven't tried running them on Litecoin yet, so I don't know if they would work.
Jtoomim, I will try to limit total connections as you suggested. I will give pypy a go as well. The rig itself has 16Gb of memory and I will always increase it to meet the needs. I will do some messing around with your fork as well on my spare rig. Thank you again for the reply and honestly, what you do for p2pool in general. I see EST block time is down on your Jtoomimnet. I tell anyone that asks to hop on if they want to mine some BTC. |
|
|
|
Hey all, been running a p2pool LTC node and its been going great until I get 10GH + of miners on my node.
Kiefff, can you describe in more detail what the issue is when it hits 10 GH/s? What goes wrong? Does your CPU get pegged at 100% on one core? Does the web UI become less responsive? Does it spit out error messages? Does your efficiency drop and your orphan rate increase? Does your machine halt and catch fire? It would be useful to have some more information on what the problem actually is. Hi, thanks for the response and sorry for lack of detail when asking for troubleshooting help. I know it can be super annoying. It seems everyone on the node, now that it is past 10GH local, now has high rejection rates(even my locally connected miners) and I also notice a increase in local stale shares. So it seems when A CPU core spikes to 100%, local dead on arrival spikes to around 15-16% and then goes back down after things seem to calm down on the CPU core. Local stale share % then starts to drop until the process starts all over again. Web UI seems to be just as responsive during these times, from what I can tell. No fire yet =] Thanks again for the reply. it seems when this comes up, the CPU core spikes and my problem above happens 2017-12-11 12:23:58.579394 Peer sent entire transaction ffe7dff1b877c24f5dab32947698137d7e35fec51ab8accc0cbc59c947d5d230 that was already received
2017-12-11 12:23:58.591211 Peer sent entire transaction 8560094e76b112e54302624cbfe9aa0f666edd19d8526fa7da46fd7c2c460749 that was already received
2017-12-11 12:23:58.596509 Peer sent entire transaction ffe7dff1b877c24f5dab32947698137d7e35fec51ab8accc0cbc59c947d5d230 that was already received
2017-12-11 12:23:58.601995 Peer sent entire transaction ffe7dff1b877c24f5dab32947698137d7e35fec51ab8accc0cbc59c947d5d230 that was already received
2017-12-11 12:23:58.820905 Peer sent entire transaction 8560094e76b112e54302624cbfe9aa0f666edd19d8526fa7da46fd7c2c460749 that was already received
2017-12-11 12:23:58.844515 Peer sent entire transaction 8560094e76b112e54302624cbfe9aa0f666edd19d8526fa7da46fd7c2c460749 that was already received
2017-12-11 12:23:59.009682 Peer sent entire transaction 8560094e76b112e54302624cbfe9aa0f666edd19d8526fa7da46fd7c2c460749 that was already received
2017-12-11 12:23:59.031231 Peer sent entire transaction 8560094e76b112e54302624cbfe9aa0f666edd19d8526fa7da46fd7c2c460749 that was already received
|
|
|
|
|
Hey all, been running a p2pool LTC node and its been going great until I get 10GH + of miners on my node. Ive ran it on my 12 core xeon(only 2.6gh clock). Then after reading that p2pool does better on single core high clock I ran the node on my i5 OC'd. Still the same issue. Now I'm trying my i7 3770 with the same issues. My pipeline is a biz connection, 100/20 to my home. Would running it with pypy work? I seen Jtoom mention it, but not sure if its just for his 1mb_segwit fork? Sorry, been trying to read ALL the pages in here before I come and ask. I'm all about p2pool, great work.
|
|
|
|
|
Is there a way to setup a password for miners? Keeping the pool private.
|
|
|
|
Hey all. Recently got p2pool working with litecoin. Pool was working for fine about 6 hours and now will not connect to any p2pool peers? I was connected to 6 since starting, now 0. Do I need to manually add other p2pool nodes?
No. It could be a firewall issue. Make sure that your firewall allows incoming connections over port 9338, which is Litecoin P2Pool's default P2P port. If your node is behind a NAT router, make sure that TCP port forwarding is enabled on the router, and that port 9338 is forwarded to your P2Pool node. I'm assuming that you've already followed these instructions when you set up your node. You may also try using sawa's P2Pool for Litecoin instead. Sawa's fork contains fixes and enhancements that improve compatibility with Litecoin. If these do not resolve your issue, then please post here your node's logs — located at /litecoin/log in your P2Pool data directory — so that we may have a closer look at what's going on when your node starts dropping connections. A snippet of your node's terminal output, of around the time your node starts dropping connections, may also be of help here. Using sawas p2pool is working quite well so far. Thanks for the info! |
|
|
|
|
Hey all. Recently got p2pool working with litecoin. Pool was working for fine about 6 hours and now will not connect to any p2pool peers? I was connected to 6 since starting, now 0. Do I need to manually add other p2pool nodes?
|
|
|
|
Seems more stable then prohashing! Keep it up buddy I appreciate having your pool available.
This pool is way more stable than prohashing, IMO. Everytime I check my miners, it seem the prohashing pool is 'Dead'. Even when checking on prohashing itself, high rejection rate. Staying away from prohashing, currently running two L3+'s on GranatGas. |
|
|
|
|
