You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by researcher cs <pr...@gmail.com> on 2016/01/04 01:09:40 UTC
Failed to bind to: 0.0.0.0/0.0.0.0:6703
I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
now i ran my topology in local mode with maven commands and worked well
BUT when i submitted it i got
org.jboss.netty.channel.ChannelException: Failed to bind to:
0.0.0.0/0.0.0.0:6703
at
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
~[netty-3.6.3.Final.jar:na]
at backtype.storm.messaging.netty.Server.<init>(Server.java:56)
~[storm-netty-0.9.0.1.jar:na]
at backtype.storm.messaging.netty.Context.bind(Context.java:27)
~[storm-netty-0.9.0.1.jar:na]
at
backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20)
~[storm-core-0.9.0.1.jar:na]
at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401)
~[storm-core-0.9.0.1.jar:na]
at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139)
~[na:1.6.0_37]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
~[na:1.6.0_37]
at
org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
~[netty-3.6.3.Final.jar:na]
at
org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366)
~[netty-3.6.3.Final.jar:na]
at
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290)
~[netty-3.6.3.Final.jar:na]
at
org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
~[netty-3.6.3.Final.jar:na]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
~[na:1.6.0_37]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
~[na:1.6.0_37]
... 1 common frames omitted
2016-01-04 01:52:07 b.s.util [INFO] Halting process:
the topology using one worker for one supervisor i'm trying to run or
submit it first in single machine
so my only storm.yaml is
storm.zookeeper.servers:
- "192.168.x.x"
nimbus.host: "192.168.x.x"
storm.local.dir: "/var/storm"
supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
worker.childopts: "-Djava.net.preferIPv4Stack=true"
drpc.servers:
- "192.168.x.x"
storm.messaging.transport: "backtype.storm.messaging.netty.Context"
storm.messaging.netty.server_worker_threads: 1
storm.messaging.netty.client_worker_threads: 1
storm.messaging.netty.buffer_size: 5242880
storm.messaging.netty.max_retries: 100
storm.messaging.netty.max_wait_ms: 1000
storm.messaging.netty.min_wait_ms: 100
zoo.cfg is
tickTime=2000
initLimit=10
syncLimit=5
dataDir=/var/zookeeper
clientPort=2181
i tried to use localhost but got same error then tried to use my ip address
i searched to fix it more but got this solution
can someone illustrate it beacuse i didn't get it well
[[
It turned out that my logback/cluster.xml configuration had a
SocketAppender that didn't have a listener on the remote host. Having an
appender defined in configuration file, even if it is not set up to receive
any log messages, will cause Storm to block and the above error message.its
due to zookeeper you have add curator separetly not required its the part
of zookeeper
]]
or can someone help me to fix it ?
importaant thing
topology using drpc and i tried to submit another topoogies worked well but
topology with drpc got this error
the project i'm trying to submit it here
https://github.com/mvogiatzis/first-stories-twitter
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
i checked the port with its process got
root 8265 8009 33 02:36 pts/8 00:00:16 java -server
-Djava.net.preferIPv4Stack=true
-Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib
-Dlogfile.name=worker-6703.log -Dstorm.home=/usr/local/storm
-Dlogback.configurationFile=/usr/local/storm/logback/cluster.xml
-Dstorm.id=fsd-1-1451867773
-Dworker.id=e44a8daf-313d-4f7d-a67f-5b900eee3764 -Dworker.port=6703 -cp
/usr/local/storm/storm-core-0.9.0.1.jar:/usr/local/storm/storm-netty-0.9.0.1.jar:/usr/local/storm/storm-console-logging-0.9.0.1.jar:/usr/local/storm/lib/netty-3.6.3.Final.jar:/usr/local/storm/lib/commons-exec-1.1.jar:/usr/local/storm/lib/ring-devel-0.3.11.jar:/usr/local/storm/lib/carbonite-1.5.0.jar:/usr/local/storm/lib/ring-jetty-adapter-0.3.11.jar:/usr/local/storm/lib/minlog-1.2.jar:/usr/local/storm/lib/tools.nrepl-0.2.3.jar:/usr/local/storm/lib/hiccup-0.3.6.jar:/usr/local/storm/lib/commons-lang-2.5.jar:/usr/local/storm/lib/math.numeric-tower-0.0.1.jar:/usr/local/storm/lib/servlet-api-2.5-20081211.jar:/usr/local/storm/lib/commons-logging-1.1.1.jar:/usr/local/storm/lib/tools.logging-0.2.3.jar:/usr/local/storm/lib/clout-1.0.1.jar:/usr/local/storm/lib/httpcore-4.1.jar:/usr/local/storm/lib/logback-classic-1.0.6.jar:/usr/local/storm/lib/servlet-api-2.5.jar:/usr/local/storm/lib/objenesis-1.2.jar:/usr/local/storm/lib/clojure-1.4.0.jar:/usr/local/storm/lib/zookeeper-3.4.6.jar:/usr/local/storm/lib/snakeyaml-1.11.jar:/usr/local/storm/lib/json-simple-1.1.jar:/usr/local/storm/lib/clj-stacktrace-0.2.2.jar:/usr/local/storm/lib/httpclient-4.1.1.jar:/usr/local/storm/lib/jzmq-2.1.0.jar:/usr/local/storm/lib/core.incubator-0.1.0.jar:/usr/local/storm/lib/libthrift7-0.7.0-2.jar:/usr/local/storm/lib/slf4j-api-1.6.5.jar:/usr/local/storm/lib/junit-3.8.1.jar:/usr/local/storm/lib/guava-13.0.jar:/usr/local/storm/lib/logback-core-1.0.6.jar:/usr/local/storm/lib/jgrapht-0.8.3.jar:/usr/local/storm/lib/commons-io-1.4.jar:/usr/local/storm/lib/curator-framework-1.0.1.jar:/usr/local/storm/lib/ring-servlet-0.3.11.jar:/usr/local/storm/lib/tools.macro-0.1.0.jar:/usr/local/storm/lib/asm-4.0.jar:/usr/local/storm/lib/jetty-6.1.26.jar:/usr/local/storm/lib/reflectasm-1.07-shaded.jar:/usr/local/storm/lib/joda-time-2.0.jar:/usr/local/storm/lib/jline-0.9.94.jar:/usr/local/storm/lib/tools.cli-0.2.2.jar:/usr/local/storm/lib/commons-fileupload-1.2.1.jar:/usr/local/storm/lib/zookeeper-3.3.3.jar:/usr/local/storm/lib/kryo-2.17.jar:/usr/local/storm/lib/clojure-complete-0.2.3.jar:/usr/local/storm/lib/compojure-1.1.3.jar:/usr/local/storm/lib/curator-client-1.0.1.jar:/usr/local/storm/lib/jetty-util-6.1.26.jar:/usr/local/storm/lib/ring-core-1.1.5.jar:/usr/local/storm/lib/disruptor-2.10.1.jar:/usr/local/storm/lib/commons-codec-1.4.jar:/usr/local/storm/lib/mockito-all-1.9.5.jar:/usr/local/storm/lib/log4j-over-slf4j-1.6.6.jar:/usr/local/storm/lib/clj-time-0.4.1.jar:/usr/local/storm/conf:/var/storm/supervisor/stormdist/fsd-1-1451867773/stormjar.jar
backtype.storm.daemon.worker fsd-1-1451867773
34879f97-2ce0-479c-b555-944a9bd50b9d 6703
e44a8daf-313d-4f7d-a67f-5b900eee3764
user 8488 7018 0 02:37 pts/30 00:00:00 grep --color=auto 8265
may be it help ! waiting your reply , Thanks in advance
On Mon, Jan 4, 2016 at 2:10 AM, researcher cs <pr...@gmail.com>
wrote:
> sorry it's not my toplogy i refered to the coder hope he can help in this
> issue
>
> On Mon, Jan 4, 2016 at 2:09 AM, researcher cs <pr...@gmail.com>
> wrote:
>
>> I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
>> now i ran my topology in local mode with maven commands and worked well
>> BUT when i submitted it i got
>>
>> org.jboss.netty.channel.ChannelException: Failed to bind to:
>> 0.0.0.0/0.0.0.0:6703
>> at
>> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
>> ~[netty-3.6.3.Final.jar:na]
>> at backtype.storm.messaging.netty.Server.<init>(Server.java:56)
>> ~[storm-netty-0.9.0.1.jar:na]
>> at backtype.storm.messaging.netty.Context.bind(Context.java:27)
>> ~[storm-netty-0.9.0.1.jar:na]
>> at
>> backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20)
>> ~[storm-core-0.9.0.1.jar:na]
>> at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401)
>> ~[storm-core-0.9.0.1.jar:na]
>> at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
>> at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
>> Caused by: java.net.BindException: Address already in use
>> at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
>> at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
>> at
>> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139)
>> ~[na:1.6.0_37]
>> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
>> ~[na:1.6.0_37]
>> at
>> org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> ~[na:1.6.0_37]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> ~[na:1.6.0_37]
>> ... 1 common frames omitted
>> 2016-01-04 01:52:07 b.s.util [INFO] Halting process:
>>
>> the topology using one worker for one supervisor i'm trying to run or
>> submit it first in single machine
>>
>> so my only storm.yaml is
>>
>> storm.zookeeper.servers:
>> - "192.168.x.x"
>> nimbus.host: "192.168.x.x"
>> storm.local.dir: "/var/storm"
>> supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
>> nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
>> worker.childopts: "-Djava.net.preferIPv4Stack=true"
>> drpc.servers:
>> - "192.168.x.x"
>> storm.messaging.transport: "backtype.storm.messaging.netty.Context"
>> storm.messaging.netty.server_worker_threads: 1
>> storm.messaging.netty.client_worker_threads: 1
>> storm.messaging.netty.buffer_size: 5242880
>> storm.messaging.netty.max_retries: 100
>> storm.messaging.netty.max_wait_ms: 1000
>> storm.messaging.netty.min_wait_ms: 100
>>
>> zoo.cfg is
>>
>> tickTime=2000
>> initLimit=10
>> syncLimit=5
>> dataDir=/var/zookeeper
>> clientPort=2181
>>
>> i tried to use localhost but got same error then tried to use my ip
>> address
>> i searched to fix it more but got this solution
>> can someone illustrate it beacuse i didn't get it well
>>
>> [[
>> It turned out that my logback/cluster.xml configuration had a
>> SocketAppender that didn't have a listener on the remote host. Having an
>> appender defined in configuration file, even if it is not set up to receive
>> any log messages, will cause Storm to block and the above error message.its
>> due to zookeeper you have add curator separetly not required its the part
>> of zookeeper
>> ]]
>>
>> or can someone help me to fix it ?
>>
>> importaant thing
>>
>> topology using drpc and i tried to submit another topoogies worked well
>> but topology with drpc got this error
>>
>>
>> the project i'm trying to submit it here
>> https://github.com/mvogiatzis/first-stories-twitter
>>
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
i checked the port with its process got
root 8265 8009 33 02:36 pts/8 00:00:16 java -server
-Djava.net.preferIPv4Stack=true
-Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib
-Dlogfile.name=worker-6703.log -Dstorm.home=/usr/local/storm
-Dlogback.configurationFile=/usr/local/storm/logback/cluster.xml
-Dstorm.id=fsd-1-1451867773
-Dworker.id=e44a8daf-313d-4f7d-a67f-5b900eee3764 -Dworker.port=6703 -cp
/usr/local/storm/storm-core-0.9.0.1.jar:/usr/local/storm/storm-netty-0.9.0.1.jar:/usr/local/storm/storm-console-logging-0.9.0.1.jar:/usr/local/storm/lib/netty-3.6.3.Final.jar:/usr/local/storm/lib/commons-exec-1.1.jar:/usr/local/storm/lib/ring-devel-0.3.11.jar:/usr/local/storm/lib/carbonite-1.5.0.jar:/usr/local/storm/lib/ring-jetty-adapter-0.3.11.jar:/usr/local/storm/lib/minlog-1.2.jar:/usr/local/storm/lib/tools.nrepl-0.2.3.jar:/usr/local/storm/lib/hiccup-0.3.6.jar:/usr/local/storm/lib/commons-lang-2.5.jar:/usr/local/storm/lib/math.numeric-tower-0.0.1.jar:/usr/local/storm/lib/servlet-api-2.5-20081211.jar:/usr/local/storm/lib/commons-logging-1.1.1.jar:/usr/local/storm/lib/tools.logging-0.2.3.jar:/usr/local/storm/lib/clout-1.0.1.jar:/usr/local/storm/lib/httpcore-4.1.jar:/usr/local/storm/lib/logback-classic-1.0.6.jar:/usr/local/storm/lib/servlet-api-2.5.jar:/usr/local/storm/lib/objenesis-1.2.jar:/usr/local/storm/lib/clojure-1.4.0.jar:/usr/local/storm/lib/zookeeper-3.4.6.jar:/usr/local/storm/lib/snakeyaml-1.11.jar:/usr/local/storm/lib/json-simple-1.1.jar:/usr/local/storm/lib/clj-stacktrace-0.2.2.jar:/usr/local/storm/lib/httpclient-4.1.1.jar:/usr/local/storm/lib/jzmq-2.1.0.jar:/usr/local/storm/lib/core.incubator-0.1.0.jar:/usr/local/storm/lib/libthrift7-0.7.0-2.jar:/usr/local/storm/lib/slf4j-api-1.6.5.jar:/usr/local/storm/lib/junit-3.8.1.jar:/usr/local/storm/lib/guava-13.0.jar:/usr/local/storm/lib/logback-core-1.0.6.jar:/usr/local/storm/lib/jgrapht-0.8.3.jar:/usr/local/storm/lib/commons-io-1.4.jar:/usr/local/storm/lib/curator-framework-1.0.1.jar:/usr/local/storm/lib/ring-servlet-0.3.11.jar:/usr/local/storm/lib/tools.macro-0.1.0.jar:/usr/local/storm/lib/asm-4.0.jar:/usr/local/storm/lib/jetty-6.1.26.jar:/usr/local/storm/lib/reflectasm-1.07-shaded.jar:/usr/local/storm/lib/joda-time-2.0.jar:/usr/local/storm/lib/jline-0.9.94.jar:/usr/local/storm/lib/tools.cli-0.2.2.jar:/usr/local/storm/lib/commons-fileupload-1.2.1.jar:/usr/local/storm/lib/zookeeper-3.3.3.jar:/usr/local/storm/lib/kryo-2.17.jar:/usr/local/storm/lib/clojure-complete-0.2.3.jar:/usr/local/storm/lib/compojure-1.1.3.jar:/usr/local/storm/lib/curator-client-1.0.1.jar:/usr/local/storm/lib/jetty-util-6.1.26.jar:/usr/local/storm/lib/ring-core-1.1.5.jar:/usr/local/storm/lib/disruptor-2.10.1.jar:/usr/local/storm/lib/commons-codec-1.4.jar:/usr/local/storm/lib/mockito-all-1.9.5.jar:/usr/local/storm/lib/log4j-over-slf4j-1.6.6.jar:/usr/local/storm/lib/clj-time-0.4.1.jar:/usr/local/storm/conf:/var/storm/supervisor/stormdist/fsd-1-1451867773/stormjar.jar
backtype.storm.daemon.worker fsd-1-1451867773
34879f97-2ce0-479c-b555-944a9bd50b9d 6703
e44a8daf-313d-4f7d-a67f-5b900eee3764
user 8488 7018 0 02:37 pts/30 00:00:00 grep --color=auto 8265
may be it help ! waiting your reply , Thanks in advance
On Mon, Jan 4, 2016 at 2:10 AM, researcher cs <pr...@gmail.com>
wrote:
> sorry it's not my toplogy i refered to the coder hope he can help in this
> issue
>
> On Mon, Jan 4, 2016 at 2:09 AM, researcher cs <pr...@gmail.com>
> wrote:
>
>> I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
>> now i ran my topology in local mode with maven commands and worked well
>> BUT when i submitted it i got
>>
>> org.jboss.netty.channel.ChannelException: Failed to bind to:
>> 0.0.0.0/0.0.0.0:6703
>> at
>> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
>> ~[netty-3.6.3.Final.jar:na]
>> at backtype.storm.messaging.netty.Server.<init>(Server.java:56)
>> ~[storm-netty-0.9.0.1.jar:na]
>> at backtype.storm.messaging.netty.Context.bind(Context.java:27)
>> ~[storm-netty-0.9.0.1.jar:na]
>> at
>> backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20)
>> ~[storm-core-0.9.0.1.jar:na]
>> at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401)
>> ~[storm-core-0.9.0.1.jar:na]
>> at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
>> at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
>> Caused by: java.net.BindException: Address already in use
>> at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
>> at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
>> at
>> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139)
>> ~[na:1.6.0_37]
>> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
>> ~[na:1.6.0_37]
>> at
>> org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
>> ~[netty-3.6.3.Final.jar:na]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>> ~[na:1.6.0_37]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> ~[na:1.6.0_37]
>> ... 1 common frames omitted
>> 2016-01-04 01:52:07 b.s.util [INFO] Halting process:
>>
>> the topology using one worker for one supervisor i'm trying to run or
>> submit it first in single machine
>>
>> so my only storm.yaml is
>>
>> storm.zookeeper.servers:
>> - "192.168.x.x"
>> nimbus.host: "192.168.x.x"
>> storm.local.dir: "/var/storm"
>> supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
>> nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
>> worker.childopts: "-Djava.net.preferIPv4Stack=true"
>> drpc.servers:
>> - "192.168.x.x"
>> storm.messaging.transport: "backtype.storm.messaging.netty.Context"
>> storm.messaging.netty.server_worker_threads: 1
>> storm.messaging.netty.client_worker_threads: 1
>> storm.messaging.netty.buffer_size: 5242880
>> storm.messaging.netty.max_retries: 100
>> storm.messaging.netty.max_wait_ms: 1000
>> storm.messaging.netty.min_wait_ms: 100
>>
>> zoo.cfg is
>>
>> tickTime=2000
>> initLimit=10
>> syncLimit=5
>> dataDir=/var/zookeeper
>> clientPort=2181
>>
>> i tried to use localhost but got same error then tried to use my ip
>> address
>> i searched to fix it more but got this solution
>> can someone illustrate it beacuse i didn't get it well
>>
>> [[
>> It turned out that my logback/cluster.xml configuration had a
>> SocketAppender that didn't have a listener on the remote host. Having an
>> appender defined in configuration file, even if it is not set up to receive
>> any log messages, will cause Storm to block and the above error message.its
>> due to zookeeper you have add curator separetly not required its the part
>> of zookeeper
>> ]]
>>
>> or can someone help me to fix it ?
>>
>> importaant thing
>>
>> topology using drpc and i tried to submit another topoogies worked well
>> but topology with drpc got this error
>>
>>
>> the project i'm trying to submit it here
>> https://github.com/mvogiatzis/first-stories-twitter
>>
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
sorry it's not my toplogy i refered to the coder hope he can help in this
issue
On Mon, Jan 4, 2016 at 2:09 AM, researcher cs <pr...@gmail.com>
wrote:
> I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
> now i ran my topology in local mode with maven commands and worked well
> BUT when i submitted it i got
>
> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
> at
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
> ~[netty-3.6.3.Final.jar:na]
> at backtype.storm.messaging.netty.Server.<init>(Server.java:56)
> ~[storm-netty-0.9.0.1.jar:na]
> at backtype.storm.messaging.netty.Context.bind(Context.java:27)
> ~[storm-netty-0.9.0.1.jar:na]
> at
> backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20)
> ~[storm-core-0.9.0.1.jar:na]
> at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401)
> ~[storm-core-0.9.0.1.jar:na]
> at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
> at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
> at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139)
> ~[na:1.6.0_37]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
> ~[na:1.6.0_37]
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
> ~[netty-3.6.3.Final.jar:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> ~[na:1.6.0_37]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> ~[na:1.6.0_37]
> ... 1 common frames omitted
> 2016-01-04 01:52:07 b.s.util [INFO] Halting process:
>
> the topology using one worker for one supervisor i'm trying to run or
> submit it first in single machine
>
> so my only storm.yaml is
>
> storm.zookeeper.servers:
> - "192.168.x.x"
> nimbus.host: "192.168.x.x"
> storm.local.dir: "/var/storm"
> supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
> nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
> worker.childopts: "-Djava.net.preferIPv4Stack=true"
> drpc.servers:
> - "192.168.x.x"
> storm.messaging.transport: "backtype.storm.messaging.netty.Context"
> storm.messaging.netty.server_worker_threads: 1
> storm.messaging.netty.client_worker_threads: 1
> storm.messaging.netty.buffer_size: 5242880
> storm.messaging.netty.max_retries: 100
> storm.messaging.netty.max_wait_ms: 1000
> storm.messaging.netty.min_wait_ms: 100
>
> zoo.cfg is
>
> tickTime=2000
> initLimit=10
> syncLimit=5
> dataDir=/var/zookeeper
> clientPort=2181
>
> i tried to use localhost but got same error then tried to use my ip address
> i searched to fix it more but got this solution
> can someone illustrate it beacuse i didn't get it well
>
> [[
> It turned out that my logback/cluster.xml configuration had a
> SocketAppender that didn't have a listener on the remote host. Having an
> appender defined in configuration file, even if it is not set up to receive
> any log messages, will cause Storm to block and the above error message.its
> due to zookeeper you have add curator separetly not required its the part
> of zookeeper
> ]]
>
> or can someone help me to fix it ?
>
> importaant thing
>
> topology using drpc and i tried to submit another topoogies worked well
> but topology with drpc got this error
>
>
> the project i'm trying to submit it here
> https://github.com/mvogiatzis/first-stories-twitter
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
i checked it already and write the result i got here in seperate message ,
what i got is the topology i submitted it ! i can't see any other process ,
can you please check the message again to see if i'm right or not ?
On Mon, Jan 4, 2016 at 5:15 PM, Derek Dagit <de...@yahoo-inc.com.invalid>
wrote:
> > org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
>
>
> If you see this, you can use a tool like lsof to find out what was
> listening on the port.
>
> `lsof -i :6703` as root user.
>
>
> Most likely, because it was port 6703, it was another worker JVM that was
> still running.
>
>
>
> --
> Derek
>
>
>
>
> ________________________________
> From: researcher cs <pr...@gmail.com>
> To: dev@storm.apache.org; user@storm.apache.org; nathan@nathanmarz.com;
> Michael Vogiatzis <mi...@micvog.com>; Michael Vogiatzis <
> michaelvogiatzis@gmail.com>
> Sent: Sunday, January 3, 2016 6:09 PM
> Subject: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
>
>
> I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
> now i ran my topology in local mode with maven commands and worked well
> BUT when i submitted it i got
>
> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
> at
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
> ~[netty-3.6.3.Final.jar:na]
> at backtype.storm.messaging.netty.Server.<init>(Server.java:56)
> ~[storm-netty-0.9.0.1.jar:na]
> at backtype.storm.messaging.netty.Context.bind(Context.java:27)
> ~[storm-netty-0.9.0.1.jar:na]
> at
> backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20)
> ~[storm-core-0.9.0.1.jar:na]
> at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401)
> ~[storm-core-0.9.0.1.jar:na]
> at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
> at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
> at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139)
> ~[na:1.6.0_37]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
> ~[na:1.6.0_37]
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
> ~[netty-3.6.3.Final.jar:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> ~[na:1.6.0_37]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> ~[na:1.6.0_37]
> ... 1 common frames omitted
> 2016-01-04 01:52:07 b.s.util [INFO] Halting process:
>
>
>
> the topology using one worker for one supervisor i'm trying to run or
> submit it first in single machine
>
>
> so my only storm.yaml is
>
> storm.zookeeper.servers:
>
> - "192.168.x.x"
>
> nimbus.host: "192.168.x.x"
> storm.local.dir: "/var/storm"
> supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
> nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
> worker.childopts: "-Djava.net.preferIPv4Stack=true"
> drpc.servers:
>
> - "192.168.x.x"
>
> storm.messaging.transport: "backtype.storm.messaging.netty.Context"
> storm.messaging.netty.server_worker_threads: 1
> storm.messaging.netty.client_worker_threads: 1
> storm.messaging.netty.buffer_size: 5242880
> storm.messaging.netty.max_retries: 100
> storm.messaging.netty.max_wait_ms: 1000
> storm.messaging.netty.min_wait_ms: 100
>
>
> zoo.cfg is
>
> tickTime=2000
> initLimit=10
> syncLimit=5
> dataDir=/var/zookeeper
> clientPort=2181
>
>
> i tried to use localhost but got same error then tried to use my ip address
> i searched to fix it more but got this solution
> can someone illustrate it beacuse i didn't get it well
>
> [[
>
> It turned out that my logback/cluster.xml configuration had a
> SocketAppender that didn't have a listener on the remote host. Having an
> appender defined in configuration file, even if it is not set up to receive
> any log messages, will cause Storm to block and the above error message.its
> due to zookeeper you have add curator separetly not required its the part
> of zookeeper
> ]]
>
>
> or can someone help me to fix it ?
>
>
> importaant thing
>
>
> topology using drpc and i tried to submit another topoogies worked well
> but topology with drpc got this error
>
>
> the project i'm trying to submit it here
> https://github.com/mvogiatzis/first-stories-twitter
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by Jean-Sebastien Vachon <je...@wantedanalytics.com>.
0.0.0.0:6703 simply means that the server will accept connections from any network interface.
If your machine has multiple NIC or Ips, you can restrict the Ip where from which it will accept connections. In your case, it will accept connection on any IP.
To contact your server you still have to use a real IP adress such as 127.0.0.1:6703 or 192.168.0.3:6703
You can run the ifconfig command to see all the IPs available on your server.
________________________________________
From: Derek Dagit <de...@yahoo-inc.com>
Sent: Wednesday, January 6, 2016 9:43 AM
To: researcher cs
Cc: user@storm.apache.org
Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
> sorry what did you mean by cluster admin here ?
That's you. :)
--
Derek
________________________________
From: researcher cs <pr...@gmail.com>
To: user@storm.apache.org; Derek Dagit <de...@yahoo-inc.com>
Sent: Tuesday, January 5, 2016 4:56 PM
Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
@Derek
sorry what did you mean by cluster admin here ?
On Tue, Jan 5, 2016 at 6:06 PM, Derek Dagit <de...@yahoo-inc.com> wrote:
0.0.0.0 can be thought of as a special address for the localhost.
>
>The error message means that port 6703 was already taken by another process when this process tried to bind it.
>
>
>The error happened because the supervisor had already launched a worker on port 6703, and while it was running, the cluster admin tried to manually launch the worker from the command line.
>
>This does not normally happen, because we normally rely on the supervisor to launch workers.
>--
>Derek
>
>
>
>
>________________________________
>From: researcher cs <pr...@gmail.com>
>To: user@storm.apache.org; Annabel Melongo <me...@yahoo.com>
>Sent: Monday, January 4, 2016 7:14 PM
>Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
>
>
>
>Sorry i didn't get where is the problem localhost ip is 127.0.0.1 in /etc/hosts file system not 0.0.0.0 ?
>
>
>
>On Tue, Jan 5, 2016 at 2:59 AM, Annabel Melongo <me...@yahoo.com> wrote:
>
>Matthias,
>>
>>
>>Check with your system administrator the ip of your cluster manager. If the localhost ip, 0.0.0.0, is invalid, then the manager has a different ip.
>>
>>
>>
>>On Monday, January 4, 2016 11:55 AM, Matthias J. Sax <mj...@apache.org> wrote:
>>
>>
>>
>>I doubt it is a port problem.
>>
>>0.0.0.0 is *no* valid IP address. Check your IP configuration.
>>
>>-Matthias
>>
>>On 01/04/2016 04:15 PM, Derek Dagit wrote:
>>>> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>>>
>>>
>>> If you see this, you can use a tool like lsof to find out what was listening on the port.
>>>
>>> `lsof -i :6703` as root user.
>>>
>>>
>>> Most likely, because it was port 6703, it was another worker JVM that was still running.
>>>
>>>
>>>
>>>
>>
>>
>>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by Derek Dagit <de...@yahoo-inc.com>.
> sorry what did you mean by cluster admin here ?
That's you. :)
--
Derek
________________________________
From: researcher cs <pr...@gmail.com>
To: user@storm.apache.org; Derek Dagit <de...@yahoo-inc.com>
Sent: Tuesday, January 5, 2016 4:56 PM
Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
@Derek
sorry what did you mean by cluster admin here ?
On Tue, Jan 5, 2016 at 6:06 PM, Derek Dagit <de...@yahoo-inc.com> wrote:
0.0.0.0 can be thought of as a special address for the localhost.
>
>The error message means that port 6703 was already taken by another process when this process tried to bind it.
>
>
>The error happened because the supervisor had already launched a worker on port 6703, and while it was running, the cluster admin tried to manually launch the worker from the command line.
>
>This does not normally happen, because we normally rely on the supervisor to launch workers.
>--
>Derek
>
>
>
>
>________________________________
>From: researcher cs <pr...@gmail.com>
>To: user@storm.apache.org; Annabel Melongo <me...@yahoo.com>
>Sent: Monday, January 4, 2016 7:14 PM
>Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
>
>
>
>Sorry i didn't get where is the problem localhost ip is 127.0.0.1 in /etc/hosts file system not 0.0.0.0 ?
>
>
>
>On Tue, Jan 5, 2016 at 2:59 AM, Annabel Melongo <me...@yahoo.com> wrote:
>
>Matthias,
>>
>>
>>Check with your system administrator the ip of your cluster manager. If the localhost ip, 0.0.0.0, is invalid, then the manager has a different ip.
>>
>>
>>
>>On Monday, January 4, 2016 11:55 AM, Matthias J. Sax <mj...@apache.org> wrote:
>>
>>
>>
>>I doubt it is a port problem.
>>
>>0.0.0.0 is *no* valid IP address. Check your IP configuration.
>>
>>-Matthias
>>
>>On 01/04/2016 04:15 PM, Derek Dagit wrote:
>>>> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>>>
>>>
>>> If you see this, you can use a tool like lsof to find out what was listening on the port.
>>>
>>> `lsof -i :6703` as root user.
>>>
>>>
>>> Most likely, because it was port 6703, it was another worker JVM that was still running.
>>>
>>>
>>>
>>>
>>
>>
>>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
@Derek
sorry what did you mean by cluster admin here ?
On Tue, Jan 5, 2016 at 6:06 PM, Derek Dagit <de...@yahoo-inc.com> wrote:
> 0.0.0.0 can be thought of as a special address for the localhost.
>
> The error message means that port 6703 was already taken by another
> process when this process tried to bind it.
>
>
> The error happened because the supervisor had already launched a worker on
> port 6703, and while it was running, the cluster admin tried to manually
> launch the worker from the command line.
>
> This does not normally happen, because we normally rely on the supervisor
> to launch workers.
> --
> Derek
>
>
>
>
> ________________________________
> From: researcher cs <pr...@gmail.com>
> To: user@storm.apache.org; Annabel Melongo <me...@yahoo.com>
> Sent: Monday, January 4, 2016 7:14 PM
> Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
>
>
> Sorry i didn't get where is the problem localhost ip is 127.0.0.1 in
> /etc/hosts file system not 0.0.0.0 ?
>
>
>
> On Tue, Jan 5, 2016 at 2:59 AM, Annabel Melongo <me...@yahoo.com>
> wrote:
>
> Matthias,
> >
> >
> >Check with your system administrator the ip of your cluster manager. If
> the localhost ip, 0.0.0.0, is invalid, then the manager has a different ip.
> >
> >
> >
> >On Monday, January 4, 2016 11:55 AM, Matthias J. Sax <mj...@apache.org>
> wrote:
> >
> >
> >
> >I doubt it is a port problem.
> >
> >0.0.0.0 is *no* valid IP address. Check your IP configuration.
> >
> >-Matthias
> >
> >On 01/04/2016 04:15 PM, Derek Dagit wrote:
> >>> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
> >>
> >>
> >> If you see this, you can use a tool like lsof to find out what was
> listening on the port.
> >>
> >> `lsof -i :6703` as root user.
> >>
> >>
> >> Most likely, because it was port 6703, it was another worker JVM that
> was still running.
> >>
> >>
> >>
> >>
> >
> >
> >
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by Derek Dagit <de...@yahoo-inc.com>.
0.0.0.0 can be thought of as a special address for the localhost.
The error message means that port 6703 was already taken by another process when this process tried to bind it.
The error happened because the supervisor had already launched a worker on port 6703, and while it was running, the cluster admin tried to manually launch the worker from the command line.
This does not normally happen, because we normally rely on the supervisor to launch workers.
--
Derek
________________________________
From: researcher cs <pr...@gmail.com>
To: user@storm.apache.org; Annabel Melongo <me...@yahoo.com>
Sent: Monday, January 4, 2016 7:14 PM
Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Sorry i didn't get where is the problem localhost ip is 127.0.0.1 in /etc/hosts file system not 0.0.0.0 ?
On Tue, Jan 5, 2016 at 2:59 AM, Annabel Melongo <me...@yahoo.com> wrote:
Matthias,
>
>
>Check with your system administrator the ip of your cluster manager. If the localhost ip, 0.0.0.0, is invalid, then the manager has a different ip.
>
>
>
>On Monday, January 4, 2016 11:55 AM, Matthias J. Sax <mj...@apache.org> wrote:
>
>
>
>I doubt it is a port problem.
>
>0.0.0.0 is *no* valid IP address. Check your IP configuration.
>
>-Matthias
>
>On 01/04/2016 04:15 PM, Derek Dagit wrote:
>>> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>>
>>
>> If you see this, you can use a tool like lsof to find out what was listening on the port.
>>
>> `lsof -i :6703` as root user.
>>
>>
>> Most likely, because it was port 6703, it was another worker JVM that was still running.
>>
>>
>>
>>
>
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
Sorry i didn't get where is the problem localhost ip is 127.0.0.1 in
/etc/hosts file system not 0.0.0.0 ?
On Tue, Jan 5, 2016 at 2:59 AM, Annabel Melongo <me...@yahoo.com>
wrote:
> Matthias,
>
> Check with your system administrator the ip of your cluster manager. If
> the localhost ip, 0.0.0.0, is invalid, then the manager has a different ip.
>
>
> On Monday, January 4, 2016 11:55 AM, Matthias J. Sax <mj...@apache.org>
> wrote:
>
>
> I doubt it is a port problem.
>
> 0.0.0.0 is *no* valid IP address. Check your IP configuration.
>
> -Matthias
>
> On 01/04/2016 04:15 PM, Derek Dagit wrote:
> >> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
> >
> >
> > If you see this, you can use a tool like lsof to find out what was
> listening on the port.
> >
> > `lsof -i :6703` as root user.
> >
> >
> > Most likely, because it was port 6703, it was another worker JVM that
> was still running.
> >
> >
> >
> >
>
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by Annabel Melongo <me...@yahoo.com>.
Matthias,
Check with your system administrator the ip of your cluster manager. If the localhost ip, 0.0.0.0, is invalid, then the manager has a different ip.
On Monday, January 4, 2016 11:55 AM, Matthias J. Sax <mj...@apache.org> wrote:
I doubt it is a port problem.
0.0.0.0 is *no* valid IP address. Check your IP configuration.
-Matthias
On 01/04/2016 04:15 PM, Derek Dagit wrote:
>> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
>
> If you see this, you can use a tool like lsof to find out what was listening on the port.
>
> `lsof -i :6703` as root user.
>
>
> Most likely, because it was port 6703, it was another worker JVM that was still running.
>
>
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
i asked more about this zeros in ip but networking fourms told that is
ususal result not error
On Mon, Jan 4, 2016 at 6:54 PM, Matthias J. Sax <mj...@apache.org> wrote:
> I doubt it is a port problem.
>
> 0.0.0.0 is *no* valid IP address. Check your IP configuration.
>
> -Matthias
>
> On 01/04/2016 04:15 PM, Derek Dagit wrote:
> >> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
> >
> >
> > If you see this, you can use a tool like lsof to find out what was
> listening on the port.
> >
> > `lsof -i :6703` as root user.
> >
> >
> > Most likely, because it was port 6703, it was another worker JVM that
> was still running.
> >
> >
> >
> >
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
- just want to make sure form this topology here in attache files for logs
can you please see if there is something wrong , i checked it but as i
thought it's normal but in the supervisor log i noticed that it still
hasn't start so i checked the command that launch worker and supervisor so
i got the error in binding port 6703
- another point : after submitted topology , emitted and transferred
columns are zeros but after i clicked show system stats got numbers in
emitted column but transefered column is zeros !
should emitted and transferred columns have numbers before click show
system stats button or this the right way to monitor the topology ?
-why metrices and access log files are empty ?
Thanks for your time and help .
On Mon, Jan 4, 2016 at 7:50 PM, Derek Dagit <de...@yahoo-inc.com> wrote:
> 0.0.0.0 is reserved as a source address. It makes sense if this is a
> worker trying to open port 6703, but it could not do it for some reason.
>
>
> --
> Derek
>
>
> ----- Original Message -----
> From: Matthias J. Sax <mj...@apache.org>
> To: user@storm.apache.org
> Sent: Monday, January 4, 2016 10:54 AM
> Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
> I doubt it is a port problem.
>
> 0.0.0.0 is *no* valid IP address. Check your IP configuration.
>
> -Matthias
>
>
> On 01/04/2016 04:15 PM, Derek Dagit wrote:
> >> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
> >
> >
> > If you see this, you can use a tool like lsof to find out what was
> listening on the port.
> >
> > `lsof -i :6703` as root user.
> >
> >
> > Most likely, because it was port 6703, it was another worker JVM that
> was still running.
> >
> >
> >
> >
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by Derek Dagit <de...@yahoo-inc.com>.
0.0.0.0 is reserved as a source address. It makes sense if this is a worker trying to open port 6703, but it could not do it for some reason.
--
Derek
----- Original Message -----
From: Matthias J. Sax <mj...@apache.org>
To: user@storm.apache.org
Sent: Monday, January 4, 2016 10:54 AM
Subject: Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
I doubt it is a port problem.
0.0.0.0 is *no* valid IP address. Check your IP configuration.
-Matthias
On 01/04/2016 04:15 PM, Derek Dagit wrote:
>> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
>
> If you see this, you can use a tool like lsof to find out what was listening on the port.
>
> `lsof -i :6703` as root user.
>
>
> Most likely, because it was port 6703, it was another worker JVM that was still running.
>
>
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by "Matthias J. Sax" <mj...@apache.org>.
I doubt it is a port problem.
0.0.0.0 is *no* valid IP address. Check your IP configuration.
-Matthias
On 01/04/2016 04:15 PM, Derek Dagit wrote:
>> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
>
>
> If you see this, you can use a tool like lsof to find out what was listening on the port.
>
> `lsof -i :6703` as root user.
>
>
> Most likely, because it was port 6703, it was another worker JVM that was still running.
>
>
>
>
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by Derek Dagit <de...@yahoo-inc.com>.
> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
If you see this, you can use a tool like lsof to find out what was listening on the port.
`lsof -i :6703` as root user.
Most likely, because it was port 6703, it was another worker JVM that was still running.
--
Derek
________________________________
From: researcher cs <pr...@gmail.com>
To: dev@storm.apache.org; user@storm.apache.org; nathan@nathanmarz.com; Michael Vogiatzis <mi...@micvog.com>; Michael Vogiatzis <mi...@gmail.com>
Sent: Sunday, January 3, 2016 6:09 PM
Subject: Failed to bind to: 0.0.0.0/0.0.0.0:6703
I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
now i ran my topology in local mode with maven commands and worked well
BUT when i submitted it i got
org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272) ~[netty-3.6.3.Final.jar:na]
at backtype.storm.messaging.netty.Server.<init>(Server.java:56) ~[storm-netty-0.9.0.1.jar:na]
at backtype.storm.messaging.netty.Context.bind(Context.java:27) ~[storm-netty-0.9.0.1.jar:na]
at backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20) ~[storm-core-0.9.0.1.jar:na]
at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401) ~[storm-core-0.9.0.1.jar:na]
at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139) ~[na:1.6.0_37]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77) ~[na:1.6.0_37]
at org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193) ~[netty-3.6.3.Final.jar:na]
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366) ~[netty-3.6.3.Final.jar:na]
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290) ~[netty-3.6.3.Final.jar:na]
at org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42) ~[netty-3.6.3.Final.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) ~[na:1.6.0_37]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ~[na:1.6.0_37]
... 1 common frames omitted
2016-01-04 01:52:07 b.s.util [INFO] Halting process:
the topology using one worker for one supervisor i'm trying to run or submit it first in single machine
so my only storm.yaml is
storm.zookeeper.servers:
- "192.168.x.x"
nimbus.host: "192.168.x.x"
storm.local.dir: "/var/storm"
supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
worker.childopts: "-Djava.net.preferIPv4Stack=true"
drpc.servers:
- "192.168.x.x"
storm.messaging.transport: "backtype.storm.messaging.netty.Context"
storm.messaging.netty.server_worker_threads: 1
storm.messaging.netty.client_worker_threads: 1
storm.messaging.netty.buffer_size: 5242880
storm.messaging.netty.max_retries: 100
storm.messaging.netty.max_wait_ms: 1000
storm.messaging.netty.min_wait_ms: 100
zoo.cfg is
tickTime=2000
initLimit=10
syncLimit=5
dataDir=/var/zookeeper
clientPort=2181
i tried to use localhost but got same error then tried to use my ip address
i searched to fix it more but got this solution
can someone illustrate it beacuse i didn't get it well
[[
It turned out that my logback/cluster.xml configuration had a SocketAppender that didn't have a listener on the remote host. Having an appender defined in configuration file, even if it is not set up to receive any log messages, will cause Storm to block and the above error message.its due to zookeeper you have add curator separetly not required its the part of zookeeper
]]
or can someone help me to fix it ?
importaant thing
topology using drpc and i tried to submit another topoogies worked well but topology with drpc got this error
the project i'm trying to submit it here
https://github.com/mvogiatzis/first-stories-twitter
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by Derek Dagit <de...@yahoo-inc.com.INVALID>.
> org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
If you see this, you can use a tool like lsof to find out what was listening on the port.
`lsof -i :6703` as root user.
Most likely, because it was port 6703, it was another worker JVM that was still running.
--
Derek
________________________________
From: researcher cs <pr...@gmail.com>
To: dev@storm.apache.org; user@storm.apache.org; nathan@nathanmarz.com; Michael Vogiatzis <mi...@micvog.com>; Michael Vogiatzis <mi...@gmail.com>
Sent: Sunday, January 3, 2016 6:09 PM
Subject: Failed to bind to: 0.0.0.0/0.0.0.0:6703
I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
now i ran my topology in local mode with maven commands and worked well
BUT when i submitted it i got
org.jboss.netty.channel.ChannelException: Failed to bind to: 0.0.0.0/0.0.0.0:6703
at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272) ~[netty-3.6.3.Final.jar:na]
at backtype.storm.messaging.netty.Server.<init>(Server.java:56) ~[storm-netty-0.9.0.1.jar:na]
at backtype.storm.messaging.netty.Context.bind(Context.java:27) ~[storm-netty-0.9.0.1.jar:na]
at backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20) ~[storm-core-0.9.0.1.jar:na]
at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401) ~[storm-core-0.9.0.1.jar:na]
at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139) ~[na:1.6.0_37]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77) ~[na:1.6.0_37]
at org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193) ~[netty-3.6.3.Final.jar:na]
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366) ~[netty-3.6.3.Final.jar:na]
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290) ~[netty-3.6.3.Final.jar:na]
at org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42) ~[netty-3.6.3.Final.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) ~[na:1.6.0_37]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ~[na:1.6.0_37]
... 1 common frames omitted
2016-01-04 01:52:07 b.s.util [INFO] Halting process:
the topology using one worker for one supervisor i'm trying to run or submit it first in single machine
so my only storm.yaml is
storm.zookeeper.servers:
- "192.168.x.x"
nimbus.host: "192.168.x.x"
storm.local.dir: "/var/storm"
supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
worker.childopts: "-Djava.net.preferIPv4Stack=true"
drpc.servers:
- "192.168.x.x"
storm.messaging.transport: "backtype.storm.messaging.netty.Context"
storm.messaging.netty.server_worker_threads: 1
storm.messaging.netty.client_worker_threads: 1
storm.messaging.netty.buffer_size: 5242880
storm.messaging.netty.max_retries: 100
storm.messaging.netty.max_wait_ms: 1000
storm.messaging.netty.min_wait_ms: 100
zoo.cfg is
tickTime=2000
initLimit=10
syncLimit=5
dataDir=/var/zookeeper
clientPort=2181
i tried to use localhost but got same error then tried to use my ip address
i searched to fix it more but got this solution
can someone illustrate it beacuse i didn't get it well
[[
It turned out that my logback/cluster.xml configuration had a SocketAppender that didn't have a listener on the remote host. Having an appender defined in configuration file, even if it is not set up to receive any log messages, will cause Storm to block and the above error message.its due to zookeeper you have add curator separetly not required its the part of zookeeper
]]
or can someone help me to fix it ?
importaant thing
topology using drpc and i tried to submit another topoogies worked well but topology with drpc got this error
the project i'm trying to submit it here
https://github.com/mvogiatzis/first-stories-twitter
Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Posted by researcher cs <pr...@gmail.com>.
sorry it's not my toplogy i refered to the coder hope he can help in this
issue
On Mon, Jan 4, 2016 at 2:09 AM, researcher cs <pr...@gmail.com>
wrote:
> I'm using storm -0.9.0.1 with zookeeper -3.4.6 ubuntu 14.04
> now i ran my topology in local mode with maven commands and worked well
> BUT when i submitted it i got
>
> org.jboss.netty.channel.ChannelException: Failed to bind to:
> 0.0.0.0/0.0.0.0:6703
> at
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
> ~[netty-3.6.3.Final.jar:na]
> at backtype.storm.messaging.netty.Server.<init>(Server.java:56)
> ~[storm-netty-0.9.0.1.jar:na]
> at backtype.storm.messaging.netty.Context.bind(Context.java:27)
> ~[storm-netty-0.9.0.1.jar:na]
> at
> backtype.storm.messaging.loader$launch_receive_thread_BANG_$fn__2984.invoke(loader.clj:20)
> ~[storm-core-0.9.0.1.jar:na]
> at backtype.storm.util$async_loop$fn__444.invoke(util.clj:401)
> ~[storm-core-0.9.0.1.jar:na]
> at clojure.lang.AFn.run(AFn.java:24) ~[clojure-1.4.0.jar:na]
> at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_37]
> Caused by: java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind0(Native Method) ~[na:1.6.0_37]
> at sun.nio.ch.Net.bind(Net.java:174) ~[na:1.6.0_37]
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:139)
> ~[na:1.6.0_37]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
> ~[na:1.6.0_37]
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290)
> ~[netty-3.6.3.Final.jar:na]
> at
> org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
> ~[netty-3.6.3.Final.jar:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> ~[na:1.6.0_37]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> ~[na:1.6.0_37]
> ... 1 common frames omitted
> 2016-01-04 01:52:07 b.s.util [INFO] Halting process:
>
> the topology using one worker for one supervisor i'm trying to run or
> submit it first in single machine
>
> so my only storm.yaml is
>
> storm.zookeeper.servers:
> - "192.168.x.x"
> nimbus.host: "192.168.x.x"
> storm.local.dir: "/var/storm"
> supervisor.childopts: "-Djava.net.preferIPv4Stack=true"
> nimbus.childopts: "-Djava.net.preferIPv4Stack=true"
> worker.childopts: "-Djava.net.preferIPv4Stack=true"
> drpc.servers:
> - "192.168.x.x"
> storm.messaging.transport: "backtype.storm.messaging.netty.Context"
> storm.messaging.netty.server_worker_threads: 1
> storm.messaging.netty.client_worker_threads: 1
> storm.messaging.netty.buffer_size: 5242880
> storm.messaging.netty.max_retries: 100
> storm.messaging.netty.max_wait_ms: 1000
> storm.messaging.netty.min_wait_ms: 100
>
> zoo.cfg is
>
> tickTime=2000
> initLimit=10
> syncLimit=5
> dataDir=/var/zookeeper
> clientPort=2181
>
> i tried to use localhost but got same error then tried to use my ip address
> i searched to fix it more but got this solution
> can someone illustrate it beacuse i didn't get it well
>
> [[
> It turned out that my logback/cluster.xml configuration had a
> SocketAppender that didn't have a listener on the remote host. Having an
> appender defined in configuration file, even if it is not set up to receive
> any log messages, will cause Storm to block and the above error message.its
> due to zookeeper you have add curator separetly not required its the part
> of zookeeper
> ]]
>
> or can someone help me to fix it ?
>
> importaant thing
>
> topology using drpc and i tried to submit another topoogies worked well
> but topology with drpc got this error
>
>
> the project i'm trying to submit it here
> https://github.com/mvogiatzis/first-stories-twitter
>