javascript - MUP Deploy failures on a project that works on another server -
i'm trying deploy meteor server configured pretty same 1 working fine. i've been going around , around of masterjames on git issues tracker mup not getting anywhere here am.
my mup.json is
{ 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 server, not destroy local mongodb on future setup 6 "setupmongo": false, 5 4 // warning: node.js required! skip if have node.js installed on server. 3 "setupnode": true, 2 1 // warning: if nodeversion omitted setup 0.10.36 default. not use v, version number. 0 "nodeversion": "0.10.36", 1 2 // install phantomjs in server 3 "setupphantom": true, 4 5 // show progress bar during upload of bundle server. 6 // might cause error in rare cases if set true, 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 checks if app comes online after deployment 24 // before mup checks that, wait no. of seconds configured below 25 "deploycheckwaittime": 150 26 } with url's changed protect guilty.
my settings.json is
{ 0 "public": { 1 2 } 3 } when run sudo mup deploy (after sudo mup setup has run successfully) i'm getting errors, there different pretty each time. not able find node-gyp installed manually, of errors are..
[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 not problem npm npm err! network , related network connectivity. npm err! network in cases behind proxy or have bad network settings. npm err! network npm err! network if behind proxy, please make sure npm err! network 'proxy' config set properly. see: 'npm 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 found in: npm err! /opt/bocorockdash/tmp/bundle/programs/server/npm-debug.log npm err! not ok code 0 -----------------------------------stdout----------------------------------- > ./bcrypt: npm install due 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' ---------------------------------------------------------------------------- or
[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 not problem npm npm err! network , related network connectivity. npm err! network in cases behind proxy or have bad network settings. npm err! network npm err! network if behind proxy, please make sure npm err! network 'proxy' config set properly. see: 'npm 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 found in: npm err! /opt/bocorockdash/tmp/bundle/programs/server/npm-debug.log npm err! not ok code 0 -----------------------------------stdout----------------------------------- > ./bcrypt: npm install due 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' ---------------------------------------------------------------------------- and on.
the server config is
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 available. distributor id: ubuntu description: ubuntu 14.04.3 lts release: 14.04 codename: trusty any ideas go here. has worked on server (all while ago setup) faultlessly months instance of same code.
solved: issues turned out nothing mup or meteor. problem mysql running on same box had processor pegged reason. restarting mysql release resources, upgrade 1.2 (although don't think had it) , deploy worked.
Comments
Post a Comment