FileBot Node doesn't start on DSM 6

[flasher111]

Hello Community,

i am new in this forum and i have a small problem with getting started the fileBot Node on my Sinology.
First of all i will give you a few informations about my system requirements.

I have a Synology DS 713+ installed with the second Beta-Version of DSM 6.
I installed:
-Java V7 --> runs perfect
-FileBot V4.6.1 --> runs perfect
and FileBot Nodes V0.1.7 --> didn't start



if i try to run FileBot Nodes a Message appears with "Der Packetdienst konnte nicht ausgeführt werden"

The log will give me the following output



i hope anybody could help me with this error.

[rednoah]

Looks like Node.js is not installed.

Also, FileBot requires at least Java 8.

[ZeroZorro]

I have exactly the same error:

Synology DS214play DSM 6.0-7274
Node.js 0.12.9-0159
Filebot 4.6.1
FileNode 0.1.8
Java: java version "1.8.0_73"
Java(TM) SE Embedded Runtime Environment (build 1.8.0_73-b02, headless)
Java HotSpot(TM) Embedded Client VM (build 25.73-b02, mixed mode)

Seems like node.js is installed but maybe in another dir? Any clues?

[ZeroZorro]

It seems like 'node' is installed in '/usr/local/bin' instead of /'usr/bin'
i copied the file to /usr/bin manually but still some errors...

[ZeroZorro]

Just did a new, clean setup following
viewtopic.php?f=3&t=1802

After installing Unofficial Java installer a got an error:

/var/packages/oracle-java-installer/scripts/postinst: line 10: /usr/local/bin/java: No such filer or directory

Probably that's where trouble starts?

[flasher111]

Looks like Node.js is not installed.

Also, FileBot requires at least Java 8.

First time i installed filebot Node i were asked to install the Node.js and i clicked "yes".
The Nodes.js installation was successful.

Today i installed Java 8 but it has no effect.
I also tried the new Version 0.1.8 from github but i have the same problems that i wrote in my first post!

i think the approach from ZeroZorro is on the right way!

[rednoah]

Did you install the Synology Node JS package? Or SynoCommunity one? I have bnotntested the latter.

If my Java installer doesn't work, check the log and see what it says. Then post a screenshot here.

[flasher111]

Did you install the Synology Node JS package? Or SynoCommunity one? I have bnotntested the latter.

If my Java installer doesn't work, check the log and see what it says. Then post a screenshot here.

i installed Node JS from Synology
(Version 0.12 and Version 4.2.3)

i also tried the Node JS from SynoCommunity

Java 8 is installed i tried it with the Synology beta packed and with the original installer from Oracle.
Java 8 is correctly installed and works.













same log message in filebot Node

[flasher111]

i found at the forum that you have your own Java Version 8 pkg.
https://app.filebot.net/syno/index.json

After installing your Java V8 Version i got two error Messages





the log file is really long so the screenshot is from the bottom.
I think the last line is critical

[rednoah]

Let's ignore java and focus on the node issue.

The Synology Node JS package should create the /usr/bin/node symlink. So either the install failed, or they changed something.

Log in via SSH, find the node executable, check that it works, and then create that symlink yourself.

[flasher111]

i opened you start.sh at /volume1/@appstore/filebot-node/server/start.sh with the terminal editor and changed the path in line 30

Code: Select all

/usr/local/bin/node --max_executable_size=16 --use_idle_notification "server/app.js"

because the node folder in Beta 2 is in the folder "local".

Now i got this Error in the log-file



i don't know what this means

[rednoah]

I guess DSM 6 changes lots of things. Consider FileBot Node broken on DSM 6 for now.

Fixing these issues is probably just a matter of updating the paths in server/start.sh to whatever has changed with DSM 6.

[rednoah]

Try server/start.sh with this ssl options:

Code: Select all

export FILEBOT_NODE_HTTPS_KEY="/usr/syno/etc/certificate/system/default/privkey.pem"
export FILEBOT_NODE_HTTPS_CRT="/usr/syno/etc/certificate/system/default/cert.pem"

@see https://forum.synology.com/enu/viewtopi ... 0&t=114697

[frikeando]

I am on the same boat, with DSM 6 (sorry for not to mention it in my post, I didn't see this topic).

Could you detail how to do that ssl option thing?

Thanks!

[rednoah]

1. Login as root
2. Have a look at /var/packages/filebot-node/target/server/start.sh
3. Fix the node call (replace with path to node executable, wherever it is on DSM 6)
4. Fix the filebot-node ssl config (replace key/crt paths with whatever works on DSM 6)

I don't have DSM 6 yet so I don't know the details. If you figure it out, please share.

[flasher111]

@rednoah,

thanks for your help! I tried it with the modified start.sh.
This is my start.sh

Code: Select all

#!/bin/sh

export FILEBOT_NODE_HOST="0.0.0.0" # bind to all interfaces
export FILEBOT_NODE_AUTH="SYNO"

export FILEBOT_NODE_HTTP="YES"
export FILEBOT_NODE_HTTP_PORT="5452"

export FILEBOT_NODE_HTTPS="YES"
export FILEBOT_NODE_HTTPS_PORT="5453"
export FILEBOT_NODE_HTTPS_KEY="/usr/syno/etc/certificate/system/default/privkey.pem"
export FILEBOT_NODE_HTTPS_CRT="/usr/syno/etc/certificate/system/default/cert.pem"

# set user
export USER="admin"

export FILEBOT_CMD="filebot"
export FILEBOT_CMD_CWD="$SYNOPKG_PKGDEST_VOL"
export FILEBOT_CMD_UID=`id -u $USER`
export FILEBOT_CMD_GID=`cat /etc/group | grep 'administrators' | cut -d: -f3` # cannot use `id -u $USER` because the result is 100:users but we need 101:administrators because users don't have execute permissions

export FILEBOT_NODE_CLIENT="" # serve client-side code via DSM only

# set working dir
cd "$SYNOPKG_PKGDEST"

# --max_executable_size (max size of executable memory (in Mbytes))
# (NOT YET SUPPORTED SYNO NODE.JS) --optimize_for_size (Enables optimizations which favor memory size over execution speed.)
# --use_idle_notification (Use idle notification to reduce memory footprint.)
/usr/local/bin/node --max_executable_size=16 --use_idle_notification "server/app.js"

but now i got this error Message

[rednoah]

I guess the path to the authenticate.cgi has changed as well. You could try modifying app.js to possibly fix that one.

[rednoah]

Looks like Synology has changed all the paths. I'll try to support DSM 6 once it's been officially released.

I'm happy to accept pull requests if anybody wants to make DSM 6 support happen themselves.
https://github.com/filebot/filebot-node

[flasher111]

for all who have the DSM 6 Beta 1 or Beta 2 installed Filebot Node does not work.
Some path or certificates has been changed. And the authenticate.cgi will not be supportet via Beta1 and2.
I installed DSM 6 RC1 where the authenticate.cgi is supportet. Filebot Node itself works but the gui didn't start.

[rednoah]

I've uploaded a test package that should work on DSM 6.

Please try and give me feedback:
https://sourceforge.net/projects/filebo ... ebot/HEAD/

[tudor131313]

Code: Select all

Locking /volume1/@appstore/filebot-node/filebot.log
Mar 25, 2016 12:47:14 AM net.sf.ehcache.store.disk.DiskStorageFactory <init>
WARNING: The index for data file /volume1/@appstore/filebot/data/admin/cache/0/web-datasource-lv2.data is out of date, probably due to an unclean shutdown. Deleting index file /volume1/@appstore/filebot/data/admin/cache/0/web-datasource-lv2.index
Mar 25, 2016 12:47:18 AM net.sf.ehcache.store.disk.DiskStorageFactory <init>
WARNING: The index for data file /volume1/@appstore/filebot/data/admin/cache/0/web-persistent-datasource.data is out of date, probably due to an unclean shutdown. Deleting index file /volume1/@appstore/filebot/data/admin/cache/0/web-persistent-datasource.index
Mar 25, 2016 12:47:18 AM net.sf.ehcache.store.disk.DiskStorageFactory <init>
WARNING: The index for data file /volume1/@appstore/filebot/data/admin/cache/0/web-datasource.data is out of date, probably due to an unclean shutdown. Deleting index file /volume1/@appstore/filebot/data/admin/cache/0/web-datasource.index
Mar 25, 2016 12:47:19 AM net.sf.ehcache.store.disk.DiskStorageFactory <init>
WARNING: The index for data file /volume1/@appstore/filebot/data/admin/cache/0/web-datasource-lv3.data is out of date, probably due to an unclean shutdown. Deleting index file /volume1/@appstore/filebot/data/admin/cache/0/web-datasource-lv3.index
Run script [fn:amc] at [Fri Mar 25 00:48:22 GMT+02:00 2016]

so far it works. the gui is back and i can't see any problems. i will post here if there are any problems, but as of now, filebot node is BACK

[Friends4U]

Not working here... with the test version (0.2.0)

[Friends4U]

I stil get "Sorry the page you are looking for is not found".

[rednoah]

Have you tried a different browser? (e.g. Chrome)

Have you tried clearing the browser cache and reloading the page?

Have you tried restarting your DiskStation?

Have you tried everything on this list? What exactly isn't working? Install failed? Service not started? Page not found? Authentication not working?

Have you tried accessing the filebot node frame directly?

Code: Select all

http://<IP>:5000/webman/3rdparty/filebot-node/index.html

[Friends4U]

Cool!

Direct works... perhaps it was a caching issue
I did not know of the direct link! Cool.

Thank you very much!