Crashes Meteor Startup with no error message

[MichaelJCole]

Hey, this project is crashing Meteor with no error message at startup. Which is kind of annoying.

I tracked it down to this function:

  function gracefulExit() {
    if (doExit && !responded) {
      //
      // Remark: Currently ignoring any exceptions from transports
      //         when catching uncaught exceptions.
      //
      clearTimeout(timeout);
      responded = true;
      process.exit(1);
    }
  }

There should probably be a console.log('Winston-papertrail failed to start'); so that it's clear why/where meteor is failing to start.

The console looks like this:

☔  meteor                                                                                                                   Mod master
[[[[[ ~/scm/project ]]]]]        

=> Started proxy.                             
=> Started MongoDB.                           
I20150815-13:54:29.362(-5)? info:  =====> Meteor App restarted Sat Aug 15 2015 13:54:29 GMT-0500 (CDT)
=> Exited with code: 1
[Repeats restarted and exited messages.]

[rootedsoftware]

+1

@MichaelJCole Did you just start using a different package, or were you able to fix this?

[MichaelJCole]

I didn't find a workaround yet. If I get back to this, I'll probably fork the package, like wylio did.

[rootedsoftware]

I noticed when I looked at the logs on https://papertrailapp.com/ I could
see more details about the crash. They weren't extremely helpful because
they were based on the built code, but they gave me something to look for
and I did eventually narrow it down to two issues in my code. First, the
wylio:mandrill package has breaking changes and second, I had a stripe
package which I was declaring the publishable key in both the client and
server startups when it should have only been in the client.

I'm not sure why these seemingly both broke, when they'd been in my code
for a while.

On Fri, Sep 25, 2015 at 2:12 PM, Michael Cole [email protected]
wrote:

I didn't find a workaround yet. If I get back to this, I'll probably fork
the package, like wylio did.

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

Joshua Bechard

Learn to do right! Seek justice, encourage the oppressed.
Defend the cause of the fatherless,
plead the case of the widow.

Isaiah 1:17

[elie222]

I think I got this error too, and removing: "debug": true from my Meteor settings file fixed it.
I don't know if this was an error in my code, and I don't know it was this package causing it either. But might help someone else out.