03-Centos7安装部署Mirrorgate-踩坑记录

FAQ

1.没有安装bzip2

解决方法 yum -y install bzip2

> phantomjs-prebuilt@2.1.16 install /root/test/mirrorgate/mirrorgate-dashboard/node_modules/phantomjs-prebuilt
> node install.js

PhantomJS not found on PATH
Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
Saving to /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
Receiving...
  [========================================] 99%
Received 22866K total.
Extracting tar contents (via spawned process)
Error extracting archive
Phantom installation failed { Error: Command failed: tar jxf /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
tar (child): bzip2：无法 exec: 没有那个文件或目录
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

2.未知错误

google一下貌似跟权限有关系 添加参数

npm install --registry https://registry.npm.taobao.org  --unsafe-perm=true --allow-root

> wd@1.11.0 install /root/test/mirrorgate/mirrorgate-dashboard/node_modules/wd
> node scripts/build-browser-scripts

/root/test/mirrorgate/mirrorgate-dashboard/node_modules/mkdirp/index.js:90
                    throw err0;
                    ^

Error: EACCES: permission denied, mkdir '/root/test/mirrorgate/mirrorgate-dashboard/node_modules/wd/build'
    at Object.mkdirSync (fs.js:750:3)
    at sync (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/mkdirp/index.js:71:13)
    at Object.<anonymous> (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/wd/scripts/build-browser-scripts.js:6:1)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:741:12)
    at startup (internal/bootstrap/node.js:285:19)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: phantomjs-prebuilt@2.1.16 (node_modules/phantomjs-prebuilt):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: phantomjs-prebuilt@2.1.16 install: `node install.js`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wd@1.11.0 install: `node scripts/build-browser-scripts`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wd@1.11.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-11-24T11_45_35_121Z-debug.log

3.未知错误

[root@node1 mirrorgate-dashboard]# gulp dist
fs.js:115
    throw err;
    ^

Error: ENOENT: no such file or directory, scandir '/root/test/mirrorgate/mirrorgate-dashboard/node_modules/node-sass/vendor'
    at Object.readdirSync (fs.js:783:3)
    at Object.getInstalledBinaries (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/node-sass/lib/extensions.js:130:13)
    at foundBinariesList (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/node-sass/lib/errors.js:20:15)
    at foundBinaries (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/node-sass/lib/errors.js:15:5)
    at Object.module.exports.missingBinary (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/node-sass/lib/errors.js:45:5)
    at module.exports (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/node-sass/lib/binding.js:15:30)
    at Object.<anonymous> (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/root/test/mirrorgate/mirrorgate-dashboard/node_modules/gulp-sass/index.js:162:21)
    at Module._compile (internal/modules/cjs/loader.js:688:30)

4.mirrorgate-api使用gradle build失败

[root@node1 mirrorgate-api]# gradle build

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'mirrorgate-api'.
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not resolve org.springframework.boot:spring-boot-gradle-plugin:1.5.3.RELEASE.
     Required by:
         project :
      > Could not resolve org.springframework.boot:spring-boot-gradle-plugin:1.5.3.RELEASE.
         > Could not get resource 'https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-gradle-plugin/1.5.3.RELEASE/spring-boot-gradle-plugin-1.5.3.RELEASE.pom'.
            > Could not GET 'https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-gradle-plugin/1.5.3.RELEASE/spring-boot-gradle-plugin-1.5.3.RELEASE.pom'.
               > Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.40.215] failed: connect timed out

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 32s

很明显仓库地址链接不到，换成国内的仓库地址。

vim build.gradle

buildscript {
    ext {
        springBootVersion = '1.5.3.RELEASE'
    }
    repositories {
        //mavenCentral()
        //jcenter()
        //新增
        repositories {
            maven{ url 'http://maven.aliyun.com/nexus/content/groups/public/'}
        }
    }

    dependencies {
        classpath("org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}")
    }
}

又一个错误，重新执行 gradle build 既然好了

[root@node1 mirrorgate-api]# gradle build
<-------------> 0% EXECUTING [1m 46s]
<-------------> 0% EXECUTING [1m 46s] of :compileClasspath > slack-ap<----------<-------------> 0%<-----<----<<<-<-<> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':compileClasspath'.
> Could not resolve com.github.allbegray:slack-api:v1.4.0.RELEASE.
  Required by:
      project :
   > Skipped due to earlier error
   > Could not resolve com.github.allbegray:slack-api:v1.4.0.RELEASE.
      > Could not get resource 'https://jitpack.io/com/github/allbegray/slack-api/v1.4.0.RELEASE/slack-api-v1.4.0.RELEASE.pom'.
         > Could not GET 'https://jitpack.io/com/github/allbegray/slack-api/v1.4.0.RELEASE/slack-api-v1.4.0.RELEASE.pom'.
            > Connect to jitpack.io:443 [jitpack.io/104.24.22.62, jitpack.io/104.24.23.62, jitpack.io/2606:4700:20:0:0:0:6818:173e, jitpack.io/2606:4700:20:0:0:0:6818:163e] failed: 网络不可达 (connect failed)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.10/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2m 6s
1 actionable task: 1 executed

解决方法： vim build.gralde

repositories {
    mavenCentral()
    maven {
        name "jitpack.io"
        //url "https://jitpack.io"
        url "http://maven.aliyun.com/nexus/content/groups/public/"
    }
}

jre问题，需要安装完整的jdk

> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not find tools.jar. Please check that /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre contains a valid JDK installation.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.10/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 1m 11s
1 actionable task: 1 executed