MUP在另一台服务器上运行的项目上部署故障

时间：2015-10-02 23:02:45

标签： javascript meteor deployment

我尝试使用meteor部署到服务器上，配置与工作正常的服务器完全相同。我已经在MasterJames的帮助下绕过这个问题，在mit问题跟踪器上找到了mup但是没有得到任何地方所以我在这里。

我的mup.json是

    {
 19   // Server authentication info
 18
 17   "servers": [
 16     {
 15       "host": "10.1.23.2",
 14       "username": "root",
 13       // "password": ""
 12       // or pem file (ssh based authentication)
 11       "pem": "/var/root/.ssh/id_dsa"
 10     }
  9   ],
  8
  7   // Install MongoDB in the server, does not destroy local MongoDB on future setup
  6   "setupMongo": false,
  5
  4   // WARNING: Node.js is required! Only skip if you already have Node.js installed on server.
  3   "setupNode": true,
  2
  1   // WARNING: If nodeVersion omitted will setup 0.10.36 by default. Do not use v, only version number.
  0   "nodeVersion": "0.10.36",
  1
  2   // Install PhantomJS in the server
  3   "setupPhantom": true,
  4
  5   // Show a progress bar during the upload of the bundle to the server.
  6   // Might cause an error in some rare cases if set to true, for instance in Shippable CI
  7   "enableUploadProgressBar": true,
  8
  9   // Application name (No spaces)
 10   "appName": "thedash",
 11
 12   // Location of app (local directory)
 13   "app": "/Users/me/Documents/src/meteor/theboard",
 14
 15   // Configure environment
 16   "env": {
 18     "ROOT_URL": "https://thedash.there.com",
 19     "PORT": 3080,
 20     "MONGO_URL": "mongodb://localhost:27017/indata/"
 21   },
 22
 23   // Meteor Up checks if the app comes online just after the deployment
 24   // before mup checks that, it will wait for no. of seconds configured below
 25   "deployCheckWaitTime": 150
 26 }

更改网址以保护有罪。

我的设置.json是

     {
  0   "public": {
  1
  2   }
  3 }

当我运行sudo mup deploy时（sudo mup setup运行成功后）我收到错误，但每次都有不同的错误。最初它无法找到我手动安装的node-gyp，但现在有些错误是.. 

    [10.1.23.2] x Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
gz
npm ERR! fetch failed https://registry.npmjs.org/semver/-/semver-4.1.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/underscore/-/underscore-1.5.2.tgz
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! System Linux 3.13.0-61-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /opt/bocorockdash/tmp/bundle/programs/server
npm ERR! node -v v0.10.36
npm ERR! npm -v 1.4.28
npm ERR! syscall read
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /opt/bocorockdash/tmp/bundle/programs/server/npm-debug.log
npm ERR! not ok code 0
-----------------------------------STDOUT-----------------------------------
 > ./bcrypt: npm install due to binary npm modules
bindings@1.0.0 node_modules/bindings

nodeunit@0.9.1 node_modules/nodeunit
└── tap@0.7.1 (inherits@2.0.1, buffer-equal@0.0.1, slide@1.1.6, deep-equal@1.0.1, yamlish@0.0.7, nopt@3.0.4, mkdirp@0.5.1, difflet@0.2.6, runforcover@0.0.2, glob@4.5.3)
make: Entering directory `/opt/bocorockdash/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
  SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
  COPY Release/bcrypt_lib.node
make: Leaving directory `/opt/bocorockdash/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'
----------------------------------------------------------------------------

或

[10.1.23.2] x Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
h failed https://registry.npmjs.org/source-map-support/-/source-map-support-0.2.8.tgz
npm ERR! fetch failed https://registry.npmjs.org/semver/-/semver-4.1.0.tgz
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! System Linux 3.13.0-61-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /opt/bocorockdash/tmp/bundle/programs/server
npm ERR! node -v v0.10.36
npm ERR! npm -v 1.4.28
npm ERR! syscall read
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /opt/bocorockdash/tmp/bundle/programs/server/npm-debug.log
npm ERR! not ok code 0
-----------------------------------STDOUT-----------------------------------
 > ./bcrypt: npm install due to binary npm modules
bindings@1.0.0 node_modules/bindings

nodeunit@0.9.1 node_modules/nodeunit
└── tap@0.7.1 (inherits@2.0.1, buffer-equal@0.0.1, slide@1.1.6, deep-equal@1.0.1, yamlish@0.0.7, nopt@3.0.4, difflet@0.2.6, mkdirp@0.5.1, runforcover@0.0.2, glob@4.5.3)
make: Entering directory `/opt/bocorockdash/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
  SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
  COPY Release/bcrypt_lib.node
make: Leaving directory `/opt/bocorockdash/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'
----------------------------------------------------------------------------

等等。

服务器配置

    npm version
{ http_parser: '1.0',
node: '0.10.36',
v8: '3.14.5.9',
ares: '1.9.0-DEV',
uv: '0.10.30',
zlib: '1.2.8',
modules: '11',
openssl: '1.0.1l',
npm: '1.4.28' }

node --version v0.10.36

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty

任何想法从哪里开始。这已经在另一台服务器上运行了（所有这些都是前一段时间用于设置），并且使用相同代码的另一个实例几个月完美无缺。

1 个答案:

答案 0 :(得分：0)

解决：这些问题与mup或meteor无关。问题是在同一个盒子上运行的mysql由于某种原因挂起了处理器。重新启动mysql以释放资源，升级到1.2（尽管我认为这与它无关）并且部署工作。

相关问题
最新问题