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

TypeError: Cannot read property '_monotonicStartTime' of null #124

Closed
wallslide opened this issue Dec 18, 2014 · 4 comments
Closed

TypeError: Cannot read property '_monotonicStartTime' of null #124

wallslide opened this issue Dec 18, 2014 · 4 comments

Comments

@wallslide
Copy link

I'm getting the following error on a Meteor project I've deployed to modulus.io:

/mnt/data/2/programs/server/packages/meteorhacks_kadira.js:3039
      throw err;                                                              
            ^
TypeError: Cannot read property '_monotonicStartTime' of null
    at Timer.unrefTimeout [as ontimeout] (timers.js:432:36)
[2014-12-18T06:42:40.365Z] Application CRASH detected. Exit code 7.
[2014-12-18T06:42:42.392Z] Application restarted with pid 11763
Kadira: completed instrumenting the app
Kadira: successfully authenticated

/mnt/data/2/programs/server/packages/meteorhacks_kadira.js:3039
      throw err;                                                              
            ^
TypeError: Cannot read property '_monotonicStartTime' of null
    at Timer.unrefTimeout [as ontimeout] (timers.js:432:36)
[2014-12-18T06:43:11.938Z] Application CRASH detected. Exit code 7.
[2014-12-18T06:43:13.963Z] Application restarted with pid 11803
Kadira: completed instrumenting the app
Kadira: successfully authenticated

/mnt/data/2/programs/server/packages/meteorhacks_kadira.js:3039
      throw err;                                                              
            ^
TypeError: Cannot read property '_monotonicStartTime' of null
    at Timer.unrefTimeout [as ontimeout] (timers.js:432:36)
[2014-12-18T06:43:43.594Z] Application CRASH detected. Exit code 7.
Kadira: completed instrumenting the app
Kadira: successfully authenticated
[2014-12-18T06:43:45.637Z] Application restarted with pid 11843

One of the error events in the KadiraUI looks like this:
https://ui.kadira.io/et/75ce0f7c-fae3-4f56-8dee-556b2dd62b83

Is this an error in the Kadira software itself, or is it just an unhandled exception caught by Kadira? Also, why is the stack trace so short?

@arunoda
Copy link
Member

arunoda commented Dec 18, 2014

It's an unhandled exception caught by Kadira
I'm quite not sure how it caused.
On Thu Dec 18 2014 at 12:23:25 PM wallslide notifications@github.com
wrote:

I'm getting the following error on a Meteor project I've deployed to
modulus.io:

/mnt/data/2/programs/server/packages/meteorhacks_kadira.js:3039
throw err;
^
TypeError: Cannot read property '_monotonicStartTime' of null
at Timer.unrefTimeout as ontimeout
[2014-12-18T06:42:40.365Z] Application CRASH detected. Exit code 7.
[2014-12-18T06:42:42.392Z] Application restarted with pid 11763
Kadira: completed instrumenting the app
Kadira: successfully authenticated

/mnt/data/2/programs/server/packages/meteorhacks_kadira.js:3039
throw err;
^
TypeError: Cannot read property '_monotonicStartTime' of null
at Timer.unrefTimeout as ontimeout
[2014-12-18T06:43:11.938Z] Application CRASH detected. Exit code 7.
[2014-12-18T06:43:13.963Z] Application restarted with pid 11803
Kadira: completed instrumenting the app
Kadira: successfully authenticated

/mnt/data/2/programs/server/packages/meteorhacks_kadira.js:3039
throw err;
^
TypeError: Cannot read property '_monotonicStartTime' of null
at Timer.unrefTimeout as ontimeout
[2014-12-18T06:43:43.594Z] Application CRASH detected. Exit code 7.
Kadira: completed instrumenting the app
Kadira: successfully authenticated
[2014-12-18T06:43:45.637Z] Application restarted with pid 11843

One of the error events in the KadiraUI looks like this:
https://ui.kadira.io/et/75ce0f7c-fae3-4f56-8dee-556b2dd62b83

Is this an error in the Kadira software itself, or is it just an unhandled
exception caught by Kadira? Also, why is the stack trace so short?


Reply to this email directly or view it on GitHub
#124.

@chasemb
Copy link

chasemb commented Dec 18, 2014

Are you on modulus? I'm getting the same issue.

@arunoda
Copy link
Member

arunoda commented Dec 18, 2014

see this: nodejs/node-v0.x-archive#8897

Don't go with node 0.10.34

@fiveisprime
Copy link

This is fixed in both Demeteorizer and directly in the Modulus CLI. Your Meteor
projects will automatically be deployed using node@0.10.33 which works.

I'll come up with a long term fix (infer the required version from Meteor) in the
near future, but your deploys will work again. <3

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

4 participants