HTML Report Error

[gisms]

Hi!!!

We provide an iped 4.0.4 for analysis, user machine contains java version "1.8.0_321" - 64-Bit.
The user tried to generated a report, but it gave an error, with the log output below:

2022-12-08 13:59:26 [INFO] [app.processing.Main] Indexador e Processador de Evidências Digitais 4.0.4
2022-12-08 13:59:26 [INFO] [engine.config.Configuration] Loading configuration from E:\xxx\IPED\xxx\iped
Warning: Nashorn engine is planned to be removed from a future JDK release
2022-12-08 13:59:28 [ERROR] [parsers.python.PythonParser] JEP não encontrado, todos os módulos python foram desligados. Veja https://github.com/sepinf-inc/IPED/wiki/User-Manual#python-modules
java.lang.UnsatisfiedLinkError: no jep in java.library.path: [E:xxx\IPED\xxxxx\iped\jre\bin, C:\WINDOWS\Sun\Java\bin, C:\WINDOWS\system32, C:\WINDOWS, C:\Program Files (x86)\Common Files\Oracle\Java\javapath, C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS, C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS, C:\ProgramData\Oracle\Java\javapath, C:\WINDOWS\system32, C:\WINDOWS, C:\WINDOWS\System32\Wbem, C:\WINDOWS\System32\WindowsPowerShell\v1.0, C:\WINDOWS\System32\OpenSSH, C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL, C:\Program Files\Intel\Intel(R) Management Engine Components\DAL, C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT, C:\Program Files\Intel\Intel(R) Management Engine Components\IPT, C:\Program Files (x86)\Kaspersky Lab\Endpoint Agent, C:\Users\MPGO\AppData\Local\Microsoft\WindowsApps, ., E:\xxx\IPED\xxx\iped\jre\bin, .]
at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.base/java.lang.Runtime.loadLibrary0(Unknown Source)
at java.base/java.lang.System.loadLibrary(Unknown Source)
at jep.MainInterpreter.initialize(MainInterpreter.java:129)
at jep.MainInterpreter.getMainInterpreter(MainInterpreter.java:101)
at jep.Jep.(Jep.java:133)
at jep.SharedInterpreter.(SharedInterpreter.java:56)
at iped.parsers.python.PythonParser.getNewJep(PythonParser.java:176)
at iped.parsers.python.PythonParser.getJep(PythonParser.java:165)
at iped.engine.task.PythonTask.getJep(PythonTask.java:98)
at iped.engine.task.PythonTask.getConfigurables(PythonTask.java:200)
at iped.engine.config.Configuration.loadConfigurables(Configuration.java:211)

(xxxx was the indentificacion hidden)

We used Iped.exe 4.0.4 that automatically calls its embedded java 11 to create the case.
When we tested and generated a report in a machine with java 1.8.0_341 it worked well.

any suggestions on what might be going on?

[lfcnassif]

Hi,

I just returned from vacation. Error above is expected, since IPED's portable python is not copied to case folder, so it complains. But it shouldn't break the report generation. Are you sure it was the report error cause? I suspect another error could have been printed in the log... Could you send the full log?

[gisms]

I will send to you.

[lfcnassif]

Thank you. Here is your aborting error (may be different than the other user one):

2022-12-08 14:00:24	[ERROR]	[app.processing.Main]			Processing Error: 
java.lang.RuntimeException: Unable to access default configuration
	at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:339) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at iped.parsers.standard.StandardParser.getTikaConfig(StandardParser.java:102) ~[iped-parsers-impl-4.0.4.jar:?]
	at iped.parsers.standard.StandardParser.<init>(StandardParser.java:110) ~[iped-parsers-impl-4.0.4.jar:?]
	at iped.engine.task.ParsingTask.init(ParsingTask.java:760) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Worker.initTasks(Worker.java:128) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Worker.<init>(Worker.java:110) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Manager.initWorkers(Manager.java:521) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Manager.process(Manager.java:261) ~[iped-engine-4.0.4.jar:?]
	at iped.app.processing.Main.startManager(Main.java:173) [iped-search-app.jar:?]
	at iped.app.processing.Main.execute(Main.java:231) [iped-search-app.jar:?]
	at iped.app.processing.Main.main(Main.java:293) [iped-search-app.jar:?]
Caused by: org.apache.tika.exception.TikaException: interrupted while waiting for DOMBuilder
	at org.apache.tika.utils.XMLReaderUtils.acquireDOMBuilder(XMLReaderUtils.java:504) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.utils.XMLReaderUtils.buildDOM(XMLReaderUtils.java:447) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:235) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:335) ~[tika-core-2.4.0-p1.jar:2.4.0]
	... 10 more
Caused by: java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(Unknown Source) ~[?:?]
	at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(Unknown Source) ~[?:?]
	at java.util.concurrent.ArrayBlockingQueue.poll(Unknown Source) ~[?:?]
	at org.apache.tika.utils.XMLReaderUtils.acquireDOMBuilder(XMLReaderUtils.java:502) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.utils.XMLReaderUtils.buildDOM(XMLReaderUtils.java:447) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:235) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:335) ~[tika-core-2.4.0-p1.jar:2.4.0]
	... 10 more

Seems something is interrupting Tika library initialization, or could be a Tika bug, not sure...

[gisms]

Nassif, I tried to simulate the error, but I couldn't anymore. Same with user version.
Curious that on the notebook I got it and thought it was java.
I'll have to wait for the user to come back.

[lfcnassif]

Thank you. It doesn't seem related to installed java version. It seems an intermittent error, usually hard to reproduce and fix...

[lfcnassif]

Thank you. Here is your aborting error (may be different than the other user one):

2022-12-08 14:00:24	[ERROR]	[app.processing.Main]			Processing Error: 
java.lang.RuntimeException: Unable to access default configuration
	at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:339) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at iped.parsers.standard.StandardParser.getTikaConfig(StandardParser.java:102) ~[iped-parsers-impl-4.0.4.jar:?]
	at iped.parsers.standard.StandardParser.<init>(StandardParser.java:110) ~[iped-parsers-impl-4.0.4.jar:?]
	at iped.engine.task.ParsingTask.init(ParsingTask.java:760) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Worker.initTasks(Worker.java:128) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Worker.<init>(Worker.java:110) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Manager.initWorkers(Manager.java:521) ~[iped-engine-4.0.4.jar:?]
	at iped.engine.core.Manager.process(Manager.java:261) ~[iped-engine-4.0.4.jar:?]
	at iped.app.processing.Main.startManager(Main.java:173) [iped-search-app.jar:?]
	at iped.app.processing.Main.execute(Main.java:231) [iped-search-app.jar:?]
	at iped.app.processing.Main.main(Main.java:293) [iped-search-app.jar:?]
Caused by: org.apache.tika.exception.TikaException: interrupted while waiting for DOMBuilder
	at org.apache.tika.utils.XMLReaderUtils.acquireDOMBuilder(XMLReaderUtils.java:504) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.utils.XMLReaderUtils.buildDOM(XMLReaderUtils.java:447) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:235) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:335) ~[tika-core-2.4.0-p1.jar:2.4.0]
	... 10 more
Caused by: java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(Unknown Source) ~[?:?]
	at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(Unknown Source) ~[?:?]
	at java.util.concurrent.ArrayBlockingQueue.poll(Unknown Source) ~[?:?]
	at org.apache.tika.utils.XMLReaderUtils.acquireDOMBuilder(XMLReaderUtils.java:502) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.utils.XMLReaderUtils.buildDOM(XMLReaderUtils.java:447) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:235) ~[tika-core-2.4.0-p1.jar:2.4.0]
	at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:335) ~[tika-core-2.4.0-p1.jar:2.4.0]
	... 10 more

Seems something is interrupting Tika library initialization, or could be a Tika bug, not sure...

I was able to reproduce exactly error above, but artificially: closing explicitly the report creation progress window right after the Starting... message disappears, this causes an interrupt signal to be sent. But I think you haven't done this of course... Another possibility is if the bootstrap/starting process dies for some unknown reason, an interrupt signal would also be sent to the main iped process. I have no more ideas...