1

我有一个安装了NodeJS和MongoDB墨盒的OpenShift设备。我已将KeystoneJS添加到，当我尝试推送更新的代码时，由于缺少模块，构建失败。下面的完整错误堆栈。gyp

是否有其他人面临节点/mongo 墨盒缺少 gyp 模块的问题？

谢谢！尼拉夫

remote: Traceback (most recent call last):
remote: File "/opt/rh/v8314/root/usr/bin/gyp", line 15, in 
remote: import gyp
remote: ImportError: No module named gyp
remote: gyp ERR! configure error
remote: gyp ERR! stack Error: gyp failed with exit code: 1
remote: gyp ERR! stack at ChildProcess.onCpExit (/opt/rh/nodejs010/root/usr/lib/node_modules/node-gyp/lib/configure.js:343:16)
remote: gyp ERR! stack at ChildProcess.emit (events.js:98:17)
remote: gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:820:12)
remote: gyp ERR! System Linux 2.6.32-504.16.2.el6.x86_64
remote: gyp ERR! command "node" "/opt/rh/nodejs010/root/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
remote: gyp ERR! cwd /var/lib/openshift/559fa9944382ec4cf1000106/app-root/runtime/repo/node_modules/keystone/node_modules/keystone-utils/node_modules/limax/node_modules/cld
remote: gyp ERR! node -v v0.10.35
remote: gyp ERR! node-gyp -v v1.0.2
remote: gyp ERR! not ok
remote:
remote: npm info cld@2.4.3 Failed to exec install script
remote: npm ERR! EEXIST, open '/var/lib/openshift/559fa9944382ec4cf1000106/.npm/0fe9cfe4-6-npm-mime-db-1-14-0-package-tgz.lock'
remote: File exists: /var/lib/openshift/559fa9944382ec4cf1000106/.npm/0fe9cfe4-6-npm-mime-db-1-14-0-package-tgz.lock
remote: Move it away, and try again.
remote: npm ERR! System Linux 2.6.32-504.16.2.el6.x86_64
remote: npm ERR! command "node" "/opt/rh/nodejs010/root/usr/bin/npm" "install" "-d"
remote: npm ERR! cwd /var/lib/openshift/559fa9944382ec4cf1000106/app-root/runtime/repo
remote: npm ERR! node -v v0.10.35
remote: npm ERR! npm -v 1.4.28
remote: npm ERR! path /var/lib/openshift/559fa9944382ec4cf1000106/.npm/0fe9cfe4-6-npm-mime-db-1-14-0-package-tgz.lock
remote: npm ERR! code EEXIST
remote: npm ERR! errno 47
4

1 回答 1

1

这个错误也开始突然发生在我身上，即使它以前曾起作用。由于某种原因，Pythongyp模块在墨盒中不可用或找不到。虽然我不知道发生了什么变化，但我通过升级npm用于部署的安装找到了解决方法。

为此，我添加了两个动作挂钩：

  1. .openshift/action_hooks/pre_build

    #!/bin/sh

#  We need to move the package.json file out of the way in pre_build, so
#  that the OpenShift git post-receive hook doesn't try and use the old
#  npm version to install the dependencies.
mv ${OPENSHIFT_REPO_DIR}/package.json \
   ${OPENSHIFT_TMP_DIR}/${OPENSHIFT_APP_UUID}_package.json

  2. .openshift/action_hooks/build

    #!/bin/sh

#  we moved the package.json file out of the way in pre_build,
#  so that the OpenShift git post-receive hook doesn't try and use the
#  old npm version to install the dependencies. Move it back in.
mv ${OPENSHIFT_TMP_DIR}/${OPENSHIFT_APP_UUID}_package.json \
   ${OPENSHIFT_REPO_DIR}/package.json

cd ${OPENSHIFT_REPO_DIR}

# We need an updated npm available for node-gyp to work reliable
npm install npm

# Now install the packages with the new npm version
./node_modules/.bin/npm install

以这种方式使用替代 npm 安装的想法来自https://github.com/ryanj/nodejs-custom-version-openshift/tree/master/.openshift/action_hooks

我也尝试使用环境变量和设置$PYTHONPATH，但在构建过程中没有成功（尽管我让它在手动安装上工作）。

于 2015-07-10T23:15:44.187 回答