Re: auto port find doesnt seem to be working

[Jonathan Hsieh <jo...@cloudera.com>]

[Please subscribe to new flume-user@incubator.apache.org list, bcc
flume-user@cloudera.org, cc flume-user@incubator.apache.org]

This may have broken in 0.9.4 (metrics/status web servers were refactored in
this upgrade).  What version are you running?

Thanks,
Jon

On Tue, Jul 12, 2011 at 10:39 AM, sm-flume <ci...@gmail.com> wrote:

> If I have a node running and then start a collector on the same IP (or
> vice versa), the auto port does not find the next port, but rather
> throws an exception. It's not fatal, but prevents the interface from
> opening. Any ideas why this would happen? And yes, autoport is set as
> true in the conf.xml file.
>
>
> 2011-07-12 13:36:21,085 [main] WARN mortbay.log: failed
> SelectChannelConnector@0.0.0.0:35862: java.net.BindException: Address
> already in use
> 2011-07-12 13:36:21,085 [main] WARN mortbay.log: failed
> Server@318efaea: java.net.BindException: Address already in use
> 2011-07-12 13:36:21,086 [main] WARN util.InternalHttpServer: Caught
> exception during HTTP server start.
> java.net.BindException: Address already in use
>        at sun.nio.ch.Net.bind(Native Method)
>        at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
> 126)
>        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>        at
>
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:
> 216)
>        at
>
> org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:
> 315)
>        at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
> 50)
>        at org.mortbay.jetty.Server.doStart(Server.java:235)
>        at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
> 50)
>        at
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:
> 188)
>        at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
>        at com.cloudera.flume.agent.FlumeNode.setup(FlumeNode.java:504)
>        at com.cloudera.flume.agent.FlumeNode.main(FlumeNode.java:665)
> 2011-07-12 13:36:21,087 [main] ERROR agent.FlumeNode: Unexpected
> exception/error thrown! Unable to start HTTP server
> com.cloudera.util.InternalHttpServer$InternalHttpServerException:
> Unable to start HTTP server
>        at
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:
> 194)
>        at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
>        at com.cloudera.flume.agent.FlumeNode.setup(FlumeNode.java:504)
>        at com.cloudera.flume.agent.FlumeNode.main(FlumeNode.java:665)
> Caused by: java.net.BindException: Address already in use
>        at sun.nio.ch.Net.bind(Native Method)
>        at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:
> 126)
>        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>        at
>
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:
> 216)
>        at
>
> org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:
> 315)
>        at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
> 50)
>        at org.mortbay.jetty.Server.doStart(Server.java:235)
>        at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
> 50)
>        at
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:
> 188)
>        ... 3 more
>



-- 
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com