Muy pocas conexiones, config.json?

Algún "nodo reciéniniciado"en algúnmomentoterminaen una situación comoesa y setrabajapara solucionarelproblema. Elescenarioesel siguiente:

• Lospares debootstrap aceptan unagran cantidad de conexiones,por lo quenunca hayningúnproblemapara conectarse aellos
• Luego,devuelven siempreelmismo subconjunto de suspares.Y estosparesno aceptan cientos de conexionespor lo queterminan siendotodos saturar ypor lotantonadie responde.
• Elnodoestá atascadoen estaetapa hasta que se leentreguemanualmente através de admin-client connect address [...] la dirección de unnodono saturado que acepta la conexión y da algunas direcciones de algunosotrosnodosno saturados ytodoestáfinalmentebien.

Estamostrabajandoen ello creandonodos saturadosmientras rechazamos una conexión adicionalenviando detodosmodos un subconjunto de susparesparaprobar ...

Some "just started node" sometime ends up in a situation like that and work is done to get rid of the problem. The scenario is the following:

• The bootstrap peers accept a big number of connection so there is never any problem to connect to them
• Then, they send back always the same subset of their peers. And these peers do not accept hundred of connection so they end up being all saturate and therefore none reply.
• The node is stuck in this stage until being given by hand via admin-client connect address [...] the address of a non saturated node that accepts the connection and gives some addresses of some other non saturated nodes and everything is finally fine.

We are working on it by making saturated nodes while refusing an extra connection sending back anyway a subset of their peers to try...

¿Está sunodoen modoprivado?Esextrañotener solo 5 conexionesmientras hay cientos deparesen las redes.¿Haintentado reiniciar sunodo?y/ogenerar unanuevaidentidad?Quizás los otrosnodos hayanincluidoeltuyoen la listanegra.

Puede agregarpares con la opción de línea de comando --peer ADDR: PORT ,o agregándolosen el archivo config.json.Através del archivo de configuración,puede,porejemplo,agregar lospares de la siguientemanera:

 {
  "p2p": {
    "bootstrap-peers": ["127.0.0.1:9731"],
}
 

Is your node in private mode ? It's bizarre to only have 5 connections while there are hundreds of peers in the networks. Have you tried to restart your node ? and/or to generate a new identity ? Maybe the other nodes have blacklisted yours.

You can either add peers with command line option --peer ADDR:PORT, or by adding them in the config.json file. Via the config file, you can for instance add the peers as follows:

{
  "p2p": {
    "bootstrap-peers": ["127.0.0.1:9731"],
}

Ok,intenté abrirpuertos,generar unanuevaidentidad,agregarparesmanualmente (comoiguer) asesorados,peronada ayudó.

Pero untipo llamado "Krixt"en la holgura de Tezos Bakingescribióeste script:

 #!/bin/bash

# get foundation nodes
for i in dubnodes franodes sinnodes nrtnodes pdxnodes; do
    for j in `dig $i.tzbeta.net +short`; do
      echo "Connecting foundation $j..."
      ~/tezos/tezos-admin-client connect address [$j]:9732
    done
done

# public nodes
for j in 0 1; do
  for i in `curl -s "http://api6.tzscan.io/v3/network?state=running&p=$j&number=50" \
    | jq -r '.[] | .point_id' | xargs`; do

    # handle ipv4 or ipv6
    numparts=$(echo $i | awk -F: '{print NF}')
    basenum=$((numparts-1))
    port=$(echo $i | cut -d: -f$numparts)
    base=$(echo $i | cut -d: -f1-$basenum)
    formatted="[$base]:$port"

    echo "Connecting $formatted..."
    ~/tezos/tezos-admin-client connect address $formatted
  done
done
 

Fuente: https://gist.github.com/utdrmac/2125a8514960e163837e86bc934f19b6

Este scriptes un verdadero refuerzo de conexión :) Ahoratengomás de 100 conexiones (de 5 antes).

Espero queesto ayude a otros con losmismosproblemas de "too few connections";)

Ok, i've tried to open ports, generated a new identity, added peers manually (like iguer) adviced, but nothing helped.

But a guy called "Krixt" in the Tezos Baking slack wrote this script:

#!/bin/bash

# get foundation nodes
for i in dubnodes franodes sinnodes nrtnodes pdxnodes; do
    for j in `dig $i.tzbeta.net +short`; do
      echo "Connecting foundation $j..."
      ~/tezos/tezos-admin-client connect address [$j]:9732
    done
done

# public nodes
for j in 0 1; do
  for i in `curl -s "http://api6.tzscan.io/v3/network?state=running&p=$j&number=50" \
    | jq -r '.[] | .point_id' | xargs`; do

    # handle ipv4 or ipv6
    numparts=$(echo $i | awk -F: '{print NF}')
    basenum=$((numparts-1))
    port=$(echo $i | cut -d: -f$numparts)
    base=$(echo $i | cut -d: -f1-$basenum)
    formatted="[$base]:$port"

    echo "Connecting $formatted..."
    ~/tezos/tezos-admin-client connect address $formatted
  done
done

Source: https://gist.github.com/utdrmac/2125a8514960e163837e86bc934f19b6

This script is a true connection booster :) I've now more than 100 connections (from 5 before).

I hope this will help others with the same "too few connections" problems ;)

Como señaló Iguer,elmodoprivado sería una razónpara causaresto. Peroparaelaborar,esto sucedeprincipalmenteporque losnodosen modoprivado sonmenosfavorablespara que unnodopar se conecte,ya queelnodoprivadoesbásicamente una sanguijuela a la red. Nointentará arrancar otrosnodos. Losnodosprivadosen sumayoría solomonitorearánpara obtener la cadena debloques y llenar sumempool,solo a veces ocasionalmente comparten una operación como hornear otransacción.

Básicamente,unnodoprivadonopermite que otros se conecten a él. Por lamisma razón,si sunodopúbliconopermite que otros se conecten a él,compartirá los síntomas de "muypocas conexiones". Noes un requisito denodopermitir que otros se conectenporqueelpropionodopuedeintentar conectarse apares conocidos y arrancar la cadena deesamanera. Peromi teoríaes que losnodos quenopermiten conexiones de otrostambién se consideranmenosfavorables,por lotanto,algunosnodospueden descartar o rechazar sunodo como unparporqueno ayuda aexpandir su alcance a la red. Ciertamente comprobaría que supuerto 9732 sepueda conectar através de sufirewall oenrutador o lo que sea. ( Documentación oficial dice queeselpuerto 19732,pero creo queesoesincorrecto segúnmi experiencia.)

Latercera razónpor la quepueden ocurrir too few connectionses rara,pero debe señalarse. Siestáen la red,bifurcación/cadena oprotocoloincorrectos,solo se conectará anodos compatibles. Todos losnodos a los queestá conectadotambiénestaránen lamisma configuración. Lo que debeteneren cuentaes asegurarse de compilar susbinarios con la rama mainnet,no con master. Además,recuerdeejecutar losbinarios correctos (actualmenteen elprotocolo 003) ymantenga susbinarios actualizados volviéndolos a compilar de vezen cuando (onotificándolospara hacerloen Riot o Slack).

As iguer pointed out, private mode would be one reason to cause this. But to elaborate, this happens mostly because private mode nodes are less favorable for a peer node to connect to as the private node is basically a leech to the network. It will not try to bootstrap other nodes. Private nodes will mostly just monitor to get the blockchain and fill its mempool, only sometimes occasionally share an operation like baking or transaction.

Fundamentally, a private node does not allow others to connect to it. For the same reason, if your public node does not allow others to connect to it, it will share the "too few connections" symptoms. It's not a node requirement to allow others to connect because the node itself can try to connect to known peers and bootstrap the chain that way. But my theory is that nodes that does not allow connections from others are also considered less favorable, hence some nodes might drop or refuse your node as a peer because it doesn't help expand their reach to the network. I would certainly check to make sure your port 9732 is connectable through your firewall or router or whatever. (Official documentations says it's port 19732, but I believe that's wrong based on my experience.)

Third reason why too few connections may happen is rare but should be pointed out. If you are on the wrong network or fork/chain or protocol, you will only connected to compatible nodes. All the nodes you are connected will be also on the same setup. Things to watch out for is to make sure to compile your binaries with mainnet branch, not master. Also, remember to run the correct binaries (currently at 003 protocol) and keep your binaries up to date by recompiling every so often(or notified to do so on Riot or Slack).

Esteesel comandopara agregar unpar deformapermanente al archivo config.jsonen el directorio de datos detezos:

Actualización de la configuración delnodo detezos --peer=13.251.160.63: 9732 --peer=...

Este comando,lamentablemente,no comprueba lasentradas yaexistentes.Demodo quepuedeterminar agregando losmismospares varias veces.

This is the command to add a peer permanently to the config.json file in the tezos data directory:

tezos-node config update --peer=13.251.160.63:9732 --peer=...

This command does unfortunately not check for already existing entries. So you can end up adding the same peers multiple times.