Error deploying app with Kadira about kadira

[patrickleet]

Release [email protected]
Versions:
meteorhacks:[email protected]
meteorhacks:[email protected]

[patrickleet]

Deploying on Modulus, FYI

[patrickleet]

Looks like that's the uncaughtException block - may be coming from somewhere else then? It works locally though

process.on('uncaughtException', function (err) { // 1
// let the server crash normally if error tracking is disabled // 2
if(!Kadira.options.enableErrorTracking) { // 3
throw err; // 4
} // 5
// 6
// looking for already tracked errors and throw them immediately // 7
// throw error immediately if kadira is not ready // 8
if(err._tracked || !Kadira.connected) { // 9
throw err; // 10
} // 11
// 12
var trace = getTrace(err, 'server-crash', 'uncaughtException'); // 13
Kadira.models.error.trackError(err, trace); // 14
Kadira.sendPayload(function () { // 15
clearTimeout(timer); // 16
throwError(err); // 17
}); // 18
// 19
var timer = setTimeout(function () { // 20
throwError(err); // 21
}, 1000*10); // 22
// 23
function throwError(err) { // 24
// sometimes error came back from a fiber. // 25
// But we don't fibers to track that error for us // 26
// That's why we throw the error on the nextTick // 27
process.nextTick(function() { // 28
// we need to mark this error where we really need to throw // 29
err._tracked = true; // 30
throw err; // 31
}); // 32
} // 33
});

[arunoda]

Yes. We track uncaughtExceptions, that's why you are getting this. Did you
talk to modulus guys?
Are you setting up the PORT env variable? If so, please avoid using it.

On Thursday, September 18, 2014, Patrick Scott [email protected]
wrote:

Looks like that's the uncaughtException block - may be coming from
somewhere else then? It works locally though

process.on('uncaughtException', function (err) { // 1
// let the server crash normally if error tracking is disabled // 2
if(!Kadira.options.enableErrorTracking) { // 3
throw err; // 4
} // 5
// 6
// looking for already tracked errors and throw them immediately // 7
// throw error immediately if kadira is not ready // 8
if(err._tracked || !Kadira.connected) { // 9
throw err; // 10
} // 11
// 12
var trace = getTrace(err, 'server-crash', 'uncaughtException'); // 13
Kadira.models.error.trackError(err, trace); // 14
Kadira.sendPayload(function () { // 15
clearTimeout(timer); // 16
throwError(err); // 17
}); // 18
// 19
var timer = setTimeout(function () { // 20
throwError(err); // 21
}, 1000*10); // 22
// 23
function throwError(err) { // 24
// sometimes error came back from a fiber. // 25
// But we don't fibers to track that error for us // 26
// That's why we throw the error on the nextTick // 27
process.nextTick(function() { // 28
// we need to mark this error where we really need to throw // 29
err._tracked = true; // 30
throw err; // 31
}); // 32
} // 33
});

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

---

Arunoda Susiripala
I curate Meteor Weekly - Check it out!
http://meteorhacks.com/meteor-weekly/?utm_source=email-footer&utm_medium=email&utm_campaign=meteorweekly

[patrickleet]

Yea the issue was on their end, a rogue node process on the servo

Thanks!

[arunoda]

Okay. Good to know.

On Thursday, September 18, 2014, Patrick Scott [email protected]
wrote:

Closed #81 #81.

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

---

Arunoda Susiripala

@arunoda http://twitter.com/arunoda
http://gplus.to/arunodahttps://github.com/arunoda
http://www.linkedin.com/in/arunoda