快速启动VM Cloudera包裹不会启动

时间:2015-12-27 04:44:26

标签: hadoop cloudera cloudera-cdh cloudera-manager cloudera-quickstart-vm

我在使用Cloudera Quickstart VM时遇到问题。让我试着通过概述我到目前为止的步骤来解释。

  1. 我想用Kafka写一些内容来连接到Web服务并提取数据Feed。
  2. 我将使用Cloudera 5.5快速入门VM作为我的游乐场。
  3. 我需要从包裹安装CDH才能获得Kafka。通过https://community.cloudera.com/t5/Apache-Hadoop-Concepts-and/cloudera-manager-5-4-0-installing-kafka-parcel-fails/td-p/30615
  4. 我看到了一个漂亮的"迁移到包裹" Cloudera VM桌面上的图标,所以我点击它并让它完成。
  5. 我尝试启动cloudera服务,现在我得到以下所有这些 -

    impala-server: unrecognized service
    
    impala-catalog: unrecognized service
    sqoop-metastore: unrecognized service
    solr-server: unrecognized service
    oozie: unrecognized service
    impala-state-store: unrecognized service
    hue: unrecognized service
    flume-ng-agent: unrecognized service
    hbase-regionserver: unrecognized service
    sqoop2-server: unrecognized service
    spark-history-server: unrecognized service
    sentry-store: unrecognized service
    hive-server2: unrecognized service
    hive-metastore: unrecognized service
    hbase-thrift: unrecognized service
    hbase-rest: unrecognized service
    hbase-master: unrecognized service
    hadoop-yarn-resourcemanager: unrecognized service
    hadoop-yarn-proxyserver: unrecognized service
    hadoop-yarn-nodemanager: unrecognized service
    hadoop-mapreduce-historyserver: unrecognized service
    hadoop-httpfs: unrecognized service
    hadoop-hdfs-secondarynamenode: unrecognized service
    hadoop-hdfs-namenode: unrecognized service
    hadoop-hdfs-journalnode: unrecognized service
    hadoop-hdfs-datanode: unrecognized service
    hbase-solr-indexer: unrecognized service
    zookeeper-server: unrecognized service
    [QuickStart] Disabling CDH services on boot...
    error reading information on service impala-server: No such file or directory
    error reading information on service impala-catalog: No such file or directory
    error reading information on service sqoop-metastore: No such file or directory
    error reading information on service solr-server: No such file or directory
    error reading information on service oozie: No such file or directory
    error reading information on service impala-state-store: No such file or directory
    error reading information on service hue: No such file or directory
    error reading information on service flume-ng-agent: No such file or directory
    error reading information on service hbase-regionserver: No such file or directory
    error reading information on service sqoop2-server: No such file or directory
    error reading information on service spark-history-server: No such file or directory
    error reading information on service sentry-store: No such file or directory
    error reading information on service hive-server2: No such file or directory
    error reading information on service hive-metastore: No such file or directory
    error reading information on service hbase-thrift: No such file or directory
    error reading information on service hbase-rest: No such file or directory
    error reading information on service hbase-master: No such file or directory
    error reading information on service hadoop-yarn-resourcemanager: No such file or directory
    error reading information on service hadoop-yarn-proxyserver: No such file or directory
    error reading information on service hadoop-yarn-nodemanager: No such file or directory
    error reading information on service hadoop-mapreduce-historyserver: No such file or directory
    error reading information on service hadoop-httpfs: No such file or directory
    error reading information on service hadoop-hdfs-secondarynamenode: No such file or directory
    error reading information on service hadoop-hdfs-namenode: No such file or directory
    error reading information on service hadoop-hdfs-journalnode: No such file or directory
    error reading information on service hadoop-hdfs-datanode: No such file or directory
    error reading information on service hbase-solr-indexer: No such file or directory
    error reading information on service zookeeper-server: No such file or directory
    [QuickStart] Starting Cloudera Manager daemons...
    [QuickStart] Waiting for Cloudera Manager API...
    
  6. 后来,当我做一个" top"命令。我还应该做什么?

1 个答案:

答案 0 :(得分:2)

这是一个非常简单的修复。我开始了cloudera经理服务

service cloudera-scm-server restart

我开始了cloudera代理

service cloudera-scm-agent restart

http://quickstart.cloudera:7180/cmf/home

进入Cloudera Manager Home

然后在状态选项卡中,我刚开始每项服务。这一切都是通过GUI轻松完成的