FileBot

Posted: **17 May 2016, 13:34**

rednoah wrote:Once again, visually describing how Package Center looks like is wholly unhelpful.

Logs, as repeatedly stated, may put some light on these issues:
Code: Select all
cat /var/log/synopkg.log

I think many just hope it's like a windows application ( plug and play) or don't reply back

Posted: **17 May 2016, 13:52**

ward0 wrote:
rednoah wrote:Once again, visually describing how Package Center looks like is wholly unhelpful.

Logs, as repeatedly stated, may put some light on these issues:
Code: Select all
cat /var/log/synopkg.log
I think many just hope it's like a windows application ( plug and play) or don't reply back

No, I'm here...just in work and not able to check any of this out. I need to learn about SSH. I have some tux experience. I'll try and get that log to you.

Thanks.

Posted: **17 May 2016, 20:28**

Thanks for your help anyway...I'm giving up and using Bliss instead. It does what I need straight from the box. Thanks.

Posted: **18 May 2016, 10:12**

tedrogers61 wrote:Thanks for your help anyway...I'm giving up and using Bliss instead. It does what I need straight from the box. Thanks.

I don't see how can you compare a music library tool and a sub title tool ...

http://www.blisshq.com/music-library-ma ... e-updated/

Posted: **22 Jun 2016, 10:31**

rednoah wrote:Once again, visually describing how Package Center looks like is wholly unhelpful.

Logs, as repeatedly stated, may put some light on these issues:
Code: Select all
cat /var/log/synopkg.log

Hi again @rednoah,

I've come back to this after some time away learning about my Syno DSM6 and using SSH etc. I've been able to get programs like Transmission and Deluge fully working and accessible on LAN and WAN; just to offer you an idea of how my abilities have developed.

Basically, I'm a lot more confident now, so I decided to give FB-node another try (hopeful that my new confidence would enable me to get it working), but I still hit up against the same problem, in that Filebot-Node 0.2.0 won't start.

Everything else (your Unofficial Java Installer, Node.js v4, MediaInfo, Chromaprint and Filebot 4.7) all install and run without issue.

To keep things simple I've done all my testing on my LAN. It is my understanding from reading that I shouldn't need any router / firewall ports forwarded / open from my Syno NAS on LAN. Outbound TCP connections from 5452 and 5453 (so that FB-node can communicate outside the network) should happen regardless of ports being open and firewall.

I've tried installing manually (download from your repo) for Filebot 4.7 and Filebot-Node 0.2.0, but I end with the same result.

I've tried to start FB-node manually via SSH by running as root and / or admin:

Code: Select all

./var/packages/filebot-node/scripts/start-stop-status start

...but every time, via either admin or root SSH, I get the error:

Code: Select all

initctl: Name may not be empty string

..
..
..
..

> > > > > MOMENT OF UTTER SHOCK ENSUES < < < < <

....WAIT! As I have been writing this...I decided to install it all again in a different order....AND IT WORKS!!!! This is inexplicable!

All I did differently was this:

1. Install Chromaprint and Media Info.
2. Click to install Filebot-Node (and allow the automatic installer to install all other components).

This is so strange that this should work now. I was really starting to doubt myself. I didn't even need to reboot the Syno. I'm also not logged in as built-in 'admin' user (in fact 'admin' user is disabled), although I am logged in as a different username with full-admin privs.

I've also been able to confirm that on my system (DS215j - DSM 6.0.1-7393 Update 1), if I remove everything related to FileBot, and install it again in the following order, then it breaks and Filebot-Node won't start (no matter if I reboot, install manually, or try to invoke via SSH start-stop-status):

1. Install Chromaprint and Media Info.
2. Install FileBot (and allow it to install Java and Node.js)
3. Install Filebot-Node.

...If I follow the above order, then Filebot-Node won't start, and frustration ensues.

Anyway, I'm glad I've been able to get it working (now to finally have a play), but it might be worth looking into why it installs perfectly one way, and not the other.

Thanks.

Posted: **22 Jun 2016, 12:05**

1.

1. Install Chromaprint and Media Info.
2. Install FileBot (and allow it to install Java and Node.js)
3. Install Filebot-Node.

I've tried this on my DS213J and I can't reproduce any issues. Works right out of the box.

2.

Code: Select all

./var/packages/filebot-node/scripts/start-stop-status start

You can't just call it like this. You'll have to set certain environment variables to call it as if DSM was calling it:

Code: Select all

export SYNOPKG_PKGNAME="filebot-node"

Posted: **22 Jun 2016, 14:00**

rednoah wrote:1.
1. Install Chromaprint and Media Info.
2. Install FileBot (and allow it to install Java and Node.js)
3. Install Filebot-Node.
I've tried this on my DS213J and I can't reproduce any issues. Works right out of the box.

2.
Code: Select all
./var/packages/filebot-node/scripts/start-stop-status start
You can't just call it like this. You'll have to set certain environment variables to call it as if DSM was calling it:
Code: Select all
export SYNOPKG_PKGNAME="filebot-node"

Re: 1...I can't explain it either...doesn't work one way, but works if I let filebot-node install everything for me.

Re: 2...thanks, this will come in useful should I need to start / stop manually. Is that the full command for both start and stop toggle?

Posted: **10 Jul 2016, 14:50**

Some update,

Now it installs flawless in a DS1515+, but failed to run on a DS215j

TB

Posted: **10 Jul 2016, 17:11**

I found if you install chroma etc, and then install filebot node and allow it to automatically install everything else, inc. filebot, then it works perfectly on ds215j. Any other order of installing, and filebot node fails to run. Don't know why. Permissions? Working directory creation? No idea, but the above method works fine for me, and I've been tearing my hair out on this one.

Posted: **18 Jul 2016, 07:11**

Hi,

For what it is worth, I am also having the same issue with a ds215j.

I'll read thought this post and collect the logs requested by the admin. I'll try the advice the last post first as a work around.

Posted: **18 Jul 2016, 07:58**

gary1001 wrote:Hi,

For what it is worth, I am also having the same issue with a ds215j.

I'll read thought this post and collect the logs requested by the admin. I'll try the advice the last post first as a work around.

I'd be very interested if my method of installation works for you on DS215J. I spent a disproportionately high amount of time trying to work this out, so I'd be very happy if it benefitted others too.

Posted: **18 Jul 2016, 09:16**

This really puzzle me. As stated before, I own a DS1515+ and a DS215j.

In the DS1515+ after one of the latest updates (do not really know which one) the installation worked nicely just installing filebot node and let the installer do all the work.

On the DS215j I tried every possible combination of rebooting and installation order but the file bot node package simply refuses to start. I basically gave up because I thought the problem was model related but since you got it working on a 215j I will give it another try and see if I can make it work.

Regards
TB

Posted: **18 Jul 2016, 09:34**

Here is the log.

https://drive.google.com/folderview?id= ... sp=sharing

Posted: **18 Jul 2016, 09:50**

The install order did not make a difference for me.

Posted: **18 Jul 2016, 10:30**

No, I just tried the following on a DS215j and DSM 6.0.1-7393 Update 1

1) Basically uninstall everything
2) Reboot
3) Install Chromaprint
4) Install MediaInfo
5) Install Filebot node

and I still get the "Failed to run..." message

Posted: **18 Jul 2016, 11:03**

gary1001 wrote:The install order did not make a difference for me.

That is very odd, because the install order is very repeatable on my system. I can break it with wrong install order, or make it work with the install order I've settled on.

Posted: **19 Jul 2016, 05:14**

I've ended up using a scheduled task to run a simple command

Code: Select all

filebot -script fn:amc --output "/volume1/video" --action move -non-strict "/volume1/video/DiskStation_Download" --log-file amc.log --def unsorted=y clean=y excludeList=amc.txt

It actually works very well. What are the advantages to using the FileBot Node?

Posted: **26 Jul 2016, 20:08**

Have same problem, Node doesnt start =(

log
2016/07/26 22:10:52 start filebot-node: begin to start version 0.2.0
2016/07/26 22:10:52 stop filebot-node: begin to stop version 0.2.0
2016/07/26 22:10:53 stop filebot-node: stop version 0.2.0 successfully, result 0
2016/07/26 22:11:03 start filebot-node: start version 0.2.0 failed, result 0
root@zzz:~#

root@zzz:~# curl -v https://10.10.1.8:5452/auth
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* Unknown SSL protocol error in connection to 10.10.1.8:5452
curl: (35) Unknown SSL protocol error in connection to 10.10.1.8:5452
root@Chkin:~# curl -v http://10.10.1.8:5452/auth
> GET /auth HTTP/1.1
> Host: 10.10.1.8:5452
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/json
< Access-Control-Allow-Origin: *
< Date: Tue, 26 Jul 2016 20:16:37 GMT
< Connection: keep-alive
< Content-Length: 51
<
{"success":true,"data":{"auth":"SYNO","user":null}}root@zzz:~#

# curl -v https://10.10.1.8: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.

have no idea how to make its work =(

Posted: **27 Jul 2016, 01:04**

recently after synology updated it self, filebot stopped worked again.
when login and try starting it pushing "execute" nothing happens

p.s. the filebot log file is empty, so nothing I can put it

Posted: **27 Jul 2016, 04:16**

yahooeyu wrote:{"success":true,"data":{"auth":"SYNO","user":null}}

The logs say that it works via HTTP but it doesn't work via HTTPS. That's easily explained by DSM using self-signed certificates and curl naturally not trusting those (you'll have to use the --insecure option for that, which is the same as clicking "I trust this site" in your browser when your browser encounters a self-signed certificate).

Posted: **27 Jul 2016, 04:20**

invis wrote:pushing "execute" nothing happens

There's 2 possible reasons:

A. The filebot node service is not running (see filebot node log)

B. Your network/firewall blocks your browser from sending requests to the filebot node service (use curl to test this, try accessing DSM from the local network)

Posted: **27 Jul 2016, 07:40**

Thanks for help.
I don't know how it happened,
but in 2 hours after it, i just reinstall NODE, and everything is work =)
magic!

Posted: **01 Aug 2016, 00:40**

rednoah wrote:
invis wrote:pushing "execute" nothing happens
There's 2 possible reasons:

A. The filebot node service is not running (see filebot node log)

B. Your network/firewall blocks your browser from sending requests to the filebot node service (use curl to test this, try accessing DSM from the local network)

I have DS213 and previous issue was - it was not working at all.
after that you helped me install it and make it work without node.
it was running without any problem until 2-3 weeks ago, probably some update from DSM came out
so my automated scheduler stopped working too :

Locking /volume1/@appstore/filebot/data/root/logs/amc.log
Cannot cast java.net.URI to [B
java.lang.ClassCastException: Cannot cast java.net.URI to [B
at net.filebot.CachedResource.get(CachedResource.java:107)
at net.filebot.MemoizedResource.get(Resource.java:36)
at net.filebot.cli.ScriptBundle.getScript(ScriptBundle.java:34)
at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:72)
at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:114)
at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:29)
at net.filebot.Main.main(Main.java:120)
Failure (Â°_Â°)

Firewall is off, tried different was to execute filebot, nothing

Posted: **29 Jan 2017, 10:59**

tedrogers61 wrote:
rednoah wrote:1.
1. Install Chromaprint and Media Info.
2. Install FileBot (and allow it to install Java and Node.js)
3. Install Filebot-Node.
I've tried this on my DS213J and I can't reproduce any issues. Works right out of the box.

2.
Code: Select all
./var/packages/filebot-node/scripts/start-stop-status start
You can't just call it like this. You'll have to set certain environment variables to call it as if DSM was calling it:
Code: Select all
export SYNOPKG_PKGNAME="filebot-node"
Re: 1...I can't explain it either...doesn't work one way, but works if I let filebot-node install everything for me.

Re: 2...thanks, this will come in useful should I need to start / stop manually. Is that the full command for both start and stop toggle?

Hi,

Is it possible to provide some clarity on how to use this export command that will allow the start-stop-status command to work.

I have tried using it in PuTTY by first running your export command then running the start-stop-status command but I get the following error:

initctl: Rejected send message, 1 matched rules; type="method_call", sender=":1.4146" (uid=1024 pid=3451 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 ")

Any help would be greatly appreciated.

Posted: **29 Jan 2017, 11:03**

Add a printenv > /path/to/output.txt in start-stop-status and then start/stop the service via DSM.

@see viewtopic.php?f=4&t=3067

FileBot

FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6

Re: FileBot Node doesn't start on DSM 6