storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From researcher cs <prog.researc...@gmail.com>
Subject Re: Failed to bind to: 0.0.0.0/0.0.0.0:6703
Date Mon, 04 Jan 2016 21:38:09 GMT
-  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 <derekd@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 <mjsax@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.
> >
> >
> >
> >
>

Mime
View raw message