FileBot

Hello,

Let me create a new topic because I do not find a solution to my problem.
I used many months FileBot Node and I was very happy until an upgrade DSM to block the launch of Node Filebote .

I of course tried to uninstall then reinstall all the following applications :

FileBot 4.7.1
Node.js 0.12
Node.js v4
Oracle Java SE : 1.8.0.101
Then
FileBot Node 0.2.0
But nothing changes.
I still have an error message to the launch of Node FileBot and he gets status screeching halt.
Message: Failed to launch the repair package
When I want to view the logs , I signal that there is no data.
When I run : FileBot -script fn: sysinfo
Here is the result :
=======================================
FileBot 4.7.1 (r4126)
JNA Native: 4.0.1
MediaInfo: java.lang.UnsatisfiedLinkError: Unable to load library 'zen': Native library (linux-x86-64/libzen.so) not found in resource path ([file:/volume1/@appstore/filebot/FileBot.jar])
Apache Commons VFS: [zip, ftps, rar, ftp, 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.7
JRE: Java(TM) SE Runtime Environment 1.8.0_101 (headless)
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 4 Core / 239 MB Max Memory / 16 MB Used Memory
OS: Linux (amd64)
Package: SPK
Data: /volume1/@appstore/filebot/data/admin
uname: Linux Diskstation 3.10.77 #7393 SMP Thu Jun 2 19:50:06 CST 2016 x86_64 GNU/Linux synology_cedarview_412+
Done ヾ(＠⌒ー⌒＠)ノ
=============================================

Can you help me or at least refer me so that I can again use FileBot Node ?

Excuse my English .

A frenchie

What have you tried so far? What exactly is not working? Are there any error messages?
viewtopic.php?f=13&t=3368

Hello,

I am having the same issue as the original poster. Re-installed everything, but Filebot Node will not start up. There is no information in the package center log. I have tried all the troubleshooting steps listed on the troubleshooting post. It's been working fine until the recent upgrades. Where else could i look for logging information?

I do see this in /var/log/synopkg.log, but not very informative:

2016/08/15 22:29:48 start filebot-node: begin to start version 0.2.1
2016/08/15 22:29:48 stop filebot-node: begin to stop version 0.2.1
2016/08/15 22:29:48 stop filebot-node: stop version 0.2.1 successfully, result 0
2016/08/15 22:29:52 start filebot-node: start version 0.2.1 failed, result 1
2016/08/15 22:41:46 start filebot-node: begin to start version 0.2.1
2016/08/15 22:41:47 stop filebot-node: begin to stop version 0.2.1
2016/08/15 22:41:48 stop filebot-node: stop version 0.2.1 successfully, result 0
2016/08/15 22:41:52 start filebot-node: start version 0.2.1 failed, result 1
2016/08/15 23:24:04 start filebot-node: begin to start version 0.2.1
2016/08/15 23:24:04 stop filebot-node: begin to stop version 0.2.1
2016/08/15 23:24:04 stop filebot-node: stop version 0.2.1 successfully, result 0
2016/08/15 23:24:07 start filebot-node: start version 0.2.1 failed, result 1

thx

You can try to do initctl start filebot-node via SSH and see what happens (more info on other threads).

******************************************************
root@Diskstation:/usr/local/filebot-node# initctl start filebot-node
filebot-node start/running, process 10504
root@Diskstation:/usr/local/filebot-node# initctl start filebot-node
initctl: Job is already running: filebot-node

******************************************************

root@Diskstation:/usr/local/filebot-node# curl -I http://192.168.1.3:5000/webman/3rdparty ... index.html
HTTP/1.1 404 Not Found
Server: nginx
Date: Tue, 16 Aug 2016 10:48:04 GMT
Content-Type: text/html
Content-Length: 11939
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding
ETag: "57502b45-2ea3"

****************************************************

The directory fileboot-node does'nt exist in /usr/syno/synoman/webman/3rdparty/

I create the directory but now :

drwxr-xr-x 2 root root 4096 Aug 16 12:29 filebot-node


root@Diskstation:/usr/local/filebot-node# ls -l /usr/syno/synoman/webman/3rdparty/fileboot-node
ls: cannot access /usr/syno/synoman/webman/3rdparty/fileboot-node: No such file or directory

**************************************************

a manual installation does not work

???????????????????

So FileBot Node Service is running then.

Have you tried this?

FileBot Node Troubleshooting wrote:Check if the FileBot Node Service is accessible by throwing a request at it:

e.g. HTTP

Code: Select all

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

e.g. HTTPS

Code: Select all

curl -v https://<HOST>:5453/auth

Look at this post, and see what's different on your machine:
viewtopic.php?f=13&t=3555&start=50#p21529

root@Diskstation:/usr/local/filebot-node# curl -v http://192.168.1.3:5452/auth
> GET /auth HTTP/1.1
> Host: 192.168.1.3:5452
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/json
< Access-Control-Allow-Origin: *
< Date: Tue, 16 Aug 2016 15:27:41 GMT
< Connection: keep-alive
< Content-Length: 51
<
{"success":true,"data":{"auth":"SYNO","user":null}}root@Diskstation:/usr/local/filebot-node# curl -v https://192.168.1.3:5453/auth
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: unable to get local issuer certificate
* TLSv1.2 (OUT), TLS alert, Client hello (1):
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.

=================================

root@Diskstation:/usr/local/filebot-node# ls -l /usr/syno/synoman/webman/3rdparty/
total 8
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 34 Aug 16 11:46 AntiVirus -> /var/packages/AntiVirus/target/app
lrwxrwxrwx 1 root root 37 Aug 16 11:46 AudioStation -> /var/packages/AudioStation/target/app
lrwxrwxrwx 1 root root 39 Aug 16 11:46 DownloadStation -> /var/packages/DownloadStation/target/ui
drwxr-xr-x 2 root root 4096 Aug 16 12:29 filebot-node
lrwxrwxrwx 1 root root 35 Aug 16 11:46 HyperBackup -> /var/packages/HyperBackup/target/ui
ect...

=================================

root@Diskstation:/usr/local/filebot-node# cat /etc/init/filebot-node.conf
description "FileBot Node Server"
chdir /usr/local/filebot-node
exec /usr/local/filebot-node/start
console log

=================================

root@Diskstation:/usr/local/filebot-node# curl -I http://localhost:5000/webman/3rdparty/f ... index.html
HTTP/1.1 404 Not Found
Server: nginx
Date: Tue, 16 Aug 2016 15:35:00 GMT
Content-Type: text/html
Content-Length: 11939
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding
ETag: "57502b45-2ea3"


===================================

root@Diskstation:/usr/local/filebot-node# ls -l /var/packages/filebot-node
total 28
drwxr-xr-x 2 root root 4096 Aug 16 12:52 conf
lrwxrwxrwx 1 root root 35 Aug 16 12:52 etc -> /usr/syno/etc/packages/filebot-node
-rw-r--r-- 1 root root 19166 Aug 16 12:52 INFO
drwxr-xr-x 2 root root 4096 Aug 16 12:52 scripts
lrwxrwxrwx 1 root root 31 Aug 16 12:52 target -> /volume1/@appstore/filebot-node

1.
FileBot Node Service is running and working fine.

2.
Synology DSM screwed up and didn't link the filebot-node client folder into it's webman/3rdparty folder.

It should look like this: Try to create that symlink manually and see if that works.

I do not know how to do a symlink, Sorry !

can you help me ?

Thank you.

Help yourself. Use Google.

1st Result:
http://www.cyberciti.biz/faq/unix-creat ... n-command/

So trying initctl as root produces this output: filebot-node start/running, process 30119 (It wouldn't work when ran as admin)

which seems to indicate it started. However, executing curl -v http://192.168.0.101:5452/auth from the command line on my Mac does not produce the same output listed in the troubleshooting post. it lists out:
Also, in DSM the FileBot Node icon is not available, so I guess the service still has not started.

This log shows that the filebot is running fine and responding to requests. DSM failed doing whatever DSM does when installing packages.

If you symlink the filebot-node client folder into the DSM webman/3rdparty folder you should be able to access is directly even if DSM doesn't show it in it's UI.

Hi,

So the package manager didn't put the sym link in /usr/syno/synoman/webman/3rdparty. After fixing that, I can see Filbert Node in the DSM UI, but it won't do anything. After setting parameters and hitting the dry run button, nothing happens. Same thing if accessed directly thru the url. The package manager tho still shows it as stopped, and if you try and start it thru the package manager, it deletes the sym link I created, which is very strange IMO. Is the package itself misconfigured?

At the moment I have no way to edit the Filebot task that is scheduled. I recently had to change the volumes on this machine, and so the task is pointing to the wrong volumes now. I can see the command in the task scheduler, but where the task directions are stored at I have no idea. Can you shed some light on that, so that I can get this working partially?

thx

DSM is supposed to create those symlinks, so it's not surprising that it's doing something, like removing previous symlinks. I have no idea why it's not working. It's a Synology DSM issue. Maybe you'll find a solution in the Synology forums.

You can modify the arguments in the *.args files here:

Got it working! I followed what someone else in another thread stated worked for them... uninstall:

"FileBot
FileBot Node
Node.js v4
Oracle Java SE

Once done, you can reinstall starting with Java, then Node, FileBot and finally FileBot Node manual installation for the latter."

I think originally I let Filebot install it's dependecies on it's own, after uninstalling it and trying to get it to work initially. Apparently something is not right with that.

However, something broke it in the last month to begin with, as it worked fine before. Either it was a recent DSM upgrade or just the Filebot packages themselves upgrading. Anyways, this is a reliable method it seems.