I have upgrade meteor to 0.8.2 and got following error when build it on VPS:

kadira: updating npm dependencies -- debug, usage...
npm http GET https://registry.npmjs.org/usage
npm http 304 https://registry.npmjs.org/usage
npm http GET https://registry.npmjs.org/bindings
npm http 304 https://registry.npmjs.org/bindings
Traceback (most recent call last):
File "/home/vb/.meteor/tools/858c88b520/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 18, in
sys.exit(gyp.script_main())
AttributeError: 'module' object has no attribute 'script_main'
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/home/vb/.meteor/tools/858c88b520/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:340:16)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:807:12)
gyp ERR! System Linux 2.6.32-431.20.3.el6.x86_64
gyp ERR! command "node" "/home/vb/.meteor/tools/858c88b520/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/vb/.meteorite/packages/kadira/meteorhacks/kadira/6073fa5bdfb36478165977804f922796b6fc82de/.npm/package-new-1xxtlqu/node_modules/usage
gyp ERR! node -v v0.10.28
gyp ERR! node-gyp -v v0.13.0
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the usage package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls usage
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 2.6.32-431.20.3.el6.x86_64
npm ERR! command "/home/vb/.meteor/tools/858c88b520/bin/node" "/home/vb/.meteor/tools/858c88b520/bin/npm" "install" "[email protected]"
npm ERR! cwd /home/vb/.meteorite/packages/kadira/meteorhacks/kadira/6073fa5bdfb36478165977804f922796b6fc82de/.npm/package-new-1xxtlqu
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/vb/.meteorite/packages/kadira/meteorhacks/kadira/6073fa5bdfb36478165977804f922796b6fc82de/.npm/package-new-1xxtlqu/npm-debug.log
npm ERR! not ok code 0

Errors prevented bundling:
While building package kadira:
error: couldn't install npm package

With meteor 0.8.1.3 it was building and working ok...
Any ideas what's wrong?

Could you please help me fix this build issue? I try to build it in a Docker container on Ubuntu 14.04
Please let me know if you need more info. Thanks!

module.js:340
throw err;
^
Error: Cannot find module '/root/.meteorite/packages/kadira/meteorhacks/kadira/fa9a6446f6efb576953f99c01c03474f56f3852e/.npm/package-new-yekpyo/node_modules/usage/node_modules/.bin/node-gyp'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:906:3
npm ERR! [email protected] install: ./build.sh
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the usage package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ./build.sh
npm ERR! You can get their info via:
npm ERR! npm owner ls usage
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.13.0-24-generic
npm ERR! command "/root/.meteor/tools/858c88b520/bin/node" "/root/.meteor/tools/858c88b520/bin/npm" "install" "[email protected]"
npm ERR! cwd /root/.meteorite/packages/kadira/meteorhacks/kadira/fa9a6446f6efb576953f99c01c03474f56f3852e/.npm/package-new-yekpyo
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/.meteorite/packages/kadira/meteorhacks/kadira/fa9a6446f6efb576953f99c01c03474f56f3852e/.npm/package-new-yekpyo/npm-debug.log
npm ERR! not ok code 0

Errors prevented bundling:
While building package kadira:
error: couldn't install npm package

Kadira 2.11.10 cause meteor app to crash:

Your app is crashing. Here's the latest log.
/mnt/project/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:3002
    throw err;                                                                
          ^
TypeError: Cannot read property 'prototype' of undefined
    at Object.Kadira._startInstrumenting (packages/meteorhacks:kadira/lib/hijack/session.js:8)
    at Object.Kadira.connect (packages/meteorhacks:kadira/lib/kadira.js:71)
    at commonErrRegExps (packages/meteorhacks:kadira/lib/auto_connect.js:19)
    at /mnt/project/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:3216:4
    at /mnt/project/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:3361:3
    at /mnt/project/.meteor/local/build/programs/server/boot.js:168:10
    at Array.forEach (native)
    at Function._.each._.forEach (/home/user/.meteor/packages/meteor-tool/.1.0.34.p6qvqg++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
    at /mnt/project/.meteor/local/build/programs/server/boot.js:82:5
=> Exited with code: 7

But this issue only happens only on my server. On my dev machine all works well.
Meteor 0.9.4. Kadira settings is stored in Meteor.settings.

in the phonegap bundele the following error occurs
I20141130-18:58:09.485(4) (android:http://meteor.local/packages/meteorhacks_kadira.js:740) Uncaught TypeError: Cannot read property 'enableErrorTracking' of undefined

ISO 8601 / 24-hour format would be great.

Right now we can see both 12-h and 24-h formats:

I'm using meteor 0.9.3 and I noticed that on the server I receive the following message:
Meteor._wrapAsync has been renamed to Meteor.wrapAsync undefined
Kadira: completed instrumenting the app

On chrome I noticed the message on the bottom right: Waiting for engine.kadira.io

This should an easy bug fix.

Would help to link to the plans or summarize each

When I'm testing the performance of my app, I navigate to various routes then check the impact of those individual actions in the Kadira charts. I've just installed Subs Manager, and still see some wait times for cached subscriptions... the only explanation (other than a Subs Manager bug) is that another user is using the app and triggering new subscriptions.

Is there a way to monitor just my own actions, separate from others, so as to have a clear understanding of the immediate impact of individual tweaks on the app performance?

I guess a quick&dirty solution would be register another ID for the app, and use that ID via Meteor.settings while running the app separately with meteor run.

Just discovered the server-info package and thought it would be cool to have that kind of stats in APM, esp. active subscriptions and documents per subscription.

Is this possible? It would be super useful in large apps because right now Kadira tells me some query took a long time to count() but I have a bunch of places in my app where that count might have occurred.

Even more useful when taking over work by another dev.

The biggest performance bottleneck we're experiencing in our app right not is that oplog is disabled, despite setting up a replica set as described here.

It would be great if Kadira drilled down into the reasons for that, e.g.

• no MONGO_OPLOG_URL env var
• query with limit or skip but without sort
• special operators

Hey,

I'm using the collection-hooks package. When calling the direct update method on a colletion without specifying options, I get the following error:

Cannot read property 'upsert' of undefined
at mongoConnectionProto.(anonymous function) [as update] (packages/kadira/lib/hijack/db.js:18)

Looks like you should check that options is defined :)

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?

Hi,

In few scenarios, I am throwing exception from server using throw new Meteor.Error(status, reason).

It was working fine, but after adding kadira, whenever server throws error, it is wrapped and all I get on front end is "Internal Server Error"

How can I get the handle of real error generated?

Thanks.

Thought I'd follow some good practice and put the appId and appSecret in my settings.json:

"kadira" : {
   "id": <abc>,
   "secret": <xyz>
}

then initialize on the server as follows:

Meteor.startup(function() {
    Kadira.connect(Meteor.settings.kadira.id, Meteor.settings.kadira.secret);
});

but that crashes Kadira!

Renaming the setting to kadira_app works:

Meteor.startup(function() {
    Kadira.connect(Meteor.settings.kadira_app.id, Meteor.settings.kadira_app.secret);
});

This happens also with the latest 2.11.2 release.

Here's the server log:

W20141006-21:04:35.931(2)? (STDERR) /Users/dirkstevens/MadeWithWonder/surveymonkey/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:2951
W20141006-21:04:35.931(2)? (STDERR)     throw err;                                                                
W20141006-21:04:35.932(2)? (STDERR)           ^
W20141006-21:04:35.940(2)? (STDERR) Error: Kadira: required appId and appSecret
W20141006-21:04:35.940(2)? (STDERR)     at Object.Kadira.connect (packages/meteorhacks:kadira/lib/kadira.js:67)
W20141006-21:04:35.946(2)? (STDERR)     at commonErrRegExps (packages/meteorhacks:kadira/lib/auto_connect.js:15)

I'm running my app at phusion passenger. 4.0.53
And the server OS is centOS 6.3

Running the app, there is an error as following:

Error: EACCES, permission denied
App 34327 stderr: at [object Object].SystemModel.buildPayload (/home/www/bookpal/site_www/programs/server/packages/meteorhacks_kadira.js:1082:28)
App 34327 stderr: at Object.Kadira._buildPayload (/home/www/bookpal/site_www/programs/server/packages/meteorhacks_kadira.js:1341:42)
App 34327 stderr: at /home/www/bookpal/site_www/programs/server/packages/meteorhacks_kadira.js:1420:26

At first, the server seems to work well.
However, after some seconds, the app tries to restart to fail several times.
About 1~3 minutes later, the server works but to restart again, again.

Excluding the Kadira configuration, the server works well and does not restart again.

What is the solution?

Attempt to install CORDOVA-PREVIEW@5 fail with metaorhacks:kadira package presented:

Refreshing package metadata. This may take a moment.
Figuring out the best package versions to use. This may take a moment.
This project is at the latest release which is compatible with your
current package constraints.

After "meteor remove metaorhacks:kadira", CORDOVA-PREVIEW@5 was installed successfully...

Right now the JSON is hard to read:

I use Kadira with http-publish & http-methods. I get this error:

ERROR TypeError: Cannot read property 'upsert' of undefined
I20140924-11:16:31.054(2)? at mongoConnectionProto.(anonymous function) "[as update]" (packages/meteorhacks:kadira/lib/hijack/db.js:18)
I20140924-11:16:31.054(2)? at Object.m.(anonymous function) (packages/mongo/collection.js:868)

If I remove kadira my app work ok

Does Kadira support Cordova ?

I am using meteor build --debug ... to generate a APK file and install it on my android phone.
When I inspect my app (using USB Debugging & Chrome) I see the following error on my console:

GET http://192.168.2.111:39455/undefined/simplentp/sync 404 (Not Found)

When using a regular desktop or mobile browser everything goes fine...

After installing Kadira 2.7.4 and Zones 1.2.1, I began to notice that some of my Meteor subscriptions would no longer work. It would typically occur when my Meteor app was up while the computer went to sleep - when it awoke after some time later I'd realize that my local collections would be empty. Meteor.call() methods would also not work. However, Meteor.status() would say that it was connected.

Unfortunately I don't have an isolated test case for you. I'm pretty sure it was Kadira and Zones because I exhaustively tested the app after removing each package, and after removing those it suddenly worked.

Not sure how helpful this is. Something to keep an eye on though.

It looks like within the past few hours, Kadira has been blocking our app. htop showed 100% or more CPU usage, and http://stockbase.com:3000 would never complete loading.

After removing kadira from .meteor/packages and the Kadira.connect(Meteor.settings.Kadira.appId, Meteor.settings.Kadira.appSecret); server code, the app runs normally (<5% CPU usage).

What made me suspect Kadira was the culprit is that I saw the Kadira: successfully authenticated message, but not the Kadira: completed instrumenting the app one despite waiting for ~15 minutes.

When the endpoint for Kadira is not configured (e.g. in the development environment), it's better not to trigger the sync procedure rather than triggering some random URL.

Hi there,

Thanks for this cool package / service. I'm getting a strange error that looks to be coming from your end. Has no real effect on me, but wanted to share with you.

Cannot read property 'stack' of null stack:
TypeError: Cannot read property 'stack' of null
at Object.Meteor._debug (packages/meteorhacks:kadira/lib/hijack/error.js:53)
at packages/spiderable/spiderable_server.js:101
at ChildProcess.exithandler (child_process.js:646:7)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:756:16)
at Process.ChildProcess._handle.onexit (child_process.js:823:5)

Thoughts?

Thanks!

[moving https://github.com/arunoda/meteor-apm-client/issues/41 here]

Aside from bugs like this,

it seems that the spline chart view may obscure some traces; in my experience with Kadira, traces could be hidden beneath other traces in the chart, or some traces didn't correlate with the chart.

I'm particularly interested in response time charts. My understanding is that traces are outliers picked among averages over 1 minute, but I've seen more than one trace under one point in the chart. Perhaps switching to bar charts (issue #29) would solve this problem? Also, displaying data points on the chart (like in this HighCharts example) would help.

I am not using iron-router
Can I add kadira in tha case?

Attempt gave the following error:
$ mrt add kadira

/usr/local/lib/node_modules/meteorite/lib/meteor.js:154
throw "Error running a command: " + error;
^
Error running a command: Error: Command failed: => Errors while scanning packages:

While building package blaze-layout:
error: no such package: 'iron-router'

HighCharts allows for chart zooming easily. This would enable the user better granularity than the predefined intervals (1 week, 24 hours, 30 minutes).

Would this be as easy as setting a parameter in the HighCharts constructor, or would it require backend code to supply the precise data for the selected interval?

[moved here from meteorapm-client]

I have a wait time of around 30 seconds (no idea how these things happen), across several operations. It would be great if Kadira could break down the time by operation. Not sure how to debug otherwise - those IDs for unsubscriptions, how can they be used? Are they just for Kadira's own debugging purpose?

[moved here from meteorapm-client]

For most of the apps, Response Time below 1.5 seconds, but in general, setting the HighCharts yAxis.label.format dynamically based on the max-min range would be nice.

CC @JohnAllen

I just tried to use your product, but I'm getting the following error on startup:

.meteor/packages/meteor-tool/.1.0.35.hg0z2p++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:173
                                             throw(ex);
                                                 ^
Error: use "new" to construct a Mongo.Collection
at new Mongo.Collection (packages/mongo/collection.js:29)
at exposeMongoLivedata (packages/meteorhacks:meteorx/lib/mongo-livedata.js:2)
at Package (packages/meteorhacks:meteorx/lib/server.js:6)
at  .meteor/local/build/programs/server/packages/meteorhacks_meteorx.js:166:4
at  .meteor/local/build/programs/server/packages/meteorhacks_meteorx.js:175:3
at  .meteor/local/build/programs/server/boot.js:168:10
at  Array.forEach (native)
at  Function._.each._.forEach (.meteor/packages/meteor-tool/.1.0.35.hg0z2p++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
at  .meteor/local/build/programs/server/boot.js:82:5

I've tried adding my keys to both settings, and directly in code, but both result in the same error. I'm using the Meteor 1.0 release.

I'll comment how to reproduce this one soon.

Currently we are overriding Meteor._debug and throwing it. Needs to change that.

Only do it if there is a zone.
If not pass the error to the original method.

You need to do this on zones.

Then capture Meteor._debug output inside kadira and send it to the engine.

Reason:

On, IE zones does not work sometimes. So throwing error makes it uncatchable and we can't track the stack from window.error. (BTW: stack trace does not provide anything in production)

Any we can track it directly from Meteor._debug and send it to engine.

This issue isn't breaking anything for me, as I worked around the issues, but I had to manually add request in our dockerfile at https://github.com/ongoworks/launchdock/blob/master/Dockerfile

Otherwise, I was getting the following error after building and then running the docker image:

/meteor/bundle/programs/server/packages/meteorhacks_kadira.js:2680
    throw err;
          ^
Error: Cannot find module 'request'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.Npm.require (/meteor/bundle/programs/server/boot.js:88:18)
    at app/server/main.js:4:15
    at app/server/main.js:124:3
    at /meteor/bundle/programs/server/boot.js:161:10
    at Array.forEach (native)
    at Function._.each._.forEach (/meteor/bundle/programs/server/node_modules/underscore/underscore.js:79:11)

Also, I'm sure this is part of the new packaging process I'm still grappling with, but locally it's kadira @ 2.9.2, but when building on linux/boot2docker, meteor downgrades Kadira to 2.9.0

upgraded meteorhacks:kadira from version 2.9.2 to version 2.9.0

Maybe the linux arch version isn't updated? Not sure how to see the arch packages though.

Please see the stack trace below:

Also I tried cordova

meteor add meteorhacks:[email protected]

this led to the error below.

I work on very special meteor project, it runs on embedded system, with ARM processor, low memory and low disk resources.

Because of that it doesn't use mongodb and does not depend on mongo-livedata.

Is there any way to use kadira without mongo-livedata? Is it a strong dependency?

Low priority. Just saw this apparently transient collection in the mongo debug interface, and I'm running Kadira on Windows. Thought maybe it shouldn't be created at all.

Seems to be coming from kadira?

Restart complete.
Kadira: completed instrumenting the app
[2014-09-17T19:30:53.899Z] Application started with pid 137857
Kadira: successfully authenticated

/mnt/data/1/programs/server/packages/meteorhacks_kadira.js:2585
throw err;
^
Error: listen EADDRINUSE
at errnoException (net.js:904:11)
at Server._listen2 (net.js:1042:14)
at listen (net.js:1064:10)
at net.js:1146:9
at dns.js:72:18
at process._tickCallback (node.js:419:13)
[2014-09-17T19:30:53.922Z] Application CRASH detected. Exit code 7.```

With Meteor 0.9.3 and latest Firefox/Chrome the tracebacks are formatted poorly like so:

How to reproduce? Setup a fresh project, add meteorhacks:kadira package, set it up so it authenticates

then run in client console:

Meteor._debug("foo", "bar")

Without Kadira this will print:

foo bar

With Kadira it prints:

["foo", "bar"]

I am running CentOS release 6.4 (Final). Has anybody resolved this already ?

Our use case may be atypical, because we monitor with Kadira a staging app, accessible only to developers. Therefore, there are only a few queries, when we test a particular function of the app:

In this case, the bell shape of the spline chart is misleading - there have been no queries actually aside from the peak of that curve.

A better shape would be a column chart, which would only show one spike for 14:21. In my opinion this would be a more accurate indication of when spikes are happening, but if some users prefer the spline display, maybe it could made a setting.

Recommendations are great for new Kadira users, but after using it for a while, the actual stats become more important. It would be nice to dedicate more screen real estate above the fold to that. One way would be add a button to collapse the recommendations.

Hello.

I'm using kadira for a long time and it works almost perfectly for me. But sometimes I want to prevent it form sending any data to kadira server (i.e. while developing). I don't want to disable it completely (i.e. with if (Meteor.settings.env === 'development')).

"You've not added oplog support"
Should be "You haven't added oplog support"

I just updated and saw that zones and inject-initial are now required. Unfortunately one of these is doing an eval which is violating my browser policy:

BrowserPolicy.content.disallowEval()

For now I've reverted to an earlier version. Is there a really compelling reason to be doing eval?Alternatively is there a way to not use these packages? Globally allowing eval is a showstopper for me.

Furthermore, are any other security implications we need to know about when adding any of these three packages? e.g. are cookies enabled?

Getting this error while running locally. Any idea on how to fix it? Thanks!

Just saw this in my logs:

/mnt/data/1/programs/server/packages/meteorhacks_kadira.js:3006
    throw err;                                                                
          ^
RangeError: Maximum call stack size exceeded

meteorhacks:kadira 2.12.0

In meteor version 0.8 session.close can be directly used to close session. Do that.

Hey guys.. .we're starting to see this.. any way to figure out whats going wrong?

=> Meteor server restarted
W20141201-16:13:02.775(-5)? (STDERR)
W20141201-16:13:02.776(-5)? (STDERR) /Users/vlad/Sites/kn/kname/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:3006
W20141201-16:13:02.777(-5)? (STDERR) throw err;
W20141201-16:13:02.777(-5)? (STDERR) ^
W20141201-16:13:02.777(-5)? (STDERR) Error: spawn ENOENT
W20141201-16:13:02.778(-5)? (STDERR) at errnoException (child_process.js:1000:11)
W20141201-16:13:02.778(-5)? (STDERR) at Process.ChildProcess._handle.onexit (child_process.js:791:34)
=> Exited with code: 7
I20141201-16:13:36.426(-5)? Kadira: completed instrumenting the app
I20141201-16:13:36.792(-5)? Kadira: successfully authenticated
=> Meteor server restarted
W20141201-16:13:37.619(-5)? (STDERR)
W20141201-16:13:37.620(-5)? (STDERR) /Users/vlad/Sites/kn/kname/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:3006
W20141201-16:13:37.621(-5)? (STDERR) throw err;
W20141201-16:13:37.621(-5)? (STDERR) ^
W20141201-16:13:37.621(-5)? (STDERR) Error: spawn ENOENT
W20141201-16:13:37.622(-5)? (STDERR) at errnoException (child_process.js:1000:11)
W20141201-16:13:37.622(-5)? (STDERR) at Process.ChildProcess._handle.onexit (child_process.js:791:34)
=> Exited with code: 7
I20141201-16:14:05.139(-5)? Kadira: completed instrumenting the app
I20141201-16:14:05.520(-5)? Kadira: successfully authenticated
=> Meteor server restarted
W20141201-16:14:06.448(-5)? (STDERR)
W20141201-16:14:06.449(-5)? (STDERR) /Users/vlad/Sites/kn/kname/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:3006
W20141201-16:14:06.450(-5)? (STDERR) throw err;
W20141201-16:14:06.450(-5)? (STDERR) ^
W20141201-16:14:06.450(-5)? (STDERR) Error: spawn ENOENT
W20141201-16:14:06.451(-5)? (STDERR) at errnoException (child_process.js:1000:11)
W20141201-16:14:06.451(-5)? (STDERR) at Process.ChildProcess._handle.onexit (child_process.js:791:34)
=> Exited with code: 7