pi@raspberrypi:~/filebot $ filebot.sh -script fn:sysinfo
[2020-09-01 14:00:06.500] Using persistent disk cache: /home/pi/filebot/data/pi/cache/0
[2020-09-01 14:00:06.999] Low Memory Limit: 172 MB
[2020-09-01 14:00:06.999] * Consider using JAVA_OPTS -Xmx256m or higher
[2020-09-01 14:00:06.999 ...

Hi,

I recently updated filebot using the update-filebot.sh script. This was the first time using that script to update filebot - I had previously been downloading with curl (raspberry Pi 4). The update worked great but when running filebot the next time I got this message:

[2020-09-01 13:50:00 ...

Great news -- that worked!

filebot was hanging for a specific movie over and over - I'd have to reboot the pi just to get it to respond after each test.

I made 2 changes: using filebot 4.9.1 and added the "-no-index" option which was recommended when running the sysinfo command (also using export ...

Here's something interesting.. I have filebot installed on my Synology NAS as well and it's working fine for the same files that have failed on my Raspberry PI.

The Synology is a lot slower and has less memory so I'd much rather run filebot on the Raspberry PI. I did notice that the filebot command ...

that's ok - I'll keep playing with it and if I figure something out I'll post -- in case there's someone else noticing this too.

thanks for the quick help!

>> try running with -Xmx384 and -Xms384

I upgraded java to "openjdk 14 2020-03-16" and set the min/max size (the above commands didn't work until I realized I needed to add "M" after each one! I'm using: export JAVA_OPTS="-Xms512M -Xmx512M"

filebot still hangs and is eventually "Killed" (not sure ...

cool thanks! I'll try all of these steps

I did find that extra logging and enabled it. sorry, i didn't want to include the full movie name but I did notice 1 thing in common between this current movie that's failing and the previous one that also failed.

I downloaded that moviedb.txt.xz file and ...

I did think I had it narrowed down to a specific file.. or at least it would always fail with the 3 movies I was trying to scrape. Since then I moved these files but it's still happening - this time on a different movie. Strangely, I've never had an issue scraping TV shows.. not sure if that's just ...

just quick update: I've stopped trying to get filebot to work with these movies and manually moved them into place.

I do think there's an issue here.. now that I took my NAS completely out of the picture I feel like it has to be with the Raspberry PI 4 or filebot (or one of the underlying libraries ...

Sorry for all of the back-to-back posts... last one for now.

Since the other thread I started had a question about my NAS - I decided to try and reproduce this all locally.

I copied 1 movie locally and ran the command:
/home/pi/filebot/filebot.sh -script fn:amc --output /home/pi/MEDIA --log all ...

I also found an older post that I created which doesn't appear to be the same issue but still wanted to point it out: https://www.filebot.net/forums/viewtopic.php?f=8&t=11310&p=47175&hilit=raspberry+pi+4#p47175

In that case, there was a huge file 6.4 Gig and it wasn't showing up when using the ...

>> Is there any specific reproducible pattern? Does it always end up getting killed when processing that specific file?

To this question, when it does happen like in this case, the filebot script will always fail. I usually manually fix the issue by manually moving/renaming the file and Kodi will ...

Thanks for the fast reply!!

I used the -no-probe option and same results (~2 minutes before the "Killed" message and the script exits). I do see an additional log entry showing up before the first 2 movies:
Failed to read media characteristics: UnsupportedOperationException ...

Hi,

I've used filebot successfully for a while now and it works for most files. But, every once and a while it will fail without any reason that I can see and I'd like to figure out what's going on.

Here's the filebot version info:
pi@raspberrypi:~ $ filebot.sh -script 'fn:sysinfo'

FileBot 4.9.0 ...

just a quick update.. I manually moved the movie file to my movies folder where filebot would normally move it to. Kodi picked it up and it plays just fine.

I also didn't see any hard drive issues on my Synology NAS (not saying there couldn't be any -- just none were reported)

Anyway, just ...

>> Doesn't make sense
To me either!

FWIW - I'm using a Synology NAS and there's 2 files in that folder.


$ ls -al
total 6283504
-rwxr-xr-x 1 pi pi 6434301987 Dec 3 11:50 Test.Movie.2019.1080p.WEBRip.DD5.1.x264-CM.mkv
-rwxr-xr-x 1 pi pi 31 Dec 3 11:50 RARBG.txt

filebot.sh -mediainfo -r . --format ...

Thanks for the quick replies!!

Sorry, I know it probably isn't the best but I was trying to hide the actual filename itself even though there's no non-ASCII characters or anything like that which I'm guessing you're looking for. The few times this has happened before the file names didn't have ...

The file definitely is there though.. in fact filebot finds it on it's own and logs the exact filename. How is that possible?

Invalid file path: /media/MEDIA/INCOMING/TEST.MOVIE.2019.1080p.WEBRip.DD5.1.x264-CM/TEST.MOVIE.2019.1080p.WEBRip.DD5.1.x264-CM.mkv

Could there be some other reason for ...

And here's the full command I'm running FWIW:

/home/pi/filebot/filebot.sh -script fn:amc --output $MEDIA --log all --log-file /tmp/filebot.log \
--filter "!readLines('/usr/local/bin/excludes.txt').contains(n)" \
--action move --conflict auto -non-strict "$FILE_PATH" --def artwork=y ...

Here's the sysinfo output:

pi@raspberrypi:~ $ filebot.sh -script fn:sysinfo
FileBot 4.9.0 (r6912)
JNA Native: 6.1.0
MediaInfo: 19.04
p7zip: p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,32 bits,4 CPUs LE)
unrar: UNRAR 5.61 beta 1 freeware
FFprobe: 4.1.4-1+rpt1~deb10u1
Chromaprint ...

Hi,

I've seen this happen a couple of times now and can't figure out what's wrong.

Invalid file path: /media/MEDIA/INCOMING/TEST.MOVIE.2019.1080p.WEBRip.DD5.1.x264-CM/TEST.MOVIE.2019.1080p.WEBRip.DD5.1.x264-CM.mkv

(obviously, that's not the exact file name)

When it initially happened I assumed ...

>> The recommended install instructions for Debian-based systems are as follows

Well, maybe I did do something to mess this up.. but, I followed these instructions originally and they didn't work for me. That's what led me to look for alternatives.

I'd like to be able to format and start over ...

Update.. I installed the portable version and it's working!

I'm surprised there's so many guides out there on getting this working when that seems like it'd be by far the easiest.. honestly, I do remember reading this elsewhere too (ie: https://www.filebot.net/forums/viewtopic.php?t=3974) but was ...

Here's the results you asked for. I'll try to get the portable package installed and working and see if that makes any difference


pi@raspberrypi:/usr/local/bin $ find /usr/lib -name "*jnidispatch*"
/usr/lib/arm-linux-gnueabihf/jni/libjnidispatch.so
/usr/lib/arm-linux-gnueabihf/jni/libjnidispatch ...

Thanks for the quick reply!

I did both steps recommended but that didn't change anything.

Ultimately I see the same results:


pi@raspberrypi:~/Downloads $ sudo filebot -script "fn:sysinfo"
FileBot 4.8.6 (r6543)
JNA Native: java.lang.UnsatisfiedLinkError: Can't obtain static method fromNative ...

FWIW: I figured out the 7z/unrar issue (although the first 2 are the ones I think I need more)
- I followed the steps listed here: https://raspberrypi.stackexchange.com/a/3618

Hi,

I'm trying to use Filebot on a raspberry pi 4 and running into issues. I know there's several other threads out there and I followed this one (https://www.filebot.net/forums/viewtopic.php?f=11&t=6028) to get Filebot installed but I'm now having issues running it.

The error I'm getting is this ...

Hi,

I installed successfully and ran the test and curious about something I see in the results:

- It says `UPDATE AVAILABLE: FileBot 4.8 (r5280)` but I did get the latest AFAIK. Is there another way to update?


~/Downloads$ filebot -script fn:sysinfo
FileBot 4.7.9 (r4984)
JNA Native: 5.1.0 ...

That command failed for me. However, just running the GUI app showed me that there was a newer version available. I updated and the command above now works.. Maybe the issue I was having was just from running an older version? I'll assume so but update if I see the issue happen again with the latest ...

I've been running filebot automated on the command line for a while now w/no issues. But, today I noticed 3 files weren't moved even though they seem to be in good order.

All 3 failed with the same error:
CmdlineException: No media files


Any ideas? Did something change with the recently with ...

very cool - thanks! I take it this is a local change, right? i tried once to use a local copy of the amc script but that failed due to missing dependencies and I never tried again. But, seems like it's worth another shot to get this to work.

(also, might good to update the official version as well ...

quick update.. here's additional info I found on the <trailer> syntax for Kodi:

http://forum.kodi.tv/showthread.php?tid=100665

I noticed that Kodi (latest stable version) wasn't playing back trailers on my movies that were processed with the AMC script.

I was able to track it down the the <trailer> XML tag that AMC script creates.. Here's what's in the .nfo file::

<trailer>ABCDEFGHIJK</trailer>

I removed this file ...