java.lang.NoClassDefFoundError

[doesreally0]

Hello,

I'm at a loss with this Java error message I'm receiving when running FileBot on Ubuntu. Everything had been working for the past 2-3 months, and I'm guessing that something was updated along the way, but I'm not sure what. I've uninstalled and reinstalled Filebot/OpenJDK and tried a newer OpenJDK version too. I've tried updating $CLASSPATH and $JAVA_HOME variables as well, as all I can find out about the ClassNotFoundException is that some java bit can't be found at run-time. Filebot GUI does work, or at least loads fine.

I'm really not even sure what class or java bit the "__script_5be466ff835bf6376f34aa367403ce28$_run_closure1" is referring too. Google is coming up blank.

Any ideas/thoughts?

Error is below :

----

Code: Select all

filebot -script fn:sysinfo
java.lang.NoClassDefFoundError: __script_5be466ff835bf6376f34aa367403ce28$_run_closure1
java.lang.NoClassDefFoundError: __script_5be466ff835bf6376f34aa367403ce28$_run_closure1
	at net.filebot.GroovyEngine.eval(Unknown Source)
	at net.filebot.cli.ScriptShell.evaluate(Unknown Source)
	at net.filebot.cli.ArgumentProcessor.runScript(Unknown Source)
	at net.filebot.cli.ArgumentProcessor.run(Unknown Source)
	at net.filebot.Main.main(Unknown Source)
Caused by: java.lang.ClassNotFoundException: __script_5be466ff835bf6376f34aa367403ce28$_run_closure1
	at net.filebot.GroovyEngine$CompiledScriptClassLoader.findClass(Unknown Source)
	... 5 more

Error (o_O)

----

Code: Select all

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.5 LTS
Release:	22.04
Codename:	jammy

----

Code: Select all

java --version
openjdk 11.0.25 2024-10-15
OpenJDK Runtime Environment (build 11.0.25+9-post-Ubuntu-1ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.25+9-post-Ubuntu-1ubuntu122.04, mixed mode, sharing)

----

Code: Select all

filebot -version
FileBot 5.1.6 (r10435) / OpenJDK Runtime Environment 11.0.25

----

many thanks!

[rednoah]

It's likely a inconsistent cache issue in the scripting engine.


1. Take a snapshot of the cache so we can debug it later if it is indeed a cache issue:

Shell: Select all

filebot -script fn:zip -d "$HOME/.filebot" --filter "f =~ /cache/" --output "$HOME/Desktop/FileBot Cache.zip"

2. Clear the cache to see if that works:

Shell: Select all

filebot -clear-cache

[doesreally0]

That worked amazing, thank you!

Let me know what you'd like me to run on the cache backup, if anything.

thanks!

[rednoah]

Let me know what you'd like me to run on the cache backup, if anything.

If you could share the cache backup via Google Drive / OneDrive / Email / etc that would be much appreciated. Then I could look into the root cause of this issue.

[doesreally0]

Hi Rednoah,

Thanks for your assistance, I've sent you a OneDrive link via PM.

Looking at the AMC.log file, it seems the corrupted cache issue may have occurred around the same time as my system disk ran out of space to operate in, so that might have been the trigger,

thanks!

[rednoah]

Looking at the AMC.log file, it seems the corrupted cache issue may have occurred around the same time as my system disk ran out of space to operate in, so that might have been the trigger,

Yep, there's probably lots of unexpected race condition that could potentially occur when I/O operations randomly fail.


Can you paste the relevant amc.log bits as well? I'm curious what the logs says in this error case.

[doesreally0]

Ah, apologies, I deleted that log file today, as I decided to move to the simple extract feature of FileBot.

[rednoah]

No worries. Cheers!