 Show Posts
|
|
Pages: [1] 2 »
|
hey guys,
I just started my ltc p2pool server again after taking a break for 6 months. I upgraded to 13.4-4 and seeing my memory usage creep up to 1gb. I restart P2pool and all is fine. I'm running Python 2.7.2+ on Ubuntu Linux server 11.10. I cant find anyone lately having the same problem. Where should I start to solve this?
PS
You should use p2pool 13.3. I've tried to upgrade 13.3 to 13.4 but the latter did not got any shares. |
|
|
|
Is anyone seeing this? or is this just normal variance?
Yes, I also meet the similar condition (look at the previous page). The client 13.4 does not function properly and nobody here tempts to explain why. Do not use it. |
|
|
|
Dear friends! Could anybody explain this situation? Hi, I've just upgrared from version 13.3 to version 13.4 by replacing files in the program folder. Immedaitely after upgrading current payout was reduced from ~1.2 to ~0.7LTC  2.7 MH/s, GMT+06 Why this happen? It must not reduce payout immediately, because payout is determined by previsously mined shares... Thank you! ----------------------------------------------- After 5 hours of mining:  No shares found: 2013-12-16 13:28:02.682000 P2Pool: 17335 shares in chain (17339 verified/17339 total) Peers: 8 (1 incoming)
2013-12-16 13:28:02.682000 Local: 2830kH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-7%) Expected time to share: 1.4 hours
2013-12-16 13:28:02.682000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0511 LTC
2013-12-16 13:28:02.682000 Pool: 1357MH/s Stale rate: 16.1% Expected time to block: 2.7 hours
2013-12-16 13:28:03.322000 Punishing share for 'Block-stale detected! height(c44ec31007ae222244e8e9b9d89a4625e49c635ea83d302437656d33197ad4da) < height(5084f0f73a84662a3fc8e56e804513adf0e376e6470499dfb169301c95f49591) or 1b152d9a != 1b152d9a'! Jumping from 12451e3b to c3be3583!
2013-12-16 13:28:03.354000 New work for worker! Difficulty: 0.000808 Share difficulty: 3.350757 Total block value: 50.000000 LTC including 0 transactions
2013-12-16 13:28:03.385000 New work for worker! Difficulty: 0.000808 Share difficulty: 3.350757 Total block value: 50.000000 LTC including 2 transactions
Version 13.4 does not work for me; I'm rolling back to version 13.3 and litecoin 0.8.5.1 |
|
|
|
Hi, I've just upgrared from version 13.3 to version 13.4 by replacing files in the program folder. Immedaitely after upgrading current payout was reduced from ~1.2 to ~0.7LTC 2.7 MH/s, GMT+06 Why this happen? It must not reduce payout immediately, because payout is determined by previsously mined shares... Thank you! ----------------------------------------------- After 5 hours of mining: No shares found: 2013-12-16 13:28:02.682000 P2Pool: 17335 shares in chain (17339 verified/17339 total) Peers: 8 (1 incoming)
2013-12-16 13:28:02.682000 Local: 2830kH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-7%) Expected time to share: 1.4 hours
2013-12-16 13:28:02.682000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0511 LTC
2013-12-16 13:28:02.682000 Pool: 1357MH/s Stale rate: 16.1% Expected time to block: 2.7 hours
2013-12-16 13:28:03.322000 Punishing share for 'Block-stale detected! height(c44ec31007ae222244e8e9b9d89a4625e49c635ea83d302437656d33197ad4da) < height(5084f0f73a84662a3fc8e56e804513adf0e376e6470499dfb169301c95f49591) or 1b152d9a != 1b152d9a'! Jumping from 12451e3b to c3be3583!
2013-12-16 13:28:03.354000 New work for worker! Difficulty: 0.000808 Share difficulty: 3.350757 Total block value: 50.000000 LTC including 0 transactions
2013-12-16 13:28:03.385000 New work for worker! Difficulty: 0.000808 Share difficulty: 3.350757 Total block value: 50.000000 LTC including 2 transactions
Version 13.4 does not work for me; I'm rolling back to version 13.3 and litecoin 0.8.5.1 |
|
|
|
|
Hi,
I have some strange problem. I've discovered that my node of version 13.3 kept litecoin log from 2013-08-21 (when I've installed it) to 2013-08-22. No log since 2013-08-23; yesterday it have stopped payment to default address for found shares. I've restarted it, and now I see log for 2013-12-04.
Why this can happen?
|
|
|
|
Get a new cpu miner?
OK to get new CPU miner  . |
|
|
|
Yes, yes! It is just dec 2012 version 1.3.0 which works with ltcmine but does not work with p2pool  2013-07-10 12:25:23: Running command: C:\guiminer\stratumproxy\mining_proxy.exe -pa scrypt -o ***.***.***.*** -p ****
2013-07-10 12:25:23: Listener for "Stratum" started
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,437 WARNING proxy jobs.<module> # C extension for midstate not available. Using default implementation instead.
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
2013-07-10 12:25:24: Listener for "Stratum": Traceback (most recent call last):
2013-07-10 12:25:24: Listener for "Stratum": File "mining_proxy.py", line 155, in main
2013-07-10 12:25:24: Listener for "Stratum": File "twisted\internet\defer.pyo", line 1045, in _inlineCallbacks
2013-07-10 12:25:24: Listener for "Stratum": File "mining_libs\utils.pyo", line 106, in detect_stratum
2013-07-10 12:25:24: Listener for "Stratum": TypeError: 'NoneType' object has no attribute '__getitem__'
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 INFO proxy mining_proxy.main # Stratum proxy version: 1.3.0
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 INFO proxy mining_proxy.main # Trying to connect to Stratum pool at ***.***.***.***:****
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 INFO proxy mining_proxy.main # Setting PoW algo: scrypt
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,460 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,460 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:****
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,460 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,466 INFO proxy mining_proxy.main # -----------------------------------------------------------------------
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,466 INFO proxy mining_proxy.main # -----------------------------------------------------------------------
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,466 INFO proxy client_service.handle_event # Setting new difficulty: 5.38747577579
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,493 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:****
2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,494 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,707 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,707 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:****
2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,707 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,720 INFO proxy client_service.handle_event # Setting new difficulty: 5.38747577579
2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,727 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:****
2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,727 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,194 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,194 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:****
2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,194 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,198 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383
2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,213 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:****
2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,213 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,836 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,836 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:****
2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,836 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,839 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383
2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,861 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:****
2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,861 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,713 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,713 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:****
2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,713 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,743 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383
2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,834 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:****
2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,834 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,507 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,507 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:****
2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,509 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,552 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383
2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,671 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:****
2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,671 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
2013-07-10 12:25:39: Listener for "Stratum": Unhandled error in Deferred:
2013-07-10 12:25:39: Listener for "Stratum": Unhandled Error
2013-07-10 12:25:39: Listener for "Stratum": Traceback (most recent call last):
2013-07-10 12:25:39: Listener for "Stratum": File "twisted\web\server.pyo", line 156, in process
2013-07-10 12:25:39: Listener for "Stratum": File "twisted\web\server.pyo", line 191, in render
2013-07-10 12:25:39: Listener for "Stratum": File "twisted\web\resource.pyo", line 216, in render
2013-07-10 12:25:39: Listener for "Stratum": File "mining_libs\getwork_listener.pyo", line 165, in render_POST
2013-07-10 12:25:39: Listener for "Stratum": --- <exception caught here> ---
2013-07-10 12:25:39: Listener for "Stratum": File "twisted\internet\defer.pyo", line 134, in maybeDeferred
2013-07-10 12:25:39: Listener for "Stratum": File "mining_libs\worker_registry.pyo", line 37, in authorize
2013-07-10 12:25:39: Listener for "Stratum": File "stratum\socket_transport.pyo", line 89, in rpc
2013-07-10 12:25:39: Listener for "Stratum": stratum.custom_exceptions.TransportException: Not connected |
|
|
|
Why do you need a proxy?
I have several getwork CPU miners behind stratum proxy. |
|
|
|
Try the proxy listed on slush pool
It does not work. This proxy is for bicoins only, it has no option -pa scrypt |
|
|
|
Do you have compatible stratum mining proxy as Windows binary? I need it for litecoin mining, but mining_proxy 1.3.0 from guiminer-scrypt is not compatible with p2pool.
Again, yes or no? |
|
|
|
I'm doing test mining with versions 13.0-13.1 for two days 2013-07-10 10:47:12.841000 Local: 348kH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 21.4 hours
2013-07-10 10:47:12.841000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 LTC
2013-07-10 10:47:12.872000 Pool: 741MH/s Stale rate: 20.0% Expected time to block: 1.4 hours
2013-07-10 10:47:18.778000
2013-07-10 10:47:18.809000 New work for worker! Difficulty: 0.000109 Share difficulty: 6.293200 Total block value: 50.001000 LTC including 10 transact
ions No shares. Expected time may be 1.6 hours then again 1 day. Is it normal? Will I get any shares with p2pool? |
|
|
|
|
Hi,
Do you have compatible stratum mining proxy as Windows binary? I need it for litecoin mining, but mining_proxy 1.3.0 from guiminer-scrypt is not compatible with p2pool.
Thank you in advance!
|
|
|
|
There are two options:
1) Pay all frozen balances proportionally from available funds (1770 returned coins + my reserves), then close pool and forget or remember this;
2) Try to cover a part of frozen balances using fees, withdrawal limits and (possible) luck. This could take some time, but the final value will be higher than 1/3.
Both options are not good for those who make withdrawals rarely, I think. Probably It would be better to pay available funds depending for last withdrawal day. That is, at first pay for work that have been performed prior to 22.06.2013 if no withdrawal have been maked since this day, than for work performed in 23.06.2013, etc. until there are available funds. Than start normal pool work . |
|
|
|
|
314.22 is also perfect (20.5 KH/s at 1000/780) but the newest 320.18 is slower (17.5 KH/z)
|
|
|
|
I think the minimum requirement for a CUDA 5 application like cudaminer is a 302.something driver.
Thank you very much, I have 306.23 on another XPx64/GT520 computer, it is sufficient |
|
|
|
What about trying it with no flags other than the pool connection ones?
"C:\Program Files (x86)\guiminer\cudaminer\cudaminer.exe" -o ... -O ... -d 0 The same result |
|
|
|
Hello, I'm trying CUDA miner on Geforce GT520 (Fermi), Windows XP x64 and ForceWare 301.42 "C:\Program Files (x86)\guiminer\cudaminer\cudaminer.exe" -D -o http://...:8332 -O ... -d 0 -i 1 -l auto -C 0 -m 1
*** CudaMiner for nVidia GPUs by Christian Buchner ***
This is version 2013-04-30 (alpha)
based on pooler-cpuminer 2.2.3 (c) 2010 Jeff Garzik, 2012 pooler
Cuda additions Copyright 2013 Christian Buchner
My donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
[2013-06-24 11:59:48] 1 miner threads started, using 'scrypt' algorithm.
[2013-06-24 11:59:48] Long-polling activated for http://...:8332/lp
[2013-06-24 11:59:48] DEBUG: got new work in 31 ms
[2013-06-24 11:59:48] GPU #0: starting up...
[2013-06-24 11:59:48] GPU #0: with compute capability 2102272726.3
[2013-06-24 11:59:48] GPU #0: interactive: 1, tex-cache: 0 , single-alloc: 1
[2013-06-24 11:59:48] GPU #0: Performing auto-tuning (Patience...)
[2013-06-24 11:59:48] GPU #0: 0.00 khash/s with configuration 0x0
[2013-06-24 11:59:48] GPU #0: using launch configuration 0x0
Incorrect compute capability Is it possible to fix the problem? The card works correctly under rpcminer-cuda for bitcoin mining. |
|
|
|
|
AMD FX 8120 shows 50 khash/s more for litecoins, it is good enough for background mining.
|
|
|
|
|
I have ~37 khash/s under Windows XP x64 and ~53 khash/s under Windows 8 x64.
8 threads, AMD FX 8320.
minerd 2.23 x64
Possibly this is due to difference in scheduler policy: Windows 8 assigns dedicated kernel for each thread whereas XP kicks threads from one kernel to another.
I do not want to upgrade Windows XP to Windows 8. Instead, I would like to change Windows XP scheduler policy - is it possible?
|
|
|
|
|
Yes, it can bring some amount of currency. The best option is LTC/FTC because this card have 256-bit memory bus that is good for script mining. Overclockers get 350/400 MH/s from this card.
|
|
|
|
|
