JNA and Mediainfo ..

Support for Ubuntu and other Desktop Linux distributions
Post Reply
whocares
Posts: 17
Joined: 11 Oct 2014, 22:19

JNA and Mediainfo ..

Post by whocares » 20 Mar 2017, 21:14

filebot -script fn:sysinfo
FileBot 4.7.8 (r4846)
JNA Native: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/linux-x86-64/libjnidispatch.so) not found in resource path ([file:/usr/share/filebot/FileBot.jar])
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load amd64 (64-bit) native library libmediainfo.so: Could not initialize class com.sun.jna.Native
7-Zip-JBinding: net.sf.sevenzipjbinding.SevenZipNativeInitializationException: Failed to load 7z-JBinding: /usr/share/filebot/lib7-Zip-JBinding.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /usr/share/filebot/lib7-Zip-JBinding.so)
Chromaprint: 1.4.2
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2017-02-20 (r481)
Groovy: 2.4.8
JRE: Java(TM) SE Runtime Environment 1.8.0_121
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 4 Core / 880 MB Max Memory / 12 MB Used Memory
OS: Linux (amd64)
Package: DEB
Data: /home/user/.filebot
uname: Linux openmediavault 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.39-1+deb8u1~bpo70+1 (2017-02-24) x86_64 GNU/Linux
Done ヾ(@⌒ー⌒@)ノ
What I tried:
I uploaded the libs from https://github.com/filebot/filebot/tree ... inux-amd64
I reinstalled mediainfo and the libs
I reinstalled filebot

I still get the error. Do you have any suggestions?

whocares
Posts: 17
Joined: 11 Oct 2014, 22:19

Re: JNA and Mediainfo ..

Post by whocares » 20 Mar 2017, 23:11

I am still on OMV 2.X (Wheezy) and I read, that there is a new version of libc which isn't supported , but you can get it with:

add to: /etc/apt/sources.list
deb http://httpredir.debian.org/debian sid main contrib non-free
deb-src http://httpredir.debian.org/debian sid main contrib non-free
apt-get update
apt-get install -t sid libc6
then remove the sid again.

Now it says: 7-Zip-JBinding: 9.20 without an error.


Next stop: Mediainfo. ;)

whocares
Posts: 17
Joined: 11 Oct 2014, 22:19

Re: JNA and Mediainfo ..

Post by whocares » 20 Mar 2017, 23:31

Switched to MediaInfo: 0.7.92 reinstalled Filebot and voila:
FileBot 4.7.8 (r4846)
JNA Native: 5.1.0
MediaInfo: 0.7.92
7-Zip-JBinding: 9.20
Chromaprint: 1.4.2
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2017-02-20 (r481)
Groovy: 2.4.8
JRE: Java(TM) SE Runtime Environment 1.8.0_121
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 4 Core / 880 MB Max Memory / 17 MB Used Memory
OS: Linux (amd64)
Package: DEB
Data: /root/.filebot
uname: Linux openmediavault 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.39-1+deb8u1~bpo70+1 (2017-02-24) x86_64 GNU/Linux
Done ヾ(@⌒ー⌒@)ノ

User avatar
rednoah
The Source
Posts: 18634
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: JNA and Mediainfo ..

Post by rednoah » 21 Mar 2017, 05:59

I'd use docker if I had trouble with dependencies:
https://hub.docker.com/r/rednoah/filebot/
:idea: Please read the FAQ and How to Request Help.

whocares
Posts: 17
Joined: 11 Oct 2014, 22:19

Re: JNA and Mediainfo ..

Post by whocares » 21 Mar 2017, 11:16

I tried docker before and it worked, but I want to use filebot within a postprocessing script. :)

User avatar
rednoah
The Source
Posts: 18634
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: JNA and Mediainfo ..

Post by rednoah » 21 Mar 2017, 12:42

whocares wrote:I tried docker before and it worked, but I want to use filebot within a postprocessing script. :)
So? Does that not work? Running command-line tools in a docker container works perfectly fine.

Run:

Code: Select all

filebot -script fn:sysinfo
Run in docker container:

Code: Select all

docker run -it -v /files:/files -v data:/data rednoah/filebot -script fn:sysinfo
:idea: Please read the FAQ and How to Request Help.

whocares
Posts: 17
Joined: 11 Oct 2014, 22:19

Re: JNA and Mediainfo ..

Post by whocares » 22 Mar 2017, 22:06

one big problem running it in docker is that it creates a container for every run... after some testing my container dir looks like this

Image

but running it as postproc in nzbget gives this
INFO Wed Mar 22 2017 22:58:07 Post-process-script filebot.py for :ugeek: failed
INFO Wed Mar 22 2017 22:58:07 filebot: + exit 94
INFO Wed Mar 22 2017 22:58:07 filebot: + [ 1 = 0 ]
INFO Wed Mar 22 2017 22:58:07 filebot: the input device is not a TTY
running the same command it shows in the log file in terminal works perfectly

And to make it work I used docker docker run -i without the t. (just to let others know)

User avatar
rednoah
The Source
Posts: 18634
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: JNA and Mediainfo ..

Post by rednoah » 22 Mar 2017, 22:48

1.
Does setting a container name make a difference?

Code: Select all

--rm --name filebot
@see https://docs.docker.com/engine/userguid ... ing-system


2.
nzbget has it's own ideas about what exit codes scripts should be returning:
https://github.com/filebot/plugins/blob ... process.sh
:idea: Please read the FAQ and How to Request Help.

whocares
Posts: 17
Joined: 11 Oct 2014, 22:19

Re: JNA and Mediainfo ..

Post by whocares » 22 Mar 2017, 23:10

Using the name switch let's docker tell you that the name is already taken. :)

Right now it's okay for me, because it works and I can easily delete the "dead" containers. I'll see how I can circumvent this at a later time and meanwhile I'll finetune the postprocessing script. It's a bit different from the "normal" filebot. I'll post it in the forum when I finish.

thanks for your time

Post Reply