make sure if is a bug

53 views
Skip to first unread message

李江平

unread,
May 20, 2016, 4:17:08 AM5/20/16
to presto...@googlegroups.com
hi presto-user:
 
I am a newer for starting to use presto-0.147.when I used,I found a problem which can cause presto-server start failed.
the information is below:
<----------------------------
2016-05-20T16:24:20.534+0900    ERROR   main    com.facebook.presto.server.PrestoServer Unable to create injector, see the following errors:

1) Error in custom provider, java.lang.RuntimeException: java.net.BindException: address always in using
  while locating io.airlift.http.server.HttpServerProvider
  at io.airlift.http.server.HttpServerModule.configure(HttpServerModule.java:64)
  while locating io.airlift.http.server.HttpServer
Caused by: java.lang.RuntimeException: java.net.BindException: address always in using
        at com.google.common.base.Throwables.propagate(Throwables.java:160)
        at io.airlift.http.server.HttpServerProvider.get(HttpServerProvider.java:151)
        at io.airlift.http.server.HttpServerProvider.get(HttpServerProvider.java:42)
        at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81)
        at com.google.inject.internal.BoundProviderFactory.provision(BoundProviderFactory.java:72)
        at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61)
        at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:62)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
        at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
        at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)
        at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
        at com.google.inject.internal.InternalInjectorCreator$1.call(InternalInjectorCreator.java:205)
        at com.google.inject.internal.InternalInjectorCreator$1.call(InternalInjectorCreator.java:199)
        at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
        at com.google.inject.internal.InternalInjectorCreator.loadEagerSingletons(InternalInjectorCreator.java:199)
        at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:180)
        at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:110)
        at com.google.inject.Guice.createInjector(Guice.java:96)
        at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:242)
        at com.facebook.presto.server.PrestoServer.run(PrestoServer.java:134)
        at com.facebook.presto.server.PrestoServer.main(PrestoServer.java:72)
Caused by: java.net.BindException: address always in using
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:433)
        at sun.nio.ch.Net.bind(Net.java:425)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:326)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:244)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:384)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at io.airlift.http.server.HttpServer.start(HttpServer.java:381)
       at io.airlift.http.server.HttpServerProvider.get(HttpServerProvider.java:147)
----------------------------->

when I used [netstat -anlp | grep 8080] to watch,I found some process to bind the 8080,so that ,maybe this is the caused rerson.
but, I always use [bin/launcher stop] to shutdown presto service. I guess maybe in the version-0.147 ,forget to deal with  the free resource .

I`m glad to recive your letter.



 

zeng zhen

unread,
May 26, 2016, 5:45:26 AM5/26/16
to Presto, xibe...@163.com
maybe you can try this command to check which process is listening to port 8080

sudo lsof -i:8080



2016年5月20日金曜日 17時17分08秒 UTC+9 李江平:
Reply all
Reply to author
Forward
0 new messages