Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 612. (Read 2591920 times)
November 30, 2012, 09:25:02 PM
Been getting a lot of 401 Authorization Required errors recently. Haven't changed anything and the user and password for bitcoind are correct.
November 30, 2012, 05:18:01 PM
Was using 9.0 fine and suddenly on reboot was spammed with this message and it closes instantly when using:
https://i.imgur.com/W4We3.png
Now I downloaded 9.2 just in case, but it connects quickly, but never do my miners seem to connect.. not even on the host machine. Anyone..?
https://i.imgur.com/W4We3.png
Now I downloaded 9.2 just in case, but it connects quickly, but never do my miners seem to connect.. not even on the host machine. Anyone..?
Firewall? Looks like its blocked somehow.
Fixed the problem, if there was any, with a reboot on 9.2 However still no explanation of 9.0 happenings.
If you see those errors ("Error when requesting noncached value:"), if means that there was a failure earlier on. I should probably mask those somehow... anyway, scroll up to see what actually went wrong.
November 30, 2012, 05:06:37 PM
Was using 9.0 fine and suddenly on reboot was spammed with this message and it closes instantly when using:
https://i.imgur.com/W4We3.png
Now I downloaded 9.2 just in case, but it connects quickly, but never do my miners seem to connect.. not even on the host machine. Anyone..?
https://i.imgur.com/W4We3.png
Now I downloaded 9.2 just in case, but it connects quickly, but never do my miners seem to connect.. not even on the host machine. Anyone..?
Firewall? Looks like its blocked somehow.
Fixed the problem, if there was any, with a reboot on 9.2 However still no explanation of 9.0 happenings.
November 30, 2012, 03:30:04 PM
P2Pool release 9.2
stales still about 20%, it is normal?
November 30, 2012, 11:42:55 AM
How to setup --submit-stale parameter in cgminer ?
Submit or no submit ?
K1773R
Thanks.
im submitting stales too since u can find a block even with an orphaned share.Submit or no submit ?
K1773R
Thanks.
i didnt find out yet how to do it with cgminer but i didnt check on that anway.
Newer versions of cgminer from the last few months will submit stales automatically because p2pool sets a header telling it too.
--no-submit-stale
That change was back in April 2.3.6
Kano, I just pm'd you regarding your usb-linux writeup - very nice work.
November 30, 2012, 10:25:27 AM
How to setup --submit-stale parameter in cgminer ?
Submit or no submit ?
K1773R
Thanks.
im submitting stales too since u can find a block even with an orphaned share.Submit or no submit ?
K1773R
Thanks.
i didnt find out yet how to do it with cgminer but i didnt check on that anway.
Newer versions of cgminer from the last few months will submit stales automatically because p2pool sets a header telling it too.
--no-submit-stale
That change was back in April 2.3.6
November 30, 2012, 09:24:35 AM
How to setup --submit-stale parameter in cgminer ?
Submit or no submit ?
K1773R
Thanks.
im submitting stales too since u can find a block even with an orphaned share.Submit or no submit ?
K1773R
Thanks.
i didnt find out yet how to do it with cgminer but i didnt check on that anway.
Newer versions of cgminer from the last few months will submit stales automatically because p2pool sets a header telling it too.
November 30, 2012, 09:16:00 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
0% stale for me 
I know how you done it......you swithed it off! lol
Same here, but I also don't want to be mining at a loss either. I love the p2p ethos, and the whole BitCoin thing - but can't afford to throw my cash into it without at least breaking even, which I'm not at the moment......
November 30, 2012, 08:59:38 AM
im submitting stales too since u can find a block even with an orphaned share.
i didnt find out yet how to do it with cgminer but i didnt check on that anway.
cgminer submits stales automatically on p2pool without any specific configuration (a pool can request stales to be submitted and cgminer honors the request).i didnt find out yet how to do it with cgminer but i didnt check on that anway.
November 30, 2012, 08:55:09 AM
im submitting stales too since u can find a block even with an orphaned share.
i didnt find out yet how to do it with cgminer but i didnt check on that anway.
cgminer submits stales automatically on p2pool without any specific configuration (a pool can request stales to be submitted and cgminer honors the request). i didnt find out yet how to do it with cgminer but i didnt check on that anway.
November 30, 2012, 08:54:50 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
0% stale for me I know how you done it......you swithed it off! lol
November 30, 2012, 08:53:22 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
0% stale for me I know how you done it......you swithed it off! lol
November 30, 2012, 08:47:37 AM
How to setup --submit-stale parameter in cgminer ?
Submit or no submit ?
K1773R
Thanks.
im submitting stales too since u can find a block even with an orphaned share.Submit or no submit ?
K1773R
Thanks.
i didnt find out yet how to do it with cgminer but i didnt check on that anway.
November 30, 2012, 08:42:32 AM
How to setup --submit-stale parameter in cgminer ?
Submit or no submit ?
K1773R
Thanks.
Submit or no submit ?
K1773R
Thanks.
November 30, 2012, 08:41:32 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
There few parameters you should look at:1. Local rate: xxx H/s (yy% DOA)
DOA there should be very low (max few %). If it is high possible miner config is bad or node GBT/lag is very high and you are mining old share.
2. Shares: xxx total (yyy orphaned, zzz dead) Efficiency: qqq%
yyy depends on mostly LUCK, some on config. Orphaned share means that someone found share at same time as you, and yet another share was put on his share not yours.
zzz depends on node and bit on luck. Dead share means that it is another share already after that one you was mining. So if your node is lagging and not fetching/passing shares fast enough you will get more dead shares.
Hi rav3n,
My local DOA rate on p2pool is 1.8% which is pretty normal for me.
I just done a few tweaks on my rig and rebooted, but before that I was over 36% stales and about 75% efficiency - where as before all this malarkey I was at a constant 98-110%+.
Ki77er, how do you manage to get a 0% stale rate when the pool stale rate is over 20%? Teach me Obe Wan.....
November 30, 2012, 08:39:07 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
There few parameters you should look at:1. Local rate: xxx H/s (yy% DOA)
DOA there should be very low (max few %). If it is high possible miner config is bad or node GBT/lag is very high and you are mining old share.
2. Shares: xxx total (yyy orphaned, zzz dead) Efficiency: qqq%
yyy depends on mostly LUCK, some on config. Orphaned share means that someone found share at same time as you, and yet another share was put on his share not yours.
zzz depends on node and bit on luck. Dead share means that it is another share already after that one you was mining. So if your node is lagging and not fetching/passing shares fast enough you will get more dead shares.
Hi rav3n,
My local DOA rate on p2pool is 1.8% which is pretty normal for me.
I just done a few tweaks on my rig and rebooted, but before that I was over 36% stales and about 75% efficiency - where as before all this malarkey I was at a constant 98-110%+.
Ki77er, how do you manage to get a 0% stale rate when the pool stale rate is over 20%? Teach me Obe Wan.....
November 30, 2012, 08:34:41 AM
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:
Not sure if it's worth worrying about or not but posting just in case.
Running the latest version as of 15 minutes ago from the GIT and I get the following:
Code:
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.
November 30, 2012, 07:56:02 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
There few parameters you should look at:1. Local rate: xxx H/s (yy% DOA)
DOA there should be very low (max few %). If it is high possible miner config is bad or node GBT/lag is very high and you are mining old share.
2. Shares: xxx total (yyy orphaned, zzz dead) Efficiency: qqq%
yyy depends on mostly LUCK, some on config. Orphaned share means that someone found share at same time as you, and yet another share was put on his share not yours.
zzz depends on node and bit on luck. Dead share means that it is another share already after that one you was mining. So if your node is lagging and not fetching/passing shares fast enough you will get more dead shares.
November 30, 2012, 07:25:41 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
0% stale for me November 30, 2012, 06:38:09 AM
After 12 hours on v9.2 my stale rate has gone up to 36% - whereas on the previous v9.1-9 it was steady at a lower (but still high) 18-22%. Connections seem quicker, but those damn "punishing share for stale" and "tx" messages are constantly thrown at me. Might go back to the previous build.......
Jump to: