Open lkfbr opened 4 years ago
Use
itemMtime = new SimpleDateFormat("EEE MMM d HH:mm:ss yyyy", Locale.getDefault()).parse(mTimeAttr).getTime();
instead
itemMtime = new SimpleDateFormat("EEE MMM d HH:mm:ss yyyy").parse(mTimeAttr).getTime();
@beyefendi that would solve only the first error. In the second case the formatter is completely different than the value it's trying to parse:
private static final SimpleDateFormat DATE_FORMATTER = new SimpleDateFormat("MM/dd/yyyy hh:mm:ss a");
I guess the underlying tool uses the system locale thus the generated format.
Same Error when running 4.17.0 on Windows 10 (german locale).
WARNING: The Accessed Time format in history file seems invalid 15.04.2020 12:04:40
java.text.ParseException: Unparseable date: "15.04.2020 12:04:40"
java.text.DateFormat.parse(DateFormat.java:366)
org.sleuthkit.autopsy.recentactivity.ExtractEdge.getHistoryArtifact(ExtractEdge.java:614)
org.sleuthkit.autopsy.recentactivity.ExtractEdge.getHistory(ExtractEdge.java:339)
org.sleuthkit.autopsy.recentactivity.ExtractEdge.processWebCacheDbFile(ExtractEdge.java:229)
org.sleuthkit.autopsy.recentactivity.ExtractEdge.process(ExtractEdge.java:171)
org.sleuthkit.autopsy.recentactivity.RAImageIngestModule.process(RAImageIngestModule.java:133)
org.sleuthkit.autopsy.ingest.DataSourceIngestPipeline$PipelineModule.process(DataSourceIngestPipeline.java:198)
org.sleuthkit.autopsy.ingest.DataSourceIngestPipeline.process(DataSourceIngestPipeline.java:111)
org.sleuthkit.autopsy.ingest.IngestJobPipeline.process(IngestJobPipeline.java:943)
org.sleuthkit.autopsy.ingest.DataSourceIngestTask.execute(DataSourceIngestTask.java:30)
org.sleuthkit.autopsy.ingest.IngestManager$ExecuteIngestJobTasksTask.run(IngestManager.java:961)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)
The errors coming from ExtractEdge should be fixed in the upcoming release.
Hello, I've encountered a quite confusing error with Recent Activity module in 4.15. When it parses an image on a system with non-US English locale, it does not parse all information and there are multiple errors like these produced in the log:
When I change locale to US English or add
-J-Duser.language=en
todefault_options
inautopsy.conf
there are no such errors and I have correct results from Recent Activity.