I was just going to suggest that a patch to be submitted that provides a more descriptive error message as it is very hard to figure out. Maybe that could be my first contribution to storm :D
On Mon, Oct 10, 2016 at 2:07 PM, Jungtaek Lim <[email protected]> wrote: > I think it would be super hard for individual users to figure out why it > happens. After Storm 1.0.0 is released, I saw a lot of similar questions > and answered one by one, but now I think it's not a good approach. > > I filed STORM-2145 <http://issues.apache.org/jira/browse/STORM-2145> and > submit a patch. It doesn't provide the way to resolve this issue, but > leaving leader nimbus information to log so that users can see its name is > expected, or need some effort to configure, or visit user/dev mailing list. > > We might need to document how to set up 'storm.local.hostname' to cluster > setup doc. Setting FQDN to only nimbus.seeds doesn't help connecting leader > Nimbus. > > - Jungtaek Lim (HeartSaVioR) > > 2016년 10월 10일 (월) 오후 8:24, Jungtaek Lim <[email protected]>님이 작성: > >> Not at all. :) >> >> If you don't manage your nodes with DNS, you may need to set >> "storm.local.hostname" to every remote nodes' Storm configuration, and make >> sure every nodes (including local machine) can resolve the name. If your IP >> is static and barely not changed, you can just set IP address to >> "storm.local.hostname". >> >> Hope this helps. >> >> Thanks, >> Jungtaek Lim (HeartSaVioR) >> >> 2016년 10월 10일 (월) 오후 7:35, Mostafa Gomaa <[email protected]>님이 작성: >> >> YES, the host name was localhost, I removed that from /etc/hosts and >> added the correct hostname. That solved the problem. Many many thanks, >> Jungataek. >> >> On Mon, Oct 10, 2016 at 12:20 PM, Jungtaek Lim <[email protected]> wrote: >> >> OK thanks for quick response. >> >> Looking at source code, it succeed to connect your Nimbus you added to >> nimbus.seeds, and got leader Nimbus information. >> But host name for leader nimbus seems not be resolvable from your local >> machine. >> >> You can open http://<ui server host>:<ui server >> port>/api/v1/nimbus/summary' and see host name for leader Nimbus. >> Please try connecting leader nimbus (just telnet) manually using host >> name which API provides. >> >> Btw, all nodes should be able to resolve each other's hostname, and local >> machine should be able to resolve nimbuses hostname. >> >> Thanks, >> Jungtaek Lim (HeartSaVioR) >> >> 2016년 10월 10일 (월) 오후 7:05, Mostafa Gomaa <[email protected]>님이 작성: >> >> Hi Jungtaek, >> >> I am using 1.0.2. Both client and nimbus machines are 1.0.2 >> >> On Mon, Oct 10, 2016 at 12:03 PM, Jungtaek Lim <[email protected]> wrote: >> >> Hi Mostafa, >> >> What's your Storm version? >> >> - Jungtaek Lim (HeartSaVioR) >> >> 2016년 10월 10일 (월) 오후 6:59, Mostafa Gomaa <[email protected]>님이 작성: >> >> Hello All, >> >> I have a single node cluster running zookeeper and nimbus on a remote >> machine. Both zookeeper and nimbus are running and I can use the storm >> client script successfully from within the machine. However, when I tried >> to list or submit topologies from a remote machine, I get the following >> error: >> >> Exception in thread "main" java.lang.RuntimeException: >> org.apache.storm.thrift.transport.TTransportException: >> java.net.ConnectException: Connection refused >> at org.apache.storm.security.auth.TBackoffConnect. >> retryNext(TBackoffConnect.java:64) >> at org.apache.storm.security.auth.TBackoffConnect.doConnectWithRetry( >> TBackoffConnect.java:56) >> at org.apache.storm.security.auth.ThriftClient.reconnect( >> ThriftClient.java:99) >> at org.apache.storm.security.auth.ThriftClient.<init>( >> ThriftClient.java:69) >> at org.apache.storm.utils.NimbusClient.<init>(NimbusClient.java:106) >> at org.apache.storm.utils.NimbusClient.getConfiguredClientAs( >> NimbusClient.java:78) >> at org.apache.storm.command.list$_main.invoke(list.clj:22) >> at clojure.lang.AFn.applyToHelper(AFn.java:152) >> at clojure.lang.AFn.applyTo(AFn.java:144) >> at org.apache.storm.command.list.main(Unknown Source) >> Caused by: org.apache.storm.thrift.transport.TTransportException: >> java.net.ConnectException: Connection refused >> at org.apache.storm.thrift.transport.TSocket.open(TSocket.java:226) >> at org.apache.storm.thrift.transport.TFramedTransport. >> open(TFramedTransport.java:81) >> at org.apache.storm.security.auth.SimpleTransportPlugin. >> connect(SimpleTransportPlugin.java:103) >> at org.apache.storm.security.auth.TBackoffConnect.doConnectWithRetry( >> TBackoffConnect.java:53) >> ... 8 more >> Caused by: java.net.ConnectException: Connection refused >> at java.net.PlainSocketImpl.socketConnect(Native Method) >> at java.net.AbstractPlainSocketImpl.doConnect( >> AbstractPlainSocketImpl.java:339) >> at java.net.AbstractPlainSocketImpl.connectToAddress( >> AbstractPlainSocketImpl.java:200) >> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java: >> 182) >> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) >> at java.net.Socket.connect(Socket.java:579) >> at org.apache.storm.thrift.transport.TSocket.open(TSocket.java:221) >> ... 11 more >> >> >> I don't think it's an iptables issue since I can telnet to the remote >> machine on both zookeeper and nimbus ports. My storm.yaml files are shown >> below: >> >> on client machine: >> >> storm.zookeeper.servers: >> - "192.168.3.115" >> >> nimbus.seeds: ["192.168.3.115"] >> >> >> on nimbus/zookeeper machine: >> >> storm.zookeeper.servers: >> - "localhost" >> >> nimbus.seeds: ["localhost"] >> storm.local.dir: "/mnt/storm" >> >> >> Any help would be greatly appreciated >> >> >> >>
