[DEPRECATED] FileBot Node Troubleshooting

Support for Synology NAS, QNAP NAS and other Embedded Linux systems
Post Reply
User avatar
rednoah
The Source
Posts: 16415
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

[DEPRECATED] FileBot Node Troubleshooting

Post by rednoah » 27 Jan 2016, 10:28

@DEPRECATED This troubleshooting guide is for early versions of Synology DSM and FileBot Node and is mostly not applicable anymore.



Here's a list of things you can try:


** View Log **


:!: Newer versions of DSM have removed the View Log button, so you can no longer easily view the log via the DSM UI. You'll need to login via SSH and run sudo cat /var/log/upstart/filebot-node.log to view the log.

Code: Select all

sudo cat /var/log/upstart/filebot-node.log
What does the log say? Package Center ► FileBot Node ► View Log
Are you having trouble installing Java? Please use the Unofficial Java Installer package from the FileBot Package Source.
Does your firewall allow TCP traffic on ports 5452 and 5453? FileBot Node will use HTTP on port 5452, and HTTPS on port 5453.
Does it work if you connect via IP and HTTP? What about HOST and HTTPS? Make sure you and the NAS are in the same local network.


Open the FileBot Node UI in a separate tab if it doesn't work from within DSM:

Code: Select all

http://<IP>:5000/webman/3rdparty/filebot-node/index.html
Here's how the server-side resources should look like:

Code: Select all

$ ls -l /usr/syno/synoman/webman/3rdparty/
lrwxrwxrwx 1 root root   40 May 31 02:31 filebot-node -> /var/packages/filebot-node/target/client
Check if the FileBot Node Service is accessible by throwing a request at it:

e.g. HTTP

Code: Select all

curl -v http://<IP>:5452/auth
e.g. HTTPS

Code: Select all

curl -v https://<HOST>:5453/auth
Expected Log Output:

filebot-node service is running and waiting for requests:

Code: Select all

filebot-node listening at http://0.0.0.0:5452
filebot-node listening at https://0.0.0.0:5453
client has successfully connected to the filebot-node service:

Code: Select all

AUTH_CACHE: {"id=XXXXXXXXXX":"admin"}
:idea: Please read the FAQ and How to Request Help.

jettechfsr
Posts: 8
Joined: 24 Dec 2018, 07:05

Re: FileBot Node Troubleshooting

Post by jettechfsr » 26 Feb 2019, 04:58

I'm I crazy or has the log file shortcut been taken away in package manager?

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

Re: FileBot Node Troubleshooting

Post by rednoah » 26 Feb 2019, 06:01

Yes, pretty much. AFAIK, there's no longer any easy way to check logs. You'll have to login via SSH and then cat the log. Maybe the DSM Text Editor app works as well.

Here's how you can find the log:

Code: Select all

$ find / -name filebot-node.log 2> /dev/null
/var/log/upstart/filebot-node.log
:idea: Please read the FAQ and How to Request Help.

jettechfsr
Posts: 8
Joined: 24 Dec 2018, 07:05

Re: FileBot Node Troubleshooting

Post by jettechfsr » 27 Feb 2019, 05:29

Thanks Having issue with new router ports not forwarding correctly

jettechfsr
Posts: 8
Joined: 24 Dec 2018, 07:05

Re: FileBot Node Troubleshooting

Post by jettechfsr » 28 Feb 2019, 06:23

[email protected]:~# $ find / -name filebot-node.log 2> /dev/null
[email protected]:~# /var/log/upstart/filebot-node.log
-ash: /var/log/upstart/filebot-node.log: Permission denied
[email protected]:~#

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

Re: FileBot Node Troubleshooting

Post by rednoah » 28 Feb 2019, 06:26

Use sudo cat to display the log file.
:idea: Please read the FAQ and How to Request Help.

jettechfsr
Posts: 8
Joined: 24 Dec 2018, 07:05

Re: FileBot Node Troubleshooting

Post by jettechfsr » 28 Feb 2019, 06:28

Code: Select all

2019-02-27T22:11:37-0600 + export FILEBOT_NODE_HOST=127.0.0.1
2019-02-27T22:11:37-0600 + FILEBOT_NODE_HOST=127.0.0.1
2019-02-27T22:11:37-0600 + export FILEBOT_NODE_AUTH=SYNO
2019-02-27T22:11:37-0600 + FILEBOT_NODE_AUTH=SYNO
2019-02-27T22:11:37-0600 + export FILEBOT_NODE_HTTP=YES
2019-02-27T22:11:37-0600 + FILEBOT_NODE_HTTP=YES
2019-02-27T22:11:37-0600 + export FILEBOT_NODE_HTTP_PORT=5452
2019-02-27T22:11:37-0600 + FILEBOT_NODE_HTTP_PORT=5452
2019-02-27T22:11:37-0600 + export USER=admin
2019-02-27T22:11:37-0600 + USER=admin
2019-02-27T22:11:37-0600 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2019-02-27T22:11:37-0600 ++ free
2019-02-27T22:11:37-0600 + export JAVA_OPTS=-Xmx460m
+ JAVA_OPTS=-Xmx460m
+ export FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ export FILEBOT_CMD=filebot
+ FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ FILEBOT_CMD_CWD=/volume1
++ id -u admin
2019-02-27T22:11:37-0600 id: admin: no such user
2019-02-27T22:11:37-0600 + export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
2019-02-27T22:11:37-0600 ++ cut -d: -f3
2019-02-27T22:11:37-0600 ++ cat /etc/group
2019-02-27T22:11:37-0600 ++ grep administrators
2019-02-27T22:11:37-0600 + export FILEBOT_CMD_GID=101
+ FILEBOT_CMD_GID=101
+ export FILEBOT_NODE_CLIENT=client
+ FILEBOT_NODE_CLIENT=client
+ cd /usr/local/filebot-node
+ node --optimize_for_size --use_idle_notification server/app.js
2019-02-27T22:11:46-0600 fs.js:1171
  return binding.chown(pathModule._makeLong(path), uid, gid);
                 ^

TypeError: uid must be an unsigned int
    at Object.fs.chownSync (fs.js:1171:18)
    at Object.<anonymous> (/volume1/@appstore/filebot-node/server/app.js:57:8)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3
2019-02-27T22:12:16-0600 + export FILEBOT_NODE_HOST=127.0.0.1
2019-02-27T22:12:16-0600 + FILEBOT_NODE_HOST=127.0.0.1
2019-02-27T22:12:16-0600 + export FILEBOT_NODE_AUTH=SYNO
2019-02-27T22:12:16-0600 + FILEBOT_NODE_AUTH=SYNO
+ export FILEBOT_NODE_HTTP=YES
+ FILEBOT_NODE_HTTP=YES
+ export FILEBOT_NODE_HTTP_PORT=5452
2019-02-27T22:12:16-0600 + FILEBOT_NODE_HTTP_PORT=5452
+ export USER=admin
+ USER=admin
2019-02-27T22:12:16-0600 ++ free
2019-02-27T22:12:16-0600 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2019-02-27T22:12:16-0600 + export JAVA_OPTS=-Xmx460m
+ JAVA_OPTS=-Xmx460m
+ export FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ export FILEBOT_CMD=filebot
+ FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ FILEBOT_CMD_CWD=/volume1
2019-02-27T22:12:16-0600 ++ id -u admin
2019-02-27T22:12:16-0600 id: admin: no such user
+ export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
++ grep administrators
2019-02-27T22:12:16-0600 ++ cat /etc/group
2019-02-27T22:12:16-0600 ++ cut -d: -f3
2019-02-27T22:12:16-0600 + export FILEBOT_CMD_GID=101
+ FILEBOT_CMD_GID=101
+ export FILEBOT_NODE_CLIENT=client
+ FILEBOT_NODE_CLIENT=client
+ cd /usr/local/filebot-node
+ node --optimize_for_size --use_idle_notification server/app.js
2019-02-27T22:12:18-0600 fs.js:1171
  return binding.chown(pathModule._makeLong(path), uid, gid);
                 ^

TypeError: uid must be an unsigned int
    at Object.fs.chownSync (fs.js:1171:18)
    at Object.<anonymous> (/volume1/@appstore/filebot-node/server/app.js:61:8)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3
2019-02-27T22:12:45-0600 + export FILEBOT_NODE_HOST=127.0.0.1
2019-02-27T22:12:45-0600 + FILEBOT_NODE_HOST=127.0.0.1
2019-02-27T22:12:45-0600 + export FILEBOT_NODE_AUTH=SYNO
2019-02-27T22:12:45-0600 + FILEBOT_NODE_AUTH=SYNO
2019-02-27T22:12:45-0600 + export FILEBOT_NODE_HTTP=YES
2019-02-27T22:12:45-0600 + FILEBOT_NODE_HTTP=YES
2019-02-27T22:12:45-0600 + export FILEBOT_NODE_HTTP_PORT=5452
2019-02-27T22:12:45-0600 + FILEBOT_NODE_HTTP_PORT=5452
2019-02-27T22:12:45-0600 + export USER=admin
2019-02-27T22:12:45-0600 + USER=admin
2019-02-27T22:12:45-0600 ++ free
2019-02-27T22:12:45-0600 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2019-02-27T22:12:45-0600 + export JAVA_OPTS=-Xmx460m
+ JAVA_OPTS=-Xmx460m
+ export FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ export FILEBOT_CMD=filebot
+ FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ FILEBOT_CMD_CWD=/volume1
2019-02-27T22:12:45-0600 ++ id -u admin
2019-02-27T22:12:45-0600 id: admin: no such user
2019-02-27T22:12:45-0600 + export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
2019-02-27T22:12:45-0600 ++ grep administrators
2019-02-27T22:12:45-0600 ++ cut -d: -f3
2019-02-27T22:12:45-0600 ++ cat /etc/group
2019-02-27T22:12:45-0600 + export FILEBOT_CMD_GID=101
+ FILEBOT_CMD_GID=101
+ export FILEBOT_NODE_CLIENT=client
+ FILEBOT_NODE_CLIENT=client
+ cd /usr/local/filebot-node
+ node --optimize_for_size --use_idle_notification server/app.js
2019-02-27T22:12:48-0600 ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  TERM: 'vt102',
  FILEBOT_CMD_UID: '',
  OLDPWD: '/volume1/@appstore/filebot-node',
  JAVA_OPTS: '-Xmx460m',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  FILEBOT_CMD_GID: '101',
  PWD: '/usr/local/filebot-node',
  FILEBOT_NODE_HOST: '127.0.0.1',
  SHLVL: '1',
  FILEBOT_CMD: 'filebot',
  UPSTART_INSTANCE: '',
  FILEBOT_NODE_HTTP_PORT: '5452',
  FILEBOT_NODE_AUTH: 'SYNO',
  UPSTART_JOB: 'filebot-node',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_CLIENT: 'client',
  _: '/usr/local/bin/node' }
2019-02-27T22:12:48-0600 USER { UID: NaN, GID: 101 }
2019-02-27T22:12:48-0600 filebot-node listening at http://127.0.0.1:5452/
2019-02-27T22:13:01-0600 AUTH_CACHE: {"id=FWO0Uj6CSJJYg15C0NEN475208":"Craig"}
2019-02-27T22:13:01-0600 AUTH_CACHE: {"id=FWO0Uj6CSJJYg15C0NEN475208":"Craig"}
2019-02-27T23:21:09-0600 + export FILEBOT_NODE_HOST=127.0.0.1
+ FILEBOT_NODE_HOST=127.0.0.1
+ export FILEBOT_NODE_AUTH=SYNO
+ FILEBOT_NODE_AUTH=SYNO
+ export FILEBOT_NODE_HTTP=YES
+ FILEBOT_NODE_HTTP=YES
+ export FILEBOT_NODE_HTTP_PORT=5452
+ FILEBOT_NODE_HTTP_PORT=5452
+ export USER=admin
+ USER=admin
++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
++ free
2019-02-27T23:21:09-0600 + export JAVA_OPTS=-Xmx460m
+ JAVA_OPTS=-Xmx460m
+ export FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ export FILEBOT_CMD=filebot
+ FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ FILEBOT_CMD_CWD=/volume1
2019-02-27T23:21:09-0600 ++ id -u admin
2019-02-27T23:21:09-0600 id: admin: no such user
2019-02-27T23:21:09-0600 + export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
2019-02-27T23:21:09-0600 ++ cut -d: -f3
2019-02-27T23:21:09-0600 ++ cat /etc/group
2019-02-27T23:21:09-0600 ++ grep administrators
2019-02-27T23:21:09-0600 + export FILEBOT_CMD_GID=101
+ FILEBOT_CMD_GID=101
+ export FILEBOT_NODE_CLIENT=client
+ FILEBOT_NODE_CLIENT=client
+ cd /usr/local/filebot-node
+ node --optimize_for_size --use_idle_notification server/app.js
2019-02-27T23:21:13-0600 fs.js:1171
  return binding.chown(pathModule._makeLong(path), uid, gid);
                 ^

TypeError: uid must be an unsigned int
    at Object.fs.chownSync (fs.js:1171:18)
    at Object.<anonymous> (/volume1/@appstore/filebot-node/server/app.js:61:8)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3
2019-02-27T23:21:49-0600 + export FILEBOT_NODE_HOST=127.0.0.1
2019-02-27T23:21:49-0600 + FILEBOT_NODE_HOST=127.0.0.1
+ export FILEBOT_NODE_AUTH=SYNO
+ FILEBOT_NODE_AUTH=SYNO
+ export FILEBOT_NODE_HTTP=YES
+ FILEBOT_NODE_HTTP=YES
+ export FILEBOT_NODE_HTTP_PORT=5452
+ FILEBOT_NODE_HTTP_PORT=5452
+ export USER=admin
+ USER=admin
++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
++ free
2019-02-27T23:21:49-0600 + export JAVA_OPTS=-Xmx460m
+ JAVA_OPTS=-Xmx460m
+ export FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ export FILEBOT_CMD=filebot
+ FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ FILEBOT_CMD_CWD=/volume1
2019-02-27T23:21:49-0600 ++ id -u admin
2019-02-27T23:21:49-0600 id: admin: no such user
2019-02-27T23:21:49-0600 + export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
++ grep administrators
2019-02-27T23:21:49-0600 ++ cat /etc/group
2019-02-27T23:21:49-0600 ++ cut -d: -f3
2019-02-27T23:21:49-0600 + export FILEBOT_CMD_GID=101
+ FILEBOT_CMD_GID=101
+ export FILEBOT_NODE_CLIENT=client
+ FILEBOT_NODE_CLIENT=client
+ cd /usr/local/filebot-node
+ node --optimize_for_size --use_idle_notification server/app.js
2019-02-27T23:21:53-0600 ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  TERM: 'vt102',
  FILEBOT_CMD_UID: '',
  OLDPWD: '/volume1/@appstore/filebot-node',
  JAVA_OPTS: '-Xmx460m',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  FILEBOT_CMD_GID: '101',
  PWD: '/usr/local/filebot-node',
  FILEBOT_NODE_HOST: '127.0.0.1',
  SHLVL: '1',
  FILEBOT_CMD: 'filebot',
  UPSTART_INSTANCE: '',
  FILEBOT_NODE_HTTP_PORT: '5452',
  FILEBOT_NODE_AUTH: 'SYNO',
  UPSTART_JOB: 'filebot-node',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_CLIENT: 'client',
  _: '/usr/local/bin/node' }
2019-02-27T23:21:53-0600 USER { UID: NaN, GID: 101 }
2019-02-27T23:21:53-0600 filebot-node listening at http://127.0.0.1:5452/
2019-02-27T23:22:01-0600 AUTH_CACHE: {"id=FWO0Uj6CSJJYg15C0NEN475208":"Craig"}

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

Re: FileBot Node Troubleshooting

Post by rednoah » 28 Feb 2019, 06:48

Here's the problem:

Code: Select all

$ id -u admin
id: admin: no such user
FileBot Node wants to run as admin user. But somehow this user doesn't exist on your system, which is very strange because admin is the default user account for DSM.

What does cat /etc/passwd say?

Code: Select all

cat /etc/passwd
:idea: Please read the FAQ and How to Request Help.

jettechfsr
Posts: 8
Joined: 24 Dec 2018, 07:05

Re: FileBot Node Troubleshooting

Post by jettechfsr » 28 Feb 2019, 13:47

Have a lot of these will work on it tonight but making progress

Code: Select all

/usr/syno/synoman:/usr/bin/nologin

jettechfsr
Posts: 8
Joined: 24 Dec 2018, 07:05

Re: FileBot Node Troubleshooting

Post by jettechfsr » 01 Mar 2019, 05:01

Ok got it fixed not sure how I checked users and verfied admin was there then had Java error removed everything reinstalled found license file and all working now thanks for the help

PetiePal
Posts: 1
Joined: 27 Mar 2019, 13:44

Re: FileBot Node Troubleshooting

Post by PetiePal » 27 Mar 2019, 13:56

Hi!

I recently set up a Synology DS1019+ NAS. (DSM 6.2.1-23824 Update 6) I got everything on there set up plus my Plex server set up and a chunk of files copied over.

I tried to follow the FileBot instructions and installed:

-Java 8-
Filebot
-Filebot Node
-MediaInfo
-MediaServer and
-ChromaPrint

It looks like all packages installed correctly, however Filebot Node refuses to start even when I try manually. I restarted the NAS as well and re-tried with no success. I can't even see a log to find out what's happening because I think it's never successfully run at all.

1. Is there anything I'm missing to install?
2. Do I have to create manual directories on the NAS folder structure for this or was it all done automatically on package installs?
3. I saw that FileBot is for pay now. Do I have to manually activate the license somehow before the service will even run? (I don't want to purchase until I know the program at least runs!)
4. I saw there are some ports that need to be allowed/forwarded through Firewall (mentioned in the beginning of this thread like TCP traffic on ports 5452 and 5453)

Thanks in advance!

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

Re: FileBot Node Troubleshooting

Post by rednoah » 27 Mar 2019, 19:43

1.
Please log in via SSH and find the filebot-node log, so we can see what's going, presumably crashing immediately on startup for some reason:

Code: Select all

find / -name filebot-node.log 2> /dev/null
:idea: Did you install the Node JS package from Synology? node needs to be installed, otherwise the node service launcher will exit with an error immediately.


2.
You'll be able to completely evaluate FileBot before / without purchasing a license. You don't need to worry about a license before you even see anything happen.
:idea: Please read the FAQ and How to Request Help.

Segarra
Posts: 11
Joined: 11 Jun 2016, 11:11

Re: FileBot Node Troubleshooting

Post by Segarra » 05 Apr 2019, 11:11

Hello to everyone, I have a little problem, since I updated "filebot" to 4.8.5, filebot-node, doesn't start anymore, before, with 4.8.2, I didn't have any problem
Could you help me?

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

Re: FileBot Node Troubleshooting

Post by rednoah » 05 Apr 2019, 11:13

FileBot Node is completely unrelated to FileBot, and one can't affect the other.

What does the log say?
:idea: Please read the FAQ and How to Request Help.

Tdoc
Posts: 22
Joined: 20 Feb 2018, 08:19

Re: FileBot Node Troubleshooting

Post by Tdoc » 10 Apr 2019, 16:42

Same issue here
viewtopic.php?p=43216&sid=9fdafc14a2bd4 ... 4c7#p43216

Trying to get the log error from filebot nod, not easy !!

CamMty
Posts: 1
Joined: 23 Feb 2019, 08:05

Re: FileBot Node Troubleshooting

Post by CamMty » 19 Apr 2019, 23:14

  • this file is not on the server yet:
    https://get.filebot.net/qnap/packages/filebot-node_0.2.8.3.qpkg
    we can't upgrade on QNAP.
    please check
    thanks

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

Re: FileBot Node Troubleshooting

Post by rednoah » 20 Apr 2019, 05:22

Please try again. Should work now.
:idea: Please read the FAQ and How to Request Help.

hellcry
Posts: 4
Joined: 07 Feb 2019, 11:04

Re: FileBot Node Troubleshooting

Post by hellcry » 24 Aug 2019, 07:28

Code: Select all

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/volume1/@appstore/filebot/jar/groovy.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Can this be solved?
I remember reported this some time ago and I was told needs an update. From then til now some time passed and updates were done on my synology nas and still have this warnings in logs, is full of them!

Link to where i report it first: https://github.com/filebot/filebot-node/issues/24

So basically I am waiting for 4.8.6 final not beta since I don't want to go beta testing.

p.s. Don't want to seem like a douche but I paid for this to use a stable version not to beta test it.

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

Re: FileBot Node Troubleshooting

Post by rednoah » 24 Aug 2019, 07:41

Well, you could use Java 8 + FileBot 4.8.5 if this warning makes you feel uncomfortable. You’d have to install Java 8 manually though since Oracle no longer publishes public builds.
:idea: Please read the FAQ and How to Request Help.

Post Reply