-
Notifications
You must be signed in to change notification settings - Fork 763
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
Efilter engine import failure during initialize #275
Comments
It seems efilter has changed its structure enough that the latest version doesn't work with the version of rekall that we have. Try installing the old version
Pinning this version in our requirements.txt is hopefully enough to fix this properly.
|
Was this an install on a new clean system? Was it ubuntu trusty? I haven't been able to reproduce this yet, so please let me know if the above fixes it. |
Was on clean ubuntu server 14.04. It did not rectify the issue so far, I'm
|
Can you go and delete all your Rekall related .pyc's? I remember some Cheers, On Wed, Oct 14, 2015 at 11:39 PM Muted Mouse notifications@github.com
|
@the80srobot for efilter |
Deleting all rekal py worked. for path in After that install_script_ubuntu.sh worked like a charm. Thanks guys. Cheers, On Wed, Oct 14, 2015 at 11:39 PM Muted Mouse notifications@github.com
— |
I just started having this problem too when switching over to the install from source script. I had to blow away all of rekall and reinstall it to get past it. I am doing some more testing now. |
I ended up blowing away rekal and installing with: Then run the install script: Those actions fixed it for me, now operational.
|
Awesome, I've changed the requirements.txt to pin efilter and will push it shortly. |
I removed rekall and rekall-core. Reinstalled deps via the ubuntu script and everything was ok. I upgraded to latest efilter and got the 'expressions' import error. I removed rekall-core and installed rekall-core and it force downgraded efilter. Removing and reinstalling rekall-core appears to be the fix. I haven't fully tested a from scratch clean install, but unless there is an install order problem it should likely not be impacted. |
I'm running in a clean VM now to verify before I close this out. |
Just finished my clean install test and it worked. |
Works for me, thanks for the reports @pidydx and @mutedmouse |
Thanks everyone.
|
You should not install efilter itself since head is broken. When you install rekall it pulls in the right version that it works with: pip install rekall works. Do not however try to upgrade efilter: pip install efilter since this will will in the latests efilter version and break rekall. |
Hi, So the install from source script for some reason ignores the version in We will be updating Rekall soon to work with latest efilter and then this Adam On Thu, Oct 15, 2015 at 6:33 AM Michael Cohen notifications@github.com
|
I confirmed the rekall efilter pinning works as below, so I'm still not sure how this failed. I couldn't reproduce the original problem with the GRR install, but there were multiple reports. We are using pip and requirements.txt to install. @mutedmouse you were using the latest install script from the repo, right? If you were using an old one that might explain it...
|
I installed the full requirements.txt in a clean virtualenv and got the same (correct) result, so I'm still not clear on how this ever failed, but I'll keep the explicit efilter install in for now. |
I had pulled the install yesterday afternoon from the github grr master
|
Greg, I can reproduce pip ignoring the version requirements with the On Thu, Oct 15, 2015 at 11:19 PM Muted Mouse notifications@github.com
|
I had this issue on a SIFT system. |
Hi, |
you need to remove all efilter references - somehow you have a new version Alternatively just update rekall to the latest version - git clone it then
On 23 December 2015 at 14:28, kftp notifications@github.com wrote:
|
Thanks for getting back to me so quickly. I just ran the setup.py install (the one in rekall-core) ; it resulted in a memory error :( My SIFT VM is set at 2GB RAM. Is this not enough ? I read here (https://github.com/google/grr-doc/blob/master/admin.adoc#memory-limit) that GRR typical memory consumption is 30GB, however I do not have a server to just test GRR. And so far it is about installing, not yet using :-D Full end of setup.py execution trace is GEN capstone.pc File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/command/easy_install.py", line 610, in easy_install File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/command/easy_install.py", line 661, in install_item File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/command/easy_install.py", line 709, in process_distribution File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/pkg_resources/init.py", line 824, in resolve File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/command/easy_install.py", line 659, in install_item File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/command/easy_install.py", line 842, in install_eggs File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/command/easy_install.py", line 1070, in build_and_install File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/command/easy_install.py", line 1056, in run_setup File "/usr/local/lib/python2.7/dist-packages/setuptools-15.0-py2.7.egg/setuptools/sandbox.py", line 240, in run_setup |
Below is a trimmed copy of the error encountered during grr_config_updater initialize portion. Confirmed efilter was latest version with pip.
File "/usr/local/lib/python2.7/dist-packages/rekall/entities/init.py", line 3, in
from rekall.entities import query
File "/usr/local/lib/python2.7/dist-packages/rekall/entities/query/init.py", line 3, in
from rekall.entities.query import analyzer
File "/usr/local/lib/python2.7/dist-packages/rekall/entities/query/analyzer.py", line 29, in
from efilter import engine
ImportError: cannot import name engine
FAILURE RUNNING: grr_config_updater initialize
Ty.
The text was updated successfully, but these errors were encountered: