[armv5] Unrecognized option: --illegal-access=permit

[aitalaat]

Hi folks,

I'm getting this error now after update

Code: Select all

Unrecognized option: --illegal-access=permit
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Any ideas? Should I revert back?

[rednoah]

Java 11+ is now required. At this point in time, Java 13.0.2 should already be installed by default via the Java Installer package:
https://www.filebot.net/linux/syno.html

[aitalaat]

@rednoah You're right. Thanks

[joneng]

@rednoah - I'm also getting this error after updating to v4.9; however, I have a DS 212j which has armv5 cpu so I can't use your java installer package.
How can I remove v4.9 and revert to previous version, or is there some other solution here?

would it be 4.8.5 spk from here https://get.filebot.net/filebot/FileBot_4.8.5/ and then do a manual install from the package center?

Thanks
Jon

[rednoah]

With armv5 you're officially out of luck as far as the Synology package is concerned, since always, I'm somewhat surprised you ever got Java 8 working in the first place.

You can always try an older version, but I wouldn't recommend that as a long-term solution:
https://get.filebot.net/filebot/

The *-portable-jdk8.tar.xz package is available for any Linux device that's stuck on Java 8 for one reason or another.

[joneng]

reverted to 4.8.5 and working ok now
thanks
Jon

[joneng]

for info, I used instructions here https://pcloadletter.co.uk/2011/08/23/j ... -synology/ to get java 8 installed
then I add the path to it in filebot.sh, e.g.
export PATH="$PATH:/var/packages/java8/target/ejdk1.8.0_211/linux_arm_sflt/jre/bin:/usr/local/chromaprint/bin:$PACKAGE_LIBRARY_PATH"

[joneng]

do you have an archive of filebot-node please? unless there is some other solution, I need to revert to a version that can use Node-js 0.10.48-0163

[rednoah]

You can find older releases here:
https://github.com/filebot/filebot-node/releases


EDIT:

I'd also like to note that with a 8+ year old device running armv5 you will eventually lose support for FileBot one way or another, rather sooner than later. I don't plan on supporting older versions of FileBot long-term, so keep that in mind when purchasing a license next time.

[joneng]

yes, fully appeciate long term support is limited, thanks for your assistance with this

I have re-scheduled a task with filebot-node but job appears to be stuck on input for about 40 mins now, e.g.

Code: Select all

Locking /usr/local/filebot-node/data/filebot.log
Run script [fn:amc] at [Tue Mar 17 09:44:34 GMT 2020]
Parameter: subtitles = eng
Parameter: clean = y
Parameter: skipExtract = y
Parameter: minLengthMS = 300000
Parameter: exec = synoindex -A "{folder}" && synoindex -a "{file}"
Parameter: excludeList = .excludes
Argument[0]: /volume1/download_station
Use excludes: /volume1/video/.excludes (1741)
Input: /volume1/download_station/Better.Call.Saul.S05E05.720p.WEB.x265-MiNX[TGx]/Better.Call.Saul.S05E05.720p.WEB.x265-MiNX.mkv

can I enable debug logging to see what it's struggling with? It was working before I had to revert so I know it can work, so could be task config?

EDIT:
after 65mins I got this far but seems stuck again:

Code: Select all

Group: [Series:better call saul] => [Better.Call.Saul.S05E05.720p.WEB.x265-MiNX.mkv]
Get [English] subtitles for 1 files
CmdlineException: OpenSubtitles: Please enter your login details by calling `filebot -script fn:configure`
Rename episodes using [TheTVDB]
Auto-detected query: [Better Call Saul]

EDIT2:
looks like a connectivity issue, any ideas what to check/change to resolve this?

Code: Select all

Fetch failed: https://api.thetvdb.com/search/series?name=Better+Call+Saul
java.lang.IllegalStateException: Failed to retrieve authorization token: null
        at net.filebot.web.TheTVDBClient.getAuthorizationToken(TheTVDBClient.java:131)
        at net.filebot.web.TheTVDBClient.getRequestHeader(TheTVDBClient.java:96)
        at net.filebot.web.TheTVDBClient.lambda$requestJson$0(TheTVDBClient.java:81)
        at net.filebot.CachedResource.lambda$fetchIfModified$9(CachedResource.java:215)
        at net.filebot.CachedResource.lambda$null$0(CachedResource.java:87)
        at net.filebot.CachedResource.retry(CachedResource.java:121)
        at net.filebot.CachedResource.lambda$get$1(CachedResource.java:87)
        at net.filebot.Cache.computeIf(Cache.java:90)
        at net.filebot.CachedResource.get(CachedResource.java:82)
        at net.filebot.web.TheTVDBClient.requestJson(TheTVDBClient.java:81)
        at net.filebot.web.TheTVDBClient.search(TheTVDBClient.java:139)
        at net.filebot.web.TheTVDBClient.fetchSearchResult(TheTVDBClient.java:158)
        at net.filebot.WebServices$TheTVDBClientWithLocalSearch.access$101(WebServices.java:193)
        at net.filebot.WebServices$TheTVDBClientWithLocalSearch.lambda$fetchSearchResult$4(WebServices.java:213)
Caused by: java.net.SocketTimeoutException
        at net.filebot.web.WebRequest.post(WebRequest.java:198)
        at net.filebot.web.TheTVDBClient.postJson(TheTVDBClient.java:75)
        at net.filebot.web.TheTVDBClient.getAuthorizationToken(TheTVDBClient.java:127)
        ... 13 more

SocketTimeoutException
Clean clutter files and empty folders

[rednoah]

No idea. FileBot wouldn't be able to give you more logging if the runtime itself is digging a hole, probably due to running the amc script with insufficient memory, but trying to muddle through.


What does filebot -script fn:sysinfo say?


PS: What you can do with any java process, is call kill -3 <PID> which send a signal to the JVM which causes it to print all stack traces, so you can guess what it's doing based on that. Might be interesting. Won't help you do anything about it though.



EDIT:

Code: Select all

Caused by: java.net.SocketTimeoutException

That's a network issue, or perhaps a strange runtime issue that causes the network issue. Nothing you can do about it. Try again tomorrow.

[joneng]

Code: Select all

# filebot -script fn:sysinfo
FileBot 4.8.5 (r6224)
JNA Native: java.lang.UnsatisfiedLinkError: Could not find JNA native support
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load arm (32-bit) native library libmediainfo.so: Could not initialize class com.sun.jna.Native
p7zip: p7zip Version 9.20 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,1 CPU)
unrar: UNRAR 5.21 freeware
FFprobe: 2.7.1
Chromaprint: java.io.IOException: Cannot run program "fpcalc": error=2, No such file or directory
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2019-05-15 (r565)
Groovy: 2.5.6
JRE: Java(TM) SE Embedded Runtime Environment 1.8.0_211
JVM: 32-bit Java HotSpot(TM) Embedded Client VM
CPU/MEM: 1 Core / 92 MB Max Memory / 11 MB Used Memory
OS: Linux (arm)
HW: Linux DiskStation 2.6.32.12 #24922 Tue Apr 23 17:32:06 CST 2019 armv5tel GNU/Linux synology_88f6281_212j
DATA: /volume1/@appstore/filebot/data/root
Package: SPK
License: FileBot License P8639211 (Valid-Until: 2020-07-23)

------------------- UPDATE AVAILABLE: FileBot 4.9.0 (r7234) --------------------

Done ヾ(＠⌒ー⌒＠)

[rednoah]

92 MB Max Memory is far from enough for the amc script. You might get simple filebot -rename calls working though.

How much RAM does your device have? Perhaps you can make it work by manually setting a higher memory limit for the java process:

Code: Select all

export JAVA_OPTS="-Xmx210m"

Now we're completely off-topic. Please create a new thread if you have further questions.

[joneng]

I uninstalled filebot and filebot-node, rebooted the DS 212j, then manually installed filebot v4.8.5 and filebot-node v0.2.8.4 and it works ok now

thanks for your help

[robwiel]

How can I revert to 4.8.5? I am stuck on Java8 211 its arm5 (ds212+).
Nvm, found *.spk

[Droopie]

@joneng Assuming you are running java 8 by rednoah, you can perform the following “hack” to get java 11 running. I don’t have the knowledge to build a package for synology thus hopefully someone else can make a better fix.

Download java 11 from the following link.
https://wiki.logicaldoc.com/wiki/Switch ... y_and_QNAP
Copy the tar onto your sinology diskstation.

ssh into your diskstation and cd /volume1/@appstore/java-8-installer

mv the tar to this folder:
sudo mv /volume1/Download/WhateverDirYouHave/openjdk-11.0.2_linux-x64_bin.tar.gz .

then extract it:
sudo tar xzf openjdk-11.0.2_linux-x64_bin.tar.gz

Rename the java 8 dir:
sudo mv jdk1.8.0_201 jdk.OLD

Rename the java 11 dir:
sudo mv jdk-11.0.2 jdk1.8.0_201

log back into your Synology using http and restart filebot.
It works for me

[rednoah]

The Java Installer package will take care of installing Java 11+ on compatible platforms such as x64 just fine. The problem is armv5 architecture for which Embedded Java 8 is the only available Java runtime.

[Eluc]

I'll leave my comment here for other that might have the same issue and end up in this thread as well. I'm on Synology x64 and had the same issue, I figured out that the Java package from rednoah was not installed, so I installed it but the issue was still here. Then I uninstalled Java 7 and Java 8 package from Synology (I got no warning that some app need them so I hope I'll be fine), I also reinstall Rednoah's package (despite that now it was offering a repair option, but I would better start fresh). I also took the opportunity to remove Node.js v4 that was no more used but I still have v8 (used by SynologyOffice) and v12 (the last one) used by other package too, I checked by trying to uninstall it too.

Now everything is working find again and I have cleaned up a bit my Synology packages. Hope it might help other.

[stooovie]

How can I revert to 4.8.5? I am stuck on Java8 211 its arm5 (ds212+).
Nvm, found *.spk

Please link

[rednoah]

➔ https://get.filebot.net/filebot/