You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Peter Linnell (Created) (JIRA)" <ji...@apache.org> on 2011/11/01 19:53:32 UTC

[jira] [Created] (BIGTOP-223) flume initscripts should be more explicit

flume initscripts should be more explicit
-----------------------------------------

                 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: Minor
             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


--
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

        

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

Posted by "Peter Linnell (Updated) (JIRA)" <ji...@apache.org>.
     [ 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

        

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

Posted by "Peter Linnell (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141563#comment-13141563 ] 

Peter Linnell commented on BIGTOP-223:
--------------------------------------

Ubuntu Issue:

for i in hadoop-0.20-namenode hadoop-0.20-secondarynamenode hadoop-0.20-datanode hadoop-0.20-jobtracker hadoop-0.20-tasktracker hadoop-hbase-master hadoop-hbase-regionserver hadoop-hbase-thrift hadoop-zookeeper oozie hue flume-master flume-node sqoop-metastore ; do service $i status ; done
hadoop-0.20-namenode is running
hadoop-0.20-secondarynamenode is running
hadoop-0.20-datanode is not running.
hadoop-0.20-jobtracker is running
hadoop-0.20-tasktracker is running
hbase-master is running
hbase-regionserver is not running.
hbase-thrift is running
hadoop-zookeeper: unrecognized service
running

    Checking status of Hue for Hadoop hue [ OK ]
    Usage: /etc/init.d/flume-master {start|stop|restart}
    Usage: /etc/init.d/flume-node {start|stop|restart}
    sqoop-metastore is running


                
>  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 ...
> 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

--
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

        

[jira] [Issue Comment Edited] (BIGTOP-223) install/ initscripts fixes

Posted by "Peter Linnell (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141563#comment-13141563 ] 

Peter Linnell edited comment on BIGTOP-223 at 11/1/11 8:57 PM:
---------------------------------------------------------------

Ubuntu Issue:

for i in hadoop-namenode hadoop-secondarynamenode hadoop--datanode hadoop-jobtracker hadoop-tasktracker hadoop-hbase-master hadoop-hbase-regionserver hadoop-hbase-thrift hadoop-zookeeper oozie hue flume-master flume-node sqoop-metastore ; do service $i status ; done
hadoop-namenode is running
hadoop-secondarynamenode is running
hadoop-datanode is not running.
hadoop-obtracker is running
hadoop-tasktracker is running
hbase-master is running
hbase-regionserver is not running.
hbase-thrift is running
hadoop-zookeeper: unrecognized service
running

    Checking status of Hue for Hadoop hue [ OK ]
    Usage: /etc/init.d/flume-master {start|stop|restart}
    Usage: /etc/init.d/flume-node {start|stop|restart}
    sqoop-metastore is running


                
      was (Author: plinnell):
    Ubuntu Issue:

for i in hadoop-0.20-namenode hadoop-0.20-secondarynamenode hadoop-0.20-datanode hadoop-0.20-jobtracker hadoop-0.20-tasktracker hadoop-hbase-master hadoop-hbase-regionserver hadoop-hbase-thrift hadoop-zookeeper oozie hue flume-master flume-node sqoop-metastore ; do service $i status ; done
hadoop-0.20-namenode is running
hadoop-0.20-secondarynamenode is running
hadoop-0.20-datanode is not running.
hadoop-0.20-jobtracker is running
hadoop-0.20-tasktracker is running
hbase-master is running
hbase-regionserver is not running.
hbase-thrift is running
hadoop-zookeeper: unrecognized service
running

    Checking status of Hue for Hadoop hue [ OK ]
    Usage: /etc/init.d/flume-master {start|stop|restart}
    Usage: /etc/init.d/flume-node {start|stop|restart}
    sqoop-metastore is running


                  
>  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/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

        

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

Posted by "Peter Linnell (Updated) (JIRA)" <ji...@apache.org>.
     [ 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 ...

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



  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


       Priority: Major  (was: Minor)
        Summary:  install/ initscripts fixes   (was: flume initscripts should be more explicit)
    
>  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 ...
> 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

--
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

        

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

Posted by "Peter Linnell (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Fix Version/s:     (was: 0.4.0)
                   0.3.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
>             Fix For: 0.3.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

        

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

Posted by "Peter Linnell (Updated) (JIRA)" <ji...@apache.org>.
     [ 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/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 ...




  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 ...




    
>  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/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

        

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

Posted by "Peter Linnell (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Due Date:     (was: 17/Nov/11)
    
>  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.3.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

        

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

Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
     [ 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

        

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

Posted by "Peter Linnell (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Due Date: 17/Nov/11
    Priority: Critical  (was: Major)

I think this should be my major effort for 0.3.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.3.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