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

Crash Looping #18

Open
zachflanders opened this issue Aug 26, 2013 · 1 comment
Open

Crash Looping #18

zachflanders opened this issue Aug 26, 2013 · 1 comment

Comments

@zachflanders
Copy link

Getting the following email from node jitsu: Redeployed and it worked for a bit before they stopped it again. Not sure where the problem is. . .

Your application was crash looping! It has been stopped.

Don't worry, once you find the source of the problem you can restart it.

To restart your application run the following jitsu command:

jitsu apps start crowdgauge 

If you are still having trouble logging in or if you have any questions, please feel free to email [email protected], visit our support center, or join the #nodejitsu channel on irc.freenode.net!

  • The Nodejitsu Team
    If you'd like to unsubscribe and stop receiving these emails click here.
@gouldingken
Copy link
Contributor

Its notoriously difficult to debug this kind of error in Nodejitsu as you can't look at the crash logs.

In the NEO branch of CrowdGauge (which is the latest branch but hasn't been merged in yet), you will see we added this code to handle (and log) uncaught exceptions.

process.on('uncaughtException', function (err) {
console.log('****************** uncaught exception:' + err);
});

Hope that helps.

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

2 participants