monitor.js produce resultados erróneos con Geth/v1.8.17-unstable-e39a9b34/linux-amd64/go1.11
monitor.js
produce el siguiente resultado en un nodo sellador con Geth/v1.8.17-unstable-e39a9b34/linux-amd64/go1.11
.
UTC: Tue, 13 Nov 2018 17:55:51 GMT
BFA peers: 9
peer in: undefined
peer in: undefined
peer in: undefined
peer out: undefined
peer out: undefined
peer out: undefined
peer out: undefined
peer out: undefined
peer out: undefined
En la línea 25 del código hace referencia a un campo node.enode
que no aparece en la estructura de datos devuelta por la llamada a admin_peers
.
16 function(nodelist) {
17 var peers = [];
18 nodelist.forEach(
19 function(node) {
20 if ( typeof(node.protocols.eth) == 'object' )
21 {
22 var dir = "out";
23 if ( node.network.inbound )
24 dir = "in";
25 peers.push( "peer "+dir+": "+node.enode );
26 }
27 }
28 );
La estructura devuelta por geth
tiene esta forma:
{
caps: ["eth/62", "eth/63"],
id: "f54c54e91bb1c89c8ecc9b7c0f129766484abb4e9f32495050e496d3a6886966",
name: "Geth/v1.8.17-unstable-2c8d5dec/linux-amd64/go1.11",
network: {
inbound: false,
localAddress: "200.16.28.27:50092",
remoteAddress: "200.3.120.174:30303",
static: false,
trusted: false
},
protocols: {
eth: {
difficulty: 1270358,
head: "0xc19e4eb617ca2b38c9322a57ac429a902bee5cf1205bdceed0aa54be49e65dcc",
version: 63
}
}
}
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information