edda icon indicating copy to clipboard operation
edda copied to clipboard

Not able to run edda with my log file

Open shalusingh0411 opened this issue 10 years ago • 15 comments

I have installed edda with "pip install edda" but i am not able to run it with my log file. I am using the log file of the same server, also the mongo instance on my local machine is on still i am getting this error.

shalu@shalu-desktop:~$ sudo edda /home/shalu/Desktop/1.log [sudo] password for shalu:

Currently parsing log-file: /home/shalu/Desktop/1.log [===================================================================================================]100%CRITICAL:edda.run_edda:No servers were found, exiting.

shalusingh0411 avatar May 27 '14 07:05 shalusingh0411

Hi there, can you tell me what version of mongod your log files are from?

samantharitter avatar May 27 '14 13:05 samantharitter

Hi Samantha, I am using 64-bit mongod db with version v2.6.1. And using the log files of the same server On May 27, 2014 7:12 PM, "Samantha Ritter" [email protected] wrote:

Hi there, can you tell me what version of mongod your log files are from?

— Reply to this email directly or view it on GitHubhttps://github.com/10gen-labs/edda/issues/124#issuecomment-44277524 .

shalusingh0411 avatar May 28 '14 04:05 shalusingh0411

Thanks. The reason you aren't able to run edda is because the current version of the visualizer on pip doesn't support mongod v2.6. This has been fixed in master, so if you clone into the repository, you should be able to run it like this:

$ python edda/run_edda.py path_to_logfile

samantharitter avatar May 28 '14 14:05 samantharitter

Thanks Samantha, i even tried like this but it didn't worked for me. It says no such file run_edda.py On May 28, 2014 8:04 PM, "Samantha Ritter" [email protected] wrote:

Thanks. The reason you aren't able to run edda is because the current version of the visualizer on pip doesn't support mongod v2.6. This has been fixed in master, so if you clone into the repository, you should be able to run it like this:

$ python edda/run_edda.py path_to_logfile

— Reply to this email directly or view it on GitHubhttps://github.com/10gen-labs/edda/issues/124#issuecomment-44414298 .

shalusingh0411 avatar May 28 '14 15:05 shalusingh0411

Hi shalusingh0411, you may be using the wrong path to run_edda.py then. You'll need to navigate into the top-level directory of the repository, or change the path you're using:

$ git clone (SSH or HTTPS git path for edda)
$ cd edda
$ python edda/run_edda.py path_to_logfile

samantharitter avatar May 28 '14 15:05 samantharitter

Hi shalusingh0411, can you tell me if this solved your problem?

samantharitter avatar May 30 '14 13:05 samantharitter

Hi, no same error came parsing complete 100% no server found. On May 30, 2014 7:10 PM, "Samantha Ritter" [email protected] wrote:

Hi shalusingh0411, can you tell me if this solved your problem?

— Reply to this email directly or view it on GitHub https://github.com/10gen-labs/edda/issues/124#issuecomment-44651340.

shalusingh0411 avatar May 30 '14 14:05 shalusingh0411

Hm, is it possible for you to email me your log file, so I can try to reproduce your problem? [email protected]

samantharitter avatar May 30 '14 14:05 samantharitter

Yes I will send it you. And will also share the procedure of how I have installed Edda on my system. On May 30, 2014 7:36 PM, "Samantha Ritter" [email protected] wrote:

Hm, is it possible for you to email me your log file, so I can try to reproduce your problem? [email protected]

— Reply to this email directly or view it on GitHub https://github.com/10gen-labs/edda/issues/124#issuecomment-44654205.

shalusingh0411 avatar May 30 '14 16:05 shalusingh0411

Hi there, I was just wondering if you'd been able to resolve your issue? I haven't received your logs, if you're still experiencing problems running edda, perhaps you could send them to me again.

samantharitter avatar Jun 13 '14 18:06 samantharitter

Samantha I am experiencing the same issue w/ mongo version 3.0. python 2.7 package and pip installed . I am doing research for a company and they gave me a log file which is rather large so i will link it to you in your email for you to download as a dropbox. Thank you.

tuanbuix avatar Mar 10 '15 22:03 tuanbuix

Is this tool abandoned now? Doesn't seem to work :/ 'ImportError: No module named bson'

timdonovanuk avatar Jun 05 '15 15:06 timdonovanuk

i am not sure. it has comparability issues at the moment and still in developing.

Date: Fri, 5 Jun 2015 08:59:42 -0700 From: [email protected] To: [email protected] CC: [email protected] Subject: Re: [edda] Not able to run edda with my log file (#124)

Is this tool abandoned now? Doesn't seem to work :/

'ImportError: No module named bson'

— Reply to this email directly or view it on GitHub.

tuanbuix avatar Jun 05 '15 16:06 tuanbuix

Hi there @timdonovanuk , it's possible that with the recent pymongo update this tool will also need to be updated. For the time being, I would try this with an older version of pymongo and see if the import error goes away. Additionally, the format of log messages may have changed in 3.0, this tool has not yet been updated for mongodb 3.0 logs.

@tuanbuix I thought we had mostly worked through your errors, are there other things you're having issues with at the moment?

Maintaining this project is something that I do when I have the time, but it's definitely in "maintenance" mode more than active feature development.

samantharitter avatar Jun 05 '15 16:06 samantharitter

Yeah we did!, we just need to match up the correct versions, was unable to parse the big log files. sample logs was a success. not sure in tim's case. he will probably needs to explain in greater detail.

Date: Fri, 5 Jun 2015 09:57:12 -0700 From: [email protected] To: [email protected] CC: [email protected] Subject: Re: [edda] Not able to run edda with my log file (#124)

Hi there @timdonovanuk , it's possible that with the recent pymongo update this tool will also need to be updated. For the time being, I would try this with an older version of pymongo and see if the import error goes away. Additionally, the format of log messages may have changed in 3.0, this tool has not yet been updated for mongodb 3.0 logs.

@tuanbuix I thought we had mostly worked through your errors, are there other things you're having issues with at the moment?

Maintaining this project is something that I do when I have the time, but it's definitely in "maintenance" mode more than active feature development.

— Reply to this email directly or view it on GitHub.

tuanbuix avatar Jun 05 '15 20:06 tuanbuix