Possibly unhandled Error: 1 at Promise$_rejecter #50

crapthings · 2017-04-24T09:46:51Z

what's wrong ?
should i use same version with meteor node -v ?

should i always use mongodb ? because it's just a client bundle.


WARNING: Did not pass a MONGO_URL. Bundling a NON-PRODUCTION version of MongoDB with your application. Read about the limitations here: https://git.io/vM72E
⠀⢀ [METEOR-NOW] - deploying build (this can take several minutes)Possibly unhandled Error: 1
    at Promise$_rejecter (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:590:44)
    at /Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/index.js:85:13
    at tryCatch1 (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/util.js:63:19)
    at Promise$_callHandler [as _callHandler] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:695:13)
    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:711:18)
    at Promise$_settlePromiseAt [as _settlePromiseAt] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:868:14)
    at Promise$_settlePromises [as _settlePromises] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:1006:14)
    at Promise$_rejectPromises [as _rejectPromises] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:999:10)
    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/async.js:74:12)
    at Async$consumeFunctionBuffer (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/async.js:37:14)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)

then [METEOR-NOW] - deploying build (this can take several minutes) forever

The text was updated successfully, but these errors were encountered:

crapthings · 2017-04-24T10:03:36Z

i have set mongourl and i've still got

⡋⠁ [METEOR-NOW] - deploying build (this can take several minutes)Possibly unhandled Error: 1
    at Promise$_rejecter (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:590:44)
    at /Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/index.js:85:13
    at tryCatch1 (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/util.js:63:19)
    at Promise$_callHandler [as _callHandler] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:695:13)
    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:711:18)
    at Promise$_settlePromiseAt [as _settlePromiseAt] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:868:14)
    at Promise$_settlePromises [as _settlePromises] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:1006:14)
    at Promise$_rejectPromises [as _rejectPromises] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:999:10)
    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/async.js:74:12)
    at Async$consumeFunctionBuffer (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/async.js:37:14)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)

crapthings · 2017-04-24T10:15:50Z

-d logs

> [debug] Retrying: FetchError: request to https://api.zeit.co/now/sync failed, reason: socket hang up
FetchError: request to https://api.zeit.co/now/sync failed, reason: socket hang up
    at ClientRequest.<anonymous> (/Users/monsterstep/.nvm/versions/node/v6.10.2/lib/node_modules/now/node_modules/node-fetch/index.js:133:11)
    at emitOne (events.js:101:20)
    at ClientRequest.emit (events.js:188:7)
    at TLSSocket.socketOnEnd (_http_client.js:345:9)
    at emitNone (events.js:91:20)
    at TLSSocket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

acomito · 2017-04-24T12:21:31Z

did you make sure to npm install for your meteor prooject? Maybe try to run meteor as well so that it downloads all the atmosphere packages.

purplecones · 2017-04-24T15:23:08Z

Might be related to the now-cli. According to the last log you posted, the error is related with the socket connection so maybe you lost connection during upload or some error occurred on now's end. I good simple test is to just deploy a super basic node app and see if that deploys successfully by just typing in now in your project folder.

ghost · 2017-04-24T15:58:17Z

I recently solved this issue.

#47 has more info. Make your meteor-now -e 'MONGO_URL=mongodb://<>'

i.e. single quote the whole as a string

crapthings · 2017-04-25T01:32:33Z

hey it still throw the error, but it did deploy the project.

and there's no node-fetch used in this project, the project is very small, its almost static html with small amount js basiclly

what i've did is just rm -rf node_modules && meteor reset then meteor-now again

but error still there

ghost · 2017-04-25T01:53:24Z

Please try this

meteor npm install && meteor reset && meteor-now

it takes time because the Docker image created for deployment installs a non-persistent mongodb on now.

If you use your own mongo_url and point to a server accessible over internet, the build is much faster.

qualitymanifest · 2017-04-25T08:10:08Z

I've had 4 successful deployments, the latest one being yesterday, but today I keep getting this error. I've tried the following:

Single quoting 'MONGO_URL=mlab uri...'
Since that didn't work, also single quoting 'ROOT_URL=...'
Rolling back to now@4.11.1 since I just upgraded to now@4.11.2.
rm -rf node_modules followed by meteor npm install and meteor reset.

Nothing has worked, I keep getting the error and then it hangs at deploying build. I'm running Meteor@1.4.4.1. The app works fine when I run it locally, including connecting to my mlab db.

If I go to https://zeit.co/dashboard and click on the URL it gives me for the deployment, I can see that it's stuck on "1. Syncing files...".

crapthings · 2017-04-25T10:56:25Z

@qualitymanifest

try use debug mode meteor now -d -e ...rest

error shows, but it did deploy successed

ghost · 2017-04-25T13:13:04Z

@crapthings I had the exact same error, Please use single quotes for the whole of your MONGO_URL options.

Instance: meteor-now -e 'MONGO_URL=mongodb://my_mango_server:27017/the_db?ssl=true'

The only other thing I can think of is that your DB is not internet connected OR firewall rule is not allowing incoming port connection

qualitymanifest · 2017-04-27T03:14:27Z

@crapthings I could see it was deploying before, by looking on my dashboard on zeit's website. But it wasn't completing the deployment - it would get stuck on "syncing files".
Anyway, I tried your suggestion of passing in -d with the rest of the command that I was using. I actually didn't get the error at all (???) and it deployed just fine. I also logged out and logged back in first, so it's possible that had something to do with it, since I hadn't tried that before. Who knows at this point, I'm just happy it's working again so I don't keep burning through my free deployments. Thanks!

d62remi · 2017-04-27T18:34:01Z

To fix this issue you can try
npm install now@4.10.3 -g

I think problem is cause by vercel/vercel#435 only for oss plan.

Now-cli is waiting for your answer to go on https://github.com/zeit/now-cli/pull/435/files#diff-f784a12f4f3daf2399f86ae70b2f69c5R617

@jkrup @purplecones an idea to fix this problem with last now-cli ?

nilsi · 2017-05-12T14:38:08Z

I did npm install now@4.10.3 -g but it did not help. Have some more output with the -d option

$ meteor-now -d
[METEOR-NOW] - running command: meteor build .meteor/local/builds --server-only --architecture=os.linux.x86_64
                                              
WARNING: The output directory is under your source tree.
         Your generated files may get interpreted as source code!
         Consider building into a different directory instead
         meteor build ../output
                                              
[METEOR-NOW] - creating Dockerfile            
[METEOR-NOW] - creating supervisor
[METEOR-NOW] - splitting bundle
[METEOR-NOW] - looking for meteor settings file development.settings.json in root of project
[METEOR-NOW] - could not read development.settings.json
[METEOR-NOW] - no settings file found
WARNING: Did not pass a MONGO_URL. Bundling a NON-PRODUCTION version of MongoDB with your application. Read about the limitations here: https://git.io/vM72E
[METEOR-NOW] - running command: cd .meteor/local/builds && now -e PORT=3000 -e MONGO_URL=mongodb://127.0.0.1:27017 -e ROOT_URL=http://localhost.com -d 
/usr/local/lib/node_modules/now/build/bin/now.js:4
const { resolve } = require('path');
      ^

SyntaxError: Unexpected token {
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:387:25)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Function.Module.runMain (module.js:447:10)
    at startup (node.js:141:18)
    at node.js:933:3
Possibly unhandled Error: 1
    at Promise$_rejecter (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:590:44)
    at /usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/index.js:85:13
    at tryCatch1 (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/util.js:63:19)
    at Promise$_callHandler [as _callHandler] (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:695:13)
    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:711:18)
    at Promise$_settlePromiseAt [as _settlePromiseAt] (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:868:14)
    at Promise$_settlePromises [as _settlePromises] (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:1006:14)
    at Promise$_rejectPromises [as _rejectPromises] (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/promise.js:999:10)
    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/async.js:74:12)
    at Async$consumeFunctionBuffer (/usr/local/lib/node_modules/meteor-now/node_modules/promise-spawner/node_modules/bluebird/js/main/async.js:37:14)
    at _combinedTickCallback (node.js:370:9)
    at process._tickCallback (node.js:401:11)

jkrup · 2017-05-16T03:07:47Z

What version of node do you have? (node --version)

nilsi · 2017-05-16T03:18:07Z

$ node --version
v5.8.0

fknipp · 2017-06-17T16:57:57Z

I ran into similar problems and solved them by performing two steps:

Installing node version 6.9.0
Installing now version 4.10.3

sudo npm install -g n
sudo n 6.9.0
sudo npm install -g now@4.10.3

I've run the meteor-now command always with -d, I didn't try, if it works without the switch as well.

webmagnets · 2017-10-10T13:34:53Z

I was getting this error and using -d worked for me. For some reason the prompt "Are you sure you want to proceed with the deployment? [y|N] " only comes up if you use "-d".

jkrup · 2017-11-18T06:32:04Z

These issues should hopefully be fixed after our re-write #75 so I'm closing this thread. Please open another issue if you have any troubles with the latest version.

jkrup closed this as completed Nov 18, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Possibly unhandled Error: 1 at Promise$_rejecter #50

Possibly unhandled Error: 1 at Promise$_rejecter #50

crapthings commented Apr 24, 2017 •

edited

crapthings commented Apr 24, 2017

crapthings commented Apr 24, 2017

acomito commented Apr 24, 2017

purplecones commented Apr 24, 2017

ghost commented Apr 24, 2017

crapthings commented Apr 25, 2017 •

edited

ghost commented Apr 25, 2017

qualitymanifest commented Apr 25, 2017 •

edited

crapthings commented Apr 25, 2017 •

edited

ghost commented Apr 25, 2017

qualitymanifest commented Apr 27, 2017 •

edited

d62remi commented Apr 27, 2017

nilsi commented May 12, 2017 •

edited

jkrup commented May 16, 2017

nilsi commented May 16, 2017

fknipp commented Jun 17, 2017

webmagnets commented Oct 10, 2017

jkrup commented Nov 18, 2017

Possibly unhandled Error: 1 at Promise$_rejecter #50

Possibly unhandled Error: 1 at Promise$_rejecter #50

Comments

crapthings commented Apr 24, 2017 • edited

crapthings commented Apr 24, 2017

crapthings commented Apr 24, 2017

acomito commented Apr 24, 2017

purplecones commented Apr 24, 2017

ghost commented Apr 24, 2017

crapthings commented Apr 25, 2017 • edited

ghost commented Apr 25, 2017

qualitymanifest commented Apr 25, 2017 • edited

crapthings commented Apr 25, 2017 • edited

ghost commented Apr 25, 2017

qualitymanifest commented Apr 27, 2017 • edited

d62remi commented Apr 27, 2017

nilsi commented May 12, 2017 • edited

jkrup commented May 16, 2017

nilsi commented May 16, 2017

fknipp commented Jun 17, 2017

webmagnets commented Oct 10, 2017

jkrup commented Nov 18, 2017

crapthings commented Apr 24, 2017 •

edited

crapthings commented Apr 25, 2017 •

edited

qualitymanifest commented Apr 25, 2017 •

edited

crapthings commented Apr 25, 2017 •

edited

qualitymanifest commented Apr 27, 2017 •

edited

nilsi commented May 12, 2017 •

edited