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 <[email protected]> To: [email protected]; Annabel Melongo <[email protected]> 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 <[email protected]> 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 <[email protected]> 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. >> >> >> >> > > >
