Ambari(二)----Ambari2.6.0源码编译安装及遇到的问题解决(超详细文档)

最新推荐文章于 2024-05-16 05:02:36 发布
最新推荐文章于 2024-05-16 05:02:36 发布
阅读量4.6k 收藏 8
点赞数 4
分类专栏： Ambari 大数据开发 文章标签： linux ambari
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_40861707/article/details/108626421
版权

本篇博客列举的所有命令行操作及问题都是使用过程中真实遇到的
如操作过程中遇到什么疑问,或文章内容有什么不严谨的地方
请在评论区留言指出,我会第一时间更正

参考链接

ambari2.6.0源码编译安装官方文档

Ambari安装以及安装使用过程中遇到的问题和解决方案

文章目录

一. 准备工作

二. 源码编译

三. ambari2.6.0源码编译遇到的问题及解决方案

四. 安装和配置Ambari

五. ambari2.6.0安装配置遇到的问题及解决方案

一. 准备工作

1.1 获取Ambari2.6.0源码
wget http://archive.apache.org/dist/ambari/ambari-2.6.0/apache-ambari-2.6.0-src.tar.gz

# 附1 wget命令安装方法:  yum install wget
# 附2 使用wget命令如遇报错:Unable to locally verify the issuer's authority  需要在wget命令后面加上--no-check-certificate 参数

tar -zxvf apache-ambari-2.6.0-src.tar.gz
1.2 搭建编译环境
1.2.1 配置java环境

注意Ambari2.6要求的版本为JDK7,Ambari2.7要求的最低版本为JDK8

vi ~/.bashrc

export JAVA_HOME=/opt/modules/jdk1.8.0_151 #以自己配置为准
export PATH=$JAVA_HOME/bin:$PATH
export _JAVA_OPTIONS="-Xmx2048m -XX:MaxPermSize=512m -Djava.awt.headless=true"


source ~/.bashrc
1.2.2 配置maven环境

注意:ambari适配的maven版本最低为3.3.9,但3.5.4之后的版本可能出现兼容问题(具体参看问题3.5)

vi ~/.bashrc

export MAVEN_HOME=/opt/modules/apache-maven-3.5.3 #以自己配置为准
export PATH=$MAVEN_HOME/bin:$PATH


source ~/.bashrc
1.2.3 安装rpm和rpmbuild
yum install rpm
yum install rpm-build
1.2.4 安装g++
yum install gcc-c++
1.2.5 检查python版本

注意:ambari要求python的版本为2.6+
一般使用系统自带的就OK

# 检查python版本,低于2.6的重新安装
python -V
1.2.6 初始化python-devel
yum install python-devel
1.2.7 安装bower, gulp

# 附 npm命令安装方式: yum install npm
npm install -g bower
npm install -g gulp
1.2.8 安装git
yum install git
1.2.9 安装python setuptools
wget https://pypi.python.org/packages/45/29/8814bf414e7cd1031e1a3c8a4169218376e284ea2553cc0822a6ea1c2d78/setuptools-36.6.0.zip#md5=74663b15117d9a2cc5295d76011e6fd1

unzip setuptools-36.6.0.zip  # 附 unzip安装命令:yum install -y unzip zip
cd setuptools-36.6.0
python setup.py install
1.2.10 设置最大打开文件数

linux系统默认最大打开文件数为1024
在源码编译过程中最大打开文件数可能超过该限制报错:

too many files are open而导致编译失败,所以需要修改最大打开文件数限制

ulimit -n 10000

二. 源码编译

2.1 配置阿里云远程仓库

为了能够提高编译过程中依赖包下载效率,maven可以配置阿里远程仓库

vi $MAVEN_HOME/conf/settings.xml


<!--在mirrors标签里添加mirror标签,内容如下:-->
    <mirror>
        <id>alimaven</id>
        <mirrorOf>central</mirrorOf>
        <name>aliyun maven</name>
        <url>http://maven.aliyun.com/nexus/content/repositories/central/</url>
    </mirror>
2.2 源码编译安装(以下命令需要在ambari源码包的根目录下执行)
# 设置ambari版本
mvn versions:set-property -Dproperty=revision -DnewVersion=2.6.0.0.0

执行源码编译命令前,请先阅读第三部分,遇到的问题及解决方案,以免踩坑

# -DskipTests参数是为了跳过单元测试,提高编译效率
# -Drat.skip参数是为了跳过licensing 检查,防止报错Too many files with unapproved license
mvn -B clean install package rpm:rpm -DnewVersion=2.6.0.0.0 -DskipTests -Drat.skip -Dpython.ver="python >= 2.6" -Preplaceurl

出现如下界面,证明源码编译成功!

在这里插入图片描述

三. 遇到的问题及解决方案

3.1 Ambari Main编译报错: RPM build execution returned: ‘127’ executing

报错详情:

[INFO] Ambari Main ....................................... FAILURE [58:16.141s]

[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.0.1:rpm (default-cli) on project ambari: RPM build execution returned: '127' executing '/bin/sh -c cd /opt/ambari/apache-ambari-2.6.0-src/target/rpm/ambari/SPECS && rpmbuild -bb --buildroot /opt/ambari/apache-ambari-2.6.0-src/target/rpm/ambari/buildroot --define '_topdir /opt/ambari/apache-ambari-2.6.0-src/target/rpm/ambari' --target noarch-redhat-linux ambari.spec' -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

报错原因:: rpm,或者rpm-build没有安装

解决方案:

# 安装rpm,rpm-build
yum install rpm
yum install rpm-build

之后使用2.2的编译命令重新编译安装即可

解决结果:

# Ambari Main编译成功
[INFO] Ambari Main 2.6.0.0.0 .............................. SUCCESS [  0.824 s]
3.2 Ambari Web编译报错: requires Maven version 3.1.0

报错详情:

[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main ....................................... SUCCESS [0.873s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [0.121s]
[INFO] Ambari Web ........................................ FAILURE [37.713s]

[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install node and yarn) on project ambari-web: The plugin com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginIncompatibleException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :ambari-web

报错原因: maven版本的问题, ambari要求, maven版本最低为3.3.9

我这里报该错误的原因是配置了高版本的maven环境,但是没有使用source ~/.bashrc命令使改动生效

mvn -version
Apache Maven 3.0.5 (Red Hat 3.0.5-17)
Maven home: /usr/share/maven
Java version: 1.8.0_262, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.262.b10-0.el7_8.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.21.1.el7.x86_64", arch: "amd64", family: "unix"

解决方案

配置高版本maven,并使用source ~/.bashrc命令使改动生效

解决结果:

#Ambari Web编译成功
[INFO] Ambari Web ......................................... SUCCESS [ 55.379 s]
3.3 Ambari Admin View编译失败: Command execution failed. Process exited with an error: 1

问题详情:

error Unexpected token {

Stack trace:
SyntaxError: Unexpected token {
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/node_modules/bower-registry-client/node_modules/request/lib/cookies.js:3:13)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)

Console trace:
Trace
    at StandardRenderer.error (/opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/lib/renderers/StandardRenderer.js:72:17)
    at Logger.<anonymous> (/opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/bin/bower:111:22)
    at emitOne (events.js:77:13)
    at Logger.emit (events.js:169:7)
    at Logger.emit (/opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39)
    at /opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/lib/commands/index.js:40:20
    at _rejected (/opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/node_modules/q/q.js:797:24)
    at /opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/node_modules/q/q.js:823:30
    at Promise.when (/opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/node_modules/q/q.js:1035:31)
    at Promise.promise.promiseDispatch (/opt/ambari/apache-ambari-2.6.0-src/ambari-admin/src/main/resources/ui/admin-web/node_modules/bower/node_modules/q/q.js:741:41)

System info:
Bower version: 1.3.8
Node version: 4.5.0
OS: Linux 3.10.0-693.21.1.el7.x86_64 x64
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:982)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:929)
    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:457)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

[INFO] Ambari Main 2.6.0.0.0 .............................. SUCCESS [  0.814 s]
[INFO] Apache Ambari Project POM 2.6.0.0.0 ................ SUCCESS [  0.131 s]
[INFO] Ambari Web 2.6.0.0.0 ............................... SUCCESS [03:07 min]
[INFO] Ambari Views 2.6.0.0.0 ............................. SUCCESS [08:32 min]
[INFO] Ambari Admin View 2.6.0.0.0 ........................ FAILURE [02:46 min]

[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.0.0:exec (Bower install) on project ambari-admin: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :ambari-admin
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.0.0:exec (Bower install) on project ambari-admin: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :ambari-admin

问题原因:

ambari-admin/pom.xml里默认的配置存在一些问题
nodeVersion,npmVersion配置项与实际不符

默认配置如下图:
在这里插入图片描述

使用如下命令查看npm和node的版本

npm -v  # 我的版本为3.10.10
node -v # 我的版本为v6.17.1

解决办法:

<!--修改ambari-admin模块下的pom.xml文件 -->
<nodeVersion>3.10.10</nodeVersion>
<npmVersion>v6.17.1</npmVersion>

解决结果:

# Ambari Admin View编译成功 
[INFO] Ambari Admin View .................................. SUCCESS [ 15.976 s]
3.4 Ambari Metrics Storm Sink编译失败: Could not resolve dependencies for project

报错详情:

[INFO] Ambari Main 2.6.0.0.0 .............................. SUCCESS [  0.816 s]
[INFO] Apache Ambari Project POM 2.6.0.0.0 ................ SUCCESS [  0.131 s]
[INFO] Ambari Web 2.6.0.0.0 ............................... SUCCESS [ 55.226 s]
[INFO] Ambari Views 2.6.0.0.0 ............................. SUCCESS [  0.957 s]
[INFO] Ambari Admin View 2.6.0.0.0 ........................ SUCCESS [01:18 min]
[INFO] utility 1.0.0.0-SNAPSHOT ........................... SUCCESS [02:47 min]
[INFO] ambari-metrics 2.6.0.0.0 ........................... SUCCESS [ 10.792 s]
[INFO] Ambari Metrics Common 2.6.0.0.0 .................... SUCCESS [02:56 min]
[INFO] Ambari Metrics Hadoop Sink 2.6.0.0.0 ............... SUCCESS [03:15 min]
[INFO] Ambari Metrics Flume Sink 2.6.0.0.0 ................ SUCCESS [01:38 min]
[INFO] Ambari Metrics Kafka Sink 2.6.0.0.0 ................ SUCCESS [05:19 min]
[INFO] Ambari Metrics Storm Sink 2.6.0.0.0 ................ FAILURE [ 22.982 s]
.......................................................................................................................
[ERROR] Failed to execute goal on project ambari-metrics-storm-sink: Could not resolve dependencies for project org.apache.ambari:ambari-metrics-storm-sink:jar:2.6.0.0.0: Could not find artifact org.apache.storm:storm-core:jar:1.1.0-SNAPSHOT in apache-hadoop (http://repo.hortonworks.com/content/groups/public/) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :ambari-metrics-storm-sink

报错原因:

ambari-metrics模块下,ambari-metrics-storm-sink部分的pom.xml文件里
storm的版本号配置有误,按照配置的版本号无法在仓库找到对应jar包

下图为其默认配置:

在这里插入图片描述

解决方案:

修改ambari-metrics模块下,ambari-metrics-storm-sink部分的pom.xml文件,修改如下:

 <properties>
    <storm.version>1.1.0</storm.version>
  </properties>

解决结果:

# Ambari Metrics Storm Sink编译成功
[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.970 s]
[INFO] Ambari Metrics Storm Sink (Legacy) ................. SUCCESS [  2.400 s]
3.5 Ambari Server编译失败: Unable to parse configuration of mojo

详细报错:

[INFO] Downloaded from alimaven: http://maven.aliyun.com/nexus/content/repositories/central/org/codehaus/groovy/groovy-all/2.4.3/groovy-all-2.4.3.jar (7.0 MB at 2.9 MB/s)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main 2.6.0.0.0 .............................. SUCCESS [  0.828 s]
[INFO] Apache Ambari Project POM 2.6.0.0.0 ................ SUCCESS [  0.126 s]
[INFO] Ambari Web 2.6.0.0.0 ............................... SUCCESS [ 55.103 s]
[INFO] Ambari Views 2.6.0.0.0 ............................. SUCCESS [  0.458 s]
[INFO] Ambari Admin View 2.6.0.0.0 ........................ SUCCESS [ 16.401 s]
[INFO] utility 1.0.0.0-SNAPSHOT ........................... SUCCESS [  0.079 s]
[INFO] ambari-metrics 2.6.0.0.0 ........................... SUCCESS [  0.319 s]
[INFO] Ambari Metrics Common 2.6.0.0.0 .................... SUCCESS [  5.443 s]
[INFO] Ambari Metrics Hadoop Sink 2.6.0.0.0 ............... SUCCESS [  2.458 s]
[INFO] Ambari Metrics Flume Sink 2.6.0.0.0 ................ SUCCESS [  2.046 s]
[INFO] Ambari Metrics Kafka Sink 2.6.0.0.0 ................ SUCCESS [  1.832 s]
[INFO] Ambari Metrics Storm Sink 2.6.0.0.0 ................ SUCCESS [  3.541 s]
[INFO] Ambari Metrics Storm Sink (Legacy) 2.6.0.0.0 ....... SUCCESS [  2.670 s]
[INFO] Ambari Metrics Collector 2.6.0.0.0 ................. SUCCESS [01:40 min]
[INFO] Ambari Metrics Monitor 2.6.0.0.0 ................... SUCCESS [  1.243 s]
[INFO] Ambari Metrics Grafana 2.1.0.0.0 ................... SUCCESS [  8.008 s]
[INFO] Ambari Metrics Assembly 2.6.0.0.0 .................. SUCCESS [01:01 min]
[INFO] Ambari Server 2.6.0.0.0 ............................ FAILURE [53:05 min]
[INFO] Ambari Functional Tests 2.6.0.0.0 .................. SKIPPED
[INFO] Ambari Agent 2.6.0.0.0 ............................. SKIPPED
[INFO] Ambari Client 2.6.0.0.0 ............................ SKIPPED
[INFO] Ambari Python Client 2.6.0.0.0 ..................... SKIPPED
[INFO] Ambari Groovy Client 2.6.0.0.0 ..................... SKIPPED
[INFO] Ambari Shell 2.6.0.0.0 ............................. SKIPPED
[INFO] Ambari Python Shell 2.6.0.0.0 ...................... SKIPPED
[INFO] Ambari Groovy Shell 2.6.0.0.0 ...................... SKIPPED
[INFO] ambari-logsearch 2.6.0.0.0 ......................... SKIPPED
[INFO] Ambari Logsearch Appender 2.6.0.0.0 ................ SKIPPED
[INFO] Ambari Logsearch Portal 2.6.0.0.0 .................. SKIPPED
[INFO] Ambari Logsearch Log Feeder 2.6.0.0.0 .............. SKIPPED
[INFO] Ambari Logsearch Solr Client 2.6.0.0.0 ............. SKIPPED
[INFO] Ambari Infra Solr Plugin 2.6.0.0.0 ................. SKIPPED
[INFO] Ambari Logsearch Assembly 2.6.0.0.0 ................ SKIPPED
[INFO] Ambari Logsearch Integration Test 2.6.0.0.0 ........ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  57:28 min
[INFO] Finished at: 2020-09-16T21:18:21+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (findbugs) on project ambari-server: Unable to parse configuration of mojo org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs for parameter pluginArtifacts: Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}' of type java.util.Collections.UnmodifiableRandomAccessList to property of type java.util.ArrayList -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginConfigurationException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :ambari-server

问题原因:

这个是maven导致的错误,可能的原因有两个:

  1. 如果maven版本是3.5.4以上,应该是版本过高导致的
  2. 还有一种可能就是Maven下载成功之后，修改了镜像或者是配置文件,有些jar包下载不下来导致的

解决方案: 降低maven版本(我最初配置的是3.6.3版本), 在3.3.9到3.5.4版本之间选择一个

配置之后的maven版本:
在这里插入图片描述

解决结果:

# 不再报该错误,报错The entity name must immediately follow the '&' in the entity reference
# 该错误请参考3.6
3.6 Ambari Server编译失败: The entity name must immediately follow the ‘&’ in the entity reference

详细报错:

[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main 2.6.0.0.0 .............................. SUCCESS [  1.405 s]
[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.131 s]
[INFO] Ambari Web ......................................... SUCCESS [ 55.516 s]
[INFO] Ambari Views ....................................... SUCCESS [  0.691 s]
[INFO] Ambari Admin View .................................. SUCCESS [ 17.159 s]
[INFO] utility 1.0.0.0-SNAPSHOT ........................... SUCCESS [  0.160 s]
[INFO] ambari-metrics ..................................... SUCCESS [  0.493 s]
[INFO] Ambari Metrics Common .............................. SUCCESS [  5.426 s]
[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  2.823 s]
[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  2.278 s]
[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  1.986 s]
[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.937 s]
[INFO] Ambari Metrics Storm Sink (Legacy) ................. SUCCESS [  2.428 s]
[INFO] Ambari Metrics Collector ........................... SUCCESS [01:33 min]
[INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.271 s]
[INFO] Ambari Metrics Grafana 2.1.0.0.0 ................... SUCCESS [  2.801 s]
[INFO] Ambari Metrics Assembly ............................ SUCCESS [01:14 min]
[INFO] Ambari Server ...................................... FAILURE [02:34 min]
[INFO] Ambari Functional Tests ............................ SKIPPED
[INFO] Ambari Agent ....................................... SKIPPED
[INFO] Ambari Client ...................................... SKIPPED
[INFO] Ambari Python Client ............................... SKIPPED
[INFO] Ambari Groovy Client ............................... SKIPPED
[INFO] Ambari Shell ....................................... SKIPPED
[INFO] Ambari Python Shell ................................ SKIPPED
[INFO] Ambari Groovy Shell ................................ SKIPPED
[INFO] ambari-logsearch ................................... SKIPPED
[INFO] Ambari Logsearch Appender .......................... SKIPPED
[INFO] Ambari Logsearch Portal ............................ SKIPPED
[INFO] Ambari Logsearch Log Feeder ........................ SKIPPED
[INFO] Ambari Logsearch Solr Client ....................... SKIPPED
[INFO] Ambari Infra Solr Plugin ........................... SKIPPED
[INFO] Ambari Logsearch Assembly .......................... SKIPPED
[INFO] Ambari Logsearch Integration Test 2.6.0.0.0 ........ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:00 min
[INFO] Finished at: 2020-09-17T09:57:12+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:xml-maven-plugin:1.0:transform (default) on project ambari-server: Failed to transform input file /opt/ambari/apache-ambari-2.6.0-src/ambari-server/target/findbugs/findbugsXml.html: The entity name must immediately follow the '&' in the entity reference. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :ambari-server

问题原因:

从报错来看是&这个符号使用的问题,导致文件编译出现问题

具体的原因可参考stackoverflow的这篇问答:

The entity name must immediately follow the ‘&’ in the entity reference

解决方案:
因为报错的findbugsXml.html文件内容过多,找出文件问题并改正成本太高,所以选择了修改ambari-server的pom.xml文件,将findbugs部分内容注释掉:

需要注释部分的原文:
在这里插入图片描述

修改之后:

      <executions>
          <!-- <execution>
            <phase>verify</phase>
            <goals> 
              <goal>check</goal>
            </goals>
          </execution> -->
        </executions>
      </plugin>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>xml-maven-plugin</artifactId>
        <version>1.0</version>
        <executions>
          <!--    
           <execution>
            <phase>verify</phase>
            <goals> 
              <goal>transform</goal>
            </goals>
          </execution>
          -->     
        </executions>

解决结果

# 该问题得到解决,编译时抛出了新的错误:
Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1.4:rpm (default-cli) on project ambari-server

# 该问题的处理方法请参照3.7
3.7 Ambari Server编译失败: Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1.4:rpm (default-cli) on project ambari-server
[INFO] Bytecompiling .py files below /opt/ambari/apache-ambari-2.6.0-src/ambari-server/target/rpm/ambari-server/buildroot/usr/lib/python2.6 using /usr/bin/python2.6
[INFO] /usr/lib/rpm/brp-python-bytecompile: line 38: /usr/bin/python2.6: No such file or directory
[INFO] error: Bad exit status from /var/tmp/rpm-tmp.c817Ww (%install)
[INFO] 
[INFO] 
[INFO] RPM build errors:
[INFO]     Bad exit status from /var/tmp/rpm-tmp.c817Ww (%install)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main 2.6.0.0.0 .............................. SUCCESS [  0.780 s]
[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.132 s]
[INFO] Ambari Web ......................................... SUCCESS [ 55.137 s]
[INFO] Ambari Views ....................................... SUCCESS [  0.432 s]
[INFO] Ambari Admin View .................................. SUCCESS [ 16.003 s]
[INFO] utility 1.0.0.0-SNAPSHOT ........................... SUCCESS [  0.076 s]
[INFO] ambari-metrics ..................................... SUCCESS [  0.287 s]
[INFO] Ambari Metrics Common .............................. SUCCESS [  4.914 s]
[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  2.738 s]
[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  2.263 s]
[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  1.938 s]
[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.701 s]
[INFO] Ambari Metrics Storm Sink (Legacy) ................. SUCCESS [  2.364 s]
[INFO] Ambari Metrics Collector ........................... SUCCESS [01:35 min]
[INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.146 s]
[INFO] Ambari Metrics Grafana 2.1.0.0.0 ................... SUCCESS [  8.122 s]
[INFO] Ambari Metrics Assembly ............................ SUCCESS [01:24 min]
[INFO] Ambari Server ...................................... FAILURE [01:15 min]
[INFO] Ambari Functional Tests ............................ SKIPPED
[INFO] Ambari Agent ....................................... SKIPPED
[INFO] Ambari Client ...................................... SKIPPED
[INFO] Ambari Python Client ............................... SKIPPED
[INFO] Ambari Groovy Client ............................... SKIPPED
[INFO] Ambari Shell ....................................... SKIPPED
[INFO] Ambari Python Shell ................................ SKIPPED
[INFO] Ambari Groovy Shell ................................ SKIPPED
[INFO] ambari-logsearch ................................... SKIPPED
[INFO] Ambari Logsearch Appender .......................... SKIPPED
[INFO] Ambari Logsearch Portal ............................ SKIPPED
[INFO] Ambari Logsearch Log Feeder ........................ SKIPPED
[INFO] Ambari Logsearch Solr Client ....................... SKIPPED
[INFO] Ambari Infra Solr Plugin ........................... SKIPPED
[INFO] Ambari Logsearch Assembly .......................... SKIPPED
[INFO] Ambari Logsearch Integration Test 2.6.0.0.0 ........ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:55 min
[INFO] Finished at: 2020-09-17T10:53:16+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:rpm-maven-plugin:2.1.4:rpm (default-cli) on project ambari-server: RPM build execution returned: '1' executing '/bin/sh -c cd '/opt/ambari/apache-ambari-2.6.0-src/ambari-server/target/rpm/ambari-server/SPECS' && 'rpmbuild' '-bb' '--target' 'x86_64-redhat-linux' '--buildroot' '/opt/ambari/apache-ambari-2.6.0-src/ambari-server/target/rpm/ambari-server/buildroot' '--define' '_topdir /opt/ambari/apache-ambari-2.6.0-src/ambari-server/target/rpm/ambari-server' '--define' '_build_name_fmt %%{ARCH}/%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm' '--define' '_builddir %{_topdir}/BUILD' '--define' '_rpmdir %{_topdir}/RPMS' '--define' '_sourcedir %{_topdir}/SOURCES' '--define' '_specdir %{_topdir}/SPECS' '--define' '_srcrpmdir %{_topdir}/SRPMS' 'ambari-server.spec'' -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :ambari-server

问题原因:

开始看到报错信息有rpm,认为是rpm,或者rpm-build没有安装导致的,使用命令行查看rpm,rpm-build都是正常的

后面在报错信息上面的INFO日志中看到如下信息:
/usr/lib/rpm/brp-python-bytecompile: line 38: /usr/bin/python2.6: No such file or directory

推测是该问题导致的编译失败

解决方案

因为装的是python2.7，有个python2.7的文件，所以建立软连接指向该文件

# 建立软连接指向/usr/bin/python2.6
ln -s /usr/bin/python2.7 /usr/bin/python2.6

之后重新编译

解决结果:

# Ambari Server终于编译成功!
[INFO] Ambari Server ...................................... SUCCESS [02:30 min]
3.8 Ambari Groovy Shell编译失败: Could not resolve dependencies for project org.apache.ambari:ambari-groovy-shell:jar:2.6.0.0.0
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main 2.6.0.0.0 .............................. SUCCESS [  0.810 s]
[INFO] Apache Ambari Project POM .......................... SUCCESS [  0.134 s]
[INFO] Ambari Web ......................................... SUCCESS [ 55.390 s]
[INFO] Ambari Views ....................................... SUCCESS [  0.421 s]
[INFO] Ambari Admin View .................................. SUCCESS [ 16.168 s]
[INFO] utility 1.0.0.0-SNAPSHOT ........................... SUCCESS [  0.094 s]
[INFO] ambari-metrics ..................................... SUCCESS [  0.287 s]
[INFO] Ambari Metrics Common .............................. SUCCESS [  5.606 s]
[INFO] Ambari Metrics Hadoop Sink ......................... SUCCESS [  2.669 s]
[INFO] Ambari Metrics Flume Sink .......................... SUCCESS [  2.226 s]
[INFO] Ambari Metrics Kafka Sink .......................... SUCCESS [  1.962 s]
[INFO] Ambari Metrics Storm Sink .......................... SUCCESS [  2.767 s]
[INFO] Ambari Metrics Storm Sink (Legacy) ................. SUCCESS [  2.400 s]
[INFO] Ambari Metrics Collector ........................... SUCCESS [01:31 min]
[INFO] Ambari Metrics Monitor ............................. SUCCESS [  1.156 s]
[INFO] Ambari Metrics Grafana 2.1.0.0.0 ................... SUCCESS [  7.677 s]
[INFO] Ambari Metrics Assembly ............................ SUCCESS [01:13 min]
[INFO] Ambari Server ...................................... SUCCESS [02:30 min]
[INFO] Ambari Functional Tests ............................ SUCCESS [  1.422 s]
[INFO] Ambari Agent ....................................... SUCCESS [02:05 min]
[INFO] Ambari Client ...................................... SUCCESS [  0.136 s]
[INFO] Ambari Python Client ............................... SUCCESS [  1.058 s]
[INFO] Ambari Groovy Client ............................... SUCCESS [ 13.309 s]
[INFO] Ambari Shell ....................................... SUCCESS [  0.133 s]
[INFO] Ambari Python Shell ................................ SUCCESS [  0.672 s]
[INFO] Ambari Groovy Shell ................................ FAILURE [04:39 min]
[INFO] ambari-logsearch ................................... SKIPPED
[INFO] Ambari Logsearch Appender .......................... SKIPPED
[INFO] Ambari Logsearch Portal ............................ SKIPPED
[INFO] Ambari Logsearch Log Feeder ........................ SKIPPED
[INFO] Ambari Logsearch Solr Client ....................... SKIPPED
[INFO] Ambari Infra Solr Plugin ........................... SKIPPED
[INFO] Ambari Logsearch Assembly .......................... SKIPPED
[INFO] Ambari Logsearch Integration Test 2.6.0.0.0 ........ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 13:58 min
[INFO] Finished at: 2020-09-17T11:52:52+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ambari-groovy-shell: Could not resolve dependencies for project org.apache.ambari:ambari-groovy-shell:jar:2.6.0.0.0: Failed to collect dependencies at org.springframework.shell:spring-shell:jar:1.1.0.RC3: Failed to read artifact descriptor for org.springframework.shell:spring-shell:jar:1.1.0.RC3: Could not transfer artifact org.springframework.shell:spring-shell:pom:1.1.0.RC3 from/to spring-milestones (http://repo.spring.io/milestone): Access denied to: http://repo.spring.io/milestone/org/springframework/shell/spring-shell/1.1.0.RC3/spring-shell-1.1.0.RC3.pom , ReasonPhrase:Forbidden. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :ambari-groovy-shell

报错原因:

这种报错是在jar包下载过程中出现的问题

类似的报错,主要有以下几种可能性
可以参照报错提示给出的链接:
DependencyResolutionException

首先根据报错提示访问了Access denied to: 指向的链接

界面显示如下:

在这里插入图片描述

去maven本地仓库查看该jar包,果然有问题:

在这里插入图片描述

到这里,开始怀疑是 ambari-shell/ambari-groovy-shell模块的pom.xml文件文件有问题
发现该配置文件下和报错有关的配置如下:

 <dependency>
      <groupId>org.springframework.shell</groupId>
      <artifactId>spring-shell</artifactId>
    </dependency>

根据关键字spring-shell去maven资料库查询,maven资料库链接如下:

maven资料库查询链接

发现spring-shell没有对应于上述pom.xml文件的配置

在这里插入图片描述

解决方案:

 vi ambari-shell/ambari-groovy-shell/pom.xml

修改spring-shell部分配置为如下:

 <dependency>
      <groupId>org.springframework.shell</groupId>
      <artifactId>spring-shell</artifactId>
      <version>1.1.0.RELEASE</version>
    </dependency>

修改之后重新编译

解决结果:

#  Ambari Groovy Shell编译成功
[INFO] Ambari Groovy Shell ................................ SUCCESS [07:49 min]
3.9 Failed to execute goal com.github.eirslett:frontend-maven-plugin

报错详情:

Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.4:yarn (yarn install) on project ambari-web:
 Failed to run task: 'yarn install --ignore-engines --pure-lockfile' failed.

报错原因:
nodejs会通过 yarn去加载依赖包,网络不稳定的时候会出现该问题,比较常见

解决方案:
保证网络环境稳定

四. 安装配置Ambari

4.1 安装配置Ambari Server

执行安装命令前,首先修改ambari-server文件

vi /usr/sbin/ambari-server

将文件标红部分,如下图:
在这里插入图片描述
修改为:

HASH="${VERSION}"

这是为了防止执行ambari-server setup出现问题:
/usr/sbin/ambari-server: line 34: buildNumber: unbound variable

安装ambari-server


yum install ambari-server/target/rpm/ambari-server/RPMS/x86_64/ambari-server*.rpm

ambari-server setup

注意:设置jdk时,应该选择3,然后输入1.2.1过程中设置的JAVA_HOME路径

执行情况如下:

Using python  /usr/bin/python
Setup ambari-server
Checking SELinux...
SELinux status is 'disabled'
Customize user account for ambari-server daemon [y/n] (n)? n
Adjusting ambari-server permissions and ownership...
Checking firewall status...
Checking JDK...
[1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
[2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
[3] Custom JDK
==============================================================================
Enter choice (1): 3
WARNING: JDK must be installed on all hosts and JAVA_HOME must be valid on all hosts.
WARNING: JCE Policy files are required for configuring Kerberos security. If you plan to use Kerberos,please make sure JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts.
Path to JAVA_HOME: /opt/modules/jdk1.8.0_151
Validating JDK on Ambari Server...done.
Completing setup...
Configuring database...
Enter advanced database configuration [y/n] (n)? n
Configuring database...
Default properties detected. Using built-in database.
Configuring ambari database...
Checking PostgreSQL...
Running initdb: This may take up to a minute.
Initializing database ... OK


About to start PostgreSQL
Configuring local database...
Configuring PostgreSQL...
Restarting PostgreSQL
Creating schema and user...
done.
Creating tables...
done.
Extracting system views...
ambari-admin-2.6.0.0.0.jar

Adjusting ambari-server permissions and ownership...
Ambari Server 'setup' completed successfully.

启动ambari server

ambari-server start

在这里插入图片描述

成功启动后在浏览器输入Ambari地址：
http://ip:<port_number>

注意: port_number默认8080,我这里设置的8083,页面访问的账户名和密码都是admin

在这里插入图片描述

4.2 安装配置Ambari Agent

安装ambari-agent

yum install ambari-agent/target/rpm/ambari-agent/RPMS/x86_64/ambari-agent-*.rpm

启动ambari-agent之前,首先修改该文件,
防止出现类似4.1中类似ambari-server出现的错误

vi /var/lib/ambari-agent/bin/ambari-agent
# 将HASH="${buildNumber}"修改为:  HASH="${VERSION}"

编辑ambari server的位置

vi /etc/ambari-agent/conf/ambari-agent.ini
# 修改hostname一行为ambari-server对应的主机名

# 在security下面添加如下行:force_https_protocol=PROTOCOL_TLSv1_2,确保有下图所示的两个配置

在这里插入图片描述

启动ambari-agent

ambari-agent start

在这里插入图片描述

如果有异常请查看日志:/var/log/ambari-agent/ambari-agent.log

4.3 修改yum源,离线安装HDP及HDP-UTILS

安装httpd服务（主服务器）

yum -y install httpd
service httpd restart
chkconfig httpd on

将HDP,HDP-UTILS安装包放到/var/www/html目录下

HDP-2.6.3.0版本下载链接

HDP-UTILS-1.1.0.21版本下载链接

# 将从上述下载链接下载的文件拷贝到该目录下
mkdir -p /var/www/html/ambari
cd /var/www/html/ambari
tar -zxvf HDP-2.6.3.0-centos7-rpm.tar.gz 
mkdir HDP-UTILS
tar -zxvf HDP-UTILS-1.1.0.21-centos7.tar.gz -C HDP-UTILS
rm -rf  HDP-2.6.3.0-centos7-rpm.tar.gz HDP-UTILS-1.1.0.21-centos7.tar.gz

现在可以通过http://ip/ambari/查看能否成功访问

在这里插入图片描述

制作本地源

  1. 安装本地源制作相关工具
yum install yum-utils createrepo yum-plugin-priorities -y
createrepo  ./
  1. 修改文件里面的源地址
vi HDP/centos7/2.6.3.0-235/hdp.repo

修改如下:

#VERSION_NUMBER=2.6.3.0-235
[HDP-2.6.3.0]
name=HDP Version - HDP-2.6.3.0
baseurl=http://ip/ambari/HDP/centos7/2.6.3.0-235
gpgcheck=1
gpgkey=http://ip/ambari/HDP/centos7/2.6.3.0-235/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1


[HDP-UTILS-1.1.0.21]
name=HDP-UTILS Version - HDP-UTILS-1.1.0.21
baseurl=http://ip/ambari/HDP-UTILS
gpgcheck=1
gpgkey=http://ip/ambari/HDP-UTILS/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1

注意: 修改时需要将我这里的ip换为自己实际ip地址

  1. yum缓存
yum clean all
yum makecache
yum repolist
4.4 安装部署hdp
  1. 登录
    默认管理员登录,账户密码均为admin
  2. 安装
    在这里插入图片描述

Get Started配置集群名字

选择版本并修改为本地源地址

在这里插入图片描述

Install Options配置主机名和ssh秘钥文件id_rsa

注意:秘钥文件在~/.ssh目录下

后续部分按照页面提示一一配置即可~
具体细节可以参照博客:

Ambari2.6.0安装HDP2.6.3链接

遇到问题可参考我的博客:

Ambari踩过的坑及解决方案

五. ambari2.6.0安装配置遇到的问题及解决方案

5.1 ambari server启动报错: java.net.BindException: Address already in use

详细报错:

# 查看server日志
cat /var/log/ambari-server/ambari-server.log

17 Sep 2020 17:44:38,714 ERROR [main] AmbariServer:1073 - Failed to run the Ambari Server
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.eclipse.jetty.server.nio.SelectChannelConnector.open(SelectChannelConnector.java:187)
	at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:316)
	at org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:265)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
	at org.eclipse.jetty.server.Server.doStart(Server.java:293)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
	at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:558)
	at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1067)

报错原因:

8080端口号被占用

如图,端口号被k8s应用占用

在这里插入图片描述

解决办法:

  1. 杀掉占用8080端口号的进程
  2. 更换ambari-server端口号,我这里选用的是第二种
# 修改ambari配置文件
vi /etc/ambari-server/conf/ambari.properties

# 增加这一行
client.api.port=<port_number>

执行结束之后,重启ambari-server

ambari-server start

解决结果:

如图,界面可以访问!

在这里插入图片描述

5.2 ambari agent启动报错: SSLError: Failed to connect. Please check openssl library versions

报错详情:agent启动后无法注册成为ambari节点,界面显示Fail

日志如下:

cat /var/log/ambari-agent/ambari-agent.log 

WARNING 2020-09-18 14:46:52,865 NetUtil.py:124 - Server at https://hdpamb154:8440 is not reachable, sleeping for 10 seconds...
INFO 2020-09-18 14:47:02,865 NetUtil.py:70 - Connecting to https://hdpamb154:8440/ca
ERROR 2020-09-18 14:47:02,867 NetUtil.py:96 - EOF occurred in violation of protocol (_ssl.c:618)
ERROR 2020-09-18 14:47:02,867 NetUtil.py:97 - SSLError: Failed to connect. Please check openssl library versions. 
Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more details.

报错原因:
https连接失败

解决方案:

  1. 首先按照提示检查openssl版本
openssl version # 如果低于 openssl-1.0.1e-16.el6.x86_64 版本，则需要更新到 openssl-1.0.1e-16.el6.x86_64 及以上版本

2.将 [https] 节的 verify 项设为禁用

vi /etc/python/cert-verification.cfg

# 在配置中更改下列参数
[https]
verify=disable
  1. 编辑 /etc/ambari-agent/conf/ambari-agent.ini 配置文件，在 [security] 节部分，确保设置如下两个值，其它值保持不变：
vi /etc/ambari-agent/conf/ambari-agent.ini


[security]
ssl_verify_cert=0
force_https_protocol=PROTOCOL_TLSv1_2

之后重启ambari-agent

ambari-agent restart

解决详情:

节点注册成功
在这里插入图片描述

new个对象先
关注
  • 4
    点赞
  • 踩
  • 8
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Ambari 2.6.1源码编译问题汇总
周源的专栏
03-01 6043
1、[INFO] Ambari Admin View .................................. FAILURE [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (Bower install) on project ambari-admin: Command ex...
Ambari2.6源码编译之ambari-web
shirukai
06-28 1637
Ambari编译之ambari-web 1.准备 1.1下载源码 安装wget yum -y install wget 下载源码 将源码下载到/opt目录下 wget http://www.apache.org/dist/ambari/ambari-2.6.0/apache-ambari-2.6.0-src.tar.gz -O /opt/apache-amba...
ambari源码编译教程
u012361112的博客
04-27 1319
前言 ambari源码编译是一个非常痛苦的过程，其官网上的编译资料非常少。本人在尝试编译ambari编码的过程中，遇到了非常多的问题，特别是ambari-web模块，吃了不少苦头。本文介绍的是ambari-2.4.0.0的源码编译过程，如果是高版本编译，可能会少一些问题。编译环境基本从零构建，我相信本教程应该适用绝大多数用户。 一、编译环境准备 1. 安装必要的编译工具： yum ins...
Ambari【部署 01】最新版本ambari-2
最新发布
2401_84545016的博客
05-16 682
需要完整版PDF学习资源Ambari本次安装的为当前最新版本。
ambari 2.6.0.0开发环境配置
weixin_34090562的博客
11-06 263
ambari 2.6.0.0开发环境配置 安装git 安装依赖 yum -y install curl-devel expat-devel gettext-devel openssl-devel zlib-devel gcc python-devel yum -yasciidoc xmlto texinfo perl-XML-SAX 安...
Ambari源码编译、安装（包括异常处理）
m0_51205511的博客
12-10 5931
本篇文章以实践做记录总结在Redhat上编译、安装 ambari-2.7.4 源码以及安装服务的全部过程，文章基本是涵盖了所有步骤，可依据此文章逐步编译、安装成功。
Ambari 2.6.0 安装部署文档
01-14
Ambari Hadoop & Spark安装部署文档，Ambari在线安装与问题解决
ambari-Kylin:Ambari集成Apache Kylin服务（离线部署、可支持HDP2.6+及HDP3.0+）
05-09
如果您在使用过程中遇到任何问题，可扫描下方二维码关注公众号【大数据实战演练】或者加我好友【create17_】，回复【加群】，群内有不少已经搭建成功的小伙伴。 概述 目前上传至ambari-Kylin上的有两个版本，一个是...
RedHat6.4全自动安装Ambari2.6.0详细教程(图文一步步)
11-23
在本教程中，我们将深入探讨如何在RedHat 6.4 (CentOS兼容)系统上进行Ambari 2.6.0的全自动安装。Ambari是Hortonworks提供的一个强大工具，用于管理和监控Hadoop生态系统，包括Hadoop、HBase、YARN等组件。以下是一...
grafanarel.s3.amazonaws.com-grafana-2.6.0-linux64.tgz
05-08
ambari编译依赖的grafana，一般找不到，大家懂得；Could not find artifact org.apache.phoenix:phoenix-core:jar:4.4.0.2.3.4.0-3347，或者hbase、grafana、hadoop 和官方的其实是一样的，放心下载, 原名称是...
grafana-2.6.0.linux-x64.tar.gz
07-11
ambari源码编译安装。被墙掉的资源文件，修改pom文件，网络地址改为上传文件后的本地路径，即可编译通过
ambari2.6.2源码编译
chengbai121444的博客
11-17 564
环境准备 系统选择：centos6.5 64位 关闭selinux：sed -i '/SELINUX/s/enforcing/disabled/' /etc/selinux/config 关闭防火墙： service iptables stop chkconfig iptables off service iptables status 安装jdk 先卸载原有的 安装配...
dubbo3 源码学习 编译报错的解决
a25017012的博客
11-07 510
从https://github.com/apache/dubbo 下载项目 然后安装 maven 要3.5 版本往上（必须，要不） 然后执行 mvn install -Dmaven.test.skip=true 然后 如果是要导入 idea 执行 mvn idea:idea 如果是要导入 eclipse 执行 mvn eclipse:eclipse 然后最后一步 导入 eclipse之前 进入eclipse 选择 windows -》lifecycle mapping ...
Ambari 2.7.3版本编译报错各问题解决
周源的专栏
04-02 8696
执行编译命令：# mvn -B clean install rpm:rpm -DnewVersion=2.7.3.0.0 -DskipTests -Dpython.ver="python >= 2.6" -Drat.skip=true -X 1、报错： [DEBUG] Configuring mojo org.apache.rat:apache-rat-plugin:0.12:check...
Android系统编译问题总结
xiaoyantan的博客
11-26 8834
1、编译9.0的时候报错如下： vendor/qcom/proprietary/camx/src/core/camxpropertyblob.h:169:10: fatal error: ‘g_camxproperties.h’ file not found #include “g_camxproperties.h” ^~~~~~~~~~~~~~~~~~~~ 1 error generated. ...
Ambari源码编译
韩小侠的专栏 已迁移至lssea.com
01-26 7562
Ambar为Apache基金会的一个顶级项目。作为一个为Hadoop系统提供一站式维护的工具，ambari支持通过web页面/RestfulApi的方式进行对集群的一键部署，最重要的是可以自己编写部署脚本部署自己的分布式系统。这个是富有价值的，现在有的公司使用的是自研的分布式框架，想要自动部署大多也是自研一套分布式框架。现在Ambari的出现，缓解了这个问题，用户只需要使用python按照规则编写
Android 9.0编译出现等待，不能make的问题
lwz的博客
11-14 2128
问题描述：Waiting up to 10s to lock out/.lock to ensure no other Soong process is running in the same output directory 解决方法：出现上种情况只要make clean下根程在new一个新的就可以了
yum安装报错Error: Package时
热门推荐
u014516601的博客
06-06 2万+
当用yum安装时报错。。。 Error: Package: glibc-headers-2.17-196.el7_4.2.x86_64 (ultra-centos-7.4-updates) Requires: glibc = 2.17-196.el7_4.2 Installed: glibc-2.17-222.el7.x86_64 (installed...
docker ambari-agent 设置ambari-server ip
06-08
要在Docker容器中设置Ambari-agent的Ambari-server IP地址，可以使用以下步骤： 1. 启动Ambari-agent容器时，使用`-e`选项设置`AMBARI_SERVER_HOST`环境变量，并将其设置为Ambari-server的IP地址。例如： ``` docker run -e AMBARI_SERVER_HOST=<ambari_server_ip> ... ``` 2. 在容器内部，编辑`/etc/ambari-agent/conf/ambari-agent.ini`文件，将`[server]`部分中的`hostname`设置为Ambari-server的IP地址。例如： ``` [server] hostname = <ambari_server_ip> ``` 3. 重启Ambari-agent服务，以使更改生效。例如： ``` ambari-agent restart ``` 这样，Ambari-agent将能够与指定的Ambari-server进行通信。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值