Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Date: Tue, 1 Nov 2011 20:57:32 +0000 (UTC)
From: "Peter Linnell (Updated) (JIRA)" <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: 
 <436118497.47457.1320181052578.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1466254498.46959.1320173612302.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (BIGTOP-223)  install/ initscripts fixes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Peter Linnell updated BIGTOP-223:
---------------------------------

    Description: 
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/hadoop-0.20-namenode: line 23: /etc/default/hadoop-0.20: No such file or directory
/usr/lib/hadoop-0.20/bin/hadoop-daemon.sh: line 42: /usr/lib/hadoop-0.20/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 ...


  was:
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/hadoop-0.20-namenode: line 23: /etc/default/hadoop-0.20: No such file or directory
/usr/lib/hadoop-0.20/bin/hadoop-daemon.sh: line 42: /usr/lib/hadoop-0.20/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 ...

hue-beeswax:
=== Uninstalling beeswax
=== Saved registry at /usr/share/hue/app.reg
=== Saved /usr/share/hue/build/env/lib/python2.4/site-packages/hue.pth


>  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
>             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/hadoop-0.20-namenode: line 23: /etc/default/hadoop-0.20: No such file or directory
> /usr/lib/hadoop-0.20/bin/hadoop-daemon.sh: line 42: /usr/lib/hadoop-0.20/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