FileBot Node cant find directories - AMC setup issues

[giBiLatoR]

System - DSM 6.2
Docker Install - using https://hub.docker.com/r/rednoah/filebot as a guide

Have totally reformatted my DS918+ trying to get this working, had it at a state where the Node was functioning correctly but not it won't function past spitting out logs. Log paste below showing main issue not being able to point it to a valid directory.

When it was working it was able to find:

Code: Select all

volume1/volume1/dir

and have also tried with just

Code: Select all

volume1/dir

to no success (this being the valid directory)

Below is the paste of the logs from the node output

Code: Select all

filebot -script 'fn:amc' volume1/Main/Downloads --output /volume1/Main/Media --action duplicate -non-strict --order Airdate --conflict index --lang en --def 'music=y' 'unsorted=y' 'artwork=y' 'clean=y' 'deleteAfterExtract=y' 'excludeList=.excludes' --log all --log-file '/usr/local/filebot-node/data/filebot.log'

------------------------------------------

Locking /usr/local/filebot-node/data/filebot.log
Illegal Argument: java.nio.file.NoSuchFileException: /volume1/volume1/Main/Downloads (volume1/Main/Downloads)
Run script [fn:amc] at [Sun Jan 06 22:27:27 UTC 2019]
Parameter: music = y
Parameter: unsorted = y
Parameter: artwork = y
Parameter: clean = y
Parameter: deleteAfterExtract = y
Parameter: excludeList = .excludes
Argument[0]: File does not exist: volume1/Main/Downloads
Illegal usage: output folder must exist and must be a directory: /volume1/Main/Media
Failure (°_°)
------------------------------------------

[Process error]

Also another strange thing which may be the root of the problem - when trying the second command it spits outs port already allocated error, and when binding to a different port it doesnt push it to local host it goes to 0.0.0.0. I am very new to unix so I may be reading this incorrectly.

Code: Select all

root@ZuinoNAS:~# docker run -it -v $PWD:/volume1/volume1  -v data:/data -p 5452:5452 rednoah/filebot:node
docker: Error response from daemon: driver failed programming external connectivity on endpoint laughing_borg (deef0ceaec7101fd1fda477f638e2eab0be2d26df567df26232b5ef20cb84aa5): Bind for 0.0.0.0:5452 failed: port is already allocated.
root@ZuinoNAS:~# docker run -it -v $PWD:/volume1/volume1  -v data:/data -p 5622:5622 rednoah/filebot:node
+ export FILEBOT_NODE_HOST=0.0.0.0
+ export FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ id -u
+ export FILEBOT_CMD_UID=0
+ id -g
+ export FILEBOT_CMD_GID=0
+ export FILEBOT_NODE_CLIENT=/usr/local/filebot-node/client
+ node --optimize_for_size --use_idle_notification /usr/local/filebot-node/server/app.js
ENVIRONMENT { FILEBOT_CMD_UID: '0',
  HOSTNAME: '07b9b08f3007',
  HOME: '/data',
  FILEBOT_NODE_AUTH: 'NONE',
  JAVA_VERSION: '10.0.2+13',
  FILEBOT_NODE_HTTP_PORT: '5452',
  TERM: 'xterm',
  FILEBOT_NODE_VERSION: '0.2.8.1',
  JAVA_DEBIAN_VERSION: '10.0.2+13-1',
  FILEBOT_VERSION: '4.8.2',
  PATH:
   '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTP: 'YES',
  LANG: 'C.UTF-8',
  DOCKER_VOLUME: '/volume1',
  FILEBOT_CMD_GID: '0',
  FILEBOT_OPTS: '-Dapplication.deployment=docker -Duser.home=/data',
  JAVA_HOME: '/docker-java-home',
  DOCKER_DATA: '/data',
  PWD: '/usr/local/filebot-node',
  FILEBOT_CMD: 'filebot',
  FILEBOT_NODE_CLIENT: '/usr/local/filebot-node/client',
  FILEBOT_CMD_CWD: '/volume1' }
USER { UID: 0, GID: 0 }
filebot-node listening at http://0.0.0.0:5452/filebot/

Love this program and have been using it successfully on windows for years!

Much thanks for what you have provided the community.

Any thoughts or suggestions much appreciated

Kind regards.

[rednoah]

As far as filebot is concerned, /volume1/Main/Media does not exist:

Code: Select all

Illegal usage: output folder must exist and must be a directory: /volume1/Main/Media

Now that's either because it really does not exist, or because FileBot just doesn't have permission to see it.


On Synology, the easiest solution is to just create a new share, so everything has the default permissions, and the just go with that.