FileBot

Yep, this one shows exactly what's happening. Looks like the problem is fixed now.

Back again with an update.

I had to reboot the NAS this morning and then filbot-node failed with the service not available message.

Stopped and restarted Filebot first with same message. Then I tried filebot Node stopped and restarted got it working.

Please post the log so I can have a look if it crashed and why:

I had another reboot -(for another reason) and it failed but stopping and starting filebot node got it working

My uneducated guess is, it is the order that things are loaded on a reboot.

filebot node needs to be after some other component - filebot may be??

Yes, I suppose it's possible that the node package will link itself into the $PATH on startup, so if that happens after FileBot Node, then FileBot Node launcher won't work.

Not sure how to fix this. Maybe QNAP forums have some more specific advice.

What does this say? I read that package have a RC_Number field which might be used for startup priority.


I've never had problems with the node package though:

SortMyQpkgs is an app that sort the loading order.

I had this installed before my rebuild and have just reinstalled it.

Next time I reboot I will see if it "sorts" filebot i theright order. My prediction is it will fix it

I'm still curious what Node package you have installed, and what RC_Number it's got by default.

rednoah wrote: ↑08 Jul 2019, 02:34 I'm still curious what Node package you have installed, and what RC_Number it's got by default.

Node V8.9.0.1

Where and what is RC Number

What does this say? I read that package have a RC_Number field which might be used for startup priority.

this is a few of the apps


[filebot-node]
Name = filebot-node
Class = null
Status = complete
Build = 20190705
Display_Name = FileBot Node
Version = 0.2.8.5
Author = FileBot
QPKG_File = filebot-node.qpkg
Date = 2019-07-05
Shell = /share/CACHEDEV1_DATA/.qpkg/filebot-node/filebot-node-service.sh
Install_Path = /share/CACHEDEV1_DATA/.qpkg/filebot-node
WebUI = /
Web_Port = 5452
RC_Number = 453
Desktop = 1
Win_Width = 1000
Win_Height = 600
Use_Proxy = 1
Proxy_Path = /filebot-node/
Enable = TRUE
store = 785ba2029dc01f8697e219cdaf3fcc6a
Official = 0
FW_Ver_Min = 4.2.0

[filebot]
Name = filebot
Class = null
Status = complete
Build = 20190403
Display_Name = FileBot
Version = 4.8.5
Author = FileBot
QPKG_File = filebot.qpkg
Date = 2019-07-05
Shell = /share/CACHEDEV1_DATA/.qpkg/filebot/filebot-service.sh
Install_Path = /share/CACHEDEV1_DATA/.qpkg/filebot
RC_Number = 452
Enable = TRUE
store = 785ba2029dc01f8697e219cdaf3fcc6a
Official = 0
FW_Ver_Min = 4.2.0



[SortMyQPKGs]
Name = SortMyQPKGs
Class = null
Status = complete
Build = 20190417
Display_Name = SortMyQPKGs
Version = 190417
Author = OneCD
QPKG_File = SortMyQPKGs.qpkg
Date = 2019-07-08
Shell = /share/CACHEDEV1_DATA/.qpkg/SortMyQPKGs/sort-my-qpkgs.sh
Install_Path = /share/CACHEDEV1_DATA/.qpkg/SortMyQPKGs
WebUI = /SortMyQPKGs.log
RC_Number = 500
Web_Port = 8080
Enable = TRUE
store = e754538ad86a655a0687f76c5190a5f8

What does the Node v8 entry say?

(node, not filebot-node, to see if there's a hint as to why node starts after filebot-node)

That is strange indeed. No idea why filebot-node might be started before node is has linked itself into the $PATH. No idea for now. Let me know if it happens again.

Since having sortmyqpkg installed no issues with opening.

I asked this before and did not get an answer.

Can I set filebot node to run automatically 3x or 4x a day?

FileBot Node is running at all times.

Presumably, you want to want to call filebot commands on a schedule. FileBot Node can help with that. Just use the Schedule button instead of the Execute button to create a scheduled task. In order to call this task x times per day, you'll have to use cron.

Unfortunately, FileBot Node cannot help you manage your cron jobs on QNAP NAS, so you'll have to do that manually by logging in via SSH. There may be 3rd party QNAP applications that can help with calling commands on a schedule.