FileBot Node 0.2.0 for DSM 6

[Tbright]

Yeah, same here
I tried uninstalling, rebooting and reinstalling all the packages in my DS215j but I am getting the "Failed to run package" error, the log is empty
TB

[tonis]

And now I just uninstalled FileBot and FileBotNode again and re-installed both from Package Center and it works again.

[Tbright]

Lucky you!!
I have just tried uninstaling/rebooting/installing again to no avail (I think I have rebooted my DS more times in the last couple of days than in the whole last year.
TB

[fildy]

Hi,

I have problem with this:

Failed to read video properties: Unable to load amd64 native library libmediainfo.so: Could not initialize class net.filebot.mediainfo.MediaInfoLibrary
I use synology ds412+ with intel processor.

is the anything that I can do to fix it?

[rednoah]

Did you install MediaInfo?

[rednoah]

Nope. But you could ask in the Synology forums, check all the logs, try everything explained here in the troubleshooting help.

Without any new information, I won't have any new ideas.


Check List:
* Does DSM install (i.e. unpack) the package? If not, what does the syslog say?
* Does DSM run the start-stop script? Is the package started? If not, what does the syslog say?
* Do FileBot Node Troubleshooting to troubleshoot potential network issues

[gnitram]

I have the same problem that coenboomkamp.

- removed all versions of Java, node and FileBot
- rebooted
- Installed Java Se 1.8.0_77 via your unofficial installer
- Installed Node.js v4
- Installed FileBot 4.7
- Installed filebot-node-0.2.0-noarch.spk (manually, i could not find FileBot Node 0.2.0-B1 anymore)
- Check the open TCP Ports 5452 and 5453 on my Router and Syno firewall
- Rebooted

And it still gives the well known "cannot open package"

The log from filebot node is empty.

The syslog say:

Code: Select all

2016/05/25 09:10:43     install filebot-node 0.2.0 successfully
2016/05/25 09:10:49     install filebot-node: begin to start version 0.2.0
2016/05/25 09:10:49     stop filebot-node: begin to stop version 0.2.0
2016/05/25 09:10:50     stop filebot-node: stop version 0.2.0 successfully, result 0
2016/05/25 09:10:54     install filebot-node: start version 0.2.0 failed, result 272

Checked /usr/syno/synoman/webman/3rdparty/ but also no filebot folder

The start-stop script say:

Code: Select all

admin@S:/usr/syno/synoman/webman/3rdparty$ cat /var/packages/filebot-node/scripts/start-stop-status
#!/bin/sh

case "$1" in
        start)
                initctl start "$SYNOPKG_PKGNAME"
                exit 0
        ;;

        stop)
                initctl stop "$SYNOPKG_PKGNAME"
                exit 0
        ;;

        status)
                initctl status "$SYNOPKG_PKGNAME" | grep "running"
                exit $?
        ;;

        log)
                echo "$SYNOPKG_PKGDEST/node.log"
                exit 0
        ;;

        *)
                exit 0
        ;;
esac

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

Code: Select all

Page not found

And finally curl -v http://<IP>:5452/auth:

Code: Select all

root@S:/# curl -v http://192.168.0.3:5452/auth
* Failed to connect to 192.168.0.3 port 5452: Connection refused
curl: (7) Failed to connect to 192.168.0.3 port 5452: Connection refused

But ports are open in my router and firewall Synology.

Any idea?

Thanks in advance for your help.

[rednoah]

What's the console output if you manually try to start the node instance?

[gnitram]

This:

Code: Select all

root@S:/usr/local/filebot-node# ./start
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: '/usr/local/filebot-node',
  LC_ALL: 'en_US.utf8',
  JAVA_OPTS: '-Xmx489m',
  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: '/usr/local/filebot-node',
  JAVA_HOME: '/usr/local/java',
  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

[rednoah]

Running manually seems to work. At that point it's definitely running, and the curl /auth test should definitely work (unless there's network issues).


This is how DSM is starting the service. Try and see if you get different results:

Code: Select all

initctl start filebot-node

[gnitram]

Perhaps the problem is with the user, look at the difference between admin and root:

Code: Select all

root@S:~# initctl start filebot-node
filebot-node start/running, process 17245
root@S:~# initctl start filebot-node
initctl: Job is already running: filebot-node

Code: Select all

admin@S:~$ initctl start filebot-node
initctl: Rejected send message, 1 matched rules; type="method_call", sender=":1.29" (uid=1024 pid=18455 comm="initctl start filebot-node ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init ")

Is possible that the Package Centre starts Filebot Node like admin?

The curl/auth doesn´t work.

Firewall off in DSM and opens ports in my router:

[rednoah]

Yeah. It's only supposed to work as root, and AFAIK the package center service is calling the start stop script as root. At this point I have no idea.

DSM fails to start the package for no reason and even if you run it manually it seems you can't connect. I'm out of ideas. Maybe you'll find more help in the Synology forums.

[gnitram]

I foud this:

You might also want to check your /etc/passwd/ and /etc/group/ as stated for those issues where the package sets up incorrectly.
The problem was that /etc/passwd/ was modified and the shell for the app-accounts for the custom services was modified to /sbin/nologin which causes the error. Switching back to /bin/sh solved my issues.

My passwd file doesn´t have something like "FilebotNode", and yours does?

Code: Select all

CloudStation:x:237243:237243::/var/packages/CloudStation/target:/sbin/nologin
CloudSync:x:177120:177120::/var/packages/CloudSync/target:/sbin/nologin

Code: Select all

root@S:/var/packages/filebot-node# ls
conf  etc  INFO  scripts  target

[rednoah]

FileBot Node service can only run as root because everything in /var/packages is owned by root. FileBot Node will run filebot commands as admin though.

Did you check Enable user home service in the User settings? Not sure if it makes a difference, but it's worth a try.

[gnitram]

user home service was already enabled.

Do you have a line like "FilebotNode11111:/var/packages/filebot-node/target:/sbin/nologin" in your /etc/passwd/?

Thx

[rednoah]

Nope. The FileBot Node install scripts are definitely not creating any users, nor do any of the start scripts try to run as such a user...

Code: Select all

$ cat /etc/passwd | grep -i "filebot" -c
0

Maybe Synology DSM is doing some magic behind the scenes on selected NAS devices? IDK.

[gnitram]

Do you have "Filebot-node" folder in /usr/syno/synoman/webman/3rdparty/ ?

I repeat the process logging like "admin" in mi local network, but doesn't work.

I don't have more ideas.

Thx.
Probably Filebot-node doesn't work in DS415play.

[rednoah]

Yep. That symlink would be absolutely necessary.

Otherwise the IFRAME can't work:

Code: Select all

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

Synology DSM should link the webapp files into that folder when the package is started. It only makes sense that if it somehow fails to run the start script it won't create that symlink.

I have no clue what the underlying issue could be. It definitely doesn't have anything to do with filebot or the device per se (node starts just fine as per previous post when started manually) and more with whatever DSM is doing.

Please repost about this issue in the Synology forums and see if anybody has any ideas how to narrow down on this issue.

[rednoah]

Maybe this helps someone, to compare with their own.

passwd

Code: Select all

cat /etc/passwd

Code: Select all

admin:x:1024:100:System default user:/var/services/homes/admin:/bin/sh
anonymous:x:21:21:Anonymous FTP User:/nonexist:/sbin/nologin
avahi:x:84:84:Avahi mDNS daemon:/noexist:/bin/false
bind:x:53:53::/:/usr/bin/nologin
daemon:x:2:2::/:/bin/sh
dbus:x:81:81::/:/usr/bin/nologin
dovecot:x:143:143:Dovecot User:/nonexist:/sbin/nologin
DownloadStation:x:125560:125560::/var/packages/DownloadStation/target:/sbin/nologin
ftp:x:21:21:Anonymous FTP User:/nonexist:/sbin/nologin
guest:x:1025:100:Guest:/var/services/homes/guest:/sbin/nologin
http:x:1023:1023:http:/var/services/web:/bin/false
HyperBackup:x:256822:256822::/var/packages/HyperBackup/target:/sbin/nologin
ldap:x:439:439::/var/lib/openldap:/usr/bin/nologin
lp:x:7:7::/var/spool/lpd:/bin/sh
lp_1458835912:x:4:7:lp:/var/spool/lpd:/sbin/nologin
mysql:x:66:66:MariaDB User:/var/services/mysql:/bin/false
nobody:x:99:99:nobody:/:/bin/false
NoteStation:x:188070:188070::/var/packages/NoteStation/target:/sbin/nologin
ntp:x:87:87:Network Time Protocol:/var/lib/ntp:/sbin/nologin
PDFViewer:x:273924:273924::/var/packages/PDFViewer/target:/sbin/nologin
postfix:x:125:125:Postfix User:/nonexist:/sbin/nologin
postgres:x:55:55:PostgreSQL User:/var/services/pgsql:/bin/sh
reinhard:x:1026:100:SMB Default User:/var/services/homes/reinhard:/sbin/nologin
root:x:0:0:root:/root:/bin/ash
rpc:x:32:32::/dev/null:/bin/false
smmsp:x:25:25:Sendmail Submission User:/var/spool/clientmqueue:/sbin/nologin
spamfilter:x:783:99:Spamassassin User:/var/spool/postfix:/sbin/nologin
SpreadSheet:x:223188:223188::/var/packages/Spreadsheet/target:/sbin/nologin
StorageAnalyzer:x:276949:276949::/var/packages/StorageAnalyzer/target:/sbin/nologin
system:x:1:1::/usr/syno/synoman:/usr/bin/nologin

webman/3rdparty

Code: Select all

ls -l /usr/syno/synoman/webman/3rdparty/

Code: Select all

lrwxrwxrwx 1 root root   36 Nov  8  2014 addon-aws_s3 -> /usr/syno/synobackup/addon/aws_s3/ui
lrwxrwxrwx 1 root root   40 Nov  8  2014 addon-azure_blob -> /usr/syno/synobackup/addon/azure_blob/ui
lrwxrwxrwx 1 root root   40 Nov  8  2014 addon-hicloud_s3 -> /usr/syno/synobackup/addon/hicloud_s3/ui
lrwxrwxrwx 1 root root   36 Nov  8  2014 addon-sfr_s3 -> /usr/syno/synobackup/addon/sfr_s3/ui
lrwxrwxrwx 1 root root   40 May 31 02:31 filebot-node -> /var/packages/filebot-node/target/client
lrwxrwxrwx 1 root root   37 May 31 02:31 GlacierBackup -> /var/packages/GlacierBackup/target/ui
-rw-r--r-- 1 root root 3901 Mar  7  2014 README

upstart/initctl config

Code: Select all

cat /etc/init/filebot-node.conf

Code: Select all

description "FileBot Node Server"
chdir /usr/local/filebot-node
exec /usr/local/filebot-node/start > /usr/local/filebot-node/node.log 2>&1

Check IFRAME

Code: Select all

curl -I http://localhost:5000/webman/3rdparty/filebot-node/index.html

Code: Select all

HTTP/1.1 200 OK
Server: nginx
Date: Tue, 31 May 2016 14:40:50 GMT
Content-Type: text/html
Content-Length: 26542
Last-Modified: Mon, 02 May 2016 11:05:05 GMT
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding
ETag: "57273461-67ae"
Accept-Ranges: bytes

Check node service

Code: Select all

curl -I http://localhost:5452/auth

Code: Select all

HTTP/1.1 200 OK
Content-Type: text/json
Access-Control-Allow-Origin: *
Date: Tue, 31 May 2016 14:40:40 GMT
Connection: keep-alive

Maybe using upstart logging will give more output?
https://github.com/filebot/filebot-node ... 9a2336f211

[rednoah]

Code: Select all

ls -l /var/packages/filebot-node

Code: Select all

drwxr-xr-x 2 root root  4096 May 31 02:31 conf
-rw-r--r-- 1 root root     0 May 26 19:36 enabled
lrwxrwxrwx 1 root root    35 May 26 19:36 etc -> /usr/syno/etc/packages/filebot-node
-rw-r--r-- 1 root root 19166 May 26 19:36 INFO
drwxr-xr-x 2 root root  4096 May 26 19:36 scripts
lrwxrwxrwx 1 root root    31 May 26 19:36 target -> /volume1/@appstore/filebot-node

If /var/packages/filebot-node doesn't exist, then Synology didn't even install/unpack the package. Even less I can do about that!

[rednoah]

Well, if you want to edit the upstart config you'll have to edit /etc/init/filebot-node.conf (not sure if that's a copy or a symlink).

You could for example change the exec command to something really simple (e.g. date), and see if initctl allows you to "start" that.

[hannnes]

Hi all, I'm new to this forum - writing - not reading

In addition I've to say, every step I found here was a challenge to me, because I'm a Terminal-Beginner…

my issue is, that also like some others here - I followed many routes precisely ... still getting the "Failed to run the Package Service" when attempting to run FileBot Node

rednoah, would you be so kind to tell me, what to do?
much, much thanks!!!

DS214play
DSM 6.0.1-7393

- Oracle Java Se 1.8.0_91 (via your installer, only version of Java installed)
- Node.js v4 4.2.6-0158 (only version of Node.js installed)
- FileBot 4.7
- FileBot Node 0.2.0 (last days manually, today via install-button package-center/Paket-Zentrum)

1.
Does /usr/syno/etc/certificate/system/default/privkey.pem exist at all?
YES

Code: Select all

find /usr/syno/etc/certificate/system/default/ -type f
/usr/syno/etc/certificate/system/default/cert.pem
/usr/syno/etc/certificate/system/default/privkey.pem
/usr/syno/etc/certificate/system/default/fullchain.pem
/usr/syno/etc/certificate/system/default/syno-ca-cert.pem

2.
./start

Code: Select all

root@VillaBiBa_DS:/usr/local/filebot-node# ./start
ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  FILEBOT_NODE_HTTPS_KEY: '/usr/syno/etc/certificate/system/default/privkey.pem',
  TERM: 'xterm-256color',
  SHELL: '/bin/ash',
  FILEBOT_CMD_UID: '1024',
  OLDPWD: '/usr/local/filebot-node',
  LC_ALL: 'en_US.utf8',
  JAVA_OPTS: '-Xmx489m',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  SUDO_USER: 'VillaChef',
  SUDO_UID: '1026',
  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: '/usr/local/filebot-node',
  JAVA_HOME: '/usr/local/java',
  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
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE 0.0.0.0:5452
    at Object.exports._errnoException (util.js:870:11)
    at exports._exceptionWithHostPort (util.js:893:20)
    at Server._listen2 (net.js:1237:14)
    at listen (net.js:1273:10)
    at net.js:1382:9
    at nextTickCallbackWith3Args (node.js:452:9)
    at process._tickCallback (node.js:358:17)
    at Function.Module.runMain (module.js:444:11)
    at startup (node.js:136:18)
    at node.js:966:3

3.
because filebot-node didn't exist in "/usr/syno/synoman/webman/3rdparty" I dit create it via

Code: Select all

mkdir /usr/syno/synoman/webman/3rdparty/filebot-node

but the result is, that in my macs Terminal all words are green, except "filebot-node", which is blue!!

root@VillaBiBa_DS:/usr/syno/synoman/webman/3rdparty# ls
addon-aws_s3 AntiVirus DownloadStation MariaDB README VPNCenter
addon-azure_blob AudioStation filebot-node PhotoStation StorageAnalyzer WebStation
addon-hicloud_s3 CardDAVServer HyperBackup phpMyAdmin TimeBackup
addon-sfr_s3 CloudStation HyperBackupVault plexconnect VideoStation

4.

Code: Select all

root@VillaBiBa_DS:~# cat /var/packages/filebot-node/scripts/start-stop-status
#!/bin/sh

case "$1" in
	start)
		initctl start "$SYNOPKG_PKGNAME"
		exit 0
	;;

	stop)
		initctl stop "$SYNOPKG_PKGNAME"
		exit 0
	;;

	status)
		initctl status "$SYNOPKG_PKGNAME" | grep "running"
		exit $?
	;;

	log)
		echo "$SYNOPKG_PKGDEST/node.log"
		exit 0
	;;

	*)
		exit 0
	;;
esac

5.

Code: Select all

root@VillaBiBa_DS:~# curl -v http://192.168.1.5:5452/auth
> GET /auth HTTP/1.1
> Host: 192.168.1.5:5452
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Content-Type: text/json
< Access-Control-Allow-Origin: *
< Date: Fri, 10 Jun 2016 21:22:45 GMT
< Connection: keep-alive
< Content-Length: 51
< 
{"success":true,"data":{"auth":"SYNO","user":null}}root@VillaBiBa_DS:~# 

6.

Code: Select all

root@VillaBiBa_DS:~# curl -v http://192.168.1.5:5453/auth
> GET /auth HTTP/1.1
> Host: 192.168.1.5:5453
> User-Agent: curl/7.47.0
> Accept: */*
> 
* Empty reply from server
curl: (52) Empty reply from server

7.
both ports 5452 and 5453 are open (router AND syno-firewall)

8.

Code: Select all

root@VillaBiBa_DS:~# filebot -script fn:sysinfo
FileBot 4.7 (r3923)
JNA Native: 4.0.1
MediaInfo: java.lang.UnsatisfiedLinkError: Unable to load library 'zen': Native library (linux-x86/libzen.so) not found in resource path ([file:/volume1/@appstore/filebot/FileBot.jar])
Apache Commons VFS: [zip, ftps, rar, ftp, tar, tgz, tbz2, sftp]
Chromaprint: java.io.IOException: Cannot run program "/usr/local/chromaprint/bin/fpcalc": error=2, No such file or directory
Extended Attributes: OK
Groovy Engine: 2.4.6
JRE: Java(TM) SE Runtime Environment 1.8.0_91 (headless)
JVM: 32-bit Java HotSpot(TM) Client VM
CPU/MEM: 4 Core / 170 MB Max Memory / 10 MB Used Memory
OS: Linux (i386)
Package: SPK
Data: /volume1/@appstore/filebot/data/root
uname: Linux VillaBiBa_DS 3.2.40 #7393 SMP PREEMPT Thu Jun 2 19:47:23 CST 2016 i686 GNU/Linux synology_evansport_214play
Done ヾ(＠⌒ー⌒＠)

9.

Code: Select all

root@VillaBiBa_DS:~# initctl start filebot-node
initctl: Job is already running: filebot-node

10.

Code: Select all

root@VillaBiBa_DS:/var/packages/filebot-node# ls
conf  etc  INFO  scripts  target

11.
Did you check Enable user home service in the User settings?
Yes - its enabled

12.

Code: Select all

http://192.168.1.5:5000/webman/3rdparty/filebot-node/index.html

delivers:

Es tut uns Leid, die von Ihnen gesuchte Seite konnte nicht gefunden werden.

© 2016 Synology Inc.

what means sorry, site not found…

13.
how can I fix THIS?:
Again filebot node (blue) and README (black) are in other colors...

Code: Select all

root@VillaBiBa_DS:~# ls -l /usr/syno/synoman/webman/3rdparty/
total 8
lrwxrwxrwx 1 root root   36 Feb 17  2015 addon-aws_s3 -> /usr/syno/synobackup/addon/aws_s3/ui
lrwxrwxrwx 1 root root   40 Feb 17  2015 addon-azure_blob -> /usr/syno/synobackup/addon/azure_blob/ui
lrwxrwxrwx 1 root root   40 Feb 17  2015 addon-hicloud_s3 -> /usr/syno/synobackup/addon/hicloud_s3/ui
lrwxrwxrwx 1 root root   36 Feb 17  2015 addon-sfr_s3 -> /usr/syno/synobackup/addon/sfr_s3/ui
lrwxrwxrwx 1 root root   34 Jun 10 22:24 AntiVirus -> /var/packages/AntiVirus/target/app
lrwxrwxrwx 1 root root   37 Jun 10 22:24 AudioStation -> /var/packages/AudioStation/target/app
lrwxrwxrwx 1 root root   38 Jun 10 22:24 CardDAVServer -> /var/packages/CardDAVServer/target/app
lrwxrwxrwx 1 root root   37 Jun 10 22:24 CloudStation -> /var/packages/CloudStation/target/app
lrwxrwxrwx 1 root root   39 Jun 10 22:24 DownloadStation -> /var/packages/DownloadStation/target/ui
drwxr-xr-x 2 root root 4096 Jun 10 22:16 filebot-node
lrwxrwxrwx 1 root root   35 Jun 10 22:24 HyperBackup -> /var/packages/HyperBackup/target/ui
lrwxrwxrwx 1 root root   40 Jun 10 22:24 HyperBackupVault -> /var/packages/HyperBackupVault/target/ui
lrwxrwxrwx 1 root root   31 Jun 10 22:24 MariaDB -> /var/packages/MariaDB/target/ui
lrwxrwxrwx 1 root root   36 Jun 10 22:24 PhotoStation -> /var/packages/PhotoStation/target/ui
lrwxrwxrwx 1 root root   34 Jun 10 22:24 phpMyAdmin -> /var/packages/phpMyAdmin/target/ui
lrwxrwxrwx 1 root root   36 Jun 10 22:24 plexconnect -> /var/packages/plexconnect/target/app
-rw-r--r-- 1 root root 3901 Jan  7  2015 README
lrwxrwxrwx 1 root root   39 Jun 10 22:24 StorageAnalyzer -> /var/packages/StorageAnalyzer/target/ui
lrwxrwxrwx 1 root root   34 Jun 10 22:24 TimeBackup -> /var/packages/TimeBackup/target/UI
lrwxrwxrwx 1 root root   36 Jun 10 22:24 VideoStation -> /var/packages/VideoStation/target/ui
lrwxrwxrwx 1 root root   34 Jun 10 22:24 VPNCenter -> /var/packages/VPNCenter/target/app
lrwxrwxrwx 1 root root   34 Jun 10 22:24 WebStation -> /var/packages/WebStation/target/ui

14.

Code: Select all

root@VillaBiBa_DS:~# cat /etc/init/filebot-node.conf
description "FileBot Node Server"

chdir /usr/local/filebot-node

exec /usr/local/filebot-node/start > /usr/local/filebot-node/node.log 2>&1

15.

Code: Select all

root@VillaBiBa_DS:~# curl -I http://localhost:5000/webman/3rdparty/filebot-node/index.html
HTTP/1.1 404 Not Found
Server: nginx
Date: Fri, 10 Jun 2016 21:42:51 GMT
Content-Type: text/html
Content-Length: 11939
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding
ETag: "57502aa1-2ea3"

16.

Code: Select all

root@VillaBiBa_DS:~# curl -I http://localhost:5452/auth
HTTP/1.1 200 OK
Content-Type: text/json
Access-Control-Allow-Origin: *
Date: Fri, 10 Jun 2016 21:43:26 GMT
Connection: keep-alive

17.

Code: Select all

root@VillaBiBa_DS:~# ls -l /var/packages/filebot-node
total 28
drwxr-xr-x 2 root root  4096 Jun 10 22:37 conf
lrwxrwxrwx 1 root root    35 Jun 10 22:37 etc -> /usr/syno/etc/packages/filebot-node
-rw-r--r-- 1 root root 19166 Jun 10 22:37 INFO
drwxr-xr-x 2 root root  4096 Jun 10 22:37 scripts
lrwxrwxrwx 1 root root    31 Jun 10 22:37 target -> /volume1/@appstore/filebot-node

18.
fine


ok, that was a lot - I hope you can see, where my issue is
much thanks!!!!
yours Hannnes

[rednoah]

It looks like filebot and node are working just fine. DSM just fails to create the webman/3rdparty symlink. You can try creating that symlink yourself (filebot-node -> /var/packages/filebot-node/target/client).

[raymondub]

Hi,

I also still can't get it to work.

Also tried the following:

- removed all versions of Java, node and FileBot
- rebooted
- Installed Java Se 1.8.0_77 via your unofficial installer
- Installed Node.js v4
- Installed FileBot 4.7
- Installed filebot-node-0.2.0-noarch.spk (manually, i could not find FileBot Node 0.2.0-B1 anymore)
- Opened TCP Ports 5452 and 5453 on my Router (manually)
- Rebooted

And it still gives the well known "cannot open package"

The log from filebot node is empty.

What is your unofficial version ? On my Nas i m using Jdownloader and for that i had to install Java 8 & jdk-8u91-linux-arm32-vfp-hflt.tar.gz but it s not working...
Can i put your unofficial java installer PLUS that package ?
I have a Nas Syno DS216j and DSM 6

thx

[rednoah]

You can look into various things, and see if there's any notable differences:
viewtopic.php?f=13&t=3555&start=50#p21529