RHEL 7.8 - Execution failed for task ':datahub-web:execYarn'.
See original GitHub issueContext: I have formerly successfully setup and tested features of DataHub on Ubuntu 18.04 LTS by creating Docker Containers for each component in the following order 1- MySQL 2- ElasticSearch + Kibana 3- Neo4J 4- Kafka + ZooKeeper + Schema Reg. 5- DataHub GMS 6- Frontend 7- MCE Consumer 8-MAE Consumer 9-MCE Ingestion I was able to setup the core Datahub components
Problem: While replicating the same setup on a Red Hat 7.8 Distribution (Limitation to use this OS) on an EC2 - the Frontend service fails to build with the following error logs. The only important thing I have changed apart from the Flavor of Linux is Images Default Directory from “default” to my “directory-in-non-root-ebs-partition”.
Error Logs:
> Task :datahub-web:execYarn
[4/4] Building fresh packages...
> Task :metadata-events:mxe-utils-avro-1.7:classes
> Task :metadata-events:mxe-utils-avro-1.7:jar
> Task :metadata-dao-impl:elasticsearch-dao:classes
> Task :metadata-dao-impl:elasticsearch-dao:jar
> Task :metadata-utils:compileJava
> Task :metadata-utils:classes
> Task :metadata-utils:jar
error /datahub-src/datahub-web/node_modules/broccoli-eyeglass/node_modules/node-sass, /datahub-src/datahub-web/node_modules/eyeglass/node_modules/node-sass: Command failed.
Exit code: 1
Command: node scripts/build.js
Arguments:
Directory: /datahub-src/datahub-web/node_modules/broccoli-eyeglass/node_modules/node-sass
Output:
Building: /datahub-src/datahub-web/build/nodejs/node-v10.6.0-linux-x64/bin/node /datahub-src/datahub-web/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ '/datahub-src/datahub-web/build/nodejs/node-v10.6.0-linux-x64/bin/node',
gyp verb cli '/datahub-src/datahub-web/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library=' ]
gyp info using node-gyp@3.8.0
gyp info using node@10.6.0 | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` succeeded python2 /usr/bin/python2
gyp verb check python version `/usr/bin/python2 -c "import sys; print "2.7.16
gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %j
gyp verb get node dir no --target version specified, falling back to host node version: 10.6.0
gyp verb command install [ '10.6.0' ]
gyp verb install input version string "10.6.0"
gyp verb install installing version: 10.6.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 10.6.0
gyp verb ensuring nodedir is created /root/.node-gyp/10.6.0
gyp verb created nodedir /root/.node-gyp
gyp http GET https://nodejs.org/download/release/v10.6.0/node-v10.6.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v10.6.0/node-v10.6.0-headers.tar.gz
gyp verb extracted file from tarball include/node/common.gypi
gyp verb extracted file from tarball include/node/config.gypi
gyp verb extracted file from tarball include/node/node.h
gyp verb extracted file from tarball include/node/node_api.h
gyp verb extracted file from tarball include/node/node_api_types.h
gyp verb extracted file from tarball include/node/node_buffer.h
gyp verb extracted file from tarball include/node/node_object_wrap.h
gyp verb extracted file from tarball include/node/node_version.h
gyp verb extracted file from tarball include/node/uv.h
gyp verb extracted file from tarball include/node/v8-inspector-protocol.h
gyp verb extracted file from tarball include/node/v8-inspector.h
.
.
.
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir /root/.node-gyp/10.6.0
gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at getNotFoundError (/datahub-src/datahub-web/node_modules/which/which.js:13:12)
gyp ERR! stack at F (/datahub-src/datahub-web/node_modules/which/which.js:68:19)
gyp ERR! stack at E (/datahub-src/datahub-web/node_modules/which/which.js:80:29)
gyp ERR! stack at /datahub-src/datahub-web/node_modules/which/which.js:89:16
gyp ERR! stack at /datahub-src/datahub-web/node_modules/isexe/index.js:42:5
gyp ERR! stack at /datahub-src/datahub-web/node_modules/isexe/mode.js:8:5
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:158:21)
gyp ERR! System Linux 3.10.0-1127.el7.x86_64
gyp ERR! command "/datahub-src/datahub-web/build/nodejs/node-v10.6.0-linux-x64/bin/node" "/datahub-src/datahub-web/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /datahub-src/datahub-web/node_modules/broccoli-eyeglass/node_modules/node-sass
gyp ERR! node -v v10.6.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
> Task :datahub-web:execYarn FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':datahub-web:execYarn'.
> Process 'command '/datahub-src/datahub-web/build/yarn/yarn-v1.13.0/bin/yarn'' finished with non-zero exit value 1
* 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 2m 57s
I have shortened the log a bit. I can provide complete one if required.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top GitHub Comments
Yes, seems like your DB is somehow not initialized properly. As pointed out by @clojurians-org running that init script directly should fix the login issue.
for login related error: you should check gms backend log and mainly it’s mysql store backend.