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
Error in search_fulltext.py #97
Comments
It seems that you have no indexes in the whoosh directory. It could be that the indexing was not done at the initial import. You can run manually the indexing by doing the following command:
and then do search again using search_fulltext.py. If you any issue, let me know. |
@adulau Thanks for reply. But running the command
Thanks |
hi @adulau |
It seems that the indexdir is not at the right place. Could you check where you Whoosh indexes were created? You can update it from the tool itself (I still need to update the code to use the directory path from the config file) |
@adulau Thanks Alexandre. I googled it (whoosh.index.EmptyIndexError: Index 'MAIN' does not exist in FileStorage('indexdir')) but i couldn't find any solution @PidgeyL This error occurs in the same configuration bug that you helped me fix it. |
Could you just check if you have the index built by db_fulltext.py? it's in indexdir with files likes MAIN_*. |
@adulau Thanks for reply. But running the command I have a folder called " idexdir " with these files This is correct? Or wrong? |
I didn't search for related issues when I opened #115, sorry for that. Had some time to do some additional debugging today:
I'll keep looking as well. |
thanks @tunkaflux I tried what you say and do not work for me :( in the folder
Then, i run And Same error.
this is strange , because in the folder indexdir files MAIN exist
|
Ok... but why did you close this? :) |
@tunkaflux Sorry, my bad :P |
Also, I noticed my indexdir is in "/home/xxx/cve-search/indexdir/". That's also the directory that gets updated when I reindex everything. Afterwards, point to the updated indexdir and try again. |
For the record, both indexdirs work for me, so are you sure that you didn't make a typo somewhere? |
@tunkaflux Which command you used to reindex everything? Thanks! |
I'm running Ubuntu 14.04, 64 and 32 bit |
Ubuntu 14.04, 64 bit here. |
Fix #97 - get index path from Configuration
Hi!
BTW, now the MAIN files are in the folder "cve-search/indexdir" any ideas? @adulau @tunkaflux @PidgeyL If you want, I can upload my image VirtualBox Ubuntu so they can check or revise my problem. |
Hi people! |
@sugusrojo Have you tried fix #97 from the Adulau repo? See commit (adulau@98bda7d) |
@tunkaflux tThanks for the Reply! |
@tunkaflux you can upload your Ubuntu Virtual Image? |
I've tried it as well and got the same kind of error. I let the VM run at the office as it's currently generating this index. I'll retry tomorrow morning when it's done. PS: Running this on Ubuntu Server 14.04-3 LTS x86_64. |
Thanks @AkiraTakizawa . I'll wait for your answer. |
The last commit should be fine. Here is an example of the use of the full-text indexing: [adulau:~/git/cve-search]↥ master* ± python3 ./sbin/db_fulltext.py -l 10 -v
Indexing CVE-ID CVE-2015-8581 The EjbObjectInputStream class in Apache TomEE allows remote attackers
Indexing CVE-ID CVE-2015-8580 Multiple use-after-free vulnerabilities in the (1) Print method and (2
Indexing CVE-ID CVE-2015-8566 The Session package 1.x before 1.3.1 for Joomla! Framework allows remo
Indexing CVE-ID CVE-2015-8565 Directory traversal vulnerability in Joomla! 3.2.0 through 3.3.x and 3
Indexing CVE-ID CVE-2015-8564 Directory traversal vulnerability in Joomla! 3.4.x before 3.4.6 allows
Indexing CVE-ID CVE-2015-8563 Cross-site request forgery (CSRF) vulnerability in the com_templates c
Indexing CVE-ID CVE-2015-8562 Joomla! 1.5.x, 2.x, and 3.x before 3.4.6 allow remote attackers to con
Indexing CVE-ID CVE-2015-8476 Multiple CRLF injection vulnerabilities in PHPMailer before 5.2.14 all
Indexing CVE-ID CVE-2015-8370 Multiple integer underflows in Grub2 1.98 through 2.02 allow physicall
Indexing CVE-ID CVE-2015-8358 Directory traversal vulnerability in the bitrix.mpbuilder module befor
Processing[##################################################] 10/10
[adulau:~/git/cve-search]↥ master* ± python3 ./bin/search_fulltext.py -q TomEE
CVE-2015-8581
[adulau:~/git/cve-search]↥ master* ± I hope this helps. |
Good morning Example:
|
@AkiraTakizawa Thank you for the test. |
I found the problem! @adulau @AkiraTakizawa @tunkaflux @PidgeyL If I run the command from the folder
If I run it from the
Example: |
Thanks for your help! That probably means there is still a relative path that is not working yet. I'll take this issue and work on it on my way home from work, and if fixed, I'll commit it tonight |
I am currently testing this, but it works perfectly for me in both cases. Can you do the following for me?
|
Thanks @PidgeyL
Add line 27
|
And if you do step two from the above directory? |
It's strange @PidgeyL Thanks
|
I'm baffled... Could you gzip your entire folder and send it to me, either by mail or upload it somewhere? That would be a lot easier to debug |
Hi! have a problem running the command
python3 search_fulltext.py -g -s >cve.json
He shows me the following
I have Whoosh==2.7.0
Is it a bug? Or am I doing something wrong?
Thank you
The text was updated successfully, but these errors were encountered: