Hi Sam, You can try to find which process has bound this port by "netstat -anp" first.
Generally, there are following cases for the binding error. 1. "local port range" is not set to exclude the port range used in Storm. 2. The previous worker was not killed correctly. 3. There is bug of assignment in some scenarios. Same port was assigned to two workers. Regards Basti -----Original Message----- From: sam mohel [mailto:[email protected]] Sent: Thursday, December 10, 2015 7:16 AM To: [email protected] Subject: Re: Problem with storm since 4 months i tried to use storm-0.9.5 but problem changed with cannot bind port 6703 i think it's same problem On Wed, Dec 9, 2015 at 8:42 PM, Harsha <[email protected]> wrote: > Sam, > you might be using very old version of storm since its showing > ZeroMQ. Can you try using newer version storm without zero mq. > -Harsha > > On Wed, Dec 9, 2015, at 10:19 AM, sam mohel wrote: > > I have this problem since 4months when I submitted topology I got > > this in the worker log file [ERROR] Async loop died! > > org.zeromq.ZMQException: > > Address already in use(0x62) > > at org.zeromq.ZMQ$Socket.bind(Native Method) at > > zilch.mq$bind.invoke(mq.clj:69) at > > backtype.storm.messaging.zmq.ZMQContext.bind(zmq.clj:57)at > > > backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__1629.i > nvoke(loader.clj:26) > > at backtype.storm.util$async_loop$fn__465.invoke(util.clj:375) > > at clojure.lang.AFn.run(AFn.java:24) at java.lang.Thread.run(Unknown > > Source) > > > > when i tried to connect port 6703 and 6702 > > > > And supervisor log file hadn't still start > > > > > > I searched everywhere but cannot find any solution I hope you can >
