Bitcoin Forum
December 10, 2016, 06:52:44 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 [224] 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2034804 times)
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
January 23, 2013, 05:50:35 PM
 #4461

Anyone know what is wrong with the pool over the past day or so?  I don't see anything in the recent code changes, but the pool seems to be finding way more blocks that it is supposed to, so something is apparently wrong...
lol. "We are making to much money! Something is wrong guys!"

It's called luck.

Since bad luck is almost often blamed on the pool being broken, I felt like it was important that someone question the proper functioning of the pool when we have good luck to keep things fair and balanced.  (in other words, it was sarcasm)

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
1481395964
Hero Member
*
Offline Offline

Posts: 1481395964

View Profile Personal Message (Offline)

Ignore
1481395964
Reply with quote  #2

1481395964
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481395964
Hero Member
*
Offline Offline

Posts: 1481395964

View Profile Personal Message (Offline)

Ignore
1481395964
Reply with quote  #2

1481395964
Report to moderator
PatMan
Hero Member
*****
Offline Offline

Activity: 924


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
January 24, 2013, 01:05:46 AM
 #4462

Nothing like a bit of luck to break the silence eh?

I'm genuinely happy for you all, really. But for my setup it still isn't worth switching back just yet, I'll wait until the wee bugs in stratum & memleak have been ironed out first I think, as I'm still earning consistently at ozcoin to be honest, suits my setup much better at the moment. Never had such a low reject rate - currently @ 986% efficiency on stratum - I just don't get that here.......yet

Besides, one good day in 60 isn't enough to sway me over, but I'll keep an eye on how you're doing here, and when it's ready, I'll be back......

Enjoy the coinage. Viva p2p.

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
Aseras
Hero Member
*****
Offline Offline

Activity: 658


View Profile
January 25, 2013, 12:59:28 AM
 #4463

Of course as usual someone had to mention luck and kill it.
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
January 25, 2013, 08:37:28 PM
 #4464

I believe the memory leak is fixed in git. Can everyone who can pull and notify me if memory is still leaking?

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
January 26, 2013, 01:53:34 AM
 #4465

I believe the memory leak is fixed in git. Can everyone who can pull and notify me if memory is still leaking?
Share chain files need to be deleted.
If not it spikes to 500MB and holds there.
After delete files it holds on 300MB.
Ubuntu x64 4GB

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
cabin
Full Member
***
Offline Offline

Activity: 205


View Profile
January 27, 2013, 02:25:35 PM
 #4466

On windows 7 mine holds at 190MB

1Cabinz1RSccAbFx2DikYomSKeMupy7M6V
Balthazar
Legendary
*
Offline Offline

Activity: 2002


Post rank racist


View Profile
January 27, 2013, 02:49:12 PM
 #4467

p2pool's main problem is being penalized for including transactions.

P2pool miners are protecting the network against >50% attacks. That is a HUGE benefit for the bitcoin network.
GBT and BlkPrep users are protecting network against >50% attacks. In fact, P2Pool users are really doing nothing in comparison with them (300-400GH/s vs. 2-3 Thash/s). For now.

novaco.in | VMWare VMHGFS driver for 3.19.x kernels | Ukrainian translation for Novacoin [Done]
฿: 1GV8D5SRkA3cPccpYhVc2wMkjwz3UREEpy: 4RgnHWtnJWEyMhqhDdazW3Hdr7cx5ybF6i
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
January 27, 2013, 06:38:34 PM
 #4468

p2pool's main problem is being penalized for including transactions.

P2pool miners are protecting the network against >50% attacks. That is a HUGE benefit for the bitcoin network.
GBT and BlkPrep users are protecting network against >50% attacks. In fact, P2Pool users are really doing nothing in comparison with them (300-400GH/s vs. 2-3 Thash/s). For now.

What's your source for 2-3 TH/s?

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
lenny_
Legendary
*
Offline Offline

Activity: 953



View Profile
January 28, 2013, 01:44:29 AM
 #4469

I believe the memory leak is fixed in git. Can everyone who can pull and notify me if memory is still leaking?

Please check my node:
http://lenny.dnsd.me:9332
Code:
Version: 11.1-5-g0e325a4
Node uptime: 0.486 days Peers: 6 out, 2 in
Not yet 12 hours uptime and already 671MB usage, according to Memory Usage details on Graph tab. I am running out of memory now as I have 1GB RAM on this machine. Soon I will have to turn it off - there is no change in memory usage since December 2012. It's still very high and unusable for me.
Current stats (I wrote simple script to print this information)
Code:
17269 pioruns   20   0  811m 639m 1776 S    4 64.6 275:51.43 python                                                                                          
17436 pioruns   20   0  601m  91m 7752 S   20  9.3  44:15.31 bitcoind                                                                                        
Linux 2.6.32-5-amd64 x86_64 GNU/Linux
Description: Debian GNU/Linux 6.0.6 (squeeze)
Python 2.6.6

Current p2pool version: 11.1-5-g0e325a4
commit 0e325a45dc1c1d40eabcf066c3b52a381ece569a

Current version: Bitcoin version v0.7.1-404-g0d3d609-beta
commit 0d3d6094faf0da252c581d58454ecc4be91aacb9


EDIT: As I finish editing this post and checking posts, it's already 681 MB on graph menu and 648 MB in top (was 639 about 15 minutes ago) ...

forrestv, what I can do for you to help debugging?
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
January 28, 2013, 01:53:32 PM
 #4470

FYI, I broke something with one of the servers that sit behind p2pool.info this weekend and the result was it was mis-reporting some blocks as orphaned (that weren't really orphaned).  It's being fixed now...

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
cabin
Full Member
***
Offline Offline

Activity: 205


View Profile
January 28, 2013, 02:16:40 PM
 #4471

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?

1Cabinz1RSccAbFx2DikYomSKeMupy7M6V
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
January 28, 2013, 04:52:11 PM
 #4472

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.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
cabin
Full Member
***
Offline Offline

Activity: 205


View Profile
January 28, 2013, 07:36:40 PM
 #4473

Ok thanks that makes sense. No I don't see it often at all.. maybe just a few times right after I start p2pool.

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.

1Cabinz1RSccAbFx2DikYomSKeMupy7M6V
Rogue Star
Member
**
Offline Offline

Activity: 88


View Profile
January 29, 2013, 01:25:19 AM
 #4474

Lenny, simply upgrading to the most recent commit in git will help. I think that 11.1-6-g19bf4ea solves the leak.
I'm still seeing the leak on my node on the latest code, so you might want to check that out when you get a chance. Another odd thing I noticed on the stats page is it is showing solved blocks >24 hours old

you can donate to me for whatever reason at: 18xbnjDDXxgcvRzv5k2vmrKQHWDjYsBDCf
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
January 29, 2013, 08:08:23 AM
 #4475

I believe the memory leak is fixed in git. Can everyone who can pull and notify me if memory is still leaking?
Version: 11.1-6-g19bf4ea
Ubuntu 64bit 4GB
When I run it on "old" sharechain (over 24hrs offline) it bumps to about 520MB
When I delete share chain and allow to re download, it walks to about 300MB and holds there.

There is still something wrong in chain handling imo (maybe txes are not cleared?).
Maybe add a check - if node starts over 12hrs after last share in chain delete it completely and redownload?

Also I still thinks, that txes should be sent on demand, not to all connected nodes. "Peer sent entire transaction..." is seen too many times in log...

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
K1773R
Legendary
*
Offline Offline

Activity: 1526


/dev/null


View Profile
January 29, 2013, 08:22:32 AM
 #4476

I believe the memory leak is fixed in git. Can everyone who can pull and notify me if memory is still leaking?
Version: 11.1-6-g19bf4ea
Ubuntu 64bit 4GB
When I run it on "old" sharechain (over 24hrs offline) it bumps to about 520MB
When I delete share chain and allow to re download, it walks to about 300MB and holds there.

There is still something wrong in chain handling imo (maybe txes are not cleared?).
Maybe add a check - if node starts over 12hrs after last share in chain delete it completely and redownload?

Also I still thinks, that txes should be sent on demand, not to all connected nodes. "Peer sent entire transaction..." is seen too many times in log...
on demand -> ask if he knows the TX, if he says no send the TX to him.

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
January 29, 2013, 09:04:34 AM
 #4477

Also I still thinks, that txes should be sent on demand, not to all connected nodes. "Peer sent entire transaction..." is seen too many times in log...
on demand -> ask if he knows the TX, if he says no send the TX to him.
I think about:
- received new share -> check txes it contains
- have all tx -> noop
- not have some txes -> ask for them node that send share
- node not send back tx in 2-5 sec -> check local bitcoin again -> ask another node/s if need

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
lenny_
Legendary
*
Offline Offline

Activity: 953



View Profile
January 29, 2013, 09:33:03 PM
 #4478

Lenny, simply upgrading to the most recent commit in git will help. I think that 11.1-6-g19bf4ea solves the leak.
Indeed, it holds for 382 MB for whole day and even decreasing over time. Thank you forrestv! Smiley
neosniperkiller
Newbie
*
Offline Offline

Activity: 8



View Profile
January 30, 2013, 08:02:33 PM
 #4479

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate:  Efficiency:  Current payout: 0.0000 BTC"

== phoenix

Now I tried to mine on it using phoenix and it can connect to the p2pool.
But somehow when phoenix says "result accepted", nothing is displayed in the p2pool concerning that result.

== bfgminer

Second try was with bfgminer, see stats below, but still nothing changed at the p2pool overview.

 [2013-01-30 20:41:44] Started at [2013-01-30 20:29:46]
 [2013-01-30 20:41:44] Pool: http://192.168.1.4:9332
 [2013-01-30 20:41:44] Runtime: 0 hrs : 11 mins : 55 secs
 [2013-01-30 20:41:44] Average hashrate: 21.4 Megahash/s
 [2013-01-30 20:41:44] Solved blocks: 0
 [2013-01-30 20:41:44] Best share difficulty: 1
 [2013-01-30 20:41:44] Queued work requests: 82
 [2013-01-30 20:41:44] Share submissions: 5
 [2013-01-30 20:41:44] Accepted shares: 5
 [2013-01-30 20:41:44] Rejected shares: 0
 [2013-01-30 20:41:44] Accepted difficulty shares: 5
 [2013-01-30 20:41:44] Rejected difficulty shares: 0
 [2013-01-30 20:41:44] Reject ratio: 0.0%
 [2013-01-30 20:41:44] Hardware errors: 0
 [2013-01-30 20:41:44] Efficiency (accepted shares * difficulty / 2 KB): 0.01
 [2013-01-30 20:41:44] Utility (accepted shares / min): 0.42/min

 [2013-01-30 20:41:44] Discarded work due to new blocks: 197
 [2013-01-30 20:41:44] Stale submissions discarded due to new blocks: 0
 [2013-01-30 20:41:44] Unable to get work from server occasions: 0
 [2013-01-30 20:41:44] Work items generated locally: 431
 [2013-01-30 20:41:44] Submitting work remotely delay occasions: 0
 [2013-01-30 20:41:44] New blocks detected on network: 1


Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?
Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 30, 2013, 10:20:02 PM
 #4480

At 21.4mh, it's going to take a LONG time to find a share.  If you check the p2pool output, it'll tell you the average time it'll take.  Wildly guessing, maybe 1/2 a day.

M

I just setup my own multi merged p2pool (LINUX VERSION) (BTCwith all the alt coins) on my local network and it's running nicely.
All the chains are fully updated and the p2pool keeps receiving information.
Trying to mine on it works, shares get accepted, but the overview keeps on displaying the following line:

"Shares: 0 (0 orphan, 0 dead) Stale rate:  Efficiency:  Current payout: 0.0000 BTC"

== phoenix

Now I tried to mine on it using phoenix and it can connect to the p2pool.
But somehow when phoenix says "result accepted", nothing is displayed in the p2pool concerning that result.

== bfgminer

Second try was with bfgminer, see stats below, but still nothing changed at the p2pool overview.

 [2013-01-30 20:41:44] Started at [2013-01-30 20:29:46]
 [2013-01-30 20:41:44] Pool: http://192.168.1.4:9332
 [2013-01-30 20:41:44] Runtime: 0 hrs : 11 mins : 55 secs
 [2013-01-30 20:41:44] Average hashrate: 21.4 Megahash/s
 [2013-01-30 20:41:44] Solved blocks: 0
 [2013-01-30 20:41:44] Best share difficulty: 1
 [2013-01-30 20:41:44] Queued work requests: 82
 [2013-01-30 20:41:44] Share submissions: 5
 [2013-01-30 20:41:44] Accepted shares: 5
 [2013-01-30 20:41:44] Rejected shares: 0
 [2013-01-30 20:41:44] Accepted difficulty shares: 5
 [2013-01-30 20:41:44] Rejected difficulty shares: 0
 [2013-01-30 20:41:44] Reject ratio: 0.0%
 [2013-01-30 20:41:44] Hardware errors: 0
 [2013-01-30 20:41:44] Efficiency (accepted shares * difficulty / 2 KB): 0.01
 [2013-01-30 20:41:44] Utility (accepted shares / min): 0.42/min

 [2013-01-30 20:41:44] Discarded work due to new blocks: 197
 [2013-01-30 20:41:44] Stale submissions discarded due to new blocks: 0
 [2013-01-30 20:41:44] Unable to get work from server occasions: 0
 [2013-01-30 20:41:44] Work items generated locally: 431
 [2013-01-30 20:41:44] Submitting work remotely delay occasions: 0
 [2013-01-30 20:41:44] New blocks detected on network: 1


Anybody knows what I'm doing wrong??
Is this normal behavior of p2pool? When does the p2pool actually increases the "shares"?
Also, how does the p2pool add the alt coin deposits? I cannot see any other accounts made than " " on the alt coin daemons.

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
Pages: « 1 ... 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 [224] 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!