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:
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.