FileBot Node doesn't start on DSM 6

[ntmf]

Sadly the FileBot Node 0.2.0 does not start:
I just get the error message: "Der Paketdienst konnte nicht ausgeführt werden"
The Protokoll does not contain any data.

I did the following things:
Have you tried a different browser? (e.g. Chrome) - Does change anything

Have you tried clearing the browser cache and reloading the page? Yes - does not start.

Have you tried restarting your DiskStation? Yes, and afterwards I deleted the Browsercache

Have you tried everything on this list - What exactly isn't working?
Install failed? Installation worked!
Service not started? This is correct!
Page not found? No answer from http://192.168.178:5000/webman/3rdparty ... index.html
Authentication not working? I think I did not get there

Does your firewall allow TCP traffic on ports 5452 and 5453? FileBot Node will use HTTP on port 5452, and HTTPS on port 5453.
The Firewall of my NAS is not activated, but HTTP will connect over 5000 and HTTPS over 5001
My Router has no Firewall as I know off.

I tried to access it from the terminal:
curl -v http://192.168.15:5452/auth
* Trying 192.168.0.15...
* connect to 192.168.0.15 port 5452 failed: Operation timed out
* Failed to connect to 192.168.15 port 5452: Operation timed out
* Closing connection 0
curl: (7) Failed to connect to 192.168.15 port 5452: Operation timed out

Right now I don't know exactly how to continue

[rednoah]

Please continue with the very first question...

Click Package Center -> FileBot Node -> View Log and see what it says.

[ntmf]

Sorry, I got the translation wrong: with "Protokoll" I meant "view log" If I open it it just opens a window which shows "No Data" - the only option in this window is "close".

I switched the language - when I chose "run" as an option, after a while it shows "stopping" and a window pops up with the massage "Failed to run the package service."

could it be a problem, that I have both Java 7 and 8 running?

[rednoah]

That probably means that the package didn't install at all, so broken package. Download again, check MD5 hashes, make sure there's no proxy between you and your DSM that corrupts the data in flight.

At this point it's not a problem specific to filebot node, so you might find more help in the Synology forums.

It has nothing to do with Java 7/8. You might wanna ssh into your DSM and check out /var/packages/filebot-node/target and see if there's anything odd.

[flasher111]

@rednoah,

thanks for updating FilebotNode!
i installed it now and the GUI works fine. But for now i have an other problem.
I got an Error in line 36: java: command not found.



Java 8 is installed on my synology.
but i haven`t installed you Java package because i got an error that my disk space is full.


i have checked my disk space and it is not full.

Code: Select all

Filesystem     1K-blocks      Used Available Use% Mounted on
/dev/md0         2385528    853032   1413712  38% /
none              501980         4    501976   1% /dev
/tmp              506260       432    505828   1% /tmp
/run              506260      2024    504236   1% /run
/dev/shm          506260         4    506256   1% /dev/shm
none                   4         0         4   0% /sys/fs/cgroup
/dev/vg1000/lv 956638596 801589120 154930692  84% /volume1

i have the same problem by installing you new Filebot Version since Version 4.6.1
so for now i installed your Version 4.6

Maybe you can check this!

Thanks for your great Work

[bentheone]

How do I update? I see all the .jar files, but what do I have to do with these?

[rednoah]

The package sets extractsize=524288000 so DSM won't install it if you have less than 500 MB of free storage.

If your NAS has less than 500 MB free storage then you seriously need to consider deleting stuff, or getting a bigger HDD.

If your disk has plenty of free space, then this might be a bug in DSM. You might want to report this kind of Package Center issue to issue to Synology support.


EDIT:


I started a thread in the Synology forums:
https://forum.synology.com/enu/viewtopi ... 09#p425109

Please report the issue to Synology support as well though. Either it's a bug in DSM, or a bug in the SPK specification.

[Tbright]

First of all, thanks for developing this!!!
I was wondering if you are planning on updating the repository any time soon now that the dsm 6 is out? I do not know how to update it from github
Thanks a lot
TB

[rednoah]

Of course, soon as in in the next 1-2 weeks.

[maxoudela]

Hi,

First of all, thank you for the work you do and the reactivity.

I had the same issue on this thread. I would like to install the new version working with DSM 6. Maybe a stupid question, but what file should I take in the web page you mentioned ? (https://sourceforge.net/projects/filebo ... ebot/HEAD/)


Do I need to delete FileBotNode in the package center before?

EDIT : Ok forgot the question, I simply took the FileBot and did a manual install of the package.

EDIT 2 : Ok it's running but I have the "the page you're looking for is not here" (or something like that). But I have not opened the ports 5452 and 5453 so it must be that..

Regards,
Sam'

[XavierC]

you can try accesing it trough the direct link http://YOURIP:5000/webman/3rdparty/file ... index.html

[tonis]

I still can't run FileBot Node after update to DSM 6. It won't start with error message "Failed to run the package service". Log is empty.

What I did:
1. Uninstalled everything.
2. Re-created download and media folders.
2. Installed Java (you need to have ~500GB free space at the moment because Synology bug).
3. Installed Node.js v4
4. Installed FileBot.
5. Checked that ports are open.

6. Installed FileBot Node and it fails to start.

[tonis]

Managed to make it work:

1. Owner for download and media folders was still root. Changed it to admin user. After that didn't work right away.
2. Re-installed everything and rebooted. Now it worked.

[ward0]

Rednoah, can you pls let us know in the topic here, when you updated the syncommunity package for DSM6

Thanks in advance.

[padremaldito]

Hi
After DSM 6 update 3 stop working. After uninstall it and reinstalled Filebot-node can't be started (0.1.8 and 0.2 version).

I've uninstalled all packages. And reinstalle in order, Java Node, Filebot, filebot-node.

Any idea?

[tonis]

For me it's also broken again. Node is not starting and Log is empty. For me it seems that DSM update 5 did it.

[tedrogers61]

New Synology owner here - first ever NAS! DS215j on DSM 6.0-7321 Update 6.

Just using it as a music server and photo dump.

I also cannot get FileBot Node 0.2.0 to start - same error - "failed to run the package service".

Whether the firewall is off or if I add exceptions for the correct ports - no difference. Ports are forwarded on router and confirmed open by Web port check tool.

My 'music' shared folder has admin permissions r/w full access.

I'm logged in as admin using LAN IP rather than quickconnect.

Is it broken? Am I (at this moment in time) pissing into the wind trying to get this working? Haha.

Thanks.

[rednoah]

1.
What exactly is working and what exactly is not?
viewtopic.php?f=13&t=3368

You did not include any logs. If something doesn't work, there will always be logs. If you can find them, ask Google where to find them.


2.

"failed to run the package service"

This message indicates that the package is never started. Presumably, no filebot code is ever called, so there is nothing that can be fixed here. Please ask Synology support.

[tedrogers61]

Well, everything installs correctly as far as I can tell.

FileBot
FileBot Node
(your) Java
Acoustic ID
Mediainfo

When I run the Node package, I get the error I mentioned. Everything else reports as running, except Node won't start.

The log for Node is blank, which supports your point about it never starting in the first place.

Are there any specific logs you require from elsewhere? I can find them no problem, I just need to know which ones.

Thanks.

[rednoah]

Unfortunately, that does not help me help you. You will need to find more information (i.e. logs) and then maybe there'll be some hints towards a solution.

* You did not include screenshots (so I can confirm that the package was installed)
* You did not include package log -> View Log -> Screenshot (so I can confirm if the package is started or not)
* You did not include curl -v http://<IP>:5452/auth output (so I can confirm if the service is running or not)
* You did not include Synology syslog output (so I can see what synology is doing / not doing)

This list is not exhaustive. More information is better. Google "failed to run the package service" and see if you find anything that might shine more light on the issue.

DSM has a "Log" app. Just click around a little bit until you find it. Otherwise check the Synology forums. I'd start by checking the typical Linux locations like /var/log via SSH first.

[tedrogers61]

Okay, I will try and turn my attention to all of this when I have the opportunity.

Thanks.

[ward0]

Unfortunately, that does not help me help you. You will need to find more information (i.e. logs) and then maybe there'll be some hints towards a solution.

* You did not include screenshots (so I can confirm that the package was installed)
* You did not include package log -> View Log -> Screenshot (so I can confirm if the package is started or not)
* You did not include curl -v http://<IP>:5452/auth output (so I can confirm if the service is running or not)
* You did not include Synology syslog output (so I can see what synology is doing / not doing)

This list is not exhaustive. More information is better. Google "failed to run the package service" and see if you find anything that might shine more light on the issue.

DSM has a "Log" app. Just click around a little bit until you find it. Otherwise check the Synology forums. I'd start by checking the typical Linux locations like /var/log via SSH first.

this might help people :

dant1 wrote:
I am having this issue with Sonarr. I only have limited experience with SSH but am willing to learn if you have any pointers to getting it working.


First, create a user called "nzbdrone". Sonarr used to be called NzbDrone, and it still relies on having a user account with that name. The package installer should auto-create the user, but that part of the installer isn't working properly on DSM 6.0, so you need to make the user account manually. Give it a random password, and assign it read/write privileges to your download share as well as your video share. Then see if the service starts up.

If it still doesn't start, try SSHing into your NAS as the root user and run the following command:

Code: Select all
chown -HR nzbdrone /usr/local/nzbdrone


That will assign ownership of the Sonarr/NzbDrone package files to the nzbdrone user.

Then try to start it up again. If it still doesn't work, report back and I'll give you some more commands to run to figure out why it isn't working

Link : https://forum.synology.com/enu/viewtopic.php?t=106960

Google is your friend for most people, Me i'm waiting for Syno to fix it in patch because i'm a lazy IT'r

[tedrogers61]

Thanks for your continued replies.

I briefly tried connecting via HTTP rather than HTTPS, and that didn't work either.

Logged in as admin. Full permission everywhere. Ports open on router. Syno Firewall off.

I also uninstalled, rebooted, reinstalled, rebooted - no success.

FBNode just won't start. Everything else reports as "running" (FileBot, AcoustiID, Java, etc).

I wish I had to time to devote to this, but I might just use other ways to get the artwork I need. Would have been nice to have it running automatically on the DiskStation though.

[ward0]

Thanks for your continued replies.

I briefly tried connecting via HTTP rather than HTTPS, and that didn't work either.

Logged in as admin. Full permission everywhere. Ports open on router. Syno Firewall off.

I also uninstalled, rebooted, reinstalled, rebooted - no success.

FBNode just won't start. Everything else reports as "running" (FileBot, AcoustiID, Java, etc).

I wish I had to time to devote to this, but I might just use other ways to get the artwork I need. Would have been nice to have it running automatically on the DiskStation though.

Do you have any Linux Exp. what so ever? Did you read my comment about SSH? Not http or https ( its the same thing btw .. just secured or not.)

You will need to use a black terminal and not a click click solution for this problem. Else use a restore and go back to DSM5

[rednoah]

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