mongodb-labs / edda

A log visualizer for MongoDB - This Repository is NOT a supported MongoDB product
232 stars 28 forks source link

Remote servers #101

Open pdtpatrick opened 12 years ago

pdtpatrick commented 12 years ago

Seems like Edda is assuming that all the logs live on one server? Is it possible to use remote servers? Or will one have to create some type of central logging or a NFS mount ?

pdtpatrick commented 12 years ago

I also keep getting blank page: http://screencast.com/t/IrvCWkIs

samantharitter commented 12 years ago

Yes, I believe you do have to have the files collected on one machine (or access remote files through an NFS so that they could behave like local files) in order to feed them through the program.

As for the blank screen, what browser are you using? Also, if you'd like to email the log files to me or to my partner, we can take a look at them.

pdtpatrick commented 12 years ago

I've tried using Chrome 20+ and Firefox 14 and Firefox Nightly build.

Here's the log:

https://gist.github.com/96bd62943695173e9c0b

kaushal commented 12 years ago

Your log runs fine on our machines, could you tell us what OS you are using, and if the chrome console is giving you any errors? On mac you can press command + option + J.

pdtpatrick commented 12 years ago

I'm using Ubuntu 12.04LTS

I installed pip doing:

sudo apt-get install python_pip

And then added build-essential and python-dev packages.

Then sudo pip install edda

Lastly:

edda log1 log2 log2. However I don't get any links so i searched for open ports and noticed port :28000 was listening. I connected to that and got a blank page. Is that the wrong link?

samantharitter commented 12 years ago

We've tested that os, so maybe it's something else. 28000 is the correct port. Did edda give you any errors before it launched the http server? You can run it with -v to track its progress in the terminal.

pdtpatrick commented 12 years ago

Here's the log with -v turned on:

https://gist.github.com/cb2ffbfa1af4e5724d76

samantharitter commented 12 years ago

Can you try to run edda on just the log you sent to us, marge.log? Also, once you run the program and open a page in chrome, does the chrome console report any errors?

pdtpatrick commented 12 years ago

https://gist.github.com/98bb9d513aac8c878006

pdtpatrick commented 12 years ago

Here's my mongo version:

ii mongodb 1:2.0.4-1ubunt

Are you using 2.0.4 as well? I installed directly from the repo and not through 10gen's repo.

pdtpatrick commented 12 years ago

Here's the js console on Chrome:

http://screencast.com/t/uP0VWdAFNeI

kaushal commented 12 years ago

So, we have found the source of your errors on that console log, the bad news is that our program isn't causing them and we still don't know why the app isn't working on your machine. If you uninstall the google dictionary chrome extension that you have you will get rid of those errors. Can you try uninstalling the extension and tell us if you still have any errors on your log, and tell us if you get the same errors in other browsers. That and please send us a screenshot of your console after you have run edda.

samantharitter commented 12 years ago

I notice in the most recent log you gave us that the server stopped serving, did you maybe Ctrl+C it too soon? It needs to stay up until you are entirely finished with the program, browser and all.

One other thing you could try, although I don't think it's the cause of your problem, is downloading the program's favicon and placing it in edda/edda/ui/display: https://github.com/kchodorow/edda/blob/master/edda/ui/display/favicon.ico We didn't include it in the packaged version, and you're getting a 404 error when the browser tries to load it.

pdtpatrick commented 12 years ago

I've uninstalled/disabled all chrome extensions - same problem.

The problem is the same on Firefox, Safari, Chrome -- all of which have no plugins enabled.

The favicon I don't think is a problem as it just add an icon atop.

The Ctrl + C was me killing the app after testing.

https://gist.github.com/2f1679858623aadfaf50

kaushal commented 12 years ago

Could you now send us your console log, and make sure you have no sort of firewall, or add block running.

pdtpatrick commented 12 years ago

Sure.

Here's a screenshot:

http://screencast.com/t/XyEPA6g9Iq

samantharitter commented 12 years ago

Can you try typing "localhost:28000" in for the url, once the server is running?

pdtpatrick commented 12 years ago

The server is running remotely. I also see that it is listening on 0.0.0.0:28000 which should work whether im doing localhost:28000 or fqdn:28000.

samantharitter commented 12 years ago

Ah. The program assumes that edda will be run on the same machine as the browser you're using to visualize. After the server serves up the basic pages (the stage you got to above) the web client makes some requests for additional data to the server at "localhost:28000." If you're running the server remotely, these requests will fail, hence the "undefined" error in your Chrome console. Can you try running edda on the machine where you're trying to view the web page?

Or, if you pulled from the repo and have the source files, and feel comfortable with JavaScript, I can guide you through trying to tweak edda to work with your remote server :)

kaushal commented 12 years ago

Hey I would like to close this issue. Would you be able to confirm that you got this problem solved or not?

pdtpatrick commented 12 years ago

Sure it can be closed. I'll wait until remote feature is added as part of the app. Thanks