Topic: [ANN][YAC][POOL]p2pool for yacoin!! - page 7. (Read 28208 times)
^ This was discussed earlier in the thread.. it's something to do with how the completed blocks have to be signed in proof-of-stake coins, meaning a very small transaction must take place on the server for a block to be accepted. The easiest way to ensure this happens was for ntkrnl to code in a minimum of 0.01 payment to the server daemon/wallet.
Probably workers not using a YAC address as their name.
I have been using my own p2pool node for some days and I have found that my wallet address, the one I use for the p2pool node had some balance. How could this be possible ? If I set up the pool to have 0 fee shouldn't all the YAC's go to the miner's address ?
The params I am using is "--fee 0".
The params I am using is "--fee 0".
I've applied the changes from this commit https://github.com/forrestv/p2pool/commit/0cb07df562 to see if it helps with my memory issues. Have just restarted the pool so apologies for any dead shares submitted.
This doesn't seem to have achieved much, and the dead share % has climbed significantly.
Wish ntkrnl had forked forrestv's github properly, might have to do the fork again myself so I know I have the latest p2pool at any given moment.
I am also having issues with memory leaks. Python is suddenly killed and although I am running it under supervise (read daemontools) when restarted it sometimes hangs forever in loading shares. Since python is not cleanly shut down maybe the data dir becomes corrupt.
Anyone else experiencing this ?
I've applied the changes from this commit https://github.com/forrestv/p2pool/commit/0cb07df562 to see if it helps with my memory issues. Have just restarted the pool so apologies for any dead shares submitted.
This doesn't seem to have achieved much, and the dead share % has climbed significantly.
Wish ntkrnl had forked forrestv's github properly, might have to do the fork again myself so I know I have the latest p2pool at any given moment.
[ANN] YAC P2P Pool http://yacpool.cloudapp.net:8336 (fast, reliable, 1% fee)
https://bitcointalksearch.org/topic/ann-yac-p2p-pool-httpyacpoolcloudappnet8336-fast-reliable-1-fee-223827
https://bitcointalksearch.org/topic/ann-yac-p2p-pool-httpyacpoolcloudappnet8336-fast-reliable-1-fee-223827
I've applied the changes from this commit https://github.com/forrestv/p2pool/commit/0cb07df562 to see if it helps with my memory issues. Have just restarted the pool so apologies for any dead shares submitted.
With regard to the non-payment, I haven't had a chance to look into it any more as yet. Any progress on that front at the user end?
With regard to the non-payment, I haven't had a chance to look into it any more as yet. Any progress on that front at the user end?
Works fine for me.
And rate is lower and lower ;]
Code:
Current block value 23.57 YAC
Expected time to block 0.126 hours
Pool rate 13.4MH/s (28% DOA+orphan)
Share difficulty 0.00667
Node uptime 4.576 (109.813 hours)
And it is paying.Expected time to block 0.126 hours
Pool rate 13.4MH/s (28% DOA+orphan)
Share difficulty 0.00667
Node uptime 4.576 (109.813 hours)
And rate is lower and lower ;]
same here, no payments at all
Ok perhaps you could post your yac address so procrypty could check his logs and see if your problem is similar to mine?
-Michael
Everytime Nfactor increases, hashrate decreases.
Thanks, why has the hashrate gone significantly down?
"blocks" : 76369,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.47514969,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 88539229,
"pooledtx" : 0,
"testnet" : false,
"Nfactor" : 8,
"N" : 512,
"powreward" : 23.43000000
What is the current block reward
same here, no payments at all
Unfortunately, yes, you are the only address in the logs with this issue.
I wonder what is wrong then. I simply downloaded the miner from the links in this thread and started it up using the command I posted earlier.
The miner is crunching away, reporting accepts and rejects completely as normal. Only there is no payout because no shares are really being accepted.
I'm running this on a plain old W530 (corei7) laptop with a LAN connection. Nothing special, except for ONE little detail. The company firewall is blocking everything going out to your port, so I am using an ssh tunnel to port 22 on a remote machine, and connecting the miner to your pool through the tunnel (at localhost:3000). As far as I know there should, however, not be any impact on the data flowing through the channel.
Last night I ran the client on my home pc, which is a stationary core2 duo machine running windows vista, and this machine has no firewall issues at all. It ran through the evening so I would expect at least *some* payment to come through. Still, nada.
Is anyone here running the same miner, with the procrypto mining pool, and getting shares accepted (and payments) without problems?
-Michael
Still getting your issue appearing in the logs I'm afraid.
Okay... just out of curiosity, does it appear like I am the only one of all your miners who is having this problem?-Michael
Unfortunately, yes, you are the only address in the logs with this issue.
Still getting your issue appearing in the logs I'm afraid.
Okay... just out of curiosity, does it appear like I am the only one of all your miners who is having this problem?
-Michael
My pool seems to be eating up all it's RAM and crashing lately.
I'm using the P2Pool version: c265896-dirty
Is there a better one out there?
I'm using the P2Pool version: c265896-dirty
Is there a better one out there?
The pool died! 
Yeh, went down for a while overnight, sorry all. Just rebooted again - note the server wasn't down for as long as the graph now shows! This was the error in the log.
Code:
2013-05-31 06:42:02.048394 Error when requesting noncached value:
2013-05-31 06:42:02.048479 > Traceback (most recent call last):
2013-05-31 06:42:02.048575 > Failure: twisted.internet.error.ConnectBindError: Couldn't bind: 24: Too many open files.
2013-05-31 06:42:02.048479 > Traceback (most recent call last):
2013-05-31 06:42:02.048575 > Failure: twisted.internet.error.ConnectBindError: Couldn't bind: 24: Too many open files.
For now I have increased the limits in /etc/security/limits.conf to
Code:
UID soft nofile 10240
UID hard nofile 10240
UID hard nofile 10240
Can't help feeling I should get to the bottom of why this limit was hit though!
Also..
I noticed the server was restarted a few hours ago. I'm still mining with the same address - perhaps you could check the logs and see if the problem still exists?
Still getting your issue appearing in the logs I'm afraid.
Jump to: