You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/10/12 07:23:43 UTC

[jira] [Commented] (BIGTOP-803) somehow puppet gets confused by the hadoop fs output

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

Prasanna Santhanam commented on BIGTOP-803:
-------------------------------------------

[~rvs] were you able to workaround this at least? I started facing the same issue with our Apache CloudStack services couple of days ago. I read your posts on the puppet google groups but I couldn't find a clear resolution there.

> somehow puppet gets confused by the hadoop fs output
> ----------------------------------------------------
>
>                 Key: BIGTOP-803
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-803
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.5.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>
> My Puppet runs have been suffering from the mysterious:
> {noformat}
> err: /Stage[main]/Hadoop_head_node/Hadoop::Create_hdfs_dirs[/hbase]/Exec[HDFS init /hbase]: Could not evaluate: Puppet::Util::Log requires a message
> {noformat}
> The only reference to this issue I was able to find is this one: https://github.com/dcere/pfc/wiki/Installing-Facter-and-Puppet-from-source
> {noformat}
> err: Could not evaluate: Puppet::Util::Log requires a message
> Solution: This means Puppet has exited abruptly. If you are exiting a provider use return inside the provider instead of exit.
> {noformat}
> and it doesn't really say much :-(
> We need to figure out a workaround and quickly too.



--
This message was sent by Atlassian JIRA
(v6.1#6144)