rm: cannot remove '/usr/local/filebot-node': Is a directory

limera1n · Post by **limera1n** » 29 Mar 2020, 20:54

Hello! I have filebot (4.9.0) and filebot node (0.2.9) installed on my synology nas (ds414). I use a simple script looking for files in downloads folder that runs filebot if there are any. The script is scheduled to run every 5 minutes via task scheduler. Everything was working like a charm until recent update of java installer (to 2.13). Firstly, the script stopped working without me changing anything (except for updating java installer in package center). When I tried to run filebot through filebot node I got the error that there are no files for selection (even though there were files in downloads folder). I tried reinstalling java installer and filebot and it helped but only for a short while. Ever since filebot was very unstable. I tried playing around with different versions of filebot, filebot node and java installer but none of this fixed the problem. Sometimes deleting excludes file would help. The last issue I got is an unknown error on filebot node launch. It appeared after I reinstalled it the last time and it looks like a window with synology logo and a cross. It appears on launch and whenever I try to do anything in filebot node. So now I cant even activate filebot license because I am accessing my nas remotely and cant ssh into it. I came across a thread with the similar problem and the issue was that node.js was missing. But I have it installed. I cant access log file because again I cant use cli. Is there anything that could be done at the moment (I am not sure when I will be able to access my nas from local network)? Any help will be greatly appreciated, I got so used to filebot.

Post by **rednoah** » 29 Mar 2020, 20:59

What does the error message say? Screenshots?

Please read How to Request Help.

limera1n · Post by **limera1n** » 29 Mar 2020, 21:21

It doesnt say anything just synology logo, here is a screenshot: https://imgur.com/vmL5L90

Post by **rednoah** » 29 Mar 2020, 21:29

Yep, probably a Node.JS issue. FileBot Node isn't running at all.

The log will tell us why: viewtopic.php?t=11030

rednoah wrote: ↑25 Aug 2019, 04:58 What does the log say? The log will tell you why FileBot Node is crashing on startup and thus can't serve requests. You'll need to login via SSH and use the find and cat commands to find and display the log file.

Q: Where is the log file?

Please login via SSH and use the find command to find the log file:
Code: Select all
find / -name filebot-node.log
e.g. Synology NAS:
Code: Select all
sudo cat /var/log/upstart/filebot-node.log
e.g. QNAP NAS
Code: Select all
cat /opt/filebot-node/filebot-node.log
e.g. Expected log entries that tell us that the filebot-node service is up and running:
Code: Select all
ENVIRONMENT { ... }
USER { ... }
filebot-node listening at http://127.0.0.1:5452/
...

limera1n · Post by **limera1n** » 30 Mar 2020, 07:56

So, until I get access to the log file there is nothing that I can do (I need to forward a port on my router to ssh into nas remotely which I cant do outside of my local network)? Btw which version of node.js should I use? currently I have v12 installed

Post by **rednoah** » 30 Mar 2020, 08:18

Well, without logs, you can only do blind trial and error, so that is not good.

I don't know the lower boundary of compatible Node.JS versions, but on my DS213J, this one is known to work: