Skip to content
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

IllegalArgumentException: Attempt to create a discovery endpoint for an enode with discovery disabled. #7887

Open
fab-10 opened this issue Nov 19, 2024 · 2 comments
Labels
bug Something isn't working good first issue Good for newcomers P5 Very Low (ex: JSON-RPC json object response not ignoring null keys, typo on a CLI description) peering snack Smaller coding task - less than a day for an experienced dev

Comments

@fab-10
Copy link
Contributor

fab-10 commented Nov 19, 2024

{"@timestamp":"2024-11-16T04:52:16,378","level":"ERROR","thread":"vert.x-virtual-thread-16139","class":"ContextImpl","message":"Unhandled exception","throwable":" java.lang.IllegalArgumentException: Attempt to create a discovery endpoint for an enode with discovery disabled.
at org.hyperledger.besu.ethereum.p2p.discovery.Endpoint.lambda$fromEnode$1(Endpoint.java:57)
at java.base/java.util.Optional.orElseThrow(Optional.java:403)
at org.hyperledger.besu.ethereum.p2p.discovery.Endpoint.fromEnode(Endpoint.java:55)
at org.hyperledger.besu.ethereum.p2p.discovery.DiscoveryPeer.fromEnode(DiscoveryPeer.java:52)
at org.hyperledger.besu.ethereum.p2p.network.DefaultP2PNetwork.lambda$createDaemonListener$6(DefaultP2PNetwork.java:374)
at org.hyperledger.besu.ethereum.p2p.discovery.dns.DNSDaemon.lambda$refreshENRRecords$0(DNSDaemon.java:104)
at java.base/java.util.Optional.ifPresent(Optional.java:178)
at org.hyperledger.besu.ethereum.p2p.discovery.dns.DNSDaemon.refreshENRRecords(DNSDaemon.java:104)
at io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:1051)
at io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:1027)
at io.vertx.core.impl.ContextImpl.emit(ContextImpl.java:328)
at io.vertx.core.impl.ContextImpl.lambda$emit$5(ContextImpl.java:335)
at io.vertx.core.impl.WorkerExecutor.lambda$execute$0(WorkerExecutor.java:68)
at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76)
at io.vertx.core.impl.ThreadPerTaskExecutorService.lambda$execute$0(ThreadPerTaskExecutorService.java:82)
at java.base/java.lang.VirtualThread.run(VirtualThread.java:329)\n"}
@fab-10 fab-10 added bug Something isn't working peering labels Nov 19, 2024
@siladu siladu added the good first issue Good for newcomers label Nov 25, 2024
@siladu
Copy link
Contributor

siladu commented Nov 25, 2024

@fab-10 What priority would you assign this?
Does it happen every time and does it impact node operation at all?

@siladu siladu added the snack Smaller coding task - less than a day for an experienced dev label Nov 25, 2024
@fab-10
Copy link
Contributor Author

fab-10 commented Nov 26, 2024

low priority, it happens seldomly and there is no evident impact

@fab-10 fab-10 added the P5 Very Low (ex: JSON-RPC json object response not ignoring null keys, typo on a CLI description) label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers P5 Very Low (ex: JSON-RPC json object response not ignoring null keys, typo on a CLI description) peering snack Smaller coding task - less than a day for an experienced dev
Projects
None yet
Development

No branches or pull requests

2 participants