You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ken Krugler (JIRA)" <ji...@apache.org> on 2018/03/04 14:22:00 UTC

[jira] [Commented] (FLINK-8848) bin/start-cluster.sh won't start jobmanager on master machine.

    [ https://issues.apache.org/jira/browse/FLINK-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16385157#comment-16385157 ] 

Ken Krugler commented on FLINK-8848:
------------------------------------

Hi [~manifoldQAQ] - in general it's best to first post to the user mailing list, and then if (after discussion) it looks like a bug, you could open a Jira issue, thanks!

> bin/start-cluster.sh won't start jobmanager on master machine.
> --------------------------------------------------------------
>
>                 Key: FLINK-8848
>                 URL: https://issues.apache.org/jira/browse/FLINK-8848
>             Project: Flink
>          Issue Type: Bug
>          Components: Cluster Management, Configuration
>    Affects Versions: 1.4.1
>         Environment: I login to a remote Ubuntu 16.04 server via ssh.
>  
> conf/masters: hostname:port
>            Reporter: Yesheng Ma
>            Priority: Major
>              Labels: easyfix, newbie, usability
>
> When I execute bin/start-cluster.sh on the master machine, actually the command `nohup /bin/bash -l /state/partition1/ysma/flink-1.4.1/bin/jobmanager.sh start cluster ...` is exexuted, which does not open the job manager.
> I think there might be something wrong with the `-l` argument, since when I use the bin/jobmanager.sh start, everything is fine. Kindly point out if I've done any configuration wrong.



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