You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org> on 2012/03/19 22:57:38 UTC

[jira] [Updated] (BIGTOP-223) install/ initscripts fixes

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

Roman Shaposhnik updated BIGTOP-223:
------------------------------------

    Fix Version/s:     (was: 0.3.0)
                   0.4.0
    
>  install/ initscripts fixes 
> ----------------------------
>
>                 Key: BIGTOP-223
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-223
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Peter Linnell
>            Assignee: Peter Linnell
>            Priority: Critical
>             Fix For: 0.4.0
>
>
> master is not running failed
> node is not running failed
> should be prefixed by flume
> I will fix this as part of my initscript audit/clean-up
> Another case:
> hbase:
> hadoop-hbase-master: unrecognized service
> hadoop-hbase-regionserver: unrecognized service
> hadoop-hbase-thrift: unrecognized service
> hadoop namenode:
> /etc/init.d/hadoopnamenode: line 23: /etc/default/hadoo-: No such file or directory
> /usr/lib/hadoop-/bin/hadoop-daemon.sh: line 42: /usr/lib/hadoop/bin/hadoop-config.sh: No such file or directory
> sqoop-metastore:
> sh: /usr/lib/sqoop/bin/stop-metastore.sh: No such file or directory
> zookeeper-server:
> JMX enabled by default
> Using config: /etc/zookeeper/zoo.cfg
> Stopping zookeeper ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira