java.lang.NoClassDefFoundError: __script_5be466ff835bf6376f34aa367403ce28

[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!

[Guillaume]

Hi, I have the same probleme and clear the cache don't resolve that.

Before I use FileBot on Windows and I use the same format of title but on Linux it's not working.

I joint a screenshot and my ZIP in this link : https://www.swisstransfer.com/d/b8d9a3d ... 8a517a7243

I hope it's help. Thank you.

[rednoah]

Your screenshot doesn't show the complete error message. The "Could not initialise..." bit would suggest a problem with JNA or libmediainfo which would be an issue completely unrelated to anything else on this thread. You can click on the " Binding ..." error message to copy the error message into the clipboard. The standalone MediaInfo tool is notably not relevant since FileBot typically ships with its own libmediainfo, depending on how you have chosen to install FileBot.


What does filebot -script fn:sysinfo say? That'll print all the relevant information, including JNA version and libmediainfo version, or an error message if one of these two doesn't work.



Please read How to Request Help for details.

[Guillaume]

Thank for your quick answer.

Code: Select all

guillaume@guillaume-mediatheque:~$ filebot -script fn:sysinfo
Initialize new disk cache: /home/guillaume/.filebot/cache/1
FileBot 5.1.7 (r10514)
JNA Native: 7.0.0
MediaInfo: java.lang.UnsatisfiedLinkError: Unable to load library 'mediainfo':
libmms.so.0: cannot open shared object file: No such file or directory
libmms.so.0: cannot open shared object file: No such file or directory
Native library (linux-x86-64/libmediainfo.so) not found in resource path (/usr/share/filebot/jar/filebot.jar)
7-Zip-JBinding: 16.02
Tools: fpcalc/1.5.0
Extended Attributes: OK
Unicode Filesystem: OK
GVFS: PlatformGVFS [/run/user/1000/gvfs]
Script Bundle: 2025-05-24 (r1007)
Groovy: 4.0.21
JRE: OpenJDK Runtime Environment 21.0.3
JVM: OpenJDK 64-Bit Server VM
CPU/MEM: 2 Core / 2.1 GB Max Memory / 94 MB Used Memory
OS: Linux (amd64)
HW: Linux guillaume-media 6.8.0-59-generic #61~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 15 17:03:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
CPU/MEM: : Intel(R) Pentium(R) CPU G3260 @ 3.30GHz / MemTotal: 8 GB / MemFree: 941 MB / MemAvailable: 4.9 GB / SwapTotal: 2.1 GB / SwapFree: 2.1 GB
STORAGE: ext4 [/] @ 5 GB | ntfs3 [/media/guillaume/Media] @ 1 TB
UID/GID: uid=1000(guillaume) gid=1000(guillaume) groups=1000(guillaume),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),125(lpadmin),137(sambashare)
DATA: /home/guillaume/.filebot
Package: DEB
Activate License [XXXXXXXX] on [Tue May 27 09:52:57 CEST 2025]
License: FileBot License XXXXXXXX(Valid-Until: 2026-03-26)
Done ヾ(＠⌒ー⌒＠)ノ

[rednoah]

Code: Select all

MediaInfo: java.lang.UnsatisfiedLinkError: Unable to load library 'mediainfo':
libmms.so.0: cannot open shared object file: No such file or directory
libmms.so.0: cannot open shared object file: No such file or directory

libmediainfo is indeed not working.


How did you install FileBot? Did you use apt install with the --install-recommends option?

Shell: Select all

sudo apt-get install -y --install-recommends filebot

The error message says that libmms.so is not installed. If libmms0 is somehow not installed then explicitly installing that might do the trick.

[Guillaume]

Hi, no I install Media info via the app catalog and filebot via .deb.

I remove all and install via command line as you say and it's working.

Thank a lot !

[rednoah]

Hi, no I install Media info via the app catalog and filebot via .deb.

I see. If you've installed MediaInfo as self-contained Flatpack / Snap / AppImage package then that won't install the typical dependencies. The libmms.so library is typically pre-installed because it's a dependency for many different packages, notably the mediainfo package.