-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
Hi Randy, which version of meteor? I remember we were having this issue recurrently at some point. |
I'm on Meteor version "Release 0.7.0.1". |
I have the same problem. |
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 |
@zenmatt Care to submit a Pull Request to that effect? (Meteor used to require a legacy version of Node.) |
Submitted. |
Thanks! |
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. |
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 themeteoric deploy
. Here's some of the output:Then a little later down, a million bundle/ files later I see this:
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:Not sure yet what exactly is going on. Something with Fibers I guess?
The text was updated successfully, but these errors were encountered: