You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Boris Prochazka <bo...@viaplay.com> on 2016/03/10 15:23:04 UTC
Can't deploy a a storm topology
Hi, I am having problem to deploy a topology to a storm cluster (1.0.0-SNAPSHOT) in docker running in virtual box on OSX. There is one nimbus, one ui, three supervisors and zookeepers.
I have configured the storm client in ~/.storm/storm.yml
nimbus.seeds:
- "192.168.99.100"
nimbus.thrift.port: 49627
The stack trace I am receiving is on the storm client when deploying is :
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:101)
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:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.storm.thrift.transport.TSocket.open(TSocket.java:221)
... 11 more
To verify that the client is connecting toward the correct host and port I have traced it with tcpdump:
$ sudo tcpdump -i vboxnet0 'tcp port 49627'
14:38:32.275894 IP 192.168.99.1.65294 > 192.168.99.100.49627: Flags [S], seq 2737883631, win 65535, options [mss 1460,nop,wscale 5,nop,nop,TS val 1184688669 ecr 0,sackOK,eol], length 0
14:38:32.276125 IP 192.168.99.100.49627 > 192.168.99.1.65294: Flags [S.], seq 1088478441, ack 2737883632, win 28960, options [mss 1460,sackOK,TS val 27246581 ecr 1184688669,nop,wscale 7], length 0
14:38:32.276155 IP 192.168.99.1.65294 > 192.168.99.100.49627: Flags [.], ack 1, win 4117, options [nop,nop,TS val 1184688669 ecr 27246581], length 0
14:38:32.282704 IP 192.168.99.1.65294 > 192.168.99.100.49627: Flags [P.], seq 1:32, ack 1, win 4117, options [nop,nop,TS val 1184688675 ecr 27246581], length 31
14:38:32.282937 IP 192.168.99.100.49627 > 192.168.99.1.65294: Flags [.], ack 32, win 227, options [nop,nop,TS val 27246582 ecr 1184688675], length 0
14:38:32.293685 IP 192.168.99.100.49627 > 192.168.99.1.65294: Flags [P.], seq 1:689, ack 32, win 227, options [nop,nop,TS val 27246583 ecr 1184688675], length 688
14:38:32.293720 IP 192.168.99.1.65294 > 192.168.99.100.49627: Flags [.], ack 689, win 4096, options [nop,nop,TS val 1184688686 ecr 27246583], length 0
14:38:42.385067 IP 192.168.99.1.65294 > 192.168.99.100.49627: Flags [F.], seq 32, ack 689, win 4096, options [nop,nop,TS val 1184698764 ecr 27246583], length 0
14:38:42.385457 IP 192.168.99.100.49627 > 192.168.99.1.65294: Flags [F.], seq 689, ack 33, win 227, options [nop,nop,TS val 27247592 ecr 1184698764], length 0
14:38:42.385672 IP 192.168.99.1.65294 > 192.168.99.100.49627: Flags [.], ack 690, win 4096, options [nop,nop,TS val 1184698764 ecr 27247592], length 0
On the server in nimbus.log it all looks good except for the last log line:
2016-03-10 13:27:26.199 o.a.s.t.s.AbstractNonblockingServer$FrameBuffer [ERROR] Read an invalid frame size of -720899. Are you using TFramedTransport on the client side?
Does any body have a clue ??
/boris
Boris Prochazka
boris.prochazka@viaplay.com
Phone: +46 70 5125122
Skypeto: boris.prochazka
--------------------------------------------------------------------
"Perfection is achieved, not when there is nothing more to add,
but when there is nothing left to take away."
- Antoine de Saint-Exupery (1900 - 1944)