Estoy tratando de sincronizar un nuevo nodo completo en la nube, sin embargo, se está sincronizando mucho más lento de lo que estoy acostumbrado: tengo aproximadamente 70,000 bloques después de aproximadamente 12 horas.
iotop
muestra que todo está inactivo y casi nada se está escribiendo.bitcoin-cli getnetworkinfo
debería tener 10 conexiones activas en este momento.Pero esto es lo que debug.log
muestra mi:
~/.bitcoin# tail -n 100 debug.log
2018-01-26 10:07:07 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:09 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:10 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:10 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:12 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:13 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:15 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:16 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:18 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:19 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:21 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:22 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:24 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:25 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:27 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:28 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:30 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:31 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:33 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:34 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:36 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:37 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:39 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:40 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:42 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:43 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:45 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:47 receive version message: /breadwallet:0.6.2/: version 70013, blocks=0, us=[redacted]:8333, peer=885
2018-01-26 10:07:52 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:52 receive version message: /breadwallet:0.6.2/: version 70013, blocks=0, us=[redacted]:8333, peer=886
2018-01-26 10:07:53 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:55 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:56 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:57 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[redacted]:8333, peer=887
2018-01-26 10:07:58 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:07:59 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:01 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:02 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:04 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:05 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:07 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:08 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:10 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:11 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:13 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:15 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:16 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:18 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:19 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:21 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:22 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:24 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:25 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:27 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:28 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:30 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:37 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:38 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:40 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:41 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:43 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:50 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:51 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:53 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:54 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:56 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:57 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:08:59 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:00 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:02 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:09 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:10 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:12 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:13 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:13 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:15 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:17 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:18 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:20 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:21 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:23 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:24 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:26 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:27 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:29 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:30 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:32 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:33 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:35 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:36 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:38 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:39 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:41 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:42 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:44 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:45 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:47 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:48 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:50 connect() to [redacted]:8333 failed after select(): No route to host (113)
2018-01-26 10:09:57 connect() to [redacted]:8333 failed after select(): No route to host (113)
He redactado las direcciones IP, pero no se puede acceder a ninguna de ellas desde mi caja vps, mientras que puedo llegar a ellas sin problemas (lo que hace que esto no sea un problema central de bitcoin sino un problema de red).
EDITAR:
Según lo solicitado, más resultados de depuración:
el host VPS, ¿puedes probar> telnet redactado 8333
Producción:
~/.bitcoin# telnet [redacted]:8333
telnet: could not resolve [redacted]:8333/telnet: Name or service not known
Y:
~/.bitcoin# nmap [redacted] -p8333
Starting Nmap 7.01 ( https://nmap.org ) at 2018-01-26 08:13 EST
Nmap scan report for [redacted] ([redacted])
Host is up (0.0069s latency).
PORT STATE SERVICE
8333/tcp filtered bitcoin
Nmap done: 1 IP address (1 host up) scanned in 0.42 seconds
Lo cual es extraño: nmap funciona pero nada más parece poder enrutar.
No estoy usando Tor ni he configurado ningún archivo bitcoin.conf. Todo está predeterminado y descargué la versión predeterminada de Linux (0.15.1) de bitcoincore.org (la suma de verificación coincide).
Además, verifique a qué interfaces está vinculado el nodo bitcoin, especialmente si su VPS tiene múltiples interfaces de red.
Solo tiene un llamado venet0
y otro llamado venet0:0
(este último tiene la IP pública enlazada). Estoy ejecutando Ubuntu 16.04.1 LTS.
Aquí están las primeras 150 líneas de debug.log (cuando se inició bitcoind por primera vez): https://gist.github.com/askmike/5ae06e6ffec122e8634df97e9dae4cf5
EDIT2:
Resultó ser un problema de firewall de mi proveedor de VPS.
Líneas como esta significan que en realidad te estás conectando a algunos nodos:
2018-01-26 10:07:57 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[redacted]:8333, peer=887
Pero me es imposible saber por lo que has publicado si ese compañero es uno que está fallando más tarde, no lo creo.
En el servidor VPS, ¿puedes probar >telnet redacted 8333
o >nmap redacted -p8333
y >traceroute redacted -p 8333
agregarlo a tu pregunta?
por cierto: si desea una herramienta para realizar la verificación de nodos, aparentemente esto funciona: https://bitcointalk.org/index.php?topic=760565.msg13820110#msg13820110
Además, verifique a qué interfaces está vinculado el nodo bitcoin, especialmente si su VPS tiene múltiples interfaces de red. Debería aparecer debug.log
poco después del reinicio del nodo.
Hay algunas opciones como -onlynet=
esa que pueden causar problemas de conectividad, ¿qué hay en su archivo de configuración o en su línea de comandos que se usa para iniciar el nodo?
¿Estás usando tor?
Podría ser simplemente un problema de firewall inteligente o filtro web con su servidor VPS.
Willtech
>route -v -n
¿cuántos destinos de 0.0.0.0 tiene en la columna de la izquierda con diferentes valores de cara en la columna de la derecha? Además, puede haber un error de permiso ya que tiene algunas entradas comoInvalid or missing banlist.dat; recreating
Willtech
>ps -eo user,group,comm |egrep 'bitcoind|bitcoin-qt' |awk '{print "Bitcoin user: " $1}'
y le da el usuario con el que inicia sesión?preguntar
telnet: Unable to connect to remote host: No route to host
). 3. Creo que el problema de la lista de prohibición fue solo un mensaje en la primera ejecución (el directorio de datos de bitcoin estaba vacío, por lo que tuvo que crear todo). 4. sí, me da el usuario con el que inicié sesión.preguntar
Willtech