[FIXED] Filebot nod dead since filebot new version
[FIXED] Filebot nod dead since filebot new version
Good day rednoah
since filebot updated itself to 4.8.5; filebot nod 4.8.2 isn't working anymore, I have uninstalled and resintalled both without any success
If I "execute" filebot nod I get a strange message https://ibb.co/ChMM2dL
If I try a "dry run" or "schedule" i get https://ibb.co/GpTPcnC
licence, configure subtitle login and help do work normaly
I am running a synology DS415Play DSM 6.2.1-23824 Update 6 (up to date) with
JAVA8.0.161-005
Media info 17.12-6
Chromaprint 1.4.3-7
Any ideas why it is broken ?
in avance thanks
since filebot updated itself to 4.8.5; filebot nod 4.8.2 isn't working anymore, I have uninstalled and resintalled both without any success
If I "execute" filebot nod I get a strange message https://ibb.co/ChMM2dL
If I try a "dry run" or "schedule" i get https://ibb.co/GpTPcnC
licence, configure subtitle login and help do work normaly
I am running a synology DS415Play DSM 6.2.1-23824 Update 6 (up to date) with
JAVA8.0.161-005
Media info 17.12-6
Chromaprint 1.4.3-7
Any ideas why it is broken ?
in avance thanks
Last edited by Tdoc on 19 Apr 2019, 14:50, edited 1 time in total.
Re: [BUG?] Filebot nod dead since filebot new version
These are FileBot Node errors, completely unrelated to what version of the FileBot command line tool you may or may not have installed.
Check the FileBot Node logs and see if there's any hints there.
Check the FileBot Node logs and see if there's any hints there.
Re: [BUG?] Filebot nod dead since filebot new version
thanks
Sorry for my ignorance, where do I found errors logs for filebot nod ?
thanks again
Sorry for my ignorance, where do I found errors logs for filebot nod ?
thanks again
Re: [BUG?] Filebot nod dead since filebot new version
You'll need to login via the SSH and use the find command to find it.
You'll find more detailed instructions for that in previous threads.
You'll find more detailed instructions for that in previous threads.
Re: [BUG?] Filebot nod dead since filebot new version
Cant access to filebotnod log even with root access
I tried with Filebot nod stopped, same denied access
What else ?
Code: Select all
login as: Admin
[email protected]'s password:
Admin@Diskstation:~$ sudo -i
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
root@Diskstation:~# $ find / -name filebot-node.log 2> /dev/null
root@Diskstation:~# /var/log/upstart/filebot-node.log
-ash: /var/log/upstart/filebot-node.log: Permission denied
I tried with Filebot nod stopped, same denied access
What else ?
Re: [BUG?] Filebot nod dead since filebot new version
Try:
Code: Select all
sudo cat /var/log/upstart/filebot-node.log
Re: [BUG?] Filebot nod dead since filebot new version
Hi rednoah
if works this time, here is the log
it looks like it does not find the "admin" user ? thats the user I use to setup and manage DSM. I have ther users then for the family
if works this time, here is the log
it looks like it does not find the "admin" user ? thats the user I use to setup and manage DSM. I have ther users then for the family
Code: Select all
2019-04-09T18:24:24+0200 + 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
2019-04-09T18:24:24+0200 ++ free
2019-04-09T18:24:24+0200 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2019-04-09T18:24:24+0200 + export JAVA_OPTS=-Xmx489m
+ JAVA_OPTS=-Xmx489m
+ 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-04-09T18:24:24+0200 ++ id -u admin
2019-04-09T18:24:24+0200 id: admin: no such user
+ export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
2019-04-09T18:24:24+0200 ++ cut -d: -f3
2019-04-09T18:24:24+0200 ++ grep administrators
2019-04-09T18:24:24+0200 ++ cat /etc/group
2019-04-09T18:24:24+0200 + 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-04-09T18:24:25+0200 fs.js:1038
return binding.chown(pathModule._makeLong(path), uid, gid);
^
TypeError: uid must be an unsigned int
at TypeError (native)
at Object.fs.chownSync (fs.js:1038:18)
at Object.<anonymous> (/volume1/@appstore/filebot-node/server/app.js:57:8)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
at node.js:1043:3
2019-04-09T18:25:44+0200 + 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
2019-04-09T18:25:44+0200 + export FILEBOT_NODE_HTTP_PORT=5452
+ FILEBOT_NODE_HTTP_PORT=5452
+ export USER=admin
+ USER=admin
2019-04-09T18:25:44+0200 ++ free
2019-04-09T18:25:44+0200 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2019-04-09T18:25:44+0200 + export JAVA_OPTS=-Xmx489m
+ JAVA_OPTS=-Xmx489m
+ 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-04-09T18:25:44+0200 ++ id -u admin
2019-04-09T18:25:44+0200 id: admin: no such user
2019-04-09T18:25:44+0200 + export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
2019-04-09T18:25:44+0200 ++ cat /etc/group
2019-04-09T18:25:44+0200 ++ grep administrators
2019-04-09T18:25:44+0200 ++ cut -d: -f3
2019-04-09T18:25:44+0200 + 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-04-09T18:25:45+0200 fs.js:1038
2019-04-09T18:25:45+0200 return binding.chown(pathModule._makeLong(path), uid, gid);
2019-04-09T18:25:45+0200 ^
2019-04-09T18:25:45+0200
2019-04-09T18:25:45+0200 TypeError: uid must be an unsigned int
2019-04-09T18:25:45+0200 at TypeError (native)
2019-04-09T18:25:45+0200 at Object.fs.chownSync (fs.js:1038:18)
2019-04-09T18:25:45+0200 at Object.<anonymous> (/volume1/@appstore/filebot-node/server/app.js:61:8)
2019-04-09T18:25:45+0200 at Module._compile (module.js:409:26)
2019-04-09T18:25:45+0200 at Object.Module._extensions..js (module.js:416:10)
2019-04-09T18:25:45+0200 at Module.load (module.js:343:32)
2019-04-09T18:25:45+0200 at Function.Module._load (module.js:300:12)
2019-04-09T18:25:45+0200 at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
at node.js:1043:3
2019-04-09T18:26:41+0200 + export FILEBOT_NODE_HOST=127.0.0.1
+ FILEBOT_NODE_HOST=127.0.0.1
2019-04-09T18:26:41+0200 + 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
2019-04-09T18:26:41+0200 + export USER=admin
+ USER=admin
2019-04-09T18:26:41+0200 ++ free
2019-04-09T18:26:41+0200 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2019-04-09T18:26:41+0200 + export JAVA_OPTS=-Xmx489m
+ JAVA_OPTS=-Xmx489m
+ 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-04-09T18:26:41+0200 ++ id -u admin
2019-04-09T18:26:41+0200 id: admin: no such user
+ export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
++ cat /etc/group
++ grep administrators
++ cut -d: -f3
2019-04-09T18:26:41+0200 + 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-04-09T18:26:42+0200 ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
TERM: 'vt102',
FILEBOT_CMD_UID: '',
OLDPWD: '/volume1/@appstore/filebot-node',
JAVA_OPTS: '-Xmx489m',
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-04-09T18:26:42+0200 USER { UID: NaN, GID: 101 }
2019-04-09T18:26:42+0200 filebot-node listening at http://127.0.0.1:5452/
2019-04-09T18:27:08+0200 AUTH_CACHE: {"id=D9d5sAH5Bhz6c1460MGN190011":"Admin"}
2019-04-09T18:27:08+0200 AUTH_CACHE: {"id=D9d5sAH5Bhz6c1460MGN190011":"Admin"}
2019-04-09T18:27:09+0200 AUTH_CACHE: {"id=D9d5sAH5Bhz6c1460MGN190011":"Admin"}
2019-04-09T18:30:02+0200 fs.js:1038
return binding.chown(pathModule._makeLong(path), uid, gid);
^
TypeError: uid must be an unsigned int
at TypeError (native)
at Object.fs.chownSync (fs.js:1038:18)
at spawnChildProcess (/volume1/@appstore/filebot-node/server/app.js:171:8)
at /volume1/@appstore/filebot-node/server/app.js:241:18
at IncomingForm.<anonymous> (/volume1/@appstore/filebot-node/server/node_modules/formidable/lib/incoming_form.js:107:9)
at emitNone (events.js:67:13)
at IncomingForm.emit (events.js:166:7)
at IncomingForm._maybeEnd (/volume1/@appstore/filebot-node/server/node_modules/formidable/lib/incoming_form.js:557:8)
at /volume1/@appstore/filebot-node/server/node_modules/formidable/lib/incoming_form.js:238:12
at WriteStream.<anonymous> (/volume1/@appstore/filebot-node/server/node_modules/formidable/lib/file.js:79:5)
2019-04-10T17:00:20+0200 + 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
2019-04-10T17:00:20+0200 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2019-04-10T17:00:20+0200 ++ free
2019-04-10T17:00:20+0200 + export JAVA_OPTS=-Xmx489m
+ JAVA_OPTS=-Xmx489m
+ 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-04-10T17:00:20+0200 ++ id -u admin
2019-04-10T17:00:20+0200 id: admin: no such user
2019-04-10T17:00:20+0200 + export FILEBOT_CMD_UID=
+ FILEBOT_CMD_UID=
2019-04-10T17:00:20+0200 ++ cat /etc/group
++ grep administrators
2019-04-10T17:00:20+0200 ++ cut -d: -f3
2019-04-10T17:00:20+0200 + 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-04-10T17:00:26+0200 ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
TERM: 'vt102',
FILEBOT_CMD_UID: '',
OLDPWD: '/volume1/@appstore/filebot-node',
JAVA_OPTS: '-Xmx489m',
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-04-10T17:00:26+0200 USER { UID: NaN, GID: 101 }
filebot-node listening at http://127.0.0.1:5452/
2019-04-10T18:45:53+0200 AUTH_CACHE: {"id=RLDSWnwQJaGBs1460MGN190011":"Admin"}
2019-04-10T18:45:53+0200 AUTH_CACHE: {"id=RLDSWnwQJaGBs1460MGN190011":"Admin"}
2019-04-10T18:45:53+0200 AUTH_CACHE: {"id=RLDSWnwQJaGBs1460MGN190011":"Admin"}
Admin@Diskstation:~$
Re: [BUG?] Filebot nod dead since filebot new version
Here's the source of the problem:
That's strange. What kind of Synology device are you using? There is supposed to be an admin user by default.
FileBot Node running filebot commands as admin user has always been the case, and unrelated to any older or newer version of FileBot Node. Without an admin user, no version of FileBot Node could have ever worked.
Code: Select all
id: admin: no such user

Re: [BUG?] Filebot nod dead since filebot new version
Hi Rednoah
as mentionned in my first post
I am running a synology DS415Play DSM 6.2.1-23824 Update 6 (up to date) with
JAVA8.0.161-005
Media info 17.12-6
Chromaprint 1.4.3-7
I have changed the administrator account name from "Admin" to "admin" now the error message is not a system (Synology DSM system) error but a filebot node error
The info gives
looks like cant access the filebot.log ?
as mentionned in my first post
I am running a synology DS415Play DSM 6.2.1-23824 Update 6 (up to date) with
JAVA8.0.161-005
Media info 17.12-6
Chromaprint 1.4.3-7
I have changed the administrator account name from "Admin" to "admin" now the error message is not a system (Synology DSM system) error but a filebot node error
Code: Select all
filebot -script 'fn:amc' /volume1/Downloads_raw --output /volume2/Video --action move -non-strict --order Airdate --conflict auto --lang en --def 'music=y' 'subtitles=fra' 'clean=y' 'skipExtract=y' 'seriesFormat=Series/{n}/{episode.special ? '\''Special'\'' : '\''Season '\''+s}/{n}.{episode.special ? '\''S00E'\''+special.pad(2) : s00e00}.{t}' 'animeFormat=Anime/{n}.{y}.{order.airdate.s00e00}.#{absolute}.{t}.[{airdate}]' 'movieFormat=Movies/{collection+'\''/'\''}{n.sortName('\''$2, $1'\'')}.{y}.{vf}.{vc}.{ac}.[{bitdepth}] bit.{audio.language}' 'musicFormat=Music/{n}/{album+'\''/'\''}{pi.pad(2)} - {artist} - {album} - {t}' 'excludeList=.excludes' --log all --log-file '/volume1/@appstore/filebot-node/data/filebot.log'
------------------------------------------
Error during startup
java.nio.file.AccessDeniedException: /volume1/@appstore/filebot-node/data/filebot.log
at net.filebot.Logging.createLogFileHandler(Logging.java:69)
at net.filebot.Main.initializeLogging(Main.java:455)
at net.filebot.Main.main(Main.java:112)
------------------------------------------
[Process error]
The info gives
Code: Select all
filebot -script 'fn:sysinfo'
------------------------------------------
FileBot 4.8.5 (r6224)
JNA Native: 5.2.2
MediaInfo: 17.12
7-Zip-JBinding: 9.20
Chromaprint: fpcalc version 1.4.3
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2019-04-09 (r559)
Groovy: 2.5.6
JRE: Java(TM) SE Runtime Environment 1.8.0_101
JVM: 32-bit Java HotSpot(TM) Client VM
CPU/MEM: 4 Core / 473 MB Max Memory / 14 MB Used Memory
OS: Linux (i386)
HW: Linux Diskstation 3.2.40 #23824 SMP PREEMPT Tue Feb 12 16:48:29 CST 2019 i686 GNU/Linux synology_evansport_415play
DATA: /volume1/@appstore/filebot/data/admin
Package: SPK
Activate License P42xxxxx
License: FileBot License P42xxxxx (Valid-Until: 2019-08-12)
Done ヾ(@⌒ー⌒@)ノ
------------------------------------------
[Process completed]
Re: [BUG?] Filebot nod dead since filebot new version
Not sure. Looks like permissions are screwed up. Have you tried uninstalling and reinstalling FileBot Node?
Is the admin account called Admin or admin by default on your device? Did you manually change it to Admin at some point in the past? Or was it always Admin? Or did it change to Admin automatically with some DSM update?

Re: [BUG?] Filebot nod dead since filebot new version
Admin was default account
I changed it to admin without a A then filebot node worked again but with error
I changed it back to Admin with a A fielbot still 'working' but with error
will unsintall and reinstall to see what is happening
I changed it to admin without a A then filebot node worked again but with error
I changed it back to Admin with a A fielbot still 'working' but with error
will unsintall and reinstall to see what is happening