You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Evans Ye (JIRA)" <ji...@apache.org> on 2014/04/18 05:49:15 UTC
[jira] [Updated] (BIGTOP-1163) puppet apply shows db init error if
the oozie server is already running
[ https://issues.apache.org/jira/browse/BIGTOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evans Ye updated BIGTOP-1163:
-----------------------------
Affects Version/s: (was: 0.4.0)
0.7.0
> puppet apply shows db init error if the oozie server is already running
> -----------------------------------------------------------------------
>
> Key: BIGTOP-1163
> URL: https://issues.apache.org/jira/browse/BIGTOP-1163
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.7.0
> Reporter: Evans Ye
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1163.1.patch
>
>
> When deploying hadoop with bigtop's puppet scripts, it will output error message like below If the oozie server is already running.
> {code}
> debug: Exec[Oozie DB init](provider=posix): Executing '/etc/init.d/oozie init'
> debug: Executing '/etc/init.d/oozie init'
> err: /Stage[main]/Hadoop_head_node/Hadoop-oozie::Server[oozie server]/Exec[Oozie DB init]/returns: change from notrun to 0 failed: /etc/init.d/oozie init returned 1 instead of one of [0] at /home/vagrant/bigtop/bigtop-deploy/puppet/modules/hadoop-oozie/manifests/init.pp:46
> notice: /Stage[main]/Hadoop_head_node/Hadoop-oozie::Server[oozie server]/Service[oozie]: Dependency Exec[Oozie DB init] has failures: true
> warning: /Stage[main]/Hadoop_head_node/Hadoop-oozie::Server[oozie server]/Service[oozie]: Skipping because of failed dependencies
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)