FileBot Node doesn't execute any commands anymore or shows an empty terminal

[dazzah]

Hello,

before v4.7.1, FileBot Node was just not loading/starting. But once released and updated through the Package Center, FileBot did everything it should for several days. It renamed my files and moved them accordingly. I created a scheduled task and it also did its job. Overall, I was pretty happy how everything turned out.

Today I logged on to add my downloads, opened up FileBot Node and I wanted to experiment with the naming schemes. I pressed on "Execute" but nothing happened. The console remained empty and it just displayed "$ logcat". I deleted the scheduled task because I thought it might cause the issue. However, pressing on any of the buttons under "Execute" (or on "Execute") itself didn't do anything.

I didn't think much of it at first and re-installed Filebot, Filebot Node, your Java package and restarted the Diskstation but the problem remains. Do you have an idea what could be the issue?

Thank you very much in advance for any help or pointers in the right direction!
---
Here is some info that I hope can be helpful. If you would like to have additional information, please let me know but at this point I don't know what else to add.

Synology: DS115
Synology version: DSM 6.0.1-7393 Update 2
Logged in as: admin
FileBot version: 4.7.1
FileBot Node version: 0.2.0
Oracle Java SE version: 1.8.0_101
FileBot Node UI can be opened in a separate tab

[rednoah]

It's probably a network problem. Please read FileBot Node Troubleshooting and ensure that the FileBot Node Service is accessible (i.e. HTTP on port 5452 and HTTPS on port 5453). Firewall issues are common if you're trying to access your diskstation from outside network.

FYI: FileBot and FileBot Node are completely independent. Updating FileBot will not affect the FileBot Node WebUI and vice versa.

[dazzah]

Thanks for the heads up rednoah! You were right. It was a network problem. It's still a bit odd because I was able to access and execute FileBot Node from outside my home network before but now that I'm home and re-checked, everything works normally again. I'll keep that in mind before I post next time.

[seenhear]

Hi there, I'm having the same problem, so I assume my issue will resolve when I return home and can try this out on the home network. So, thanks for the above solution/explanation.
However, if I need to use this from within my home network (I don't want to open up extra ports on my router - instead I use synology's ddns service) then it kind of defeats the point of having a version of filebot that works from within DSM. If I have to do it from my home network, I can just use the command line version from a ssh window.
I know there's more to the web gui version than that, but to me the main benefit of filebot running within DSM is to be able to manage files and such while outside of my home network.
Is there any chance you can make a future version that runs through DSM when accessed via synology's quickconnect service?
Thanks!

[rednoah]

Nope, definitely not something intended to do and many many hours on.

Also, probably not feasible:
https://github.com/SynoCommunity/spksrc/issues/1832

[seenhear]

OK cool. I was just curious. Thanks!
FYI, the problem was solved by accessing from my home LAN.

[frikeando]

In my case, I have the ports open on the router and the symbology configured, but i cannot reach them, following the FAQ rednoah posted... what am i doing wrong?

I cannot access ssh in synology, if that helps.

[rednoah]

If the FileBot Node Service is running, and if the ports are forwarded, then it'll work. If it doesn't work then either the node service is not running, or the ports are not forwarded.

The logs should tell you if the node service is running and waiting for connection. And Google should tell you everything you need to know about port forwarding and checking if it's working or not.

PS: not being able to access SSH means that either the service is not running, or the ports are blocked. So it's the same concept.

[frikeando]

Node is now running. When I go to the terminal:

Code: Select all

iMac:~ user$ curl -v http://diskstation.local:5453/auth
*   Trying 192.168.1.188...
* Connected to diskstation.local (192.168.1.188) port 5453 (#0)
> GET /auth HTTP/1.1
> Host: diskstation.local:5453
> User-Agent: curl/7.49.1
> Accept: */*
> 
* Empty reply from server
* Connection #0 to host diskstation.local left intact
curl: (52) Empty reply from server

So I suppose everything should work. But, I get the "$ logcat" on Node window...

[rednoah]

1.
Your curl test yields no response because you use HTTP protocol on a port that expects HTTPS.


2.
The FileBot Node WebUI is empty because your browser can't communicate with the node service.

It's a network issue. If you open the network/debug console in your browser you will see network errors.

[invis]

having the same issue on my ds213
last time Rednoah helped me install filebot node directly, but after some dsm updates it stopped working, doesnt execute manually or using planner.

Ports are forwarded..

P.S. looks like node.js v4 wont be supported at all anymore on ds213

[rednoah]

According to this log, the node service is running just fine.

[invis]

the ports are forwarded, but when I try checking them - it says there is no service under those ports.
it doesn't even execute manually, not even talking about the schedule run.

P.S. there is node 0.2.1 update available, but without node.js v4 can't install it Is there a chance on making it run?

[rednoah]

1.
If the log says "Listening at ..." it means it's working. Run some tests with curl on the diskstation, then local network, then remote network, to narrow down the problem.


2.
Synology Package Manager doesn't support A OR B dependencies, so it won't let you install the SPK. FileBot Node itself will work with any node executable though, so you can make it work if you extract the files yourself.

[invis]

according to my investigation upstart process do not start at all. see what i found below

sh-4.3# curl -I http://192.168.1.110:5453
curl: (7) Failed to connect to 192.168.1.110 port 5453: Connection refused
sh-4.3# curl -I -k https://192.168.1.110:5453
curl: (7) Failed to connect to 192.168.1.110 port 5453: Connection refused



sh-4.3# netstat -ntlpu | egrep "5452|5453"
sh-4.3#


sh-4.3# initctl restart pkgctl-filebot
pkgctl-filebot start/running
sh-4.3# initctl restart pkgctl-filebot-node
pkgctl-filebot-node start/running
sh-4.3# ps ax | grep file
3478 ? Ss 0:00 /sbin/dbus-daemon --system --nopidfile
4760 pts/4 S+ 0:00 grep file
10275 ? S 0:00 /usr/syno/ipsec/libexec/pluto --nofork --secretsfile /usr/syno/etc/packages/VPNCenter/l2tp/ipsec.secrets --ipsecdir /etc/ipsec.d --use-netkey --uniqueids --nat_traversal --virtual_private %v4:10.0.0.0/8,%v4:192.168.0.0/16,%v4:172.16.0.0/12 --listen 192.168.1.110 --nhelpers -1 --secctx_attr_value 32001
sh-4.3#



sh-4.3# tail -f /var/log/upstart/pkgctl-filebot.log
2016-08-09T03:33:53+0300 ======== stop filebot ========
2016-09-03T23:12:29+0300 ======== start filebot ========
2016-09-05T20:49:32+0300 ======== stop filebot ========
2016-09-05T20:50:50+0300 ======== start filebot ========
2016-09-05T20:57:42+0300 ======== stop filebot ========
2016-09-05T20:57:43+0300 ======== start filebot ========
2016-09-05T21:01:21+0300 ======== stop filebot ========
2016-09-05T21:02:32+0300 ======== start filebot ========
2016-09-05T21:11:56+0300 ======== stop filebot ========
2016-09-05T21:11:56+0300 ======== start filebot ========
^C
sh-4.3# tail -f /var/log/upstart/pkgctl-filebot-node.log
2016-09-05T20:46:34+0300 ======== stop filebot-node ========
2016-09-05T20:46:34+0300 ======== start filebot-node ========
2016-09-05T20:47:24+0300 ======== stop filebot-node ========
2016-09-05T20:47:24+0300 ======== start filebot-node ========
2016-09-05T20:49:28+0300 ======== stop filebot-node ========
2016-09-05T20:57:39+0300 ======== stop filebot-node ========
2016-09-05T21:01:50+0300 ======== stop filebot-node ========
2016-09-05T21:02:27+0300 ======== start filebot-node ========
2016-09-05T21:12:02+0300 ======== stop filebot-node ========
2016-09-05T21:12:03+0300 ======== start filebot-node ========

is there a way to start process manually? and in debug mode? i have also tried to start as in upstart config but get no stdout and stderr at all.

[rednoah]

You can start it from console by using the start script.

[invis]

sh-4.3# initctl restart pkgctl-filebot
pkgctl-filebot start/running
sh-4.3# initctl restart pkgctl-filebot-node
pkgctl-filebot-node start/running

This is how I manually restarted the application but no log appear. Can I start it not from upstart script but something like :
/Usr/bin/filebot -param1 -param2

[rednoah]

I'd start it by using the filebot-node start script. It's pretty useless to try anything else until we know if that works or not.

[invis]

I'd start it by using the filebot-node start script. It's pretty useless to try anything else until we know if that works or not.

where this start script is located?

[rednoah]

Have you tried to find it?

Code: Select all

find /volume1 | grep filebot | grep start

[invis]

ok, here is what we got so far.

+ node --max_executable_size=16 --use_idle_notification server/app.js

module.js:340
throw err;
^
Error: Cannot find module '/volume1/homes/admin/server/app.js'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:935:3

[rednoah]

Your working directory is wrong. server/app.js is located relative to start, not relative to your user home.

[invis]

Trying to reinstall everything.
Having an issue with installing filebot-node-0.2.1-noarch.spk, it doesn't allow you to install it, unless the nodejs4 is installed.
How can I manually install it? Is there a way to make the spk file not require nodejs4 for installation or any other option?
Thanks

[rednoah]

Running filebot-node without any DSM interaction is possible. I test and develop on Mac.

You could just download and extract the filebot-node-0.2.1-generic.tar.bz2 package and then start it manually. This package doesn't do any user authentication, so make sure that your DSM isn't accessible from outside your local network.

[invis]

tried running it manually and here is what I've got

admin@Synology:/volume1/Temporary/fileboot$ node ./server/app.js

fs.js:870
return binding.chown(pathModule._makeLong(path), uid, gid);
^
TypeError: uid must be an unsigned int
at Object.fs.chownSync (fs.js:870:18)
at Object.<anonymous> (/volume1/Temporary/fileboot/server/app.js:53:8)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:935:3

what am i doing wrong?