Re: [Vol-users] Failed to import errors on last few revisions
19 Mar
2012
19 Mar
'12
4:56 p.m.
Mike,
(sigh) I keep forgetting about that....it's probably the third or
fourth time I forgot to do it.
That got rid of most of the errors, now I get:
Volatile Systems Volatility Framework 2.1_alpha
*** Failed to import volatility.plugins.zeusscan1 (AttributeError:
'module' object has no attribute 'ImpScan')
*** Failed to import volatility.plugins.zeusscan2 (AttributeError:
'module' object has no attribute 'ApiHooks')
*** Failed to import volatility.plugins.evtlogs (AttributeError:
'module' object has no attribute 'LdrModules')
*** Failed to import volatility.plugins.timeliner (AttributeError:
'module' object has no attribute 'LdrModules')
Determining profile based on KDBG search...
So I'm guessing those are plugin issues and not with Volatility itself.
Tom
On Mon, Mar 19, 2012 at 1:57 PM, Mike Auty <mike.auty(a)gmail.com> wrote:
Hi Tom,
Please could you make sure to clean out your *.pyc files (or run make
clean), and then try using volatility again. Python should regenerate
these compiled python files whenever the contents of the original python
files change, but since subversion can set the timestamps of the newer
files in the past, this doesn't always happen. If you're still
experiencing problems after that, then we can investigate further...
Thanks,
Mike 5:)