You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/02/07 09:18:00 UTC

[jira] [Closed] (FLINK-11536) cannot start standalone cluster - failed to bind to /0.0.0.0:6123

     [ https://issues.apache.org/jira/browse/FLINK-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-11536.
---------------------------------
    Resolution: Not A Problem

> cannot start standalone cluster - failed to bind to /0.0.0.0:6123
> -----------------------------------------------------------------
>
>                 Key: FLINK-11536
>                 URL: https://issues.apache.org/jira/browse/FLINK-11536
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Hongkai Wu
>            Priority: Major
>
> I'm deploying a standalone flink cluster with version 1.7 on EC2. I install java openjdk9.
> Once I run bin/start-cluster.sh, the log says:
> 2019-02-06 07:52:12,460 ERROR akka.remote.transport.netty.NettyTra
>  nsport - failed to bind to /0.0.0.0:6123, shutt
>  ing down Netty transport
>  2019-02-06 07:52:12,466 INFO org.apache.flink.runtime.entrypoint.
>  ClusterEntrypoint - Shutting StandaloneSessionClusterEntry
>  point down with application status FAILED. Diagnostics java.net.Bi
>  ndException: Could not start actor system on any port in port rang
>  e 6123
>  
> How can I fix this?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)