Any luck with open-sourced Kadira?

help
1

We have a rogue app that’s bombing on Galaxy, trying to consume over 1GB of RAM. I figured this is a job for Kadira, to see what’s eating up so much memory.

I followed the very basic instructions, but am not having luck. All three services are running, but when my app tries to connect, it says:

I20170516-16:41:32.067(-5)? Kadira: completed instrumenting the app
I20170516-16:41:32.118(-5)? Kadira: authentication failed - check your appId & appSecret

The ID and secret are definitely correct. The rma process shows some weirdness going on:

[run:system-30min ] MongoDB server version: 3.2.13
[run:system-30min ] WARNING: shell and server versions do not match
[run:system-1min  ] very strange! - no entries found
[run:system-1min  ] + set +x
[run:system-1min  ] Tue May 16 16:52:59 CDT 2017: end map-reduce process (tooks 3 secs)
[run:errors-3hour ] MongoDB shell version v3.4.4
[run:errors-3hour ] connecting to: mongodb://ds143081-a.mlab.com:43081/kadira-data
[run:system-30min ] loading file: profiles/30min.js
[run:system-30min ] loading file: providers/system.js
[run:system-30min ] loading file: env-30min-system.js
[run:system-30min ] loading file: lib.js
[run:system-30min ] loading file: mapreduce.js
[run:system-30min ] loading file: incremental-aggregation.js
[run:system-30min ] connecting to: mongodb://ds143081-a.mlab.com:43081/kadira-data
[run:errors-3hour ] MongoDB server version: 3.2.13
[run:errors-3hour ] WARNING: shell and server versions do not match
[run:system-30min ] MongoDB server version: 3.2.13
[run:system-30min ] WARNING: shell and server versions do not match
[run:system-30min ] authenticating appDb:  ds143081-a.mlab.com:43081/kadira-data
[run:errors-3hour ] loading file: profiles/3hour.js
[run:errors-3hour ] loading file: providers/errors.js
[run:errors-3hour ] loading file: env-3hour-errors.js
[run:errors-3hour ] loading file: lib.js
[run:errors-3hour ] loading file: mapreduce.js
[run:errors-3hour ] loading file: incremental-aggregation.js
[run:errors-3hour ] connecting to: mongodb://ds143081-a.mlab.com:43081/kadira-data
[run:system-30min ] NO CONFIG DEFINED!
[run:system-30min ] {
[run:system-30min ] 	"value.res" : "1min",
[run:system-30min ] 	"value.appId" : {
[run:system-30min ] 		"$ne" : "c90153bf-147d-41e5-86e7-584872a61d2b"
[run:system-30min ] 	}
[run:system-30min ] }
[run:system-30min ]   Using local MR
[run:system-30min ]    need to fetch: 0
[run:errors-3hour ] MongoDB server version: 3.2.13
[run:errors-3hour ] WARNING: shell and server versions do not match
[run:errors-3hour ] authenticating appDb:  ds143081-a.mlab.com:43081/kadira-data
[run:system-30min ]    fetched in: 45 ms
[run:system-30min ]    writing completed in: 0 ms
[run:system-30min ] very strange! - no entries found
[run:system-30min ] + set +x
[run:system-30min ] Tue May 16 16:52:59 CDT 2017: end map-reduce process (tooks 2 secs)
[run:errors-3hour ] NO CONFIG DEFINED!
[run:errors-3hour ] {
[run:errors-3hour ] 	"value.res" : "30min",
[run:errors-3hour ] 	"value.appId" : {
[run:errors-3hour ] 		"$ne" : "c90153bf-147d-41e5-86e7-584872a61d2b"
[run:errors-3hour ] 	}
[run:errors-3hour ] }
[run:errors-3hour ]   Using local MR
[run:errors-3hour ]    need to fetch: 0
[run:errors-3hour ]    fetched in: 36 ms
[run:errors-3hour ]    writing completed in: 1 ms
[run:errors-3hour ] very strange! - no entries found
[run:errors-3hour ] + set +x
[run:errors-3hour ] Tue May 16 16:53:00 CDT 2017: end map-reduce process (tooks 3 secs)
(truncated)

Side note: can we hack this thing to get pro-plan features?

2

Take all the line breaks out of your config file. {json:“one line only”}

I always get that when loading in config settings. Looks like the case?

3

I wrote about that here

maybe it helps!

4

Hmm… not totally sure on this. I couldn’t even get OAuth working (to log in with my Meteor account). One has to make their own Meteor dev app and specify a callback URL, and put that key & secret into the settings. I also had to fix quite a few mistakes to get it semi-working but still couldn’t get past signin.

This would be a great candidate for Dockerization. :slight_smile:

5

I’m having the same issue

6

Finally got it working
It was firewall issue
Make sure your Meteor host can curl Kadira at http://ip:11011
curl http://ip:11011
It should returns nothing
If it returns nothing, it means it can connect to the server