Я немогу вывести заработанные BTC с пула!!!

При работе на вашем пуле очень часто происходит эта ошибка:

Warning: Software caused connection abort: recv failed: disabling long polling fo 60s
Warning: Unexpected end of file from server: disabling long polling fo 60s

На других пулах такого вообже не наблюдается.

alexmac:~ alex$ ping pool.50btc.com
PING pool.50btc.com (176.9.130.36): 56 data bytes
64 bytes from 176.9.130.36: icmp_seq=0 ttl=56 time=33.002 ms
64 bytes from 176.9.130.36: icmp_seq=1 ttl=56 time=31.669 ms
64 bytes from 176.9.130.36: icmp_seq=2 ttl=56 time=31.594 ms
64 bytes from 176.9.130.36: icmp_seq=3 ttl=56 time=31.787 ms
64 bytes from 176.9.130.36: icmp_seq=4 ttl=56 time=30.762 ms
64 bytes from 176.9.130.36: icmp_seq=5 ttl=56 time=31.311 ms
64 bytes from 176.9.130.36: icmp_seq=6 ttl=56 time=32.738 ms
64 bytes from 176.9.130.36: icmp_seq=7 ttl=56 time=32.250 ms
64 bytes from 176.9.130.36: icmp_seq=8 ttl=56 time=31.246 ms
64 bytes from 176.9.130.36: icmp_seq=9 ttl=56 time=37.738 ms
64 bytes from 176.9.130.36: icmp_seq=10 ttl=56 time=32.399 ms
64 bytes from 176.9.130.36: icmp_seq=11 ttl=56 time=32.131 ms
64 bytes from 176.9.130.36: icmp_seq=12 ttl=56 time=31.961 ms
64 bytes from 176.9.130.36: icmp_seq=13 ttl=56 time=32.937 ms
64 bytes from 176.9.130.36: icmp_seq=14 ttl=56 time=31.764 ms
64 bytes from 176.9.130.36: icmp_seq=15 ttl=56 time=32.232 ms
64 bytes from 176.9.130.36: icmp_seq=16 ttl=56 time=32.815 ms
64 bytes from 176.9.130.36: icmp_seq=17 ttl=56 time=33.005 ms
64 bytes from 176.9.130.36: icmp_seq=18 ttl=56 time=33.130 ms
64 bytes from 176.9.130.36: icmp_seq=19 ttl=56 time=32.735 ms
64 bytes from 176.9.130.36: icmp_seq=20 ttl=56 time=31.699 ms
64 bytes from 176.9.130.36: icmp_seq=21 ttl=56 time=31.703 ms
64 bytes from 176.9.130.36: icmp_seq=22 ttl=56 time=31.709 ms
64 bytes from 176.9.130.36: icmp_seq=23 ttl=56 time=32.641 ms
64 bytes from 176.9.130.36: icmp_seq=24 ttl=56 time=31.767 ms
64 bytes from 176.9.130.36: icmp_seq=25 ttl=56 time=31.843 ms
64 bytes from 176.9.130.36: icmp_seq=26 ttl=56 time=33.363 ms
64 bytes from 176.9.130.36: icmp_seq=27 ttl=56 time=30.862 ms
64 bytes from 176.9.130.36: icmp_seq=28 ttl=56 time=32.943 ms
64 bytes from 176.9.130.36: icmp_seq=29 ttl=56 time=31.268 ms
64 bytes from 176.9.130.36: icmp_seq=30 ttl=56 time=31.500 ms
64 bytes from 176.9.130.36: icmp_seq=31 ttl=56 time=33.119 ms
64 bytes from 176.9.130.36: icmp_seq=32 ttl=56 time=31.187 ms
64 bytes from 176.9.130.36: icmp_seq=33 ttl=56 time=31.026 ms
64 bytes from 176.9.130.36: icmp_seq=34 ttl=56 time=32.369 ms
64 bytes from 176.9.130.36: icmp_seq=35 ttl=56 time=32.036 ms
64 bytes from 176.9.130.36: icmp_seq=36 ttl=56 time=32.118 ms
64 bytes from 176.9.130.36: icmp_seq=37 ttl=56 time=32.988 ms
64 bytes from 176.9.130.36: icmp_seq=38 ttl=56 time=31.950 ms
64 bytes from 176.9.130.36: icmp_seq=39 ttl=56 time=31.918 ms
64 bytes from 176.9.130.36: icmp_seq=40 ttl=56 time=32.339 ms
64 bytes from 176.9.130.36: icmp_seq=41 ttl=56 time=31.161 ms
64 bytes from 176.9.130.36: icmp_seq=42 ttl=56 time=33.001 ms
64 bytes from 176.9.130.36: icmp_seq=43 ttl=56 time=32.499 ms
^C
--- pool.50btc.com ping statistics ---
44 packets transmitted, 44 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 30.762/32.232/37.738/1.080 ms



traceroute to pool.50btc.com (176.9.130.36), 64 hops max, 52 byte packets
 1  speedport.ip (192.168.2.1)  1.526 ms  0.764 ms  1.190 ms
 2  217.0.119.68 (217.0.119.68)  17.135 ms  17.199 ms  16.402 ms
 3  217.0.77.58 (217.0.77.58)  17.200 ms  17.747 ms  17.962 ms
 4  f-ed4-i.f.de.net.dtag.de (62.154.14.218)  25.971 ms  26.230 ms  26.070 ms
 5  62.157.251.34 (62.157.251.34)  26.592 ms  26.714 ms  25.930 ms
 6  hos-bb2.juniper1.rz15.hetzner.de (213.239.240.157)  53.775 ms  31.557 ms  31.980 ms
 7  hos-tr4.ex3k8.rz15.hetzner.de (213.239.244.105)  35.320 ms  32.771 ms  32.642 ms
 8  static.118.56.9.176.clients.your-server.de (176.9.56.118)  31.468 ms  32.109 ms  32.030 ms
 9  pool.50btc.com (176.9.130.36)  33.022 ms !Z  32.591 ms !Z  33.264 ms !Z

50BTC.com

bus-0-0: poll loop time: 39ms (USB: 12ms network: 27ms)   getwork time: 47ms  submit time: 47ms
bus-0-1: poll loop time: 42ms (USB: 12ms network: 30ms)   getwork time: 51ms  submit time: 45ms
bus-0-2: poll loop time: 39ms (USB: 12ms network: 27ms)   getwork time: 45ms  submit time: 43ms
bus-0-3: poll loop time: 39ms (USB: 12ms network: 27ms)   getwork time: 47ms  submit time: 45ms
bus-0-4: poll loop time: 39ms (USB: 12ms network: 27ms)   getwork time: 47ms  submit time: 43ms
bus-0-5: poll loop time: 38ms (USB: 12ms network: 26ms)   getwork time: 48ms  submit time: 42ms
bus-0-6: poll loop time: 39ms (USB: 12ms network: 27ms)   getwork time: 47ms  submit time: 46ms
bus-0-7: poll loop time: 36ms (USB: 12ms network: 24ms)   getwork time: 48ms  submit time: 40ms
bus-0-8: poll loop time: 40ms (USB: 12ms network: 28ms)   getwork time: 46ms  submit time: 45ms
bus-0-9: poll loop time: 40ms (USB: 12ms network: 28ms)   getwork time: 49ms  submit time: 47ms
bus-0-10: poll loop time: 37ms (USB: 12ms network: 25ms)   getwork time: 44ms  submit time: 50ms
bus-0-11: poll loop time: 37ms (USB: 12ms network: 25ms)   getwork time: 46ms  submit time: 44ms
bus-0-12: poll loop time: 42ms (USB: 12ms network: 30ms)   getwork time: 44ms  submit time: 43ms
bus-0-13: poll loop time: 40ms (USB: 12ms network: 28ms)   getwork time: 51ms  submit time: 40ms
bus-0-14: poll loop time: 38ms (USB: 12ms network: 26ms)   getwork time: 48ms  submit time: 47ms
bus-0-15: poll loop time: 38ms (USB: 12ms network: 26ms)   getwork time: 48ms  submit time: 47ms
bus-0-16: poll loop time: 40ms (USB: 12ms network: 28ms)   getwork time: 45ms  submit time: 50ms
bus-0-17: poll loop time: 39ms (USB: 12ms network: 28ms)   getwork time: 42ms  submit time: 41ms
bus-0-18: poll loop time: 41ms (USB: 12ms network: 28ms)   getwork time: 51ms  submit time: 41ms
bus-0-19: poll loop time: 41ms (USB: 12ms network: 29ms)   getwork time: 48ms  submit time: 46ms
Total hash rate: 44074,1 MH/s
Total submitted hash rate: 43547,4 MH/s

То что в германии это меня радует. Я сам в Берлине
Только при подключение к другим сервакам в германии у меня показатели лучше.

В частности "Битминтер"
poll loop time: 25мс
network: 14мс
getwork time: 34мс
submit time: 35мс

Незнаю, может вам это поможет и вы там чтонибудь подкрутите и станет быстрее. )))

Ja reshil seichas ezhe razok pomainitj u was. Posmotrim naskolko stabilno servak rabotaet. A to ja zametil, chto on za perwie 3 chasa padal sowsem.
A v kakoi strane server nahoditsja? A to v logah ja ezhe i "overflow" preduprezhdenija zametil. Mne horoshiy "connect" ochenj wazhen. 

Nu wot, ja podozhdal poka prekratilsj wiplati posle ostanowki mininga. Poschital i wsje ok. Primerno stolko ja i dolzhen bil poluchitj za 3 chasa raboti.
Tolko kak-to stranno statistika na servake rabotaet, wezde esli PPS sistema rascheta, to srazu widno skolko bitcoinow twoih. A tut wiplati ezhe 2 chasa prihodili.

Da, moi miner pokazivaet, chto reshenija postupajut s normalnoi skorostju na server. A wot statistika gluchit konkretno. Ja seichas perestal mainitj na 50BTC, a reshenija postupajut dalshe. Koroche balance BTC rastet))))
Fakt to, chto ja za opredelenniy otrezok wremeni dolzhen poluchatj namnogo bolshe, chem seichas mne na 50BTC platjat...

chto to gluchit wash pull. Javno neprawilno schitaet. Ja poka podozhdu na btc-guilde...

you're still alive)) 13 hours block!!!

Pool need PPS payment system too.

Yes, i am new. one-two month only. Chances are that I do not know. Did not want to hurt anyone, I'm sorry.

i have used exactly this libusbx. I folow only steps from "windows-build.txt" from scratch.
I have used in the assembly of these options: --enable-ztex --disable-opencl --enable-scrypt --enable-cpumining
Nothing more.
CPU mining works.....
Q: And why you write "only ignore luke-jr"? He sayd it will be a solution in the next version of BFGminer for Ztex boards.

no, i cant use prebuilt binary. I have only macs computer without OpenGl GPU. If i try start your binary, cgminer break starting with error. (need OpenGL files)
I try today first time with cgminer!!!) maybe i make something wrong, maybe it can be disabled using OpenGL before starting with some options. But i cant find how? Only one solution i found: bild my own binary of cgminer.)))

Maybe i must try to bild cgminer with old libusb? same version which used BTCMiner? at all possible in cgminer 2.7.4?

Yes, with BTCMiner on the same computer all work perfect.
I tested cgminer only with one quad Board.
i have loaded bitstream with ZTEX BTCMiner to Board but it looks as though cggminer unresolved the ZTEX Board.

I have compiled cgminer 2.7.4 with ztex support, but if start i get always:

Ztex check device: Failed to open handle with error -12
prepare device: -12

Whats wrong?

Hi cgminer gurus!
Please explain me, how get it work my 50x ZTEX quads with last cgminer on Windows 7 prof. 32 bit. Step by step.
Or somebody have a link where this procedure already published.
Thx.

Hi redditorex
I cant mine on pa.mtred.com
can you activate my account for mining on pa.mtred.com
Thx

In last two days, i have tested mining on EclipseMC, Deepbit, MtRed. Only huge blocks on the way. Is somethig wrong with common luck))? I hope soon come "lucky wave"

At the moment, Bitminter the most stable pool in Europe. I am back to help you.
But more luck needed)))

More important for me to see a working prototype. In developing of the new chip design is a very high percentage of errors.