-
Notifications
You must be signed in to change notification settings - Fork 32
Unable to find nodes #189
Comments
I partly believe this may be an issue with the instance of node 8.7 making connection through HTTPS. There was an existing issue in node Can you try new version (say, Alternatively, we can also test isolate protocol by explicitly provide only HTTP endpoints to see if the issue persists: const neo = new Neo({
endpoints: [
{ endpoint: 'http://seed1.ngd.network:10332' },
{ endpoint: 'http://seed2.ngd.network:10332' },
{ endpoint: 'http://seed3.ngd.network:10332' },
{ endpoint: 'http://seed4.ngd.network:10332' },
{ endpoint: 'http://seed5.ngd.network:10332' },
{ endpoint: 'http://seed6.ngd.network:10332' },
{ endpoint: 'http://seed7.ngd.network:10332' },
{ endpoint: 'http://seed8.ngd.network:10332' },
{ endpoint: 'http://seed9.ngd.network:10332' },
{ endpoint: 'http://seed10.ngd.network:10332' },
]
}) |
Another point worth mention, the log verbose levels as seen in https://github.com/marcosrachid/nodejs-neo-fullnode/blob/master/index.js is considerably noisy. There are bound to have node connectivity failures for various of server side reasons (most common one is: I cloned the repo https://github.com/marcosrachid/nodejs-neo-fullnode/, modify all log levels to
My environment:
|
I tried to upgrade my node.js, but nothing has changed. And also tried to change my internet bandwidth, but still same errors. I will try testing on another computer and give you a feedback. |
On a windows environment with a better bandwidth, it works with success. What OS are you running your instance ? |
Oh sorr. I just saw you already answered my question. So I think my problem was just a slow internet. Thanks @rockacola. |
Context (Environment)
neo-js
Version: 0.11.0node
Version: v8.7.0Expected behavior
Neo Mesh should find an applicable node and sync the missing blocks.
Actual behavior
I based this project on rockacola's examples and neo-js configurations but it keeps me returning these messages:
Mesh info: Unable to find a suitable node to perform benchmark.
2018-11-23 10:05:46.769 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed4.switcheo.network:10331 Message: Request failed with status code 503
neo.mesh is ready.
Blockchain Height: 2998189
No sync progress yet
2018-11-23 10:05:51.165 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed5.switcheo.network:10331 Message: Request failed with status code 503
No sync progress yet
2018-11-23 10:05:55.262 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed6.cityofzion.io:443 Message: write EPROTO 140680443647808:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/s23_clnt.c:772:
2018-11-23 10:05:55.286 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed7.cityofzion.io:443 Message: write EPROTO 140680443647808:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/s23_clnt.c:772:
2018-11-23 10:05:56.490 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed1.switcheo.network:10331 Message: Request failed with status code 504
No sync progress yet
2018-11-23 10:06:00.794 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: http://node1.ams2.bridgeprotocol.io Message: connect ECONNREFUSED 198.211.127.188:80
2018-11-23 10:06:01.407 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed9.cityofzion.io:443 Message: write EPROTO 140680443647808:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/s23_clnt.c:772:
2018-11-23 10:06:01.409 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed0.cityofzion.io:443 Message: write EPROTO 140680443647808:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/s23_clnt.c:772:
2018-11-23 10:06:01.410 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: https://seed8.cityofzion.io:443 Message: write EPROTO 140680443647808:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/s23_clnt.c:772:
No sync progress yet
2018-11-23 10:06:05.050 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: http://node1.nyc3.bridgeprotocol.io Message: connect ECONNREFUSED 165.227.186.72:80
2018-11-23 10:06:05.085 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: http://node2.nyc3.bridgeprotocol.io Message: connect ECONNREFUSED 159.65.244.191:80
2018-11-23 10:06:05.134 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: http://node2.ams2.bridgeprotocol.io Message: connect ECONNREFUSED 37.139.22.119:80
2018-11-23 10:06:05.356 Mesh info: node.getBlockCount() failed, but to continue. Endpoint: http://node1.sgp1.bridgeprotocol.io Message: connect ECONNREFUSED 206.189.94.221:80
SYNCER REPORT:
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: