[jira] [Commented] (BIGTOP-2529) Vagrant Provisioner failed to start up daemons

["Evans Ye (JIRA)" <ji...@apache.org>]

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

Evans Ye commented on BIGTOP-2529:
----------------------------------

Going to commit this if no objection.

> Vagrant Provisioner failed to start up daemons
> ----------------------------------------------
>
>                 Key: BIGTOP-2529
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2529
>             Project: Bigtop
>          Issue Type: Bug
>          Components: provisioner
>    Affects Versions: 1.1.0
>         Environment: Vagrant 1.8.4
> Mac OS X
>            Reporter: Evans Ye
>            Assignee: Evans Ye
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> The Vagrant Provisioner won't work out-of-the-box anymore:
> {code}
> ==> bigtop1: Error: Could not start Service[hadoop-yarn-resourcemanager]: Execution of '/bin/systemctl start hadoop-yarn-resourcemanager' returned 1: Job for hadoop-yarn-resourcemanager.service failed because the control process exited with error code. See "systemctl status hadoop-yarn-resourcemanager.service" and "journalctl -xe" for details.
> ==> bigtop1: Error: /Stage[main]/Hadoop::Resourcemanager/Service[hadoop-yarn-resourcemanager]/ensure: change from stopped to running failed: Could not start Service[hadoop-yarn-resourcemanager]: Execution of '/bin/systemctl start hadoop-yarn-resourcemanager' returned 1: Job for hadoop-yarn-resourcemanager.service failed because the control process exited with error code. See "systemctl status hadoop-yarn-resourcemanager.service" and "journalctl -xe" for details.
> {code}
> We should fix it by upgrading to CentOS 7.2 Box.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)