Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy outputs "Error restarting process: bundle/main.js" message and fails. #18

Open
the0ther opened this issue Feb 6, 2014 · 8 comments

Comments

@the0ther
Copy link

the0ther commented Feb 6, 2014

I'm on an Ubuntu 12.10 instance, from alestic.com and have followed instructions you've provided as closely as I can.

The meteoric init seemed to go without a hitch. I SSH'd into my instance and found the site files in /home/meteor. I was able to run the site over port 80 "by hand". Very cool! Then I issued the meteoric deploy. Here's some of the output:

$ meteoric deploy                        
Updating codebase
Already on 'master'
Already up-to-date.
Creating new bundle. This may take a few minutes

Stand back while Meteorite does its thing
✓ iron-router
    tag: https://github.com/EventedMind/iron-router.git#v0.6.1
✓ spin
    tag: https://github.com/SachaG/meteor-spin.git#v0.2.0
✓ accounts-ui-bootstrap-dropdown
    tag: https://github.com/erobit/meteor-accounts-ui-bootstrap-dropdown.git#v0.6.5.1

Done installing smart packages

Ok, everything's ready. Here comes Meteor!

iron-router: updating npm dependencies -- connect...

Then a little later down, a million bundle/ files later I see this:

Starting forever
error:   Error restarting process: bundle/main.js
error:   Cannot find forever process: bundle/main.js
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: bundle/main.js

I SSH'd into my instance and tried out forever list as su and as non-su user. The su user showed no forever processes running. The non-su (ubuntu) user showed one forever job running. I looked at its logfile and found the following error:

/home/meteor/bundle/programs/server/node_modules/fibers/fibers.js:13
        throw new Error('`'+ modPath+ '.node` is missing. Try reinstalling `node-fibe
              ^
Error: `/home/meteor/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.11/fibers.node` is missing. Try reinstalling `node-fibers`?
    at Object.<anonymous> (/home/meteor/bundle/programs/server/node_modules/fibers/fibers.js:13:8)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (/home/meteor/bundle/programs/server/boot.js:1:75)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
error: Forever detected script exited with code: 1

Not sure yet what exactly is going on. Something with Fibers I guess?

@julien-c
Copy link
Owner

julien-c commented Feb 7, 2014

Hi Randy, which version of meteor? I remember we were having this issue recurrently at some point.

@the0ther
Copy link
Author

the0ther commented Feb 7, 2014

I'm on Meteor version "Release 0.7.0.1".

@zenmatt
Copy link
Contributor

zenmatt commented Feb 13, 2014

I have the same problem.

@zenmatt
Copy link
Contributor

zenmatt commented Feb 13, 2014

FYI I solved this problem by upgrading to the latest version of Node, the Ubuntu repo is outdated. Follow the instructions here: https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager

@julien-c
Copy link
Owner

@zenmatt Care to submit a Pull Request to that effect?

(Meteor used to require a legacy version of Node.)

@zenmatt
Copy link
Contributor

zenmatt commented Feb 13, 2014

Submitted.

@julien-c
Copy link
Owner

Thanks!

@the0ther
Copy link
Author

Thanks guys for looking at this. I'm still having problems, looking into it right now. My original issue may have been specious. Will update once I know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants