 Show Posts
|
|
Pages: [1] 2 3 »
|
|
Before or after the sale?
|
|
|
|
|
Will it be made public before the sale?
|
|
|
|
|
does your twitter work, #valorem doesn;t seem to work
|
|
|
|
|
projects looks interesting, I have joined your twitter campaign
|
|
|
|
|
What happens to unsold coins in the ICO?
|
|
|
|
|
Can't wait to convert my bitcoin into Fizcoins.
|
|
|
|
|
Is their a limit to the number of masternodes I can run?
|
|
|
|
|
Thanks, I added it to my twitter
|
|
|
|
|
Can’t wait for this to go live.
|
|
|
|
Gracias por responder.  Conclusión:
Utiliza la versión 0.10.x y comprueba en el fichero debug.log que Bitcoin Core está trabajando y procesando nuevos bloques. Si es así, déjalo funcionando durante unas cuantas horas hasta que veas que recibes una nueva ráfaga que actualiza varios días de una sola vez.
Por cierto, la hora de las entradas de debug.log no tienen por qué coincidir con la hora de tu ordenador.
El archivo de texto debug.log si está registrando todos los eventos relacionados al bitcoin core. Hace 2 dias formatié el disco duro, reinstalé windows con unos pocos programas incluyendo el cliente btc. Comenzó a descargar la cadena de bloques pero luego de haber pasado casi dos dias descargándola, repentinamente se quedo muerto y no bajó mas nada. No sé si tuvo algo que ver el hecho que poco antes de congelarse la descarga, el cpu comenzo a correr al 100% de carga debido a que esa pc tambien ejecuto aplicaciones de computación distribuída: Folding@Home y WCG/Boinc. La descarga se paralizó en bloque 294999, 1 año y 8 semanas. Siendo la misma cantidad de tiempo que aparecía la otras veces que se congelaba la descarga. Restablecí el bitcoin core a las opciones por defecto para asignar otra carpeta como destino de la cadena de bloques. Actualmente estoy descargando la cadena desde cero a ver si se vuelve a congelear en el mismo bloque. Luego les cuento como me fué. Para descargar la cadena de bloques no es necesario tener abierto el puerto 8333.
¿El puerto 8333 solo se abre cuando se tiene cliente btc en modo servidor? Recuerdo que en 2011 cuando minaba con gpu usando GUIminer, en "Solo Mode" ademas del user:pass tambien pedía IP:Puerto del servidor pero creo aquel entonces era 8332. A mi se me ocurre otra cosa, y es que intercambies las conexiones de los 2 ISP. Solo para comprobar que te sincroniza en el PC que no lo hacía o que dicho ISP tiene algo capado.
Y ya que te pones, pon en uno la versión 0.10.2 y en otro la 0.11 RC1, así las pruebas. Ya antes había hecho la prueba alternando los ISP en las pcs pero no hubo ningun cambio en la descarga de la cadena de bloques. Ambos tienen la versión 0.10.2. |
|
|
|
|
Tengo 2 pc en mi casa, cada una con el bitcoin core corriendo 24/7.
Ademas tengo 2 isp, cada uno con su respectivo router y el puerto 8333 tcp/udp redireccionado al ip del pc correspondiente.
Es decir, cada pc usa un isp diferente.
El problema es que la pc2 nunca termina de actualizar la cadena de bloques.
Siempre dice "Sincronizando con la red" o "Ninguna fuente de bloques disponible" aunque tenga varias conexiones activas hacia la red segun lo indican las 4 barras encendidas.
He probado varias cosas:
1)Copiar las carpetas que contienen la cadena bloques (blocks y chainstate) de un pc para el otro. Pero nada, sigue sin descargar la cadena de bloques.
2)Borrar TODO en el directorio que contiene la cadena de bloques para que la descargue nuevamente. La comienza a descargar pero siempre en algun punto se queda estancado y no descarga mas.
3)Desinstalar y reinstalar el Bitcoin Core.
4)Pense que el firewall bloqueaba las conexiones entrantes tpc/udp 8333.
Pero ambas pc tienen el mismo firewall sin ninguna configuracion especial para Bitcoin-qt y la otra pc simepre actualiza la cadena de bloques.
Ademas que si el firewall bloqueara al botcoin core, entonces no dejaria que este se conectara y comenzara a descargar la cadena.
Ya no se que hacer.
¿Alguna sugrencia?
Muchas gracias.-
|
|
|
|
Don't forget to aim the blade at port 8330 also.
I switch to port 8330 on BEB and seems to be working fine so far. BFGminer 4.0.0 and 4.2.0 shows both devices: BFL 0 and PXY 0. Thanks! EDIT: The problem seems to be something related with user:pass If I set the BEB with same user:pass used in BFGminer, then PX1 shows up. I used to mine BFL jalapeño with bfgminer pointing to worker1:pass1, and BEB with minigproxy pointing to worker2:pass2. Now BFL + BEB with bfgminer pointing to worker1:pass1, but worker2:pass2 at BEB config page, then works fine. If change to worker1:pass1 at BEB config page, then PXY 1 appears. |
|
|
|
I don't know if this is what is causing your problem, but port 8332 is the default port for the bitcoin daemon - so anything trying to connect to bitcoind may instead connect to your BFGMiner instance.
Just as an experiment, try using port 8330 instead and see if the problem persists.
Port 8332 is what I used in BEB config page. BFGminer 4.0.0 runs ok using port 8332. Only shows BFL 0 + PXY 0, and PXY 1 doesn't appear. I tried port 8330 with bfgminer 4.2.0 but shows BFL 0 only, PXY 0 does not appear. Then I tried port 8330 with bfgminer 4.0.0 but does not shows both devices, BFL 0 only. |
|
|
|
Hi there. I used to run a BFL jalapeño with bfgminer, and a block erupter blade with miningproxy. Now I'm running both (BFL jalapeño + BEB) with bfgminer as follows: bfgminer --http-port 8332 -o stratum.btcguild.com:3333 -u Qu4k3r_A -p mypass After begin to run bfgminer it shows both devices (BFL 0, PXY 0) but few minutes later a third device (PXY 1) shows up which is sick most of time and a little bit later is dead. Sometimes bfgminer shows three devices at once.  ¿Is this normal, should I worry about it? Thanks in advance. |
|
|
|
|
You mean at config page?
Current Server: 192.168.1.1:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Yes, they are always OOOOOOO
|
|
|
|
If you refresh during a hang, do the chips still read O or are some of them X'd?
Do you mean, when I click "refresh" button at config page during a hang, if stats readings stay at 00000? Oh well, mostly I think, I have to close cmd window and restart mining_proxy .bat file in order to make stats readings get higher. What is X'd? Sorry I dont know what that means. |
|
|
|
Here? 3.29V It's have be working about 10hrs without hang. If hangs again I'll let you know what was the reading. Edit: It hangs again after 12hrs, voltage reading was 3.28v  |
|
|
|
Hi there. My blade blew the new 10amp fuse the same day I bought it. I contacted the seller and told him I'll have to send it back. He told me that he was sorry for the issue, and ask me if I want to return it for replace or refund, in deed he gave me the address to return it. Also wanted to know the cost of return shipping in order to refund that amount to me. Well, that was very polite and gentle. I have not answered him yet. I'm kind of doubtful. I would like to try the blade just a week more so I changed the fuse again, and if it works flawless, then I would keep it. But now it works a litlle wierd some times. I mean after 8-10 hours of working seem to be freezed. All counters of stats were reset to zero. The ".bat" file of minig proxy stay just waiting or listening for, like freezed, the lines on cmd window dont move. So, I have to restart it manually to make it work again. I happened like 4 or 5 times and I have used it 4 days only. I had filled DNS with 8.8.8.8 and 8.8.4.4, but now I realized that must be the router IP on primary DNS and 8.8.8.8 (or other) in secondary DNS. I do not know if that have anything to see with the problem. What do you suggest to me? Keep it and try few more days, or just return it and get a new one. Thanks in advance.- |
|
|
|
Looks to be the case, yeah. The R fuse is actually 8A, pretty sure; the blue-board blades came with 10A fuses. There ought be no problem using that current rating. If you don't have any SMD fuses handy, test with a 10A automotive blade fuse. If that works, it works; if the test fuse blows, there's something further wrong with the board.
Oh well, I will look for them. There is an electronic supplier store near to my house. Thanks for your help. EDIT: I made a bridge with a paper clip on fuse terminals and guess what? I powered it on! All leds were blinking and could access to the config menu 192.168.1.254:8000 LOL I'll buy a 10A fuse tomorrow early in the morning.  Thanks again.- |
|
|
|
|
