Some machines have incorrect local routing tables, need workarounds
See original GitHub issueCorda insists to to bind (I believe Artemis) to the interface with public hostname/IP address. This doesn’t necessary equal IP address visible in the internet. Actually, in cloud (Azure for sure) it’s not equal.
[ERROR] 2017-02-23T10:33:52,544 [main] Main.main - Exception during node startup
org.apache.activemq.artemis.api.core.ActiveMQNotConnectedException: AMQ119007: Cannot connect to server(s). Tried with all available servers.
at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:785) ~[artemis-core-client-1.5.1.jar:1.5.1]
at net.corda.node.services.messaging.NodeMessagingClient.start(NodeMessagingClient.kt:127) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.Node.startMessagingService(Node.kt:151) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.AbstractNode$start$3.invoke(AbstractNode.kt:263) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.AbstractNode$start$3.invoke(AbstractNode.kt:75) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.AbstractNode$initialiseDatabasePersistence$2.invoke(AbstractNode.kt:321) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.AbstractNode$initialiseDatabasePersistence$2.invoke(AbstractNode.kt:75) ~[node-0.9-SNAPSHOT.jar:?]
at org.jetbrains.exposed.sql.transactions.ThreadLocalTransactionManagerKt.inTopLevelTransaction(ThreadLocalTransactionManager.kt:69) ~[exposed-0.5.0.jar:?]
at org.jetbrains.exposed.sql.transactions.ThreadLocalTransactionManagerKt.transaction(ThreadLocalTransactionManager.kt:57) ~[exposed-0.5.0.jar:?]
at net.corda.node.utilities.DatabaseSupportKt.databaseTransaction(DatabaseSupport.kt:39) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.AbstractNode.initialiseDatabasePersistence(AbstractNode.kt:320) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.Node.initialiseDatabasePersistence(Node.kt:201) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.AbstractNode.start(AbstractNode.kt:202) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.internal.Node.start(Node.kt:206) ~[node-0.9-SNAPSHOT.jar:?]
at net.corda.node.Corda.main(Corda.kt:109) [node-0.9-SNAPSHOT.jar:?]```
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:18 (6 by maintainers)
Top Results From Across the Web
How to Troubleshoot Routing Problems - Auvik Networks
Fast and effective ways to troubleshoot internet routing issues from network expert and author Kevin Dooley.
Read more >Default gateway route doesn't appear in Routing Table
Workaround 1: Manually add the default route for the Interface · Click Start, click Run, type cmd in the Open box, and then...
Read more >Routing Tables in Computer Network - GeeksforGeeks
Routers use Routing Tables to determine out which interface the packet will be sent. A routing table lists all networks for which routes...
Read more >Chapter 21 Fixing Common PPP Problems (Tasks)
Ensure that the intermediate routers have not been misconfigured. Often the problem can be found in the path back to the peer. (Optional)...
Read more >Linux Hacks to Fix Routing Problems - UMD Physics
Hack to fix it: In the rc.machine file, use the /sbin/ip command to set up a somewhat more complicated routing scenario with a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Azure/AWS machine with public IP address has all ports forwarded by default.
The problem is with Corda not be able to translate node-name to local IP address. Adding node-name to /etc/hosts instantly resolve the problem.
Great!