[QNAP] /usr/local/bin/node: Permission denied

[parkerc]

Hi,

As I’m a little late to the game with QNAP and FileBot..

Please can I check that the above is still up to date and is working on the latest firmware version 4.4.2 ?

Is there an order I should install the packages provided in the App Repository ?

[rednoah]

Please can I check that the above is still up to date and is working on the latest firmware version 4.4.2 ?

Yes. The firmware version doesn't matter.

Is there an order I should install the packages provided in the App Repository ?

You can install the packages in any order.

[parkerc]

Great thanks @rednoah

I’ve installed all the packages and just ‘opened’ FileBot Node, which gives me the following message...

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Any ideas ?

[rednoah]

What does the log say?

Did you install Node.js yet?

FileBot Node requires node. You will need to install the latest Node.js package.

[parkerc]

Did you install Node.js yet?

Argh, sorry, that’s going to be it, looking in the main QNAP repository - there seems to be 3 Node.js versions available v4, v6 and v8 - so I’ll install the latest v8..

[parkerc]

Ok, perhaps not, v8 installed, FileBot and FileBot stopped and restarted, but still the same ‘Service Unavailable’ message

Where do I find the logs for this, is there a command to run ?

[rednoah]

Where do I find the logs for this, is there a command to run ?

➔ viewtopic.php?t=11030

[perchu]

I had the same issue, the only solution I got is to launch through ssh the "filebot-node-service.sh start"

[rednoah]

I had the same issue, the only solution I got is to launch through ssh the "filebot-node-service.sh start"

What does the log say when QNAP fails to run that command on startup?

[perchu]

QNAP doesn't seem to try to run that command.

I'm still learning QNAP. I have checked in /var/log but found nothing.

[rednoah]

QNAP doesn't seem to try to run that command.

If QNAP really doesn't run service.sh start when starting a package, then you could try contacting QNAP support to see if they can help you figure why their software doesn't behave.

[parkerc]

In the filebot-node.log file, found in /share/CACHEDEV1_DATA/.qpkg/filebot-node/ it has the following content

Code: Select all

 ls: cannot access : No such file or directory
Node.js is not installed. Please install Node.js in the App Center.
/share/CACHEDEV1_DATA/.qpkg/filebot-node/start: line 38: /usr/local/bin/node: Permission denied

Node.js, was the original concern, and I addressed that by installing the v8 .qpkg from QNAP App Center

[rednoah]

Well, that explains why node is not working:

Code: Select all

/share/CACHEDEV1_DATA/.qpkg/filebot-node/start: line 38: /usr/local/bin/node: Permission denied

If you can get node -version to work, then FileBot Node will work. Please ask QNAP for help on how to fix their Node.JS packages.

Perhaps it's just missing the executable permission for some odd reason. Try chmod +x /usr/local/bin/node and see if it works.

[parkerc]

Interestingly - I also couldn’t open the FileBot-node.log file via the command line (ssh) as that also gave me the permission denied message too . (And you can only ssh in as the admin) - So I think it’s a wider permission issue than just node.