Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 278. (Read 2591928 times)
September 27, 2014, 12:35:34 PM
I am having issues with my bitcoind not responding after a few hours running. I am trying to keep my p2pool node active. Just cant figure out what bitcoind is crashing.
September 26, 2014, 04:52:34 PM
How high can the efficiency go?
On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.
Efficiency is a measure of how your node is doing compared to the rest of the network. It compares your orphans/deads to the network. The lower your ratio of orphans/deads to the network's, the higher your efficiency.On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.
If you want to see the code...
web.py:
Code:
global_stale_prop = p2pool_data.get_average_stale_prop(node.tracker, node.best_share_var.value, look behind)
...
efficiency=(1 - (stale_orphan_shares+stale_doa_shares)/shares)/(1 - global_stale_prop) if shares else None
...
efficiency=(1 - (stale_orphan_shares+stale_doa_shares)/shares)/(1 - global_stale_prop) if shares else None
data.py:
Code:
def get_average_stale_prop(tracker, share_hash, lookbehind):
stales = sum(1 for share in tracker.get_chain(share_hash, lookbehind) if share.share_data['stale_info'] is not None)
return stales/(lookbehind + stales)
stales = sum(1 for share in tracker.get_chain(share_hash, lookbehind) if share.share_data['stale_info'] is not None)
return stales/(lookbehind + stales)
September 26, 2014, 04:19:16 PM
How high can the efficiency go?
On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.
Efficiency is a measure of how your node is doing compared to the rest of the network. It compares your orphans/deads to the network. The lower your ratio of orphans/deads to the network's, the higher your efficiency.On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.
If you want to see the code...
web.py:
Code:
global_stale_prop = p2pool_data.get_average_stale_prop(node.tracker, node.best_share_var.value, look behind)
...
efficiency=(1 - (stale_orphan_shares+stale_doa_shares)/shares)/(1 - global_stale_prop) if shares else None
...
efficiency=(1 - (stale_orphan_shares+stale_doa_shares)/shares)/(1 - global_stale_prop) if shares else None
data.py:
Code:
def get_average_stale_prop(tracker, share_hash, lookbehind):
stales = sum(1 for share in tracker.get_chain(share_hash, lookbehind) if share.share_data['stale_info'] is not None)
return stales/(lookbehind + stales)
stales = sum(1 for share in tracker.get_chain(share_hash, lookbehind) if share.share_data['stale_info'] is not None)
return stales/(lookbehind + stales)
September 26, 2014, 03:11:11 PM
How high can the efficiency go?
On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.
On my node I'm running around 107% right now with 20 peers (9 incoming) (plus my miners), but last night it hit 117.6% when I had 14 peers ( 6 incoming).
How is the efficiency deterermined / calculated? what are the criteria / factors?
Thanks.
September 26, 2014, 09:21:33 AM
Shellshock, Aftershock & P2Pool
If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.
Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:
Code:
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
If you see:
Quote
vulnerable
this is a test
this is a test
You are vulnerable and should update bash immediately.
Linux users should run:
Code:
sudo apt-get update
sudo apt-get install bash
sudo apt-get install bash
Apple has promised a security fix for Mac users soon.
Code:
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test
That's on Ubuntu 14.04LTS fully updated as of the time of writing this post. OSX 10.9.5 Mavericks is still vulnerable:bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test
Code:
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
vulnerable
this is a test
vulnerable
this is a test
September 26, 2014, 08:42:31 AM
Shellshock, Aftershock & P2Pool
If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.
Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:
Code:
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
If you see:
Quote
vulnerable
this is a test
this is a test
You are vulnerable and should update bash immediately.
Linux users should run:
Code:
sudo apt-get update
sudo apt-get install bash
One advantage of running windows servers 😉 sudo apt-get install bash
Apple has promised a security fix for Mac users soon.
September 26, 2014, 08:33:20 AM
Shellshock, Aftershock & P2Pool
If you have not heard, a new vulnerability called Shellshock — also called the "Bash Bug" — is affecting both Linux computers and Macs, and it has the potential to let attackers take control of your computer or server.
Many P2Pool nodes run on Linux and Mac, to test your node open up a shell and run:
Code:
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
If you see:
Quote
vulnerable
this is a test
this is a test
You are vulnerable and should update bash immediately.
Linux users should run:
Code:
sudo apt-get update
sudo apt-get install bash
sudo apt-get install bash
Apple has promised a security fix for Mac users soon.
September 26, 2014, 12:28:30 AM
Well bugger me. Just found my first ever block - only took me 18 months.........
That deserves a spliff. Nice
That deserves a spliff. Nice
Sarcasm alert! :-)
September 25, 2014, 10:13:51 AM
Well bugger me. Just found my first ever block - only took me 18 months.........
That deserves a spliff. Nice
That deserves a spliff. Nice
Cool Dude!!!!!
I guess I will never get one, just hung up my operation.... 4T and the income verses electric is not good.....
Hope you find more!!!!
September 24, 2014, 05:49:59 PM
I got the answer I needed on the spondoolies thread, thanks. It works fine.
September 24, 2014, 05:12:29 PM
Well bugger me. Just found my first ever block - only took me 18 months.........
That deserves a spliff. Nice
That deserves a spliff. Nice
Cheers
September 24, 2014, 04:11:07 PM
Well bugger me. Just found my first ever block - only took me 18 months.........
That deserves a spliff. Nice
That deserves a spliff. Nice
September 24, 2014, 10:02:45 AM
Does anyone know of any good bitcoin p2pool scanners besides these two:
http://p2pool-nodes.info
http://p2pool.hostv.pl
Thanks!
http://p2pools.org/btc http://p2pool-nodes.info
http://p2pool.hostv.pl
Thanks!
September 24, 2014, 08:09:39 AM
Does anyone know of any good bitcoin p2pool scanners besides these two:
http://p2pool-nodes.info
http://p2pool.hostv.pl
Thanks!
http://p2pool-nodes.info
http://p2pool.hostv.pl
Thanks!
https://github.com/litecoin-project/p2pool-scanner
September 23, 2014, 10:22:59 PM
Does anyone know of any good bitcoin p2pool scanners besides these two:
http://p2pool-nodes.info
http://p2pool.hostv.pl
Thanks!
http://p2pool-nodes.info
http://p2pool.hostv.pl
Thanks!
September 23, 2014, 07:26:27 PM
Instead of using Control-C, you can issue the kill command:
Thank you very much, jonnybravo0311. Intelligent, pointed, and useful verbosity at it's best. I'll spend some time going over the man for kill, now that you've pointed me in that direction. Code:
kill -KILLARG pid
For exampleCode:
kill -15 1234
To get a listing of all available on your system, just do:Code:
kill -l
That will return a list something like this:Code:
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG
17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD
21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU
25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH
29) SIGINFO 30) SIGUSR1 31) SIGUSR2
By default, if you don't specify the name/number, kill will use 15 (SIGTERM). It's basically a nice way of telling the process to terminate. If you're feeling particularly uncaring, you can use 9 (SIGKILL), which effectively bypasses the process altogether and tells the kernel to force the process to die. Control C is effectively sending 2 (SIGINT) to the process. It's a bit more complex, as Control C sends the SIGINT to all of the processes in the process group controlled by the program; however, for p2pool, it's effectively the same since there's only a single process.5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG
17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD
21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU
25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH
29) SIGINFO 30) SIGUSR1 31) SIGUSR2
September 23, 2014, 07:01:53 PM
Is there a graceful method of shutting down the p2pool terminal? I haven't been able to find anything for it so I'm simply using Control C ... is there another / better option?
That's as graceful as it gets........you could sing a lullaby
You don't really want to be turning it off - let it run, & run, & run........
I'm still experimenting so it's on and off at the moment.
Next step is set it up for merged.
Ordered new dual xeon server to be dedicated to pools, once it's ready to go then it will run & run & run ...
I wouldn't buy hardware to run p2pool. My miners and my p2pool node are not in the same place and my efficiency is currently 108%. Pay $20 a month for a Linode near your miners and stop paying when you stop mining (which for most of us is any minute now).
You'll get incredible network connectivity and the flexibility to turn things off without being stuck with equipment you don't need (like thousands of dollars of ASICs
It was $2,500 for all the parts, so it's pretty reasonable for a server. The funds came from mining so it's not out-of-pocket funds.
I plan on running numerous pools from it at the same time.
I have a 50mb/s (down) fibre connection.
Running it will help to reduce the winter gas bill.
My electricity costs are fairly low where I live.
You make some good points regarding rental and about self-mining no longer being sustainable for most. I agree, it won't be long until it can no longer provide a positive ROI.
Thanks for the feedback.
September 23, 2014, 06:28:19 PM
Is there a graceful method of shutting down the p2pool terminal? I haven't been able to find anything for it so I'm simply using Control C ... is there another / better option?
That's as graceful as it gets........you could sing a lullaby
You don't really want to be turning it off - let it run, & run, & run........
I'm still experimenting so it's on and off at the moment.
Next step is set it up for merged.
Ordered new dual xeon server to be dedicated to pools, once it's ready to go then it will run & run & run ...
I wouldn't buy hardware to run p2pool. My miners and my p2pool node are not in the same place and my efficiency is currently 108%. Pay $20 a month for a Linode near your miners and stop paying when you stop mining (which for most of us is any minute now).
You'll get incredible network connectivity and the flexibility to turn things off without being stuck with equipment you don't need (like thousands of dollars of ASICs
September 23, 2014, 03:49:18 PM
Is there a graceful method of shutting down the p2pool terminal? I haven't been able to find anything for it so I'm simply using Control C ... is there another / better option?
That's as graceful as it gets........you could sing a lullaby
You don't really want to be turning it off - let it run, & run, & run........
I'm still experimenting so it's on and off at the moment.
Next step is set it up for merged.
Ordered new dual xeon server to be dedicated to pools, once it's ready to go then it will run & run & run ...
Code:
kill -KILLARG pid
For exampleCode:
kill -15 1234
To get a listing of all available on your system, just do:Code:
kill -l
That will return a list something like this:Code:
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG
17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD
21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU
25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH
29) SIGINFO 30) SIGUSR1 31) SIGUSR2
By default, if you don't specify the name/number, kill will use 15 (SIGTERM). It's basically a nice way of telling the process to terminate. If you're feeling particularly uncaring, you can use 9 (SIGKILL), which effectively bypasses the process altogether and tells the kernel to force the process to die. Control C is effectively sending 2 (SIGINT) to the process. It's a bit more complex, as Control C sends the SIGINT to all of the processes in the process group controlled by the program; however, for p2pool, it's effectively the same since there's only a single process. 5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG
17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD
21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU
25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH
29) SIGINFO 30) SIGUSR1 31) SIGUSR2
September 23, 2014, 03:36:20 PM
Is there a graceful method of shutting down the p2pool terminal? I haven't been able to find anything for it so I'm simply using Control C ... is there another / better option?
That's as graceful as it gets........you could sing a lullaby
You don't really want to be turning it off - let it run, & run, & run........
I'm still experimenting so it's on and off at the moment.
Next step is set it up for merged.
Ordered new dual xeon server to be dedicated to pools, once it's ready to go then it will run & run & run ...
Jump to: