[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[mdude77]

I have just received my new Ant S1's trying to connect them to my node on the local network  I have setup the following 3 pools

Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

I use:

http://192.168.0.194:9332

so, try putting the http:// in front of it.

M

No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client

sounds like a routing problem?  What happens if you put http://192.168.1.20:9332  in your browser?

M

[1713540799]

1713540799

[1713540799]

1713540799

[andmax]

I have just received my new Ant S1's trying to connect them to my node on the local network  I have setup the following 3 pools

Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

I use:

http://192.168.0.194:9332

so, try putting the http:// in front of it.

M

No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client

sounds like a routing problem?  What happens if you put http://192.168.1.20:9332  in your browser?

M

I get my node webpage. I have been mining with Antminer U1's for a few months now without a problem I can ping 192.168.1.20 from the network/diagnostics tab on the Ant S1 and it finds it

It won't connect to any p2pools I've tried a few and no connection, my mate had the same problem with his S1's in Houston Texas, will only connect to mining pools, so there must be a setting within the S1 that needs fixing

[mdude77]

I have just received my new Ant S1's trying to connect them to my node on the local network  I have setup the following 3 pools

Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

I use:

http://192.168.0.194:9332

so, try putting the http:// in front of it.

M

No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client

sounds like a routing problem?  What happens if you put http://192.168.1.20:9332  in your browser?

M

I get my node webpage. I have been mining with Antminer U1's for a few months now without a problem I can ping 192.168.1.20 from the network/diagnostics tab on the Ant S1 and it finds it

can you post a screenshot of your S1 config page?

M

[windpath]

I have just received my new Ant S1's trying to connect them to my node on the local network  I have setup the following 3 pools

Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

Have you tried: stratum+tcp://192.168.1.20:9332

[jjw]

I have just received my new Ant S1's trying to connect them to my node on the local network  I have setup the following 3 pools

Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

I'm a relative P2Pool noob myself running an S1 and was able to get it going without too much difficulty.  Had a couple of minor IP addressing issues myself, but fully operator error.  I'm about 10 days ahead of you on this so will offer my "noob" experience.   

You say you were mining for awhile with U1s...were those mining to the same local p2pool node at 192.168.1.20?

You mention dhcp...I'm assuming the machine you're running your node on is configured to use 192.168.1.20 as a static address rather than getting dhcp leases?  That was one of my early problems...I'd assumed my machine was using a static (as I try to avoid DHCP as a rule on LANs) and I tried a bunch of other things before it occured to me that dynamic ip addressing was the issue.

Since you can ping 192.168.1.20 but the ant doesn't see the pool its a possibility that you're pinging a different machine thats not running the p2pool and your bitcoind (or qt).

Lastly, your bitcoind is running and fully synced?

In addition to a screenshot of your S! config screen a shot of your P2Pool window would be helpful as well

good luck

[andmax]

I have just received my new Ant S1's trying to connect them to my node on the local network  I have setup the following 3 pools

Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

I'm a relative P2Pool noob myself running an S1 and was able to get it going without too much difficulty.  Had a couple of minor IP addressing issues myself, but fully operator error.  I'm about 10 days ahead of you on this so will offer my "noob" experience.   

You say you were mining for awhile with U1s...were those mining to the same local p2pool node at 192.168.1.20?

You mention dhcp...I'm assuming the machine you're running your node on is configured to use 192.168.1.20 as a static address rather than getting dhcp leases?  That was one of my early problems...I'd assumed my machine was using a static (as I try to avoid DHCP as a rule on LANs) and I tried a bunch of other things before it occured to me that dynamic ip addressing was the issue.

Since you can ping 192.168.1.20 but the ant doesn't see the pool its a possibility that you're pinging a different machine thats not running the p2pool and your bitcoind (or qt).

Lastly, your bitcoind is running and fully synced?

In addition to a screenshot of your S! config screen a shot of your P2Pool window would be helpful as well

good luck

Thanks everyone for your help, Yes my node is setup with static ip 192.168.1.20. I received an email from Bitmain yesterday saying that the order you put the pools in on the config page isn't necessarily the order they connect at, the S1 will connect to the pool that responds the quickest, whether that is correct or not I don't know but I just removed Eclipse from my list and it connected up to my node fine, still doesn't show up my mates node as alive in the list on the miner status page as his node is my backup node in "Pool 2" but it is working now, thanks for all your help.


EDIT: I figured out the problem, there needs to be a password in the password section for each pool, even though you don't need a password to join a p2pool node the software needs something in there to work. Hope this helps someone else. Thanks everyone

[regtable69]

Has anyone got experience with compiling a win 32 qt.exe in linux? Is it really as much a ball ache as i have found it to be? Iv tried  qt creator method in win and linux. Also tried the mingw option and can get neither working.

[Polyatomic]

I've come to the conclusion my S2 doesn't work properly with p2pool because:

1 - p2pool can't feed it work fast enough.  Not likely because of vardiff, setting it to the max it seems to support (1024) doesn't change things
2 - the 10 second restarts
3 - something with my hardware

I'm thinking it's #2.

M

Have you tried lowering cgminer queue , the default seems to be 9999 on the S1.I would imagine the S2 is the same. Just exploring options here , don't freak out man.

[jjw]

It makes me sad to say this, but I've got to end my experiment with P2Pool.

I'm without question a hobbyist miner running a single antminer S1, and I was thrilled with the concept of P2Pool.

I've been running the node continuously for 20 days now, with a handful of 6-8 hours periods when I rolled over to backup nodes with much worse latecies, and just ran the numbers and have grossed .00624 BTC per day running a solid 200+ GH/s.

I guess I'm just a victim of bad luck/variance.

Was certainly willing to *risk* sacrificing some profitability to contribute towards decentralization, (and to keep myself busy/entertained configuring and optimizing my node) but getting HALF of my expected BTC for 3 weeks has pushed me to the point where I won't come close to breaking even on hardware barring a substantial spike in BTC prices (or a decline in difficulty, lol)

I still love the concept and will be keeping a close eye on things and will probably rejoin if I obtain more hashing power (something I'm seriously considering) or if some refinements are implemented to reduce variance for small miners (something I know forrestv has mentioned as a project/goal).

Wish you all lots of luck, and wanted to give particular thanks to mdude77 and jonnybravo0311 without whose posts I NEVER would have gotten a node going, much less running optimally.

[mdude77]

I've come to the conclusion my S2 doesn't work properly with p2pool because:

1 - p2pool can't feed it work fast enough.  Not likely because of vardiff, setting it to the max it seems to support (1024) doesn't change things
2 - the 10 second restarts
3 - something with my hardware

I'm thinking it's #2.

M

Have you tried lowering cgminer queue , the default seems to be 9999 on the S1.I would imagine the S2 is the same. Just exploring options here , don't freak out man.

That would be done how?

M

[PatMan]

I use -Q 0 on all my S1's with p2pool - I believe queuing should be disabled with p2pool anyway.....

[ceslick]

I have also noticed a drop of Blocks being found suddenly on P2Pool.

I was averaging 1-2 a day but now nothing in 3 days!

I am also a hobbyist and enjoy the idea of my own pool etc. I currently run 400GHS with another 400 arriving soon and am really wondering if I should pursue p2pool or start mining a larger pool..


Anyone else having similar issues with blocks not been found for the last 3 days?

[mdude77]

I have also noticed a drop of Blocks being found suddenly on P2Pool.

I was averaging 1-2 a day but now nothing in 3 days!

I am also a hobbyist and enjoy the idea of my own pool etc. I currently run 400GHS with another 400 arriving soon and am really wondering if I should pursue p2pool or start mining a larger pool..


Anyone else having similar issues with blocks not been found for the last 3 days?

It's called variance.  And variance can suck really bad on tiny pools (like p2pool).

M

[PatMan]

Anyone else having similar issues with blocks not been found for the last 3 days?

Erm.....everyone?

When p2pool finds a block, everyone gets a share of it. So when p2pool doesn't..........

[norgan]

that's the price we pay for being distributed. it does all work out even in the end apparently, just need some patience.
My first 2 weeks on p2pool have paid much more than I had got from larger pools and I'm only mining with 36gh/s! (again variance but it shows the p2pool can pay well even for small miners).

[windpath]

Looking forward to a 2-4 block surge when our luck comes back

Seriously though, over time it does even out, and generally p2pool comes out on top.

Leaving the pool during a long downturn (like 3-5 days, we are at 3 now) is like throwing the baby out with the bath water.

Luck, like anything else in life, is bound to change.

After a long streak of bad luck we typically see a long streak of _ _ _ _ luck

[bobsag3]

Happy to say we will be ramping up our private-for-now node, should add back a good 20-30th starting soon

[windpath]

Happy to say we will be ramping up our private-for-now node, should add back a good 20-30th starting soon

Good timing Glad your coming over....

[a.miner]

P2Pool puts up a nice web page that you can view in a browser to monitor your pool performance.

However, my p2pool node are behind a firewall, and I only let ports 8333 and 9333 through that wall.  And 22, for SSH and SFTP.

So, how can I monitor my p2pool node remotely under these conditions?

There are a lot of interesting files in ~/p2pool/data/bitcoin with intriguing names like graph_db and log and stats and such like.

I could just grab these files with SFTP and extract the information I want once I have them here.

Where can I find documentation for the file formats?

[windpath]

Where can I find documentation for the [log] file formats?

Would LOVE to find/see this....