Curious about this... my FileBot stopped working after a recent DSM update. The FileBot Node wouldn't run so I thought I would try a reboot. In Package Centre the Node is still showing as Stopped, but the logs indicate it is started and it is actually processing my files.
Can anyone explain this?
Node Showing Stopped by Actually Started
Re: Node Showing Stopped by Actually Started
"Stopped" just means the node service is not running. FileBot itself is a command-line tool, so it'll always show up as "Started" even though nothing is running in the background.
What Synology shows as Started / Stopped is entirely defined by the return value of this call:
https://github.com/filebot/filebot-node ... status#L15
What Synology shows as Started / Stopped is entirely defined by the return value of this call:
https://github.com/filebot/filebot-node ... status#L15
Please read the