-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Connect to Any Peer #3514
Comments
|
Even without any fast sync. backups, it shows the same errors. |
And, some more errors. `06:14:45.273 INFO [nioEventLoopGroup-6-1] net channel active, /47.52.157.251:52752 06:14:45.535 ERROR [nioEventLoopGroup-6-1] net Close peer /47.52.157.251:52752, exception caught 06:14:46.980 ERROR [nioEventLoopGroup-6-2] net Close peer /211.72.175.250:33756, exception caught |
Fixed! I was using the wrong JDK version. Please note that you need to use JDK 1.8. |
1. What did you do?
Used the compiled JAR file and then downloaded a backup from Trongrid to sync faster.
2. What did you expect to see?
Expected for the node to find peers and sync.
3. What did you see instead?
It is unable to find any peers and the error logs show some errors.
`
05:20:46.059 INFO [pool-1-thread-1] net connect peer 195.201.83.170 18888 9983aff733de7ccf5a2cf65afd74052099b1a0103273d2e22efd342f77e9c5345c2093545afb399b7af6c6ab6047d7b0d0966a8737f3b131e28165e8b7a62941
05:20:46.062 INFO [pool-1-thread-1] net connect peer 188.116.36.9 18888 a85e4bcfb0e20c39b4c2e2a6d0a25855012f945ec96ddbb322a46f5ecd820d709bf9ff122deca291d0487948e4d0c85f6cbd8beb6b17e7160465fb4d72b6b475
05:20:46.064 INFO [pool-1-thread-1] net connect peer 47.254.150.38 18888 76f69c560046e74399f8807a4bb75d3d14ca04643a615ea46972ec80c74895e7e80099ebaa73ded5f14e93a908142107213d28bb5a5fd55a0b745d8510b01a7c
05:20:46.065 INFO [pool-1-thread-1] net connect peer 8.211.60.253 18888 19074584f41fe6cd162b0f41f105243b9548682181fd675b7b2b626d05f26d4a24a1da247faa41ae0624ee169cb941c7aab52073f785b06c860bef877228df22
05:20:46.066 INFO [pool-1-thread-1] net connect peer 54.36.114.4 18888 b0d15bc7a1a5b0e41f26dfb50a1a50462a2a358204c345d73bcf4a2fba4293154a680472ff3da9530e57588cd589409b3915b01b12057186bc2d9d748b552d41
05:20:46.071 INFO [pool-1-thread-1] net connect peer 176.9.36.4 18888 a5b313b015e1a3d9e8b4df0da020b5b77d637a31cabc5a3cdcb6e94caacd2fb06375869dc6ef4b1c0df0d476001e6f4516ca8afc2df45c29718d66db951f2115
05:20:46.079 INFO [pool-1-thread-1] net connect peer 62.171.175.19 18888 f49c94a327b902e324148197d5e1ed8f7965af676b7ee464c2d938799fdd1f3a8eb6976d691c8b18ad14b379cef024da8fb7569f85fa9328e60a60859ff68d68
05:20:46.095 INFO [pool-1-thread-1] net connect peer 84.239.4.56 18888 74b9a64e5d2e8a18f4b38b922fd9531d78a01e6c985b8b40584911804b6a08ea0bc51a9a6f1265abc92b77ddad9e0fd1a2422df085507049e3b8fcaff45edb49
05:20:46.114 INFO [TronJClientWorker-0] net channel active, /195.201.83.170:18888
05:20:46.124 ERROR [TronJClientWorker-0] net Close peer /195.201.83.170:18888, exception caught
java.lang.NullPointerException: null
at org.tron.core.ChainBaseManager.getGenesisBlockId(ChainBaseManager.java:349)
at org.tron.common.overlay.server.HandshakeHandler.sendHelloMsg(HandshakeHandler.java:123)
at org.tron.common.overlay.server.HandshakeHandler.channelActive(HandshakeHandler.java:81)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:213)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:199)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelActive(AbstractChannelHandlerContext.java:192)
at io.netty.channel.ChannelInboundHandlerAdapter.channelActive(ChannelInboundHandlerAdapter.java:64)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:213)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:199)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelActive(AbstractChannelHandlerContext.java:192)
at io.netty.channel.ChannelInboundHandlerAdapter.channelActive(ChannelInboundHandlerAdapter.java:64)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:213)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:199)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelActive(AbstractChannelHandlerContext.java:192)
at io.netty.channel.ChannelInboundHandlerAdapter.channelActive(ChannelInboundHandlerAdapter.java:64)
at io.netty.handler.timeout.IdleStateHandler.channelActive(IdleStateHandler.java:271)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:213)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:199)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelActive(AbstractChannelHandlerContext.java:192)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelActive(DefaultChannelPipeline.java:1422)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:213)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:199)
at io.netty.channel.DefaultChannelPipeline.fireChannelActive(DefaultChannelPipeline.java:941)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:311)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:341)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:634)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:546)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:460)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
at java.base/java.lang.Thread.run(Thread.java:834)`
It looks like my node is unable to connect to any peer.
The text was updated successfully, but these errors were encountered: