 Show Posts
|
|
Pages: [1] 2 3 »
|
I am trying to connect asicminer BE cubes by miner_proxy with p2pool by stratum. Firstly, I am solved issue for geting job form p2pool to proxy by stratum, with patching protocol.py in stratum, by adding MAX_LENGTH = 16384000. Now job received by proxy, but cubes can not get works by getwork. C:\Python27\python.exe C:\stratum-mining-proxy-master\mining_proxy.py -gp 1234 -o 192.168.1.2 -p 9332
ecdsa package not installed. Signing of messages not available.
2014-04-17 11:19:33,654 INFO proxy jobs.<module> # C extension for midstate not available. Using default implementation instead.
2014-04-17 11:19:33,661 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
File "C:\stratum-mining-proxy-master\mining_proxy.py", line 182, in main
new_host = (yield utils.detect_stratum(args.host, args.port))
File "C:\Users\Ed\AppData\Roaming\Python\Python27\site-packages\twisted\internet\defer.py", line 1039, in _inlineCallbacks
result = g.send(result)
File "C:\stratum-mining-proxy-master\mining_libs\utils.py", line 69, in detect_stratum
header = f.response_headers.get('x-stratum', None)[0]
TypeError: 'NoneType' object has no attribute '__getitem__'
2014-04-17 11:19:33,667 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.6
2014-04-17 11:19:33,673 WARNING proxy mining_proxy.test_update # Checking for updates...
2014-04-17 11:19:34,398 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at 192.168.1.2:9332
2014-04-17 11:19:34,401 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2014-04-17 11:19:34,403 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at 192.168.1.2:9332
2014-04-17 11:19:34,403 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2014-04-17 11:19:34,407 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2014-04-17 11:19:34,408 WARNING proxy mining_proxy.main # PROXY IS LISTENING ON ALL IPs ON PORT 3333 (stratum) AND 1234 (getwork)
2014-04-17 11:19:34,410 WARNING proxy mining_proxy.main # -----------------------------------------------------------------------
2014-04-17 11:19:34,410 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:34,411 INFO proxy client_service.handle_event # New job 218120647496641940954239730939632275078 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:34,545 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:34,548 INFO proxy client_service.handle_event # New job 233046745934337131359805487615947343187 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:34,555 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:34,558 INFO proxy client_service.handle_event # New job 284941301167202598133416390532168241875 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:34,573 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:34,576 INFO proxy client_service.handle_event # New job 52839956628851028754347912368349498747 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:34,582 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:34,585 INFO proxy client_service.handle_event # New job 277582709765589873348201656238505047486 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:39,424 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:39,427 INFO proxy client_service.handle_event # New job 322025871892336027966607250075456363594 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:39,444 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:39,447 INFO proxy client_service.handle_event # New job 43771082499366205961820283141945869025 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:39,453 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:39,454 INFO proxy client_service.handle_event # New job 30759498972173187666825674470747965721 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:39,486 INFO proxy client_service.handle_event # Setting new difficulty: 41.8985580334
2014-04-17 11:19:39,487 INFO proxy client_service.handle_event # New job 174567020690227360933972996388366795346 for prevhash 6a692fa7, clean_jobs=True
2014-04-17 11:19:40,905 INFO proxy mining_proxy.on_shutdown # Shutting down proxy...
2014-04-17 11:19:40,907 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at 192.168.1.2:9332
2014-04-17 11:19:40,910 INFO stats stats.print_stats # 0 peers connected, state changed 1 times
If I run miner_proxy.py by default, it work normally. |
|
|
|
I use bfgminer -http-port 8330 to proxy for an ASICMiner BE Cube and it works very well with p2pool.
this is Long Poll: inactive sheme, could you please check your Efficieny: ?% |
|
|
|
Don't use the mining proxy? iirc p2pool works fine with getwork.
ASICMiner Block Erupter Cube directed to p2pool has only about 60% efficiency and p2pool not show hashrate fo it insted console msg: I believe others have said cubes don't work well with p2pool. But hey, 60% is better than 0% with the proxy.  Seriously, I suggest another pool with a cube. cubes work well with proxy - 97-98% efficiency... will be fine that proxy work with p2pool... |
|
|
|
Don't use the mining proxy? iirc p2pool works fine with getwork.
ASICMiner Block Erupter Cube directed to p2pool has only about 60% efficiency and p2pool not show hashrate fo it insted console msg: 2014-04-16 12:28:24.499000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:24.795000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:24.795000 Hash: b06b586f4dac49697137d0d941e4bb5460f6b340cd1b2bc02236bf79cdcf8ad
2014-04-16 12:28:24.795000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:24.811000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:24.811000 Hash: fbc6c59bd5586e439ea88260933111aefff5a2d5c8916302453781ce60c494ed
2014-04-16 12:28:24.811000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:24.826000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:24.826000 Hash: 4d1503faebd95b9e174da6e32146fbc131767282eb88d4b2c8edf6e6fd17ed47
2014-04-16 12:28:24.826000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.060000 P2Pool: 17688 shares in chain (14732 verified/17692 total) Peers: 6 (0 incoming)
2014-04-16 12:28:25.060000 Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ???
2014-04-16 12:28:25.060000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2014-04-16 12:28:25.060000 Pool: 165TH/s Stale rate: 13.0% Expected time to block: 1.8 days
2014-04-16 12:28:25.232000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.232000 Hash: 63311e01ab25caf7eb4760d5557ec77eaf7cfe037568d7f6abd23359d31f9a03
2014-04-16 12:28:25.232000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.248000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.248000 Hash: e403b813ac18c496bdb9e7c98141944ddf0454abd39c1a38189823b3e8fcdcfb
2014-04-16 12:28:25.248000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.263000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.263000 Hash: 3987e9f12da6fbf7dd74b871f6e3994317da901e4de3366cd673915f981043a6
2014-04-16 12:28:25.263000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.279000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.279000 Hash: e004ab6b08d567116c9334d6c1cbafb92c00fccbab6f0407f705efd2765c99a7
2014-04-16 12:28:25.279000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.638000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.638000 Hash: e89f94af0e8430c4ab61b98a03b4e95d09888a14389b1691ea8c8486b446d783
2014-04-16 12:28:25.638000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.669000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.669000 Hash: 78bb795c7ebdf9d232f8e7227c5a3f1b4db6a2f10e967baf51e6a1ff2412a202
2014-04-16 12:28:25.669000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.684000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.684000 Hash: 49ae678a407d942dfaa7247a88e4b602d6c61ba4a6d26ef82751073de15c67ad
2014-04-16 12:28:25.684000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:25.716000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:25.716000 Hash: ad28087bd567f5c6616ce674d80d0f9fa2d71f472538eefc7a13105cdc85e9e6
2014-04-16 12:28:25.716000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.028000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.043000 Hash: 9af797c5688dfa2ff9e6739b4b57d457349eb21e02e2b54ae7f160ff766052d6
2014-04-16 12:28:26.043000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.059000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.059000 Hash: cfa674770ea156cb8aa45f188d07a623fc2d57a94ccedbb7007086f7544055d9
2014-04-16 12:28:26.059000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.106000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.106000 Hash: 5647fe3176bbe09fb5adc9bad7a502f92806708cfd3b47475210cd6698051ec8
2014-04-16 12:28:26.106000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
2014-04-16 12:28:26.308000 Worker cube253 submitted share with hash > target:
2014-04-16 12:28:26.308000 Hash: 7147c9870bcb9967e40e588e86e2471035bd78dc89c3998a3b146d2adb24f6e8
2014-04-16 12:28:26.308000 Target: db24b5c57d9bb0000000000000000000000000000000000000000000
|
|
|
|
anyone found solution for incompatibility mining_proxy with p2pool? C:\>mining_proxy -o 127.0.0.1 -p 9332 -gp 8330
2014-04-16 11:30:30,444 INFO proxy jobs.<module> # C extension for midstate not available. Using default implementation instead.
2014-04-16 11:30:30,444 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed
Traceback (most recent call last):
File "mining_proxy.py", line 182, in main
AttributeError: 'module' object has no attribute '_parse'
2014-04-16 11:30:30,444 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.5
2014-04-16 11:30:30,460 WARNING proxy mining_proxy.test_update # Checking for updates...
2014-04-16 11:30:31,022 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at 127.0.0.1:9332
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: stratum.custom_exceptions.TransportException: SocketTransportClientFactory connection timed out
2014-04-16 11:31:09,132 INFO proxy mining_proxy.on_shutdown # Shutting down proxy...
|
|
|
|
на закладке графики не все работают, и в момент обращения к оной в лог пишутся ошибки |
|
|
|
кому интересно пощупать другой фронт-енд для собственной ноды... грамотно, но не доделано... у меня он давно стоял, со старым п2пулом работал корректно, с новым глючит (графики и ошибки в лог валят) проект кажется заброшен начинаю делать донейты юзерам p2pool клева  ток я пока ниче не получил, хотя адрес свой в 3) вижу... |
|
|
|
|
по поводу нового п2пул
в списке ласт блок:
74015 Sun Feb 09 2014 20:55:22 GMT+0200 (Финляндия (зима)) 0000000000af00da0cd31a46079e6e64fa940e8126692e915aade0016bbc3e22
у меня в кошельке последняя тразакция Feb 09 2014 07:14, т.е. 8ми часовой не видно...
эксплориер, чтоб посмотреть адреса в транзакции не работает...
все ли в порядке?
|
|
|
|
P2Pool исправлен на предмет соединений с 0.4.4.7.
я понимаю, удача и все такое, но за последние сутки п2пул не нашел ни одного блока... |
|
|
|
Обновление клиента 0.4.4.7.
.......
перестал запускаться п2пул 2014-01-28 18:14:17.662000 p2pool (version p2pool-11.4.3)
2014-01-28 18:14:17.663000
2014-01-28 18:14:17.663000 Testing bitcoind RPC connection to 'http://127.0.0.1:8344/' with username 'чч'...
2014-01-28 18:14:17.715000 ...success!
2014-01-28 18:14:17.715000 Current block hash: чч
2014-01-28 18:14:17.716000 Current block height: чч
2014-01-28 18:14:17.716000
2014-01-28 18:14:17.716000 Testing bitcoind P2P connection to '127.0.0.1:7777'... и более ниче не происходит |
|
|
|
|
а Standard Shipping это чем отправляют?
пришло письмо, у них там вроде завал с отправками...
|
|
|
|
|
а долго они сейчас жолопены отправляют, если платить в биткоинах?
|
|
|
|
каждые 3 часа p2pool теряет связь с кошельком 2013-10-19 10:30:42.456000 P2Pool: 5811 shares in chain (3279 verified/5815 total) Peers: 8 (2 incoming) 2013-10-19 10:30:42.456000 Local: 1752kH/s in last 10.0 minutes Local dead on arrival: ~23.1% (19-28%) Expected time to 2013-10-19 10:30:42.457000 Shares: 14 (2 orphan, 1 dead) Stale rate: ~21.4% (7-48%) Efficiency: ~90.4% (60-107%) Current 2013-10-19 10:30:42.457000 Pool: 64884kH/s Stale rate: 13.0% Expected time to block: 7.3 hours 2013-10-19 10:30:45.459000 > ######################################## 2013-10-19 10:30:45.460000 > >>> Warning: LOST CONTACT WITH BITCOIND for 1.1 minutes! Check that it isn't frozen or dead! 2013-10-19 10:30:45.461000 > ######################################## лечится перезапуском пула все версии последние от сюда http://sourceforge.net/projects/novacoin/files/майнер cgminer-3.5.0, до того нормально копал в этом же кошельке соло, без простоев... ктонить еще сталкивался? |
|
|
|
Минимальный размер транзакции, которая точно не даст нуля - это 12,17 новы. Можно вычислить как 365/30.
Меньшие могут дать ноль. Причем чем транзакция меньше, тем более он вероятен.  ахренительно, с учетом того что после каждой пос генерации нашедшая сумма дробится напополам.... у меня было много блоков по 12+ но теперь от них осталось в лучшем случае 3+ |
|
|
|
Сегодня офигенное утро. НАКОНЕЦ-ТО! Доля 482NVC и входящая транзакция в 44NVC. А я уж было думал, что что-то не так.
а нули сыпались? а то я тоже в сомнениях что что то не так... |
|
|
|
Все он правильно показывает. а кто не правильно? клиент 443 баланс дет на 50 нов отличается |
|
|
|
у меня ещё не одного POS блока не было  с похожими данными? |
|
|
|
За месяц 3000 монет сгенерировали 261 монету, боюсь такое уже не скоро повториться...
интересное кино! у меня 267 монет сделали только 2....2 транзакции по 1....остальные 38 транзакций 0!!!!! самые молодые монеты от 16.04.13... з.ы. спасибо хоть unconfirmed транзакции прекратились |
|
|
|
start your client with following parameter : (append it to your shortcut command), it should do the trick. loaded only 108222 blocks upd. deleted all files (except wallet and conf.) in appdata loaded only 175038 blocks on 0.1.3-44 client |
|
|
|
|
