FileBot Node doesn't work on DSM 6

[NeoReloaded]

However, I still have an issue with it.
It does the job when I ask for it manually. But, when it has been added to Task Scheduler, it never works.
I have scheduled a task called "FileBot Task" with the user "admin". Programmed each day, starting at 03:00, every 15 minutes, until 22:45. I even can see the time of the next task on the widget window increased every 15 minutes. But nothing ever happens. What did I miss ?
Thanks for your help, once again !

[rednoah]

Logs?

[NeoReloaded]

/usr/local/filebot-node/task "1459151080117" # -script 'fn:amc' /volume1/Torrents/Incoming --output /volume1/video --action hardlink -non-strict --conflict auto --lang en --def 'artwork=y' 'subtitles=fra' 'skipExtract=y' 'minLengthMS=300000' 'minFileSize=100000000' 'seriesFormat=TV Shows/{n}/Saison {s}/{n} - {sxe} - {t}' 'animeFormat=Anime/{n} ({y})/{n} ({y})' 'movieFormat=Movies/{n} ({y})/{n} ({y})' 'excludeList=.excludes' --log all --log-file '/volume1/@appstore/filebot-node/data/filebot.log'

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

/usr/local/bin/filebot: line 21: cd: /root: Permission denied
Locking /volume1/@appstore/filebot-node/data/filebot.log
Mar 28, 2016 10:00:06 AM net.filebot.Main main
SEVERE: Unexpected error during startup
java.nio.file.AccessDeniedException: /volume1/@appstore/filebot/data/root/temp
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384)
at java.nio.file.Files.createDirectory(Files.java:674)
at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781)
at java.nio.file.Files.createDirectories(Files.java:767)
at net.filebot.util.FileUtilities.createFolders(FileUtilities.java:165)
at net.filebot.Main.main(Main.java:138)

I see ! Maybe the problem is that I run this task for the user "admin" ?

[rednoah]

When FileBot Node creates the Task then it will be set to run as user admin. If you change it to root you might break things.

Running tasks as root is not supported, not tested, and absolutely not recommended.

If you run as root, especially when running for the first time, you might be initializing some folders with root permissions, breaking things for everyone.

Uninstall, then reinstall everything. Never ever run as root. Always run as admin.

[lefouyou]

Hi,

I don't think my problem is directly related but when I launch a filebot command I got this error : http://i.imgur.com/XebOdis.png.

I am running DSM 6 with FileBot 4.6.1 (r3315) / Java(TM) SE Embedded Runtime Environment 1.8.0_77 (headless)
and java

java version "1.8.0_77"
Java(TM) SE Embedded Runtime Environment (build 1.8.0_77-b03, headless)
Java HotSpot(TM) Embedded Client VM (build 25.77-b03, mixed mode)

Thanks for your help

[rednoah]

That's a generic Java/HTTPS/SSL issue and not specific to FileBot. I'm sure you'll find lots of information if you just google for that error message.

Also, sysinfo output?

[lefouyou]

It gives me the same error http://i.imgur.com/TA3i8kp.png, i don't understand how can it be SSL related, it is not even mention in the trace ?

Sorry but i really don't understand

[rednoah]

The WebRequest.fetch() method is clearly doing some sort of network request, HTTPS in this case. Stacktraces may not always be completely accurate, especially within the JRE classes which might get highly optimized at runtime (and thus not allow accurate stacktraces).

java.lang.SecurityException is always something that is very strange and generally not an issue with the application itself, but with the whole runtime configuration.

Try uninstalling and reinstalling everything Java related. You can try my Java installer, but if it really doesn't work for you, you might want to give the Synology Java packages a shot.

[NeoReloaded]

When FileBot Node creates the Task then it will be set to run as user admin. If you change it to root you might break things.

Running tasks as root is not supported, not tested, and absolutely not recommended.

If you run as root, especially when running for the first time, you might be initializing some folders with root permissions, breaking things for everyone.

Uninstall, then reinstall everything. Never ever run as root. Always run as admin.

Once again you were right ! Last night before going to bed, I've uninstalled, then reinstalled everything. And this morning all tasks went good ! Thank you so much for your help !

[lefouyou]

Thanks, I tried to re install Synology Java Package and it worked fine, thanks for your help

[Hansson]

Hi,

after upgrading do DSM 6.0, FileBot Node couldn't be launched anymore (while FileBot was still running). I´ve tried to follow some of the suggestions here but a new problem came up.

Full deinstall and install of FileBot, FileBot Node and the unofficial Java installer.

Problem: I can´t reinstall the unofficial Java installer due to following message "The available disk space of this system in insufficient".

I checked via ssh:
Filesystem Size Used Avail Use% Mounted on
/dev/md0 2.3G 754M 1.5G 35% /
none 320M 4.0K 320M 1% /dev
/tmp 330M 408K 329M 1% /tmp
/run 330M 3.4M 326M 2% /run
/dev/shm 330M 12K 330M 1% /dev/shm
/dev/vg1000/lv 3.6T 3.2T 397G 90% /volume1

Am I missing something here? Shouldn't the unofficial Java Installer just be 180m?

I really don´t get it. Has someone an idea?

Many thanks in advance

[rednoah]

That seems to be a bug in DSM:
https://forum.synology.com/enu/viewtopi ... 3&t=116230

[vletroye]

ok, once connected via ssh, as admin + sudo -i (can't connect as root anymore with DSM 6.0), if I go to the target folder and type ./start, I get

Code: Select all

ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  FILEBOT_NODE_HTTPS_KEY: '/usr/syno/etc/certificate/system/default/privkey.pem',
  TERM: 'xterm',
  SHELL: '/bin/ash',
  FILEBOT_CMD_UID: '1024',
  OLDPWD: '/var/packages/filebot-node/target',
  LC_ALL: 'en_US.utf8',
  JAVA_OPTS: '-Xmx4167m',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  SUDO_USER: 'admin',
  SUDO_UID: '1024',
  USERNAME: 'root',
  PAGER: 'more',
  FILEBOT_NODE_HTTPS_PORT: '5453',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  MAIL: '/var/mail/root',
  FILEBOT_CMD_GID: '101',
  PWD: '/var/packages/filebot-node/target',
  LANG: 'en_US.utf8',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTPS_CRT: '/usr/syno/etc/certificate/system/default/cert.pem',
  HOME: '/root',
  SUDO_COMMAND: '/bin/ash',
  SHLVL: '2',
  TERMINFO: '/usr/share/terminfo',
  FILEBOT_CMD: 'filebot',
  FILEBOT_NODE_HTTPS: 'YES',
  LOGNAME: 'root',
  FILEBOT_NODE_HTTP_PORT: '5452',
  PGDATA: '/var/services/pgsql',
  FILEBOT_NODE_AUTH: 'SYNO',
  SUDO_GID: '100',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_CLIENT: '',
  _: '/usr/local/bin/node' }
USER { UID: 1024, GID: 101 }
filebot-node listening at http://0.0.0.0:5452
filebot-node listening at https://0.0.0.0:5453

NB.: if I don't do sudo -i first, it fails with a permission error.

So, via ssh, it seems to run fine. But still, trying to start the package via the UI, I get again the error "Fail to run the service package".

Is there any log that I could check ?

[vletroye]

By the way, not running as root but running as admin here is the output of the ./start command:

Code: Select all

ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  FILEBOT_NODE_HTTPS_KEY: '/usr/syno/etc/certificate/system/default/privkey.pem',
  SHELL: '/bin/sh',
  TERM: 'xterm',
  FILEBOT_CMD_UID: '1024',
  SSH_CLIENT: '192.168.0.125 50638 22',
  OLDPWD: '/var/packages/filebot-node/target',
  SSH_TTY: '/dev/pts/1',
  LC_ALL: 'en_US.utf8',
  JAVA_OPTS: '-Xmx4167m',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  PAGER: 'more',
  FILEBOT_NODE_HTTPS_PORT: '5453',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  MAIL: '/var/mail/admin',
  FILEBOT_CMD_GID: '101',
  PWD: '/var/packages/filebot-node/target',
  LANG: 'en_US.utf8',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTPS_CRT: '/usr/syno/etc/certificate/system/default/cert.pem',
  HOME: '/var/services/homes/admin',
  SHLVL: '2',
  TERMINFO: '/usr/share/terminfo',
  FILEBOT_CMD: 'filebot',
  FILEBOT_NODE_HTTPS: 'YES',
  LOGNAME: 'admin',
  SSH_CONNECTION: '192.168.0.125 50638 192.168.0.200 22',
  FILEBOT_NODE_HTTP_PORT: '5452',
  PGDATA: '/var/services/pgsql',
  FILEBOT_NODE_AUTH: 'SYNO',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_CLIENT: '',
  _: '/usr/local/bin/node' }
USER { UID: 1024, GID: 101 }
filebot-node listening at http://0.0.0.0:5452
fs.js:549
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: EACCES: permission denied, open '/usr/syno/etc/certificate/system/default/privkey.pem'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.readFileSync (fs.js:397:15)
    at Object.<anonymous> (/volume1/@appstore/filebot-node/server/app.js:537:17)
    at Module._compile (module.js:410:26)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Function.Module.runMain (module.js:442:10)
    at startup (node.js:136:18)

I.e.: it fails to listen on the https port, not being authorized to read the private key ?!.

[rednoah]

Have you tried clicking on "View Log" yet?
viewtopic.php?f=13&t=3368

[vletroye]

Yes... and it still empty (since I have reinstalled Filebot-node, after the upgrade to DSM 6.0)

V.

[rednoah]

You are using filebot-node-0.2.0-B1-noarch.spk uploaded on 2016-03-30 correct?

[vletroye]

Yes, I am. And to be sure, I just redownloaded it (https://sourceforge.net/projects/filebo ... k/download), uninstall the previous version and install that one. I still have the error message when DSM tries to run the package (after installation)

V.

[rednoah]

Then I'm out of ideas. Check the Synology system logs.

According to /var/packages/filebot-node/scripts/start-stop-status it always returns 0 so there should be no reason why DSM would report it can't start the package (regardless of whether it works or not).

Maybe you'll find some hints in the system logs:

Code: Select all

cat /var/log/messages

[vletroye]

Does this ring a bell for you : pkgstartstop.cpp:253 Failed to start pkgctl-filebot-node (err=-2) [0xEA00 service_start.c:141]

cat /var/log/messages

Code: Select all

Apr  1 22:08:04 Hades synoscgi_SYNO.Core.Package.Uninstallation_1_uninstall[30479]: resource_api.cpp:231 Release service-cfg for filebot-node when 0x0004 (done)
Apr  1 22:08:35 Hades synoscgi_SYNO.Core.Package.Installation_1_install[31505]: resource_api.cpp:163 Acquire service-cfg for filebot-node when 0x0001 (done)
Apr  1 22:08:48 Hades synoscgi_SYNO.Core.Package.Control_1_start[32085]: pkgstartstop.cpp:253 Failed to start pkgctl-filebot-node (err=-2) [0xEA00 service_start.c:141]

cat /var/log/synopkg.log

Code: Select all

2016/04/01 22:08:35     install filebot-node 0.2.0 successfully
2016/04/01 22:08:48     start filebot-node: begin to start version 0.2.0
2016/04/01 22:08:48     stop filebot-node: begin to stop version 0.2.0
2016/04/01 22:08:48     stop filebot-node: stop version 0.2.0 successfully, result 0
2016/04/01 22:08:52     start filebot-node: start version 0.2.0 failed, result 272

If I start manually in a ssh instead of via the Package Center, but just like done in the start-stop-status scripts, I don't get any error:

Code: Select all

root@Hades:/usr/local/bin# initctl start filebot-node
filebot-node start/running, process 13674
root@Hades:/usr/local/bin# initctl status filebot-node
filebot-node start/running, process 13674
root@Hades:/usr/local/bin# initctl stop filebot-node
filebot-node stop/waiting
root@Hades:/usr/local/bin# initctl status filebot-node
filebot-node stop/waiting

[drcursor]

Had the same issue as the user above...random "Invalid Signature" errors when running filebot.
- Removed all java and filebot packages and installed again using the unofficial java installer : same error
- Tried running against a local amc script : same error
- Removed cache files : started working again! ( rm -Rf /volume1/@appstore/filebot/data/* )

[vletroye]

I tried both
rm -Rf /volume1/@appstore/filebot-node/data/*
rm -Rf /volume1/@appstore/filebot/data/*

But it didn't help

[rednoah]

Uninstalling <package> removes the /volume1/@appstore/<package> folder, so this won't work if uninstalling doesn't work.

[vletroye]

I am not expert in DSM & packages, but which account is running the packages ?

I just noticed that running my Schedule Task "filebot -script 'fn:amc' etc..." does not work when run as 'admin'.
It only works if run as 'root'.

[rednoah]

Synology packages run as root. While filebot-node runs as root, it will call filebot as admin. FileBot should only ever be called as admin. If you call filebot as root, it my changes the permissions and break it for everyone but root, thus you should never ever call filebot as root.

If you have permission issues, fix the permissions. Don't just run everything as root. It's just gonna fuck up the permissions even more, because files/folders created by root, will only be accessible to root.