You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Naga Vij <nv...@gmail.com> on 2014/08/26 08:15:02 UTC
supervisor not listening on port 6700?
Hello,
I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box) on
these two systems -
> cat /etc/redhat-release
CentOS release 6.3 (Final)
and
> sw_vers
ProductName: Mac OS X
ProductVersion: 10.9.2
BuildVersion: 13C64
After starting supervisor, I notice it is not listening on the configured
port (6700) -
> nc -zv localhost 6700
nc: connectx to localhost port 6700 (tcp) failed: Connection refused
When I submit topology, I see this scrolling message in the terminal window
for supervisor -
23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
I don't see any worker id in UI. No error in logs.
Any idea what could be happening?
Thanks in advance.
Naga
Suggestions
Posted by Sridhar G <Sr...@microland.com>.
Hi All,
Any suggestions on Repetitive Count Algorithm’s for implementation.
Regards,
Sridhar
Believe in the impossible and remove the improbable
The information contained in this transmission may contain privileged and confidential information of Microland Limited, including information protected by privacy laws. It is intended only for the use of Microland Limited. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
I have filed https://issues.apache.org/jira/browse/STORM-478
Taylor - Please assign it to me, and I will provide patch.
On Wed, Aug 27, 2014 at 9:10 AM, Harsha <st...@harsha.io> wrote:
> Looks like a build/release issue with storm 0.9.2. we might need to
> update the package there shouldn't be two versions of netty in lib dir.
> Can you please file a JIRA for this.
> Thanks,
> Harsha
>
>
> On Wed, Aug 27, 2014, at 08:54 AM, Naga Vij wrote:
>
> Got it ; Thank you!
>
> BTW, I have worked around this issue thus ...
>
> > Noticed two netty jars in lib dir - netty-3.2.2.Final.jar and
> netty-3.6.3.Final.jar
> > Eliminated both of them, and placed netty-3.9.4.Final.jar
>
> The core & worker processes are steady now.
>
>
>
>
> On Wed, Aug 27, 2014 at 8:08 AM, Harsha <st...@harsha.io> wrote:
>
>
> You need to do these following steps
>
> git clone https://github.com/apache/incubator-storm.git
>
> git checkout v0.9.2-incubating -b 0.9.2-incubating
>
>
> On Wed, Aug 27, 2014, at 08:03 AM, Naga Vij wrote:
>
> Is the Git Url right? I just tried and got ...
>
> > git clone
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
> Cloning into 'v0.9.2-incubating'...
> fatal: repository '
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/' not
> found
>
>
> On Wed, Aug 27, 2014 at 7:41 AM, Harsha <st...@harsha.io> wrote:
>
>
>
> Storm 0.9.2 is tag under github repo
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating.
> -Harsha
>
> On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
>
> Does anyone know what the git branch name is for 0.9.2 ?
>
>
> On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij <nv...@gmail.com> wrote:
>
> When it gets into `still hasn't started` state, I have noticed this in UI -
>
> java.lang.RuntimeException: java.net.ConnectException: Connection refused
> at
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128)
> at backtype.storm.utils.DisruptorQueue.
>
> and am wondering how to overcome this.
>
>
> On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I left supervisor running with the `still hasn't started` state on one
> window, and tried starting the worker on another window. That triggered an
> attempt to start another worker (with another distinct id) in the first
> window (the supervisor window) which in turn went into the `still hasn't
> started` state.
>
>
> On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> I am even having the almost same versions of storm (0.9.1) and kafka. And
> my topologies were also facing the same issue. When I ran the worker
> command directly, I came to know that somehow hostname was wrong in the
> configuration passed to the workers. So, I fixed that in storm config and
> my topology worked after that. However, now again it has stuck with same
> "still hasn't started" error message and in my case now the error in
> running the worker command is "Address already in use" for supervisor port.
>
> So, what is the error when you directly run the worker command?
>
>
> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I fail to understand why that should happen, as testing with LocalCluster
> goes through fine.
>
> I did a clean fresh start to figure out what could be happening, and here
> are my observations -
>
> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's
> tmp dir}
> - used local pseudo cluster on my mac
> - nimbus process started fine
> - supervisor process started fine
> - ensured toplogy works fine with (the embedded) LocalCluster
> - topology was then submitted to local pseudo cluster on my mac ; that's
> when I see ``still hasn't started`` messages in supervisor terminal
> window
>
> When submitting topology to local pseudo cluster, had to add jars to
> overcome these ...
>
> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
> Caused by: java.lang.ClassNotFoundException: scala.Product
>
> Above were overcome by adding these to lib dir -
>
> storm-kafka-0.9.2-incubating.jar
> kafka_2.10-0.8.1.1.jar
> scala-library-2.10.1.jar
>
> I have tried the command in log as well ; hasn't helped.
>
> What am I missing?
>
>
> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>
> This is the clue. One of your topology is failing to start. You must see
> the worker command before these logs in the same log file. Just try to run
> those directly on console and it would show the exact error.
>
>
> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>
> Hello,
>
> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box) on
> these two systems -
>
> > cat /etc/redhat-release
> CentOS release 6.3 (Final)
>
> and
>
> > sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.9.2
> BuildVersion: 13C64
>
> After starting supervisor, I notice it is not listening on the
> configured port (6700) -
>
> > nc -zv localhost 6700
> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>
> When I submit topology, I see this scrolling message in the terminal
> window for supervisor -
>
> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>
> I don't see any worker id in UI. No error in logs.
>
> Any idea what could be happening?
>
> Thanks in advance.
>
> Naga
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
The released package is the one having issues. You can assign JIRA to me,
and I will provide patch. My JIRA username is nagab
On Wed, Aug 27, 2014 at 10:39 AM, Harsha <st...@harsha.io> wrote:
> Taylor,
> I noticed its not there in the master but what about the released
> package. If users are installing the apache released package they might
> face this issue. Its has two netty jars in the lib dir.
> Thanks,
> Harsha
>
>
>
> On Wed, Aug 27, 2014, at 10:36 AM, P. Taylor Goetz wrote:
>
> This has been resolved in the master branch.
>
> -Taylor
>
> On Aug 27, 2014, at 12:10 PM, Harsha <st...@harsha.io> wrote:
>
>
> Looks like a build/release issue with storm 0.9.2. we might need to update
> the package there shouldn't be two versions of netty in lib dir.
> Can you please file a JIRA for this.
> Thanks,
> Harsha
>
>
> On Wed, Aug 27, 2014, at 08:54 AM, Naga Vij wrote:
>
> Got it ; Thank you!
>
> BTW, I have worked around this issue thus ...
>
> > Noticed two netty jars in lib dir - netty-3.2.2.Final.jar and
> netty-3.6.3.Final.jar
> > Eliminated both of them, and placed netty-3.9.4.Final.jar
>
> The core & worker processes are steady now.
>
>
>
>
> On Wed, Aug 27, 2014 at 8:08 AM, Harsha <st...@harsha.io> wrote:
>
>
> You need to do these following steps
>
> git clone https://github.com/apache/incubator-storm.git
>
> git checkout v0.9.2-incubating -b 0.9.2-incubating
>
>
> On Wed, Aug 27, 2014, at 08:03 AM, Naga Vij wrote:
>
> Is the Git Url right? I just tried and got ...
>
> > git clone
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
> Cloning into 'v0.9.2-incubating'...
> fatal: repository '
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/' not
> found
>
>
> On Wed, Aug 27, 2014 at 7:41 AM, Harsha <st...@harsha.io> wrote:
>
>
>
> Storm 0.9.2 is tag under github repo
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating.
> -Harsha
>
> On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
>
> Does anyone know what the git branch name is for 0.9.2 ?
>
>
> On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij <nv...@gmail.com> wrote:
>
> When it gets into `still hasn't started` state, I have noticed this in UI -
>
> java.lang.RuntimeException: java.net.ConnectException: Connection refused
> at
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128)
> at backtype.storm.utils.DisruptorQueue.
>
> and am wondering how to overcome this.
>
>
> On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I left supervisor running with the `still hasn't started` state on one
> window, and tried starting the worker on another window. That triggered an
> attempt to start another worker (with another distinct id) in the first
> window (the supervisor window) which in turn went into the `still hasn't
> started` state.
>
>
> On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> I am even having the almost same versions of storm (0.9.1) and kafka. And
> my topologies were also facing the same issue. When I ran the worker
> command directly, I came to know that somehow hostname was wrong in the
> configuration passed to the workers. So, I fixed that in storm config and
> my topology worked after that. However, now again it has stuck with same
> "still hasn't started" error message and in my case now the error in
> running the worker command is "Address already in use" for supervisor port.
>
> So, what is the error when you directly run the worker command?
>
>
> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I fail to understand why that should happen, as testing with LocalCluster
> goes through fine.
>
> I did a clean fresh start to figure out what could be happening, and here
> are my observations -
>
> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's
> tmp dir}
> - used local pseudo cluster on my mac
> - nimbus process started fine
> - supervisor process started fine
> - ensured toplogy works fine with (the embedded) LocalCluster
> - topology was then submitted to local pseudo cluster on my mac ; that's
> when I see ``still hasn't started`` messages in supervisor terminal
> window
>
> When submitting topology to local pseudo cluster, had to add jars to
> overcome these ...
>
> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
> Caused by: java.lang.ClassNotFoundException: scala.Product
>
> Above were overcome by adding these to lib dir -
>
> storm-kafka-0.9.2-incubating.jar
> kafka_2.10-0.8.1.1.jar
> scala-library-2.10.1.jar
>
> I have tried the command in log as well ; hasn't helped.
>
> What am I missing?
>
>
> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>
> This is the clue. One of your topology is failing to start. You must see
> the worker command before these logs in the same log file. Just try to run
> those directly on console and it would show the exact error.
>
>
> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>
> Hello,
>
> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box) on
> these two systems -
>
> > cat /etc/redhat-release
> CentOS release 6.3 (Final)
>
> and
>
> > sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.9.2
> BuildVersion: 13C64
>
> After starting supervisor, I notice it is not listening on the
> configured port (6700) -
>
> > nc -zv localhost 6700
> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>
> When I submit topology, I see this scrolling message in the terminal
> window for supervisor -
>
> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>
> I don't see any worker id in UI. No error in logs.
>
> Any idea what could be happening?
>
> Thanks in advance.
>
> Naga
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Re: supervisor not listening on port 6700?
Posted by Harsha <st...@harsha.io>.
Taylor,
I noticed its not there in the master but what about the
released package. If users are installing the apache released
package they might face this issue. Its has two netty jars in
the lib dir.
Thanks,
Harsha
On Wed, Aug 27, 2014, at 10:36 AM, P. Taylor Goetz wrote:
This has been resolved in the master branch.
-Taylor
On Aug 27, 2014, at 12:10 PM, Harsha <[1...@harsha.io>
wrote:
Looks like a build/release issue with storm 0.9.2. we might
need to update the package there shouldn't be two versions of
netty in lib dir.
Can you please file a JIRA for this.
Thanks,
Harsha
On Wed, Aug 27, 2014, at 08:54 AM, Naga Vij wrote:
Got it ; Thank you!
BTW, I have worked around this issue thus ...
> Noticed two netty jars in lib dir - netty-3.2.2.Final.jar and
netty-3.6.3.Final.jar
> Eliminated both of them, and placed netty-3.9.4.Final.jar
The core & worker processes are steady now.
On Wed, Aug 27, 2014 at 8:08 AM, Harsha <[2...@harsha.io>
wrote:
You need to do these following steps
git clone [3]https://github.com/apache/incubator-storm.git
git checkout v0.9.2-incubating -b 0.9.2-incubating
On Wed, Aug 27, 2014, at 08:03 AM, Naga Vij wrote:
Is the Git Url right? I just tried and got ...
> git clone
[4]https://github.com/apache/incubator-storm/tree/v0.9.2-incuba
ting
Cloning into 'v0.9.2-incubating'...
fatal: repository
'[5]https://github.com/apache/incubator-storm/tree/v0.9.2-incub
ating/' not found
On Wed, Aug 27, 2014 at 7:41 AM, Harsha <[6...@harsha.io>
wrote:
Storm 0.9.2 is tag under github
repo [7]https://github.com/apache/incubator-storm/tree/v0.9.2-i
ncubating.
-Harsha
On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
Does anyone know what the git branch name is for 0.9.2 ?
On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij
<[8...@gmail.com> wrote:
When it gets into `still hasn't started` state, I have noticed
this in UI -
java.lang.RuntimeException: java.net.ConnectException:
Connection refused at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(Disrup
torQueue.java:128) at backtype.storm.utils.DisruptorQueue.
and am wondering how to overcome this.
On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij
<[9...@gmail.com> wrote:
I left supervisor running with the `still hasn't started` state
on one window, and tried starting the worker on another
window. That triggered an attempt to start another worker
(with another distinct id) in the first window (the supervisor
window) which in turn went into the `still hasn't started`
state.
On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal
<[1...@infoobjects.com> wrote:
I am even having the almost same versions of storm (0.9.1) and
kafka. And my topologies were also facing the same issue. When
I ran the worker command directly, I came to know that somehow
hostname was wrong in the configuration passed to the workers.
So, I fixed that in storm config and my topology worked after
that. However, now again it has stuck with same "still hasn't
started" error message and in my case now the error in running
the worker command is "Address already in use" for supervisor
port.
So, what is the error when you directly run the worker command?
On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij
<[1...@gmail.com> wrote:
I fail to understand why that should happen, as testing with
LocalCluster goes through fine.
I did a clean fresh start to figure out what could be
happening, and here are my observations -
- fresh clean start: cleanup in zk (rmr /storm), and /bin/rm
-fr {storm's tmp dir}
- used local pseudo cluster on my mac
- nimbus process started fine
- supervisor process started fine
- ensured toplogy works fine with (the embedded) LocalCluster
- topology was then submitted to local pseudo cluster on my mac
; that's when I see ``still hasn't started`` messages in
supervisor terminal window
When submitting topology to local pseudo cluster, had to add
jars to overcome these ...
Caused by: java.lang.ClassNotFoundException:
storm.kafka.BrokerHosts
Caused by: java.lang.ClassNotFoundException:
kafka.api.OffsetRequest
Caused by: java.lang.ClassNotFoundException: scala.Product
Above were overcome by adding these to lib dir -
storm-kafka-0.9.2-incubating.jar
kafka_2.10-0.8.1.1.jar
scala-library-2.10.1.jar
I have tried the command in log as well ; hasn't helped.
What am I missing?
On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal
<[1...@infoobjects.com> wrote:
>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
This is the clue. One of your topology is failing to start. You
must see the worker command before these logs in the same log
file. Just try to run those directly on console and it would
show the exact error.
On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij
<[1...@gmail.com> wrote:
Hello,
I am trying out Storm 0.9.2-incubating pseudo cluster (on just
one box) on these two systems -
> cat /etc/redhat-release
CentOS release 6.3 (Final)
and
> sw_vers
ProductName: Mac OS X
ProductVersion: 10.9.2
BuildVersion: 13C64
After starting supervisor, I notice it is not listening on the
configured port (6700) -
> nc -zv localhost 6700
nc: connectx to localhost port 6700 (tcp) failed: Connection
refused
When I submit topology, I see this scrolling message in the
terminal window for supervisor -
23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor
- dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
I don't see any worker id in UI. No error in logs.
Any idea what could be happening?
Thanks in advance.
Naga
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[14]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[15]+1 (408) 988-2000 Work
[16]+1 (408) 716-2726 Fax
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[17]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[18]+1 (408) 988-2000 Work
[19]+1 (408) 716-2726 Fax
References
1. mailto:storm@harsha.io
2. mailto:storm@harsha.io
3. https://github.com/apache/incubator-storm.git
4. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
5. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/
6. mailto:storm@harsha.io
7. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
8. mailto:nvbuchu1@gmail.com
9. mailto:nvbuchu1@gmail.com
10. mailto:vikas@infoobjects.com
11. mailto:nvbuchu1@gmail.com
12. mailto:vikas@infoobjects.com
13. mailto:nvbuchu1@gmail.com
14. http://www.infoobjects.com/
15. tel:%2B1%20%28408%29%20988-2000
16. tel:%2B1%20%28408%29%20716-2726
17. http://www.infoobjects.com/
18. tel:%2B1%20%28408%29%20988-2000
19. tel:%2B1%20%28408%29%20716-2726
Re: supervisor not listening on port 6700?
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
This has been resolved in the master branch.
-Taylor
> On Aug 27, 2014, at 12:10 PM, Harsha <st...@harsha.io> wrote:
>
> Looks like a build/release issue with storm 0.9.2. we might need to update the package there shouldn't be two versions of netty in lib dir.
> Can you please file a JIRA for this.
> Thanks,
> Harsha
>
>
>> On Wed, Aug 27, 2014, at 08:54 AM, Naga Vij wrote:
>> Got it ; Thank you!
>>
>> BTW, I have worked around this issue thus ...
>>
>> > Noticed two netty jars in lib dir - netty-3.2.2.Final.jar and netty-3.6.3.Final.jar
>> > Eliminated both of them, and placed netty-3.9.4.Final.jar
>>
>> The core & worker processes are steady now.
>>
>>
>>
>>
>> On Wed, Aug 27, 2014 at 8:08 AM, Harsha <st...@harsha.io> wrote:
>>
>> You need to do these following steps
>> git clone https://github.com/apache/incubator-storm.git
>>
>> git checkout v0.9.2-incubating -b 0.9.2-incubating
>>
>>
>>
>>> On Wed, Aug 27, 2014, at 08:03 AM, Naga Vij wrote:
>>> Is the Git Url right? I just tried and got ...
>>>
>>> > git clone https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
>>> Cloning into 'v0.9.2-incubating'...
>>> fatal: repository 'https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/' not found
>>>
>>>
>>> On Wed, Aug 27, 2014 at 7:41 AM, Harsha <st...@harsha.io> wrote:
>>>
>>>
>>> Storm 0.9.2 is tag under github repo https://github.com/apache/incubator-storm/tree/v0.9.2-incubating.
>>> -Harsha
>>>
>>>> On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
>>>> Does anyone know what the git branch name is for 0.9.2 ?
>>>>
>>>>
>>>> On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij <nv...@gmail.com> wrote:
>>>> When it gets into `still hasn't started` state, I have noticed this in UI -
>>>>
>>>> java.lang.RuntimeException: java.net.ConnectException: Connection refused at backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128) at backtype.storm.utils.DisruptorQueue.
>>>>
>>>> and am wondering how to overcome this.
>>>>
>>>>
>>>> On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij <nv...@gmail.com> wrote:
>>>> I left supervisor running with the `still hasn't started` state on one window, and tried starting the worker on another window. That triggered an attempt to start another worker (with another distinct id) in the first window (the supervisor window) which in turn went into the `still hasn't started` state.
>>>>
>>>>
>>>> On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com> wrote:
>>>> I am even having the almost same versions of storm (0.9.1) and kafka. And my topologies were also facing the same issue. When I ran the worker command directly, I came to know that somehow hostname was wrong in the configuration passed to the workers. So, I fixed that in storm config and my topology worked after that. However, now again it has stuck with same "still hasn't started" error message and in my case now the error in running the worker command is "Address already in use" for supervisor port.
>>>>
>>>> So, what is the error when you directly run the worker command?
>>>>
>>>>
>>>> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>>>> I fail to understand why that should happen, as testing with LocalCluster goes through fine.
>>>>
>>>> I did a clean fresh start to figure out what could be happening, and here are my observations -
>>>>
>>>> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's tmp dir}
>>>> - used local pseudo cluster on my mac
>>>> - nimbus process started fine
>>>> - supervisor process started fine
>>>> - ensured toplogy works fine with (the embedded) LocalCluster
>>>> - topology was then submitted to local pseudo cluster on my mac ; that's when I see ``still hasn't started`` messages in supervisor terminal window
>>>>
>>>> When submitting topology to local pseudo cluster, had to add jars to overcome these ...
>>>>
>>>> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
>>>> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
>>>> Caused by: java.lang.ClassNotFoundException: scala.Product
>>>>
>>>> Above were overcome by adding these to lib dir -
>>>>
>>>> storm-kafka-0.9.2-incubating.jar
>>>> kafka_2.10-0.8.1.1.jar
>>>> scala-library-2.10.1.jar
>>>>
>>>> I have tried the command in log as well ; hasn't helped.
>>>>
>>>> What am I missing?
>>>>
>>>>
>>>> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com> wrote:
>>>> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>>>>
>>>> This is the clue. One of your topology is failing to start. You must see the worker command before these logs in the same log file. Just try to run those directly on console and it would show the exact error.
>>>>
>>>>
>>>> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>>>> Hello,
>>>>
>>>> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box) on these two systems -
>>>>
>>>> > cat /etc/redhat-release
>>>> CentOS release 6.3 (Final)
>>>>
>>>> and
>>>>
>>>> > sw_vers
>>>> ProductName: Mac OS X
>>>> ProductVersion: 10.9.2
>>>> BuildVersion: 13C64
>>>>
>>>> After starting supervisor, I notice it is not listening on the configured port (6700) -
>>>>
>>>> > nc -zv localhost 6700
>>>> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>>>>
>>>> When I submit topology, I see this scrolling message in the terminal window for supervisor -
>>>>
>>>> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor - dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>>>>
>>>> I don't see any worker id in UI. No error in logs.
>>>>
>>>> Any idea what could be happening?
>>>>
>>>> Thanks in advance.
>>>>
>>>> Naga
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Vikas Agarwal
>>>> 91 – 9928301411
>>>>
>>>> InfoObjects, Inc.
>>>> Execution Matters
>>>> http://www.infoobjects.com
>>>> 2041 Mission College Boulevard, #280
>>>> Santa Clara, CA 95054
>>>> +1 (408) 988-2000 Work
>>>> +1 (408) 716-2726 Fax
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Vikas Agarwal
>>>> 91 – 9928301411
>>>>
>>>> InfoObjects, Inc.
>>>> Execution Matters
>>>> http://www.infoobjects.com
>>>> 2041 Mission College Boulevard, #280
>>>> Santa Clara, CA 95054
>>>> +1 (408) 988-2000 Work
>>>> +1 (408) 716-2726 Fax
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
Re: supervisor not listening on port 6700?
Posted by Harsha <st...@harsha.io>.
Looks like a build/release issue with storm 0.9.2. we might
need to update the package there shouldn't be two versions of
netty in lib dir.
Can you please file a JIRA for this.
Thanks,
Harsha
On Wed, Aug 27, 2014, at 08:54 AM, Naga Vij wrote:
Got it ; Thank you!
BTW, I have worked around this issue thus ...
> Noticed two netty jars in lib dir - netty-3.2.2.Final.jar and
netty-3.6.3.Final.jar
> Eliminated both of them, and placed netty-3.9.4.Final.jar
The core & worker processes are steady now.
On Wed, Aug 27, 2014 at 8:08 AM, Harsha <[1...@harsha.io>
wrote:
You need to do these following steps
git clone [2]https://github.com/apache/incubator-storm.git
git checkout v0.9.2-incubating -b 0.9.2-incubating
On Wed, Aug 27, 2014, at 08:03 AM, Naga Vij wrote:
Is the Git Url right? I just tried and got ...
> git clone
[3]https://github.com/apache/incubator-storm/tree/v0.9.2-incuba
ting
Cloning into 'v0.9.2-incubating'...
fatal: repository
'[4]https://github.com/apache/incubator-storm/tree/v0.9.2-incub
ating/' not found
On Wed, Aug 27, 2014 at 7:41 AM, Harsha <[5...@harsha.io>
wrote:
Storm 0.9.2 is tag under github
repo [6]https://github.com/apache/incubator-storm/tree/v0.9.2-i
ncubating.
-Harsha
On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
Does anyone know what the git branch name is for 0.9.2 ?
On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij
<[7...@gmail.com> wrote:
When it gets into `still hasn't started` state, I have noticed
this in UI -
java.lang.RuntimeException: java.net.ConnectException:
Connection refused at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(Disrup
torQueue.java:128) at backtype.storm.utils.DisruptorQueue.
and am wondering how to overcome this.
On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij
<[8...@gmail.com> wrote:
I left supervisor running with the `still hasn't started` state
on one window, and tried starting the worker on another
window. That triggered an attempt to start another worker
(with another distinct id) in the first window (the supervisor
window) which in turn went into the `still hasn't started`
state.
On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal
<[9...@infoobjects.com> wrote:
I am even having the almost same versions of storm (0.9.1) and
kafka. And my topologies were also facing the same issue. When
I ran the worker command directly, I came to know that somehow
hostname was wrong in the configuration passed to the workers.
So, I fixed that in storm config and my topology worked after
that. However, now again it has stuck with same "still hasn't
started" error message and in my case now the error in running
the worker command is "Address already in use" for supervisor
port.
So, what is the error when you directly run the worker command?
On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij
<[1...@gmail.com> wrote:
I fail to understand why that should happen, as testing with
LocalCluster goes through fine.
I did a clean fresh start to figure out what could be
happening, and here are my observations -
- fresh clean start: cleanup in zk (rmr /storm), and /bin/rm
-fr {storm's tmp dir}
- used local pseudo cluster on my mac
- nimbus process started fine
- supervisor process started fine
- ensured toplogy works fine with (the embedded) LocalCluster
- topology was then submitted to local pseudo cluster on my mac
; that's when I see ``still hasn't started`` messages in
supervisor terminal window
When submitting topology to local pseudo cluster, had to add
jars to overcome these ...
Caused by: java.lang.ClassNotFoundException:
storm.kafka.BrokerHosts
Caused by: java.lang.ClassNotFoundException:
kafka.api.OffsetRequest
Caused by: java.lang.ClassNotFoundException: scala.Product
Above were overcome by adding these to lib dir -
storm-kafka-0.9.2-incubating.jar
kafka_2.10-0.8.1.1.jar
scala-library-2.10.1.jar
I have tried the command in log as well ; hasn't helped.
What am I missing?
On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal
<[1...@infoobjects.com> wrote:
>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
This is the clue. One of your topology is failing to start. You
must see the worker command before these logs in the same log
file. Just try to run those directly on console and it would
show the exact error.
On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij
<[1...@gmail.com> wrote:
Hello,
I am trying out Storm 0.9.2-incubating pseudo cluster (on just
one box) on these two systems -
> cat /etc/redhat-release
CentOS release 6.3 (Final)
and
> sw_vers
ProductName: Mac OS X
ProductVersion: 10.9.2
BuildVersion: 13C64
After starting supervisor, I notice it is not listening on the
configured port (6700) -
> nc -zv localhost 6700
nc: connectx to localhost port 6700 (tcp) failed: Connection
refused
When I submit topology, I see this scrolling message in the
terminal window for supervisor -
23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor
- dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
I don't see any worker id in UI. No error in logs.
Any idea what could be happening?
Thanks in advance.
Naga
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[13]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[14]+1 (408) 988-2000 Work
[15]+1 (408) 716-2726 Fax
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[16]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[17]+1 (408) 988-2000 Work
[18]+1 (408) 716-2726 Fax
References
1. mailto:storm@harsha.io
2. https://github.com/apache/incubator-storm.git
3. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
4. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/
5. mailto:storm@harsha.io
6. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
7. mailto:nvbuchu1@gmail.com
8. mailto:nvbuchu1@gmail.com
9. mailto:vikas@infoobjects.com
10. mailto:nvbuchu1@gmail.com
11. mailto:vikas@infoobjects.com
12. mailto:nvbuchu1@gmail.com
13. http://www.infoobjects.com/
14. tel:%2B1%20%28408%29%20988-2000
15. tel:%2B1%20%28408%29%20716-2726
16. http://www.infoobjects.com/
17. tel:%2B1%20%28408%29%20988-2000
18. tel:%2B1%20%28408%29%20716-2726
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
Got it ; Thank you!
BTW, I have worked around this issue thus ...
> Noticed two netty jars in lib dir - netty-3.2.2.Final.jar and
netty-3.6.3.Final.jar
> Eliminated both of them, and placed netty-3.9.4.Final.jar
The core & worker processes are steady now.
On Wed, Aug 27, 2014 at 8:08 AM, Harsha <st...@harsha.io> wrote:
> You need to do these following steps
>
> git clone https://github.com/apache/incubator-storm.git
>
> git checkout v0.9.2-incubating -b 0.9.2-incubating
>
>
> On Wed, Aug 27, 2014, at 08:03 AM, Naga Vij wrote:
>
> Is the Git Url right? I just tried and got ...
>
> > git clone
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
> Cloning into 'v0.9.2-incubating'...
> fatal: repository '
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/' not
> found
>
>
> On Wed, Aug 27, 2014 at 7:41 AM, Harsha <st...@harsha.io> wrote:
>
>
>
> Storm 0.9.2 is tag under github repo
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating.
> -Harsha
>
> On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
>
> Does anyone know what the git branch name is for 0.9.2 ?
>
>
> On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij <nv...@gmail.com> wrote:
>
> When it gets into `still hasn't started` state, I have noticed this in UI -
>
> java.lang.RuntimeException: java.net.ConnectException: Connection refused
> at
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128)
> at backtype.storm.utils.DisruptorQueue.
>
> and am wondering how to overcome this.
>
>
> On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I left supervisor running with the `still hasn't started` state on one
> window, and tried starting the worker on another window. That triggered an
> attempt to start another worker (with another distinct id) in the first
> window (the supervisor window) which in turn went into the `still hasn't
> started` state.
>
>
> On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> I am even having the almost same versions of storm (0.9.1) and kafka. And
> my topologies were also facing the same issue. When I ran the worker
> command directly, I came to know that somehow hostname was wrong in the
> configuration passed to the workers. So, I fixed that in storm config and
> my topology worked after that. However, now again it has stuck with same
> "still hasn't started" error message and in my case now the error in
> running the worker command is "Address already in use" for supervisor port.
>
> So, what is the error when you directly run the worker command?
>
>
> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I fail to understand why that should happen, as testing with LocalCluster
> goes through fine.
>
> I did a clean fresh start to figure out what could be happening, and here
> are my observations -
>
> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's
> tmp dir}
> - used local pseudo cluster on my mac
> - nimbus process started fine
> - supervisor process started fine
> - ensured toplogy works fine with (the embedded) LocalCluster
> - topology was then submitted to local pseudo cluster on my mac ; that's
> when I see ``still hasn't started`` messages in supervisor terminal
> window
>
> When submitting topology to local pseudo cluster, had to add jars to
> overcome these ...
>
> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
> Caused by: java.lang.ClassNotFoundException: scala.Product
>
> Above were overcome by adding these to lib dir -
>
> storm-kafka-0.9.2-incubating.jar
> kafka_2.10-0.8.1.1.jar
> scala-library-2.10.1.jar
>
> I have tried the command in log as well ; hasn't helped.
>
> What am I missing?
>
>
> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>
> This is the clue. One of your topology is failing to start. You must see
> the worker command before these logs in the same log file. Just try to run
> those directly on console and it would show the exact error.
>
>
> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>
> Hello,
>
> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box) on
> these two systems -
>
> > cat /etc/redhat-release
> CentOS release 6.3 (Final)
>
> and
>
> > sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.9.2
> BuildVersion: 13C64
>
> After starting supervisor, I notice it is not listening on the
> configured port (6700) -
>
> > nc -zv localhost 6700
> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>
> When I submit topology, I see this scrolling message in the terminal
> window for supervisor -
>
> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>
> I don't see any worker id in UI. No error in logs.
>
> Any idea what could be happening?
>
> Thanks in advance.
>
> Naga
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Re: supervisor not listening on port 6700?
Posted by Harsha <st...@harsha.io>.
You need to do these following steps
git clone [1]https://github.com/apache/incubator-storm.git
git checkout v0.9.2-incubating -b 0.9.2-incubating
On Wed, Aug 27, 2014, at 08:03 AM, Naga Vij wrote:
Is the Git Url right? I just tried and got ...
> git clone
[2]https://github.com/apache/incubator-storm/tree/v0.9.2-incuba
ting
Cloning into 'v0.9.2-incubating'...
fatal: repository
'[3]https://github.com/apache/incubator-storm/tree/v0.9.2-incub
ating/' not found
On Wed, Aug 27, 2014 at 7:41 AM, Harsha <[4...@harsha.io>
wrote:
Storm 0.9.2 is tag under github
repo [5]https://github.com/apache/incubator-storm/tree/v0.9.2-i
ncubating.
-Harsha
On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
Does anyone know what the git branch name is for 0.9.2 ?
On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij
<[6...@gmail.com> wrote:
When it gets into `still hasn't started` state, I have noticed
this in UI -
java.lang.RuntimeException: java.net.ConnectException:
Connection refused at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(Disrup
torQueue.java:128) at backtype.storm.utils.DisruptorQueue.
and am wondering how to overcome this.
On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij
<[7...@gmail.com> wrote:
I left supervisor running with the `still hasn't started` state
on one window, and tried starting the worker on another
window. That triggered an attempt to start another worker
(with another distinct id) in the first window (the supervisor
window) which in turn went into the `still hasn't started`
state.
On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal
<[8...@infoobjects.com> wrote:
I am even having the almost same versions of storm (0.9.1) and
kafka. And my topologies were also facing the same issue. When
I ran the worker command directly, I came to know that somehow
hostname was wrong in the configuration passed to the workers.
So, I fixed that in storm config and my topology worked after
that. However, now again it has stuck with same "still hasn't
started" error message and in my case now the error in running
the worker command is "Address already in use" for supervisor
port.
So, what is the error when you directly run the worker command?
On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij
<[9...@gmail.com> wrote:
I fail to understand why that should happen, as testing with
LocalCluster goes through fine.
I did a clean fresh start to figure out what could be
happening, and here are my observations -
- fresh clean start: cleanup in zk (rmr /storm), and /bin/rm
-fr {storm's tmp dir}
- used local pseudo cluster on my mac
- nimbus process started fine
- supervisor process started fine
- ensured toplogy works fine with (the embedded) LocalCluster
- topology was then submitted to local pseudo cluster on my mac
; that's when I see ``still hasn't started`` messages in
supervisor terminal window
When submitting topology to local pseudo cluster, had to add
jars to overcome these ...
Caused by: java.lang.ClassNotFoundException:
storm.kafka.BrokerHosts
Caused by: java.lang.ClassNotFoundException:
kafka.api.OffsetRequest
Caused by: java.lang.ClassNotFoundException: scala.Product
Above were overcome by adding these to lib dir -
storm-kafka-0.9.2-incubating.jar
kafka_2.10-0.8.1.1.jar
scala-library-2.10.1.jar
I have tried the command in log as well ; hasn't helped.
What am I missing?
On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal
<[1...@infoobjects.com> wrote:
>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
This is the clue. One of your topology is failing to start. You
must see the worker command before these logs in the same log
file. Just try to run those directly on console and it would
show the exact error.
On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij
<[1...@gmail.com> wrote:
Hello,
I am trying out Storm 0.9.2-incubating pseudo cluster (on just
one box) on these two systems -
> cat /etc/redhat-release
CentOS release 6.3 (Final)
and
> sw_vers
ProductName: Mac OS X
ProductVersion: 10.9.2
BuildVersion: 13C64
After starting supervisor, I notice it is not listening on the
configured port (6700) -
> nc -zv localhost 6700
nc: connectx to localhost port 6700 (tcp) failed: Connection
refused
When I submit topology, I see this scrolling message in the
terminal window for supervisor -
23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor
- dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
I don't see any worker id in UI. No error in logs.
Any idea what could be happening?
Thanks in advance.
Naga
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[12]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[13]+1 (408) 988-2000 Work
[14]+1 (408) 716-2726 Fax
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[15]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[16]+1 (408) 988-2000 Work
[17]+1 (408) 716-2726 Fax
References
1. https://github.com/apache/incubator-storm.git
2. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
3. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/
4. mailto:storm@harsha.io
5. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
6. mailto:nvbuchu1@gmail.com
7. mailto:nvbuchu1@gmail.com
8. mailto:vikas@infoobjects.com
9. mailto:nvbuchu1@gmail.com
10. mailto:vikas@infoobjects.com
11. mailto:nvbuchu1@gmail.com
12. http://www.infoobjects.com/
13. tel:%2B1%20%28408%29%20988-2000
14. tel:%2B1%20%28408%29%20716-2726
15. http://www.infoobjects.com/
16. tel:%2B1%20%28408%29%20988-2000
17. tel:%2B1%20%28408%29%20716-2726
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
Is the Git Url right? I just tried and got ...
> git clone https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
Cloning into 'v0.9.2-incubating'...
fatal: repository '
https://github.com/apache/incubator-storm/tree/v0.9.2-incubating/' not found
On Wed, Aug 27, 2014 at 7:41 AM, Harsha <st...@harsha.io> wrote:
>
> Storm 0.9.2 is tag under github repo
> https://github.com/apache/incubator-storm/tree/v0.9.2-incubating.
> -Harsha
> On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
>
> Does anyone know what the git branch name is for 0.9.2 ?
>
>
> On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij <nv...@gmail.com> wrote:
>
> When it gets into `still hasn't started` state, I have noticed this in UI -
>
> java.lang.RuntimeException: java.net.ConnectException: Connection refused
> at
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128)
> at backtype.storm.utils.DisruptorQueue.
>
> and am wondering how to overcome this.
>
>
> On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I left supervisor running with the `still hasn't started` state on one
> window, and tried starting the worker on another window. That triggered an
> attempt to start another worker (with another distinct id) in the first
> window (the supervisor window) which in turn went into the `still hasn't
> started` state.
>
>
> On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> I am even having the almost same versions of storm (0.9.1) and kafka. And
> my topologies were also facing the same issue. When I ran the worker
> command directly, I came to know that somehow hostname was wrong in the
> configuration passed to the workers. So, I fixed that in storm config and
> my topology worked after that. However, now again it has stuck with same
> "still hasn't started" error message and in my case now the error in
> running the worker command is "Address already in use" for supervisor port.
>
> So, what is the error when you directly run the worker command?
>
>
> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>
> I fail to understand why that should happen, as testing with LocalCluster
> goes through fine.
>
> I did a clean fresh start to figure out what could be happening, and here
> are my observations -
>
> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's
> tmp dir}
> - used local pseudo cluster on my mac
> - nimbus process started fine
> - supervisor process started fine
> - ensured toplogy works fine with (the embedded) LocalCluster
> - topology was then submitted to local pseudo cluster on my mac ; that's
> when I see ``still hasn't started`` messages in supervisor terminal
> window
>
> When submitting topology to local pseudo cluster, had to add jars to
> overcome these ...
>
> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
> Caused by: java.lang.ClassNotFoundException: scala.Product
>
> Above were overcome by adding these to lib dir -
>
> storm-kafka-0.9.2-incubating.jar
> kafka_2.10-0.8.1.1.jar
> scala-library-2.10.1.jar
>
> I have tried the command in log as well ; hasn't helped.
>
> What am I missing?
>
>
> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>
> This is the clue. One of your topology is failing to start. You must see
> the worker command before these logs in the same log file. Just try to run
> those directly on console and it would show the exact error.
>
>
> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>
> Hello,
>
> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box) on
> these two systems -
>
> > cat /etc/redhat-release
> CentOS release 6.3 (Final)
>
> and
>
> > sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.9.2
> BuildVersion: 13C64
>
> After starting supervisor, I notice it is not listening on the
> configured port (6700) -
>
> > nc -zv localhost 6700
> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>
> When I submit topology, I see this scrolling message in the terminal
> window for supervisor -
>
> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>
> I don't see any worker id in UI. No error in logs.
>
> Any idea what could be happening?
>
> Thanks in advance.
>
> Naga
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
>
>
>
>
>
>
>
>
Re: supervisor not listening on port 6700?
Posted by Harsha <st...@harsha.io>.
Storm 0.9.2 is tag under github
repo [1]https://github.com/apache/incubator-storm/tree/v0.9.2-i
ncubating.
-Harsha
On Tue, Aug 26, 2014, at 10:26 PM, Naga Vij wrote:
Does anyone know what the git branch name is for 0.9.2 ?
On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij
<[2...@gmail.com> wrote:
When it gets into `still hasn't started` state, I have noticed
this in UI -
java.lang.RuntimeException: java.net.ConnectException:
Connection refused at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(Disrup
torQueue.java:128) at backtype.storm.utils.DisruptorQueue.
and am wondering how to overcome this.
On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij
<[3...@gmail.com> wrote:
I left supervisor running with the `still hasn't started` state
on one window, and tried starting the worker on another
window. That triggered an attempt to start another worker
(with another distinct id) in the first window (the supervisor
window) which in turn went into the `still hasn't started`
state.
On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal
<[4...@infoobjects.com> wrote:
I am even having the almost same versions of storm (0.9.1) and
kafka. And my topologies were also facing the same issue. When
I ran the worker command directly, I came to know that somehow
hostname was wrong in the configuration passed to the workers.
So, I fixed that in storm config and my topology worked after
that. However, now again it has stuck with same "still hasn't
started" error message and in my case now the error in running
the worker command is "Address already in use" for supervisor
port.
So, what is the error when you directly run the worker command?
On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij
<[5...@gmail.com> wrote:
I fail to understand why that should happen, as testing with
LocalCluster goes through fine.
I did a clean fresh start to figure out what could be
happening, and here are my observations -
- fresh clean start: cleanup in zk (rmr /storm), and /bin/rm
-fr {storm's tmp dir}
- used local pseudo cluster on my mac
- nimbus process started fine
- supervisor process started fine
- ensured toplogy works fine with (the embedded) LocalCluster
- topology was then submitted to local pseudo cluster on my mac
; that's when I see ``still hasn't started`` messages in
supervisor terminal window
When submitting topology to local pseudo cluster, had to add
jars to overcome these ...
Caused by: java.lang.ClassNotFoundException:
storm.kafka.BrokerHosts
Caused by: java.lang.ClassNotFoundException:
kafka.api.OffsetRequest
Caused by: java.lang.ClassNotFoundException: scala.Product
Above were overcome by adding these to lib dir -
storm-kafka-0.9.2-incubating.jar
kafka_2.10-0.8.1.1.jar
scala-library-2.10.1.jar
I have tried the command in log as well ; hasn't helped.
What am I missing?
On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal
<[6...@infoobjects.com> wrote:
>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
This is the clue. One of your topology is failing to start. You
must see the worker command before these logs in the same log
file. Just try to run those directly on console and it would
show the exact error.
On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij
<[7...@gmail.com> wrote:
Hello,
I am trying out Storm 0.9.2-incubating pseudo cluster (on just
one box) on these two systems -
> cat /etc/redhat-release
CentOS release 6.3 (Final)
and
> sw_vers
ProductName: Mac OS X
ProductVersion: 10.9.2
BuildVersion: 13C64
After starting supervisor, I notice it is not listening on the
configured port (6700) -
> nc -zv localhost 6700
nc: connectx to localhost port 6700 (tcp) failed: Connection
refused
When I submit topology, I see this scrolling message in the
terminal window for supervisor -
23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor
- dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
I don't see any worker id in UI. No error in logs.
Any idea what could be happening?
Thanks in advance.
Naga
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[8]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[9]+1 (408) 988-2000 Work
[10]+1 (408) 716-2726 Fax
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
[11]http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
[12]+1 (408) 988-2000 Work
[13]+1 (408) 716-2726 Fax
References
1. https://github.com/apache/incubator-storm/tree/v0.9.2-incubating
2. mailto:nvbuchu1@gmail.com
3. mailto:nvbuchu1@gmail.com
4. mailto:vikas@infoobjects.com
5. mailto:nvbuchu1@gmail.com
6. mailto:vikas@infoobjects.com
7. mailto:nvbuchu1@gmail.com
8. http://www.infoobjects.com/
9. tel:%2B1%20%28408%29%20988-2000
10. tel:%2B1%20%28408%29%20716-2726
11. http://www.infoobjects.com/
12. tel:%2B1%20%28408%29%20988-2000
13. tel:%2B1%20%28408%29%20716-2726
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
Does anyone know what the git branch name is for 0.9.2 ?
On Tue, Aug 26, 2014 at 10:24 PM, Naga Vij <nv...@gmail.com> wrote:
> When it gets into `still hasn't started` state, I have noticed this in UI -
>
> java.lang.RuntimeException: java.net.ConnectException: Connection refused
> at
> backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128)
> at backtype.storm.utils.DisruptorQueue.
>
> and am wondering how to overcome this.
>
>
> On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij <nv...@gmail.com> wrote:
>
>> I left supervisor running with the `still hasn't started` state on one
>> window, and tried starting the worker on another window. That triggered an
>> attempt to start another worker (with another distinct id) in the first
>> window (the supervisor window) which in turn went into the `still hasn't
>> started` state.
>>
>>
>> On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com>
>> wrote:
>>
>>> I am even having the almost same versions of storm (0.9.1) and kafka.
>>> And my topologies were also facing the same issue. When I ran the worker
>>> command directly, I came to know that somehow hostname was wrong in the
>>> configuration passed to the workers. So, I fixed that in storm config and
>>> my topology worked after that. However, now again it has stuck with same
>>> "still hasn't started" error message and in my case now the error in
>>> running the worker command is "Address already in use" for supervisor port.
>>>
>>> So, what is the error when you directly run the worker command?
>>>
>>>
>>> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>>>
>>>> I fail to understand why that should happen, as testing with
>>>> LocalCluster goes through fine.
>>>>
>>>> I did a clean fresh start to figure out what could be happening, and
>>>> here are my observations -
>>>>
>>>> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr
>>>> {storm's tmp dir}
>>>> - used local pseudo cluster on my mac
>>>> - nimbus process started fine
>>>> - supervisor process started fine
>>>> - ensured toplogy works fine with (the embedded) LocalCluster
>>>> - topology was then submitted to local pseudo cluster on my mac ;
>>>> that's when I see ``still hasn't started`` messages in supervisor
>>>> terminal window
>>>>
>>>> When submitting topology to local pseudo cluster, had to add jars to
>>>> overcome these ...
>>>>
>>>> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
>>>> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
>>>> Caused by: java.lang.ClassNotFoundException: scala.Product
>>>>
>>>> Above were overcome by adding these to lib dir -
>>>>
>>>> storm-kafka-0.9.2-incubating.jar
>>>> kafka_2.10-0.8.1.1.jar
>>>> scala-library-2.10.1.jar
>>>>
>>>> I have tried the command in log as well ; hasn't helped.
>>>>
>>>> What am I missing?
>>>>
>>>>
>>>> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
>>>> wrote:
>>>>
>>>>> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>>>>>
>>>>> This is the clue. One of your topology is failing to start. You must
>>>>> see the worker command before these logs in the same log file. Just try to
>>>>> run those directly on console and it would show the exact error.
>>>>>
>>>>>
>>>>> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one
>>>>>> box) on these two systems -
>>>>>>
>>>>>> > cat /etc/redhat-release
>>>>>> CentOS release 6.3 (Final)
>>>>>>
>>>>>> and
>>>>>>
>>>>>> > sw_vers
>>>>>> ProductName: Mac OS X
>>>>>> ProductVersion: 10.9.2
>>>>>> BuildVersion: 13C64
>>>>>>
>>>>>> After starting supervisor, I notice it is not listening on the
>>>>>> configured port (6700) -
>>>>>>
>>>>>> > nc -zv localhost 6700
>>>>>> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>>>>>>
>>>>>> When I submit topology, I see this scrolling message in the terminal
>>>>>> window for supervisor -
>>>>>>
>>>>>> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
>>>>>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>>>>>>
>>>>>> I don't see any worker id in UI. No error in logs.
>>>>>>
>>>>>> Any idea what could be happening?
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> Naga
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Vikas Agarwal
>>>>> 91 – 9928301411
>>>>>
>>>>> InfoObjects, Inc.
>>>>> Execution Matters
>>>>> http://www.infoobjects.com
>>>>> 2041 Mission College Boulevard, #280
>>>>> Santa Clara, CA 95054
>>>>> +1 (408) 988-2000 Work
>>>>> +1 (408) 716-2726 Fax
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Vikas Agarwal
>>> 91 – 9928301411
>>>
>>> InfoObjects, Inc.
>>> Execution Matters
>>> http://www.infoobjects.com
>>> 2041 Mission College Boulevard, #280
>>> Santa Clara, CA 95054
>>> +1 (408) 988-2000 Work
>>> +1 (408) 716-2726 Fax
>>>
>>>
>>
>
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
When it gets into `still hasn't started` state, I have noticed this in UI -
java.lang.RuntimeException: java.net.ConnectException: Connection refused
at
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:128)
at backtype.storm.utils.DisruptorQueue.
and am wondering how to overcome this.
On Tue, Aug 26, 2014 at 10:04 PM, Naga Vij <nv...@gmail.com> wrote:
> I left supervisor running with the `still hasn't started` state on one
> window, and tried starting the worker on another window. That triggered an
> attempt to start another worker (with another distinct id) in the first
> window (the supervisor window) which in turn went into the `still hasn't
> started` state.
>
>
> On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
>> I am even having the almost same versions of storm (0.9.1) and kafka. And
>> my topologies were also facing the same issue. When I ran the worker
>> command directly, I came to know that somehow hostname was wrong in the
>> configuration passed to the workers. So, I fixed that in storm config and
>> my topology worked after that. However, now again it has stuck with same
>> "still hasn't started" error message and in my case now the error in
>> running the worker command is "Address already in use" for supervisor port.
>>
>> So, what is the error when you directly run the worker command?
>>
>>
>> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>>
>>> I fail to understand why that should happen, as testing with
>>> LocalCluster goes through fine.
>>>
>>> I did a clean fresh start to figure out what could be happening, and
>>> here are my observations -
>>>
>>> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr
>>> {storm's tmp dir}
>>> - used local pseudo cluster on my mac
>>> - nimbus process started fine
>>> - supervisor process started fine
>>> - ensured toplogy works fine with (the embedded) LocalCluster
>>> - topology was then submitted to local pseudo cluster on my mac ; that's
>>> when I see ``still hasn't started`` messages in supervisor terminal
>>> window
>>>
>>> When submitting topology to local pseudo cluster, had to add jars to
>>> overcome these ...
>>>
>>> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
>>> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
>>> Caused by: java.lang.ClassNotFoundException: scala.Product
>>>
>>> Above were overcome by adding these to lib dir -
>>>
>>> storm-kafka-0.9.2-incubating.jar
>>> kafka_2.10-0.8.1.1.jar
>>> scala-library-2.10.1.jar
>>>
>>> I have tried the command in log as well ; hasn't helped.
>>>
>>> What am I missing?
>>>
>>>
>>> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
>>> wrote:
>>>
>>>> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>>>>
>>>> This is the clue. One of your topology is failing to start. You must
>>>> see the worker command before these logs in the same log file. Just try to
>>>> run those directly on console and it would show the exact error.
>>>>
>>>>
>>>> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one
>>>>> box) on these two systems -
>>>>>
>>>>> > cat /etc/redhat-release
>>>>> CentOS release 6.3 (Final)
>>>>>
>>>>> and
>>>>>
>>>>> > sw_vers
>>>>> ProductName: Mac OS X
>>>>> ProductVersion: 10.9.2
>>>>> BuildVersion: 13C64
>>>>>
>>>>> After starting supervisor, I notice it is not listening on the
>>>>> configured port (6700) -
>>>>>
>>>>> > nc -zv localhost 6700
>>>>> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>>>>>
>>>>> When I submit topology, I see this scrolling message in the terminal
>>>>> window for supervisor -
>>>>>
>>>>> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
>>>>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>>>>>
>>>>> I don't see any worker id in UI. No error in logs.
>>>>>
>>>>> Any idea what could be happening?
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> Naga
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Vikas Agarwal
>>>> 91 – 9928301411
>>>>
>>>> InfoObjects, Inc.
>>>> Execution Matters
>>>> http://www.infoobjects.com
>>>> 2041 Mission College Boulevard, #280
>>>> Santa Clara, CA 95054
>>>> +1 (408) 988-2000 Work
>>>> +1 (408) 716-2726 Fax
>>>>
>>>>
>>>
>>
>>
>> --
>> Regards,
>> Vikas Agarwal
>> 91 – 9928301411
>>
>> InfoObjects, Inc.
>> Execution Matters
>> http://www.infoobjects.com
>> 2041 Mission College Boulevard, #280
>> Santa Clara, CA 95054
>> +1 (408) 988-2000 Work
>> +1 (408) 716-2726 Fax
>>
>>
>
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
I left supervisor running with the `still hasn't started` state on one
window, and tried starting the worker on another window. That triggered an
attempt to start another worker (with another distinct id) in the first
window (the supervisor window) which in turn went into the `still hasn't
started` state.
On Tue, Aug 26, 2014 at 7:50 PM, Vikas Agarwal <vi...@infoobjects.com>
wrote:
> I am even having the almost same versions of storm (0.9.1) and kafka. And
> my topologies were also facing the same issue. When I ran the worker
> command directly, I came to know that somehow hostname was wrong in the
> configuration passed to the workers. So, I fixed that in storm config and
> my topology worked after that. However, now again it has stuck with same
> "still hasn't started" error message and in my case now the error in
> running the worker command is "Address already in use" for supervisor port.
>
> So, what is the error when you directly run the worker command?
>
>
> On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
>
>> I fail to understand why that should happen, as testing with LocalCluster
>> goes through fine.
>>
>> I did a clean fresh start to figure out what could be happening, and here
>> are my observations -
>>
>> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's
>> tmp dir}
>> - used local pseudo cluster on my mac
>> - nimbus process started fine
>> - supervisor process started fine
>> - ensured toplogy works fine with (the embedded) LocalCluster
>> - topology was then submitted to local pseudo cluster on my mac ; that's
>> when I see ``still hasn't started`` messages in supervisor terminal
>> window
>>
>> When submitting topology to local pseudo cluster, had to add jars to
>> overcome these ...
>>
>> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
>> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
>> Caused by: java.lang.ClassNotFoundException: scala.Product
>>
>> Above were overcome by adding these to lib dir -
>>
>> storm-kafka-0.9.2-incubating.jar
>> kafka_2.10-0.8.1.1.jar
>> scala-library-2.10.1.jar
>>
>> I have tried the command in log as well ; hasn't helped.
>>
>> What am I missing?
>>
>>
>> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
>> wrote:
>>
>>> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>>>
>>> This is the clue. One of your topology is failing to start. You must see
>>> the worker command before these logs in the same log file. Just try to run
>>> those directly on console and it would show the exact error.
>>>
>>>
>>> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box)
>>>> on these two systems -
>>>>
>>>> > cat /etc/redhat-release
>>>> CentOS release 6.3 (Final)
>>>>
>>>> and
>>>>
>>>> > sw_vers
>>>> ProductName: Mac OS X
>>>> ProductVersion: 10.9.2
>>>> BuildVersion: 13C64
>>>>
>>>> After starting supervisor, I notice it is not listening on the
>>>> configured port (6700) -
>>>>
>>>> > nc -zv localhost 6700
>>>> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>>>>
>>>> When I submit topology, I see this scrolling message in the terminal
>>>> window for supervisor -
>>>>
>>>> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
>>>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>>>>
>>>> I don't see any worker id in UI. No error in logs.
>>>>
>>>> Any idea what could be happening?
>>>>
>>>> Thanks in advance.
>>>>
>>>> Naga
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Vikas Agarwal
>>> 91 – 9928301411
>>>
>>> InfoObjects, Inc.
>>> Execution Matters
>>> http://www.infoobjects.com
>>> 2041 Mission College Boulevard, #280
>>> Santa Clara, CA 95054
>>> +1 (408) 988-2000 Work
>>> +1 (408) 716-2726 Fax
>>>
>>>
>>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
Re: supervisor not listening on port 6700?
Posted by Vikas Agarwal <vi...@infoobjects.com>.
I am even having the almost same versions of storm (0.9.1) and kafka. And
my topologies were also facing the same issue. When I ran the worker
command directly, I came to know that somehow hostname was wrong in the
configuration passed to the workers. So, I fixed that in storm config and
my topology worked after that. However, now again it has stuck with same
"still hasn't started" error message and in my case now the error in
running the worker command is "Address already in use" for supervisor port.
So, what is the error when you directly run the worker command?
On Tue, Aug 26, 2014 at 9:39 PM, Naga Vij <nv...@gmail.com> wrote:
> I fail to understand why that should happen, as testing with LocalCluster
> goes through fine.
>
> I did a clean fresh start to figure out what could be happening, and here
> are my observations -
>
> - fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's
> tmp dir}
> - used local pseudo cluster on my mac
> - nimbus process started fine
> - supervisor process started fine
> - ensured toplogy works fine with (the embedded) LocalCluster
> - topology was then submitted to local pseudo cluster on my mac ; that's
> when I see ``still hasn't started`` messages in supervisor terminal
> window
>
> When submitting topology to local pseudo cluster, had to add jars to
> overcome these ...
>
> Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
> Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
> Caused by: java.lang.ClassNotFoundException: scala.Product
>
> Above were overcome by adding these to lib dir -
>
> storm-kafka-0.9.2-incubating.jar
> kafka_2.10-0.8.1.1.jar
> scala-library-2.10.1.jar
>
> I have tried the command in log as well ; hasn't helped.
>
> What am I missing?
>
>
> On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
> wrote:
>
>> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>>
>> This is the clue. One of your topology is failing to start. You must see
>> the worker command before these logs in the same log file. Just try to run
>> those directly on console and it would show the exact error.
>>
>>
>> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box)
>>> on these two systems -
>>>
>>> > cat /etc/redhat-release
>>> CentOS release 6.3 (Final)
>>>
>>> and
>>>
>>> > sw_vers
>>> ProductName: Mac OS X
>>> ProductVersion: 10.9.2
>>> BuildVersion: 13C64
>>>
>>> After starting supervisor, I notice it is not listening on the
>>> configured port (6700) -
>>>
>>> > nc -zv localhost 6700
>>> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>>>
>>> When I submit topology, I see this scrolling message in the terminal
>>> window for supervisor -
>>>
>>> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
>>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>>>
>>> I don't see any worker id in UI. No error in logs.
>>>
>>> Any idea what could be happening?
>>>
>>> Thanks in advance.
>>>
>>> Naga
>>>
>>>
>>
>>
>> --
>> Regards,
>> Vikas Agarwal
>> 91 – 9928301411
>>
>> InfoObjects, Inc.
>> Execution Matters
>> http://www.infoobjects.com
>> 2041 Mission College Boulevard, #280
>> Santa Clara, CA 95054
>> +1 (408) 988-2000 Work
>> +1 (408) 716-2726 Fax
>>
>>
>
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
+1 (408) 988-2000 Work
+1 (408) 716-2726 Fax
Re: supervisor not listening on port 6700?
Posted by Naga Vij <nv...@gmail.com>.
I fail to understand why that should happen, as testing with LocalCluster
goes through fine.
I did a clean fresh start to figure out what could be happening, and here
are my observations -
- fresh clean start: cleanup in zk (rmr /storm), and /bin/rm -fr {storm's
tmp dir}
- used local pseudo cluster on my mac
- nimbus process started fine
- supervisor process started fine
- ensured toplogy works fine with (the embedded) LocalCluster
- topology was then submitted to local pseudo cluster on my mac ; that's
when I see ``still hasn't started`` messages in supervisor terminal window
When submitting topology to local pseudo cluster, had to add jars to
overcome these ...
Caused by: java.lang.ClassNotFoundException: storm.kafka.BrokerHosts
Caused by: java.lang.ClassNotFoundException: kafka.api.OffsetRequest
Caused by: java.lang.ClassNotFoundException: scala.Product
Above were overcome by adding these to lib dir -
storm-kafka-0.9.2-incubating.jar
kafka_2.10-0.8.1.1.jar
scala-library-2.10.1.jar
I have tried the command in log as well ; hasn't helped.
What am I missing?
On Mon, Aug 25, 2014 at 11:41 PM, Vikas Agarwal <vi...@infoobjects.com>
wrote:
> >> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
>
> This is the clue. One of your topology is failing to start. You must see
> the worker command before these logs in the same log file. Just try to run
> those directly on console and it would show the exact error.
>
>
> On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
>
>> Hello,
>>
>> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box)
>> on these two systems -
>>
>> > cat /etc/redhat-release
>> CentOS release 6.3 (Final)
>>
>> and
>>
>> > sw_vers
>> ProductName: Mac OS X
>> ProductVersion: 10.9.2
>> BuildVersion: 13C64
>>
>> After starting supervisor, I notice it is not listening on the configured
>> port (6700) -
>>
>> > nc -zv localhost 6700
>> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>>
>> When I submit topology, I see this scrolling message in the terminal
>> window for supervisor -
>>
>> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>>
>> I don't see any worker id in UI. No error in logs.
>>
>> Any idea what could be happening?
>>
>> Thanks in advance.
>>
>> Naga
>>
>>
>
>
> --
> Regards,
> Vikas Agarwal
> 91 – 9928301411
>
> InfoObjects, Inc.
> Execution Matters
> http://www.infoobjects.com
> 2041 Mission College Boulevard, #280
> Santa Clara, CA 95054
> +1 (408) 988-2000 Work
> +1 (408) 716-2726 Fax
>
>
Re: supervisor not listening on port 6700?
Posted by Vikas Agarwal <vi...@infoobjects.com>.
>> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started<<
This is the clue. One of your topology is failing to start. You must see
the worker command before these logs in the same log file. Just try to run
those directly on console and it would show the exact error.
On Tue, Aug 26, 2014 at 11:45 AM, Naga Vij <nv...@gmail.com> wrote:
> Hello,
>
> I am trying out Storm 0.9.2-incubating pseudo cluster (on just one box) on
> these two systems -
>
> > cat /etc/redhat-release
> CentOS release 6.3 (Final)
>
> and
>
> > sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.9.2
> BuildVersion: 13C64
>
> After starting supervisor, I notice it is not listening on the configured
> port (6700) -
>
> > nc -zv localhost 6700
> nc: connectx to localhost port 6700 (tcp) failed: Connection refused
>
> When I submit topology, I see this scrolling message in the terminal
> window for supervisor -
>
> 23:11:44.532 [Thread-2] INFO backtype.storm.daemon.supervisor -
> dd7c588e-5fa0-4c4b-96ed-de0d420001e9 still hasn't started
>
> I don't see any worker id in UI. No error in logs.
>
> Any idea what could be happening?
>
> Thanks in advance.
>
> Naga
>
>
--
Regards,
Vikas Agarwal
91 – 9928301411
InfoObjects, Inc.
Execution Matters
http://www.infoobjects.com
2041 Mission College Boulevard, #280
Santa Clara, CA 95054
+1 (408) 988-2000 Work
+1 (408) 716-2726 Fax