mup deploy failure

[sebakerckhof]

Mup setup was successful. mup deploy however, gave me a failed 'Invoking deployment process'.

Mup-ing from a windows 7 to a debian 7.8 (wheezy) box.

Output:

[linuxvm] x Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    bundled package wasn't found in unpacked tree
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
    child_process: customFds option is deprecated, use stdio instead.
    ../src/coroutine.cc: In function 'void* find_thread_id_key(void*)':
    ../src/coroutine.cc:64:53: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
    ../src/coroutine.cc:90:3: warning: 'thread_id' may be used uninitialized in this function [-Wmaybe-uninitialized]
    sudo: stop: command not found
    sudo: start: command not found
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to localhost port 80 : Connection refused App did not pick up! Please check app logs. -----------------------------------STDOUT----------------------------------- rc/coroutine.o CC(target) Release/obj.target/fibers/src/libcoro/coro.o SOLINK_MODULE(target) Release/obj.target/fibers.node SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished COPY Release/fibers.node make: Leaving directory /opt/quiz/tmp/bundle/programs/server/node_modules/fibers/build' Installed in/opt/quiz/tmp/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.28/fibers.node` underscore@1.5.2 node_modules/underscore

    semver@4.1.0 node_modules/semver

    eachline@2.3.3 node_modules/eachline
    └── type-of@2.0.1

    chalk@0.5.1 node_modules/chalk
    ├── ansi-styles@1.1.0
    ├── escape-string-regexp@1.0.3
    ├── supports-color@0.2.0
    ├── has-ansi@0.1.0 (ansi-regex@0.2.1)
    └── strip-ansi@0.3.0 (ansi-regex@0.2.1)

    source-map-support@0.2.8 node_modules/source-map-support
    └── source-map@0.1.32 (amdefine@0.1.0)

    fibers@1.0.5 node_modules/fibers
    Waiting for MongoDB to initialize. (5 minutes)
    connected
    Waiting for 15 seconds while app is booting up
    Checking is app booted or not?
    ----------------------------------------------------------------------------

Completed TaskList: Deploy app 'quiz' (linux)

[arunoda]

Check mup logs -n 400.

On Tue, May 5, 2015 at 2:37 PM sebakerckhof notifications@github.com wrote:

Mup setup was successful. mup deploy however, gave me a failed 'Invoking deployment process'.

Mup-ing from a windows 7 to a debian 7.8 (wheezy) box.

Output:

[linuxvm] x Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
bundled package wasn't found in unpacked tree
npm WARN package.json meteor-dev-bundle@0.0.0 No description
npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
npm WARN package.json meteor-dev-bundle@0.0.0 No README data
child_process: customFds option is deprecated, use stdio instead.
../src/coroutine.cc: In function 'void* find_thread_id_key(void*)':
../src/coroutine.cc:64:53: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
../src/coroutine.cc:90:3: warning: 'thread_id' may be used uninitialized in this function [-Wmaybe-uninitialized]
sudo: stop: command not found
sudo: start: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to localhost port 80 : Connection refused App did not pick up! Please check app logs.

-----------------------------------STDOUT----------------------------------- rc/coroutine.o CC(target) Release/obj.target/fibers/src/libcoro/coro.o SOLINK_MODULE(target) Release/obj.target/fibers.node SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished COPY Release/fibers.node make: Leaving directory /opt/quiz/tmp/bundle/programs/server/node_modules/fibers/build' Installed in /opt/quiz/tmp/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.28/fibers.node` underscore@1.5.2 node_modules/underscore

semver@4.1.0 node_modules/semver

eachline@2.3.3 node_modules/eachline
└── type-of@2.0.1

chalk@0.5.1 node_modules/chalk
├── ansi-styles@1.1.0
├── escape-string-regexp@1.0.3
├── supports-color@0.2.0
├── has-ansi@0.1.0 (ansi-regex@0.2.1)
└── strip-ansi@0.3.0 (ansi-regex@0.2.1)

source-map-support@0.2.8 node_modules/source-map-support
└── source-map@0.1.32 (amdefine@0.1.0)

fibers@1.0.5 node_modules/fibers
Waiting for MongoDB to initialize. (5 minutes)
connected
Waiting for 15 seconds while app is booting up
Checking is app booted or not?
----------------------------------------------------------------------------

Completed TaskList: Deploy app 'quiz' (linux)

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/408.

[sebakerckhof]

No log files seems to have been made: [linuxvm] tail: [linuxvm] cannot open `/var/log/upstart/quiz.log' for reading[linuxvm] : No such file or directory[linuxvm]

[arunoda]

Okay then try to increase deployCheckWaitTime.

See: https://github.com/arunoda/meteor-up#deploy-wait-time

Seems like your app is taking some time to do initial tasks.

On Tue, May 5, 2015 at 2:39 PM sebakerckhof notifications@github.com wrote:

No log files seems to have been made: [linuxvm] tail: [linuxvm] cannot open `/var/log/upstart/quiz.log' for reading[linuxvm] : No such file or directory[linuxvm]

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/408#issuecomment-99002169.

[arunoda]

Okay. It seems like you are using the Ubuntu 15.04? Is it? If so, use 14.04.

We don't yet support 15.04. Otherwise you can use mupx: https://github.com/arunoda/meteor-up/tree/mupx

On Tue, May 5, 2015 at 2:48 PM sebakerckhof notifications@github.com wrote:

Still fails with a wait time of 120s. Output is a bit different, still no logs though. I can run the app in dev modus on the same vm...

[kndedu01.barco.com] x Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
dle@0.0.0 No description
npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
npm WARN package.json meteor-dev-bundle@0.0.0 No README data
child_process: customFds option is deprecated, use stdio instead.
../src/coroutine.cc: In function 'void* find_thread_id_key(void*)':
../src/coroutine.cc:64:53: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
../src/coroutine.cc:90:3: warning: 'thread_id' may be used uninitialized in this function [-Wmaybe-uninitialized]
sudo: stop: command not found
sudo: start: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to localhost port 80: Connection refused sudo: stop: command not found sudo: start: command not found

Latest deployment failed! Reverted back to the previous version.

-----------------------------------STDOUT-----------------------------------

c/coroutine.o CC(target) Release/obj.target/fibers/src/libcoro/coro.o SOLINK_MODULE(target) Release/obj.target/fibers.node SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished COPY Release/fibers.node make: Leaving directory /opt/quiz/tmp/bundle/programs/server/node_modules/fibers/build' Installed in /opt/quiz/tmp/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.28/fibers.node` underscore@1.5.2 node_modules/underscore

semver@4.1.0 node_modules/semver

eachline@2.3.3 node_modules/eachline
└── type-of@2.0.1

chalk@0.5.1 node_modules/chalk
├── ansi-styles@1.1.0
├── escape-string-regexp@1.0.3
├── supports-color@0.2.0

├── strip-ansi@0.3.0 (ansi-regex@0.2.1)
└── has-ansi@0.1.0 (ansi-regex@0.2.1)

source-map-support@0.2.8 node_modules/source-map-support
└── source-map@0.1.32 (amdefine@0.1.0)

fibers@1.0.5 node_modules/fibers
Waiting for MongoDB to initialize. (5 minutes)
connected
Waiting for 120 seconds while app is booting up
Checking is app booted or not?
----------------------------------------------------------------------------

Completed TaskList: Deploy app 'quiz' (linux)

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/408#issuecomment-99006122.

[sebakerckhof]

No, It's debian 7.8.

[arunoda]

Okay. It's the same story. For now, you need to use a Ubuntu box.

On Tue, May 5, 2015 at 3:23 PM sebakerckhof notifications@github.com wrote:

No, It's debian 7.8.

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/408#issuecomment-99015013.

[sebakerckhof]

I just tried on ubuntu 14.04 and it failed on the same step, but with a somewhat different message:

                [192.168.31.131] x Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    npm WARN cannot run in wd bcrypt@0.7.8 node-gyp rebuild (wd=/opt/quiz/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt)
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
    ../src/coroutine.cc: In function ‘void* find_thread_id_key(void*)’:
    ../src/coroutine.cc:64:53: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
      for (pthread_key_t ii = coro_thread_key - 1; ii >= 0; --ii) {
                                                         ^
    ../src/coroutine.cc:90:3: warning: ‘thread_id’ may be used uninitialized in this function [-Wmaybe-uninitialized]
       if (tls == thread_id) {
       ^
    -----------------------------------STDOUT-----------------------------------
    target) Release/obj.target/fibers/src/fibers.o
      CXX(target) Release/obj.target/fibers/src/coroutine.o
      CC(target) Release/obj.target/fibers/src/libcoro/coro.o
      SOLINK_MODULE(target) Release/obj.target/fibers.node
      SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished
      COPY Release/fibers.node
    make: Leaving directory `/opt/quiz/tmp/bundle/programs/server/node_modules/fibers/build'
    Installed in `/opt/quiz/tmp/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node`
    underscore@1.5.2 node_modules/underscore

    semver@4.1.0 node_modules/semver

    eachline@2.3.3 node_modules/eachline
    └── type-of@2.0.1

    chalk@0.5.1 node_modules/chalk
    ├── ansi-styles@1.1.0
    ├── escape-string-regexp@1.0.3
    ├── supports-color@0.2.0
    ├── has-ansi@0.1.0 (ansi-regex@0.2.1)
    └── strip-ansi@0.3.0 (ansi-regex@0.2.1)

    source-map-support@0.2.8 node_modules/source-map-support
    └── source-map@0.1.32 (amdefine@0.1.0)

    fibers@1.0.5 node_modules/fibers
    Waiting for MongoDB to initialize. (5 minutes)
    ----------------------------------------------------------------------------

Completed TaskList: Deploy app 'quiz' (linux)

[arunoda]

You need to have node version 0.10.x on the server, not 0.12.x. I hope that's the issue.

On Tue, May 5, 2015 at 5:01 PM sebakerckhof notifications@github.com wrote:

I just tried on ubuntu 14.04 and it failed on the same step, but with a somewhat different message:

            [192.168.31.131] x Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
npm WARN cannot run in wd bcrypt@0.7.8 node-gyp rebuild (wd=/opt/quiz/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt)
npm WARN package.json meteor-dev-bundle@0.0.0 No description
npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
npm WARN package.json meteor-dev-bundle@0.0.0 No README data
../src/coroutine.cc: In function ‘void* find_thread_id_key(void*)’:
../src/coroutine.cc:64:53: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
  for (pthread_key_t ii = coro_thread_key - 1; ii >= 0; --ii) {
                                                     ^
../src/coroutine.cc:90:3: warning: ‘thread_id’ may be used uninitialized in this function [-Wmaybe-uninitialized]
   if (tls == thread_id) {
   ^
-----------------------------------STDOUT-----------------------------------
target) Release/obj.target/fibers/src/fibers.o
  CXX(target) Release/obj.target/fibers/src/coroutine.o
  CC(target) Release/obj.target/fibers/src/libcoro/coro.o
  SOLINK_MODULE(target) Release/obj.target/fibers.node
  SOLINK_MODULE(target) Release/obj.target/fibers.node: Finished
  COPY Release/fibers.node
make: Leaving directory `/opt/quiz/tmp/bundle/programs/server/node_modules/fibers/build'
Installed in `/opt/quiz/tmp/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node`
underscore@1.5.2 node_modules/underscore

semver@4.1.0 node_modules/semver

eachline@2.3.3 node_modules/eachline
└── type-of@2.0.1

chalk@0.5.1 node_modules/chalk
├── ansi-styles@1.1.0
├── escape-string-regexp@1.0.3
├── supports-color@0.2.0
├── has-ansi@0.1.0 (ansi-regex@0.2.1)
└── strip-ansi@0.3.0 (ansi-regex@0.2.1)

source-map-support@0.2.8 node_modules/source-map-support
└── source-map@0.1.32 (amdefine@0.1.0)

fibers@1.0.5

node_modules/fibers Waiting for MongoDB to initialize. (5 minutes)

Completed TaskList: Deploy app 'quiz' (linux)

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/408#issuecomment-99044892.

[sebakerckhof]

It's 0.10.36. Installed by mup. I just reinstalled it manually, but the error stays.

[sebakerckhof]

To eliminate a problem with my meteor code I tried to deploy telescope, but got the same error. Tried to deploy to ubuntu 14.04 with nodejs 0.10.36

[ddresch]

Similar problem here:

-----------------------------------STDERR-----------------------------------
    fo spawn args   '-Dnode_root_dir=/home/admin/.node-gyp/0.10.36',
    gyp info spawn args   '-Dmodule_root_dir=/opt/my-app/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
    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 info spawn make
    gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
    gyp info ok 
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) couldn't connect to host
    Latest deployment failed! Reverted back to the previous version.
    -----------------------------------STDOUT-----------------------------------
    /opt/my-app/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'

    > fibers@1.0.1 install /opt/my-app/tmp/bundle/programs/server/node_modules/fibers
    > node ./build.js

    `linux-x64-v8-3.14` exists; testing
    Binary is fine; exiting
    underscore@1.5.2 node_modules/underscore

    eachline@2.3.3 node_modules/eachline
    └── type-of@2.0.1

    semver@4.1.0 node_modules/semver

    source-map-support@0.2.8 node_modules/source-map-support
    └── source-map@0.1.32 (amdefine@0.1.0)

    fibers@1.0.1 node_modules/fibers

    chalk@0.5.1 node_modules/chalk
    ├── ansi-styles@1.1.0
    ├── escape-string-regexp@1.0.3
    ├── supports-color@0.2.0
    ├── has-ansi@0.1.0 (ansi-regex@0.2.1)
    └── strip-ansi@0.3.0 (ansi-regex@0.2.1)
    Waiting for MongoDB to initialize. (5 minutes)
    connected
    my-app stop/waiting
    my-app start/running, process 20421
    Waiting for 50 seconds while app is booting up
    Checking is app booted or not?
    my-app stop/waiting
    my-app start/running, process 20661
    ----------------------------------------------------------------------------

node Version 0.10.36 Ubuntu 12.04.5 LTS

mup logs output:

[134.119.11.176] Error: Can't find npm module 'string'. Did you forget to call 'Npm.depends' in package.js within the 'aldeed_simple-schema' package?
    at Object.Npm.require (/opt/my-app/app/programs/server/boot.js:147:17)
    at expectedType (packages/aldeed:simple-schema/simple-schema.js:8:1)
    at /opt/my-app/app/programs/server/packages/aldeed_simple-schema.js:2015:4
    at /opt/my-app/app/programs/server/packages/aldeed_simple-schema.js:2983:3
    at /opt/my-app/app/programs/server/boot.js:205:10
    at Array.forEach (native)
    at Function._.each._.forEach (/opt/my-app/app/programs/server/node_modules/underscore/underscore.js:79:11)
    at /opt/my-app/app/programs/server/boot.js:116:5
[134.119.11.176] error: Forever detected script exited with code: 8

But it's not the case? Simple-Schema is referencing the NPM string package.

Also others experiencing this error: https://github.com/aldeed/meteor-simple-schema/issues/353

Any advice on how to track it down where the failure is happening?

Stuck on this since two days and still no idea how to go on now.

[ddresch]

So switched to mupx for testing but the same error there:

Error: Can't find npm module 'string'. Did you forget to call 'Npm.depends' in package.js within the 'aldeed_simple-schema' package?
    at Object.Npm.require (/opt/my-app/app/programs/server/boot.js:147:17)

But to get that far I needed to add my user e.g. admin to the docker user group, if not I got this error:

/var/run/docker.sock: permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?

[arunoda]

You may need to add your user to the root user group or give permission like this. See: https://github.com/arunoda/meteor-up#ssh-based-authentication-with-sudo

Docker needs root access.

On Wed, May 6, 2015 at 7:21 PM Dirk Dresch notifications@github.com wrote:

So switched to mupx for testing but the same error there:

Error: Can't find npm module 'string'. Did you forget to call 'Npm.depends' in package.js within the 'aldeed_simple-schema' package? at Object.Npm.require (/opt/my-app/app/programs/server/boot.js:147:17)

But to get that far I needed to add my user e.g. admin to the docker user group, if not I got this error:

/var/run/docker.sock: permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/408#issuecomment-99468750.

[ddresch]

This is done like you describe it, as I wrote the user permission problem is not the case. It's about this "Cant't find npm module 'string'...." problem.

[arunoda]

Hmm. That's weird. It's getting when running as a bundle. Not sure about the issue. I hope author can answer well.

[evallgar]

First time trying mup. I like to keep things simple first time so I uploaded "simple-todos" demo app.

I followed all instructions but keep getting this error.

Started TaskList: Deploy app 'simple-todos' (linux) [45.55.229.72] - Uploading bundle [45.55.229.72] - Uploading bundle: SUCCESS [45.55.229.72] - Setting up Environment Variables [45.55.229.72] - Setting up Environment Variables: SUCCESS [45.55.229.72] - Invoking deployment process [45.55.229.72] x Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
root_dir=/root/.node-gyp/0.10.36',
gyp info spawn args   '-Dmodule_root_dir=/opt/simple-todos/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
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 info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
gyp info ok
npm WARN package.json meteor-dev-bundle@0.0.0 No description
npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
npm WARN package.json meteor-dev-bundle@0.0.0 No README data
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to localhost port 80: Connection refused Latest deployment failed! Reverted back to the previous version. -----------------------------------STDOUT----------------------------------- ke: Leaving directory `/opt/simple-todos/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'

> fibers@1.0.5 install /opt/simple-todos/tmp/bundle/programs/server/node_modules/fibers
> node ./build.js

`linux-x64-v8-3.14` exists; testing
Binary is fine; exiting
underscore@1.5.2 node_modules/underscore

eachline@2.3.3 node_modules/eachline
└── type-of@2.0.1

semver@4.1.0 node_modules/semver

chalk@0.5.1 node_modules/chalk
├── ansi-styles@1.1.0
├── escape-string-regexp@1.0.3
├── supports-color@0.2.0
├── has-ansi@0.1.0 (ansi-regex@0.2.1)
└── strip-ansi@0.3.0 (ansi-regex@0.2.1)

source-map-support@0.2.8 node_modules/source-map-support
└── source-map@0.1.32 (amdefine@0.1.0)

fibers@1.0.5 node_modules/fibers
Waiting for MongoDB to initialize. (5 minutes)
connected
simple-todos stop/waiting
simple-todos start/running, process 15477
Waiting for 120 seconds while app is booting up
Checking is app booted or not?
simple-todos stop/waiting
simple-todos start/running, process 15937
----------------------------------------------------------------------------

[EricMaeker]

I have the same issue on my Debian jessie VPS. Unable to deploy any apps. Here is the command line log:

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------

“ Checkout Kadira!
  It's the best way to monitor performance of your app.
  Visit: https://kadira.io/mup ”

Building Started: /home/eric/Bureau/Files/Programmation/Current/SSR/ssr

Started TaskList: Deploy app 'ssr' (linux)
[maeker.fr] - Uploading bundle
[maeker.fr] ✔ Uploading bundle: SUCCESS
[maeker.fr] - Setting up Environment Variables
[maeker.fr] ✔ Setting up Environment Variables: SUCCESS
[maeker.fr] - Invoking deployment process
[maeker.fr] ✘ Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    '-Dnode_root_dir=/root/.node-gyp/0.10.36',
    gyp info spawn args   '-Dmodule_root_dir=/opt/ssr/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
    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 info spawn make
    gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
    gyp info ok 
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 8000: Connexion refusée
    Latest deployment failed! Reverted back to the previous version.
    -----------------------------------STDOUT-----------------------------------
    arget/bcrypt_lib.node
      COPY Release/bcrypt_lib.node
    make: Leaving directory '/opt/ssr/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'

    > fibers@1.0.5 install /opt/ssr/tmp/bundle/programs/server/node_modules/fibers
    > node ./build.js

    `linux-x64-v8-3.14` exists; testing
    Binary is fine; exiting
    underscore@1.5.2 node_modules/underscore

    eachline@2.3.3 node_modules/eachline
    └── type-of@2.0.1

    semver@4.1.0 node_modules/semver

    chalk@0.5.1 node_modules/chalk
    ├── ansi-styles@1.1.0
    ├── escape-string-regexp@1.0.3
    ├── supports-color@0.2.0
    ├── has-ansi@0.1.0 (ansi-regex@0.2.1)
    └── strip-ansi@0.3.0 (ansi-regex@0.2.1)

    source-map-support@0.2.8 node_modules/source-map-support
    └── source-map@0.1.32 (amdefine@0.1.0)

    fibers@1.0.5 node_modules/fibers
    Waiting for MongoDB to initialize. (5 minutes)
    connected
    ssr stop/waiting
    ssr start/running, process 17870
    Waiting for 30 seconds while app is booting up
    Checking is app booted or not?
    ssr stop/waiting
    ssr start/running, process 18060
    ----------------------------------------------------------------------------
Completed TaskList: Deploy app 'ssr' (linux)

On the server:

/opt/ssr/app/programs/server/node_modules/fibers/future.js:245
                        throw(ex);
                              ^
ReferenceError: require is not defined
    at app/node_modules/bcrypt/node_modules/bindings/bindings.js:6:10
    at app/node_modules/bcrypt/node_modules/bindings/bindings.js:168:3
    at /opt/ssr/app/programs/server/boot.js:222:10
    at Array.forEach (native)
    at Function._.each._.forEach (/opt/ssr/app/programs/server/node_modules/underscore/underscore.js:79:11)
    at /opt/ssr/app/programs/server/boot.js:117:5
error: Forever detected script exited with code: 8
error: Script restart attempt #12

/opt/ssr/app/programs/server/node_modules/fibers/future.js:245
                        throw(ex);
                              ^
Error: ENOENT, no such file or directory '/opt/ssr/app/programs/server/app/lib/collections/stats_schema.coffee.js'
    at Object.fs.openSync (fs.js:439:18)
    at Object.fs.readFileSync (fs.js:290:15)
    at /opt/ssr/app/programs/server/boot.js:118:19
    at Array.forEach (native)
    at Function._.each._.forEach (/opt/ssr/app/programs/server/node_modules/underscore/underscore.js:79:11)
    at /opt/ssr/app/programs/server/boot.js:117:5
error: Forever detected script exited with code: 8
 >> stepping down to gid: meteoruser
 >> stepping down to uid: meteoruser

$ node -v
v0.10.36
$ npm -v
1.4.28
$ uname -a
Linux ... 2.6.32-042stab108.5 #1 SMP Wed Jun 17 20:20:17 MSK 2015 x86_64 GNU/Linux

[JuusoV]

Im running to the same issue. Anyone got a solution?

[yhyuan]

I am having the same issue.

[dnprock]

I use 0.10.x node and increased deployCheckWaitTime to 120 seconds (60 didn't work). This works for me. My app is fairly large.

[atomdigital]

Hello. An error occurs when install Meteor UP. 1) When installing the meteor, an error: http://c2n.me/3mzzOmJ STDERR -------------- ---------------------         rm: can not be removed «/ var / cache / apt / archives / lock»: No such file or directory         gpg: requesting key 7F0CEB10 with hkp server keyserver.ubuntu.com         gpg: key 7F0CEB10: "Richard Kreuter richard@10gen.com" is not changed         gpg: Total processed: 1         gpg: unchanged: 1         sudo: stop: command not found         sudo: start: command not found         ----------------------------------- STDOUT -------------- ---------------------         above http://downloads-distro.mongodb.org dist Release         The cache http://downloads-distro.mongodb.org dist / 10gen amd64 Packages         IGN http://repo.mongodb.org wheezy / mongodb-org / 3.0 / main Translation-ru_RU         IGN http://repo.mongodb.org wheezy / mongodb-org / 3.0 / main Translation-ru         IGN http://repo.mongodb.org wheezy / mongodb-org / 3.0 / main Translation-en         IGN http://downloads-distro.mongodb.org dist / 10gen Translation-ru_RU         IGN http://downloads-distro.mongodb.org dist / 10gen Translation-ru         IGN http://downloads-distro.mongodb.org dist / 10gen Translation-en         Reading package lists ...         Reading package lists ...         Building dependency tree ...         Reading state information ...         It is already the newest version mongodb-org.         It is already the newest version mongodb-org-server.         mongodb-org-server is installed manually.         It is already the newest version mongodb-org-shell.         It is already the newest version mongodb-org-tools.         0 upgraded, 0 installed new packages, to remove the packages marked 0 and 0 not upgraded.         -------------------------------------------------- --------------------------

2) Mongodb installed and installed without mup mongodb: 2.1)We install a separate mongodb: sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 7F0CEB10 echo 'deb http://downloads-distro.mongodb.org/repo/ubuntu-upstart dist 10gen' | sudo tee /etc/apt/sources.list.d/mongodb.list sudo apt-get update sudo apt-get install mongodb-org http://c2n.me/3mzADai

2.2) install mup: http://clip2net.com/s/3mzuWb4 create project: http://c2n.me/3mzuKiI open in browser: http://c2n.me/3mzuGTN (close console -> close app) Start: http://c2n.me/3mzyeyy deploy: http://c2n.me/3mzBi7C application does not work http://c2n.me/3mzBwBD

Please help to establish meteoup!

[MasterJames]

Have you tried mupx? Please explain more about your "Start" section/code as that seems where something first goes wrong and it seemed unclear to me, Thanks.

[atomdigital]

mupx, now we try to set. That it was explained about the ""Start" section/code"? When you try to run it mup an error http://c2n.me/3mzyeyy

[atomdigital]

npm install -g mupx: http://c2n.me/3mAqU4D muox init: http://c2n.me/3mAr93v file: mup.json { // Server authentication info "servers": [ { "host": "ait.moscow", "username": "root", "password": "mypass-root", "env": {} } ], // Install MongoDB on the server. Does not destroy the local MongoDB on future setups "setupMongo": true,

// Application name (no spaces). "appName": "meteorx", // Location of app (local directory). This can reference '~' as the users home directory. // i.e., "app": "~/Meteor/my-app", // This is the same as the line below. "app": "/meteor/myapp2/", // Configure environment // ROOT_URL must be set to your correct domain (https or http) "env": { // port 80 – apache //port 88 – nginx (gitlab) //port 10000 webmin "PORT": 3000, "ROOT_URL": "http://ait.moscow" }, // Meteor Up checks if the app comes online just after the deployment. // Before mup checks that, it will wait for the number of seconds configured below. "deployCheckWaitTime": 15, // show a progress bar while uploading. // Make it false when you deploy using a CI box. "enableUploadProgressBar": true }

Install mupx: http://c2n.me/3mAsmKu Error: Started TaskList: Setup (linux) [ait.moscow] - Installing Docker [ait.moscow] x Installing Docker: FAILED

    ----------------------------------- STDERR -------------- ---------------------
    be: not found
    Warning: current kernel is not supported by the linux-image-extra-virtual
     package. We have no AUFS support. Consider installing the packages
     linux-image-virtual kernel and linux-image-extra-virtual for AUFS support.
    + Sleep 10
    + Sh -c sleep 3; apt-get update
    + Sh -c sleep 3; apt-get install -y -q apt-transport-https ca-certificates
    + Sh -c apt-key adv --keyserver hkp: //p80.pool.sks-keyservers.net: 80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
    gpg: requesting key 2C52609D with hkp server p80.pool.sks-keyservers.net
    gpg: key 2C52609D: imported public key "Docker Release Tool (releasedocker) <docker@docker.com>"
    gpg: Total processed: 1
    gpg: imported: 1 (RSA: 1)
    + Sh -c mkdir -p /etc/apt/sources.list.d
    + Sh -c echo deb https://apt.dockerproject.org/repo debian-jessie main> /etc/apt/sources.list.d/docker.list
    + Sh -c sleep 3; apt-get update; apt-get install -y -q docker-engine
    E: Sub-process / usr / bin / dpkg returned an error code (1)
    ----------------------------------- STDOUT -------------- ---------------------
    d: warning: start and stop actions are no longer supported; falling back to defaults
    Configurable packet libnih1 (1.0.3-4.3) ...
    Configurable packet libnih-dbus1 (1.0.3-4.3) ...
    Configurable packet mountall (2.54) ...
    Adjustable package aufs-tools (1: 3.2+ 20130722-1.1) ...
    Configurable packet cgroupfs-mount (1.1) ...
    Configurable packet libapparmor1: amd64 (2.9.0-3) ...
    Adjustable package docker-engine (1.8.1-0 ~ jessie) ...
    Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
    invoke-rc.d: initscript docker, action "start" failed.
    dpkg: error processing package docker-engine (--configure):
     subprocess installed post-installation script returned error code 1
    Processed triggers for libc-bin (2.19-18) ...
    Processed triggers for systemd (215-17 + deb8u1) ...
    Processed triggers for initramfs-tools (0.120) ...
    Processed triggers for dbus (1.8.18-0 + deb8u1) ...
    When processing the next packet errors occurred:
     docker-engine

[MasterJames]

Your mupx setup graphic shows a problem with the kernel and it suggests a solution there in the "stderr". What versions for nodejs, meteor & mup(x) as well as your deployment target (a supported Ubuntu version)?

[atomdigital]

Installation is performed according to the manual https://github.com/arunoda/meteor-up/tree/mupx . I assume that the installed the latest stable version

[atomdigital]

node: http://c2n.me/3mAThhS

[arunoda]

@atomdigital You need to have Ubuntu 14.04 version. I hope that's the issue here.

[atomdigital]

Debian GNU/Linux 8

[arunoda]

That's the issue. You need to have a Ubuntu 14.04 for the best use. That's because we use upstart is mup.

[atomdigital]

on our server is not convenient to use Ubuntu

[atomdigital]

Is there a way to set mup to our server ? Does it matter that our server fixed network services :http://c2n.me/3mAWjC1

[atomdigital]

Please help!

[arunoda]

Mup assumes you have upstart. So, that's why it's not working. Also, it assumes you don't have node installed on the system.

[atomdigital]

Node.js we will delete. Please explain what the "upstart"? Thank you!

[arunoda]

It's a init system comes with Ubuntu. I hope debian has SystemD. I hope it's pretty hard to change it.

Also, seems like your server has a very old kernel.

So, what I suggest you to use a new VM or directly deploy your app using meteor build. See: http://docs.meteor.com/#/full/deploying

On Wed, Aug 26, 2015 at 11:32 AM atomdigital notifications@github.com wrote:

Node.js we will delete. Please explain what the "upstart"? Thank you!

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/408#issuecomment-134846518.

[atomdigital]

Debian has SystemD. The core of our system is not old. Node.js is now removed, during the installation "npm install -g mup", the system generates an error : "npm: command not found " Install only the NMP: "apt-get -t jessie install npm" ?

[atomdigital]

Established "mup-dev" https://www.npmjs.com/package/deb-mup#uses-sysvinit-instead-of-upstart the installation was successful http://clip2net.com/s/3mEAoPE During deploy error: http://c2n.me/3mEEt9G

Building Started: /app1 events.js:72 throw er; // Unhandled 'error' event Error: spawn ENOENT

People write that the error is treated modified versions . touched up version 10.0 the problem persists. https://github.com/arunoda/meteor-up/issues/570

PLEASE HELP!!!

[atomdigital]

Errors eliminated, now everything works . We established a meteor on Debian. the problem was the following: 1) The entire setting is necessary to perform not in the server console and the console of the local computer on which you install mup, meteor, node + nmp. 2) To use a special version of debian deb-mup: https://www.npmjs.com/package/deb-mup#uses-sysvinit-instead-of-upstart 3) If the installation mup an error , you can manually set the node, mongodb and start the installation mup.

Please answer the question, I do not want to use with root, what the minimum rights I have to give a new user ?

[Maay]

@arunoda I suppose, I have the same error but with mongo? Have you met this?

|⇒ mup deploy

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------

“ Checkout Kadira!
  It's the best way to monitor performance of your app.
  Visit: https://kadira.io/mup ”

Building Started: /Users/maay/for_soul/bassfunk

Started TaskList: Deploy app 'bassfunk' (linux)
[178.62.193.206] - Uploading bundle
[178.62.193.206] - Uploading bundle: SUCCESS
[178.62.193.206] - Setting up Environment Variables
[178.62.193.206] - Setting up Environment Variables: SUCCESS
[178.62.193.206] - Invoking deployment process
[178.62.193.206] x Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    le=node.lib',
    gyp info spawn args   '-Dmodule_root_dir=/opt/bassfunk/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
    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 info spawn make
    gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
    gyp info ok 
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
    stop: Unknown instance: 
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 80: Connection refused
    Latest deployment failed! Reverted back to the previous version.
    -----------------------------------STDOUT-----------------------------------
    odules/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/bassfunk/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'

    > fibers@1.0.1 install /opt/bassfunk/tmp/bundle/programs/server/node_modules/fibers
    > node ./build.js

    `linux-x64-v8-3.14` exists; testing
    Binary is fine; exiting
    underscore@1.5.2 node_modules/underscore

    semver@2.2.1 node_modules/semver

    source-map-support@0.2.5 node_modules/source-map-support
    └── source-map@0.1.29 (amdefine@0.1.0)

    fibers@1.0.1 node_modules/fibers
    Waiting for MongoDB to initialize. (5 minutes)
    connected
    bassfunk start/running, process 21760
    Waiting for 15 seconds while app is booting up
    Checking is app booted or not?
    bassfunk stop/waiting
    bassfunk start/running, process 21836
    ----------------------------------------------------------------------------

[MasterJames]

Extending the wait time sometimes helps. Put it up to 120 and lower to what still works.

"deployCheckWaitTime": 15

I also suggest if you have problems with mup to try mupx (the development branch for mup) as it can save you some grief.

[adam-hanna]

_EDIT - FIXED_ Ok, so this version of mup no longer works with meteor 1.3+. Apparently even mupx is having some problems. I eventually found a forked version that worked for me. I also updated node to v0.10.43

See this comment, here.

_//////////////////////////_

Updated from meteor 1.0.X to 1.3.2.4 and having a similar issue. Was working fine before the meteor update. Here is my console:

Started TaskList: Deploy app 'faze1SelfServe' (linux)
[104.131.30.123] - Uploading bundle
[104.131.30.123] - Uploading bundle: SUCCESS
[104.131.30.123] - Setting up Environment Variables
[104.131.30.123] - Setting up Environment Variables: SUCCESS
[104.131.30.123] - Invoking deployment process
[104.131.30.123] x Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
    npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/opt/faze1SelfServe/tmp/bundle/programs/server)
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 3015: Connection refused
    Latest deployment failed! Reverted back to the previous version.
    -----------------------------------STDOUT-----------------------------------
    ules/ansi-regex

    ansi-styles@1.1.0 node_modules/ansi-styles

    chalk@0.5.1 node_modules/chalk

    escape-string-regexp@1.0.5 node_modules/escape-string-regexp

    supports-color@0.2.0 node_modules/supports-color

    has-ansi@0.1.0 node_modules/has-ansi

    strip-ansi@0.3.0 node_modules/strip-ansi

    eachline@2.3.3 node_modules/eachline

    type-of@2.0.1 node_modules/type-of

    amdefine@1.0.0 node_modules/amdefine

    asap@2.0.3 node_modules/asap

    underscore@1.5.2 node_modules/underscore

    meteor-promise@0.5.1 node_modules/meteor-promise

    promise@7.0.4 node_modules/promise

    source-map-support@0.3.2 node_modules/source-map-support

    semver@4.1.0 node_modules/semver

    source-map@0.1.32 node_modules/source-map

    fibers@1.0.8 node_modules/fibers
    Waiting for MongoDB to initialize. (5 minutes)
    connected
    faze1SelfServe stop/waiting
    faze1SelfServe start/running, process 3419
    Waiting for 15 seconds while app is booting up
    Checking is app booted or not?
    faze1SelfServe stop/waiting
    faze1SelfServe start/running, process 3480