FileBot Node not loading after update

[drcranii]

FileBot Node,

Synology DSM auto-updated to DSM 6.2.3-25426 and FileNod v0.2.9 needed Repair after update.
Performed repair in package center. After package has been repaired it shows as running but it would not launch.
Reinstalled FileBot Node and same problem it would not open while it shows as running.

Any recommendations how to fix FileBot Node?

Synology Log Center:

Code: Select all

Level Log    Time                User Event

Info  System 2020-05-28 18:44:27 user Package [FileBot Node] has been successfully installed.
Info  System 2020-05-28 18:43:30 user Package [FileBot Node] has been successfully uninstalled.
...
Info  System 2020-05-28 18:36:37 user Package [FileBot Node] has been successfully repaired.
...

FileNode Log via SSH:

Code: Select all

2020-05-28T18:44:27-0700 lrwxrwxrwx 1 root root 49 Mar 25 11:31 /usr/local/bin/node -> /volume1/@appstore/Node.js_v12/usr/local/bin/node
2020-05-28T18:44:27-0700 ENVIRONMENT {
  FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  TERM: 'vt102',
  FILEBOT_CMD_UID: '1024',
  JAVA_OPTS: '',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  FILEBOT_CMD_GID: '101',
  PWD: '/usr/local/filebot-node',
  FILEBOT_NODE_HOST: '127.0.0.1',
  SHLVL: '1',
  FILEBOT_CMD: 'filebot',
  UPSTART_INSTANCE: '',
  FILEBOT_NODE_HTTP_PORT: '5452',
  FILEBOT_NODE_AUTH: 'SYNO',
  UPSTART_JOB: 'filebot-node',
  FILEBOT_NODE_DATA: '/usr/local/filebot-node/data',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_CLIENT: 'client',
  _: '/usr/local/bin/node',
  OLDPWD: '/volume1/@appstore/filebot-node'
}
2020-05-28T18:44:27-0700 USER { UID: 1024, GID: 101 }
2020-05-28T18:44:28-0700 filebot-node listening at http://127.0.0.1:5452/

[rednoah]

1.
Looks like FileBot Node itself is running.

The nginx reverse proxy configuration could be a problem though, if DSM has changed how things work:
https://github.com/filebot/filebot-node ... -node.conf

Probably not something that can be fixed easily by a layman. But if you're familiar with Linux and nginx, then you might be able to investigate what has changed, and perhaps find a work around.


2.
Please include filebot -script fn:sysinfo output. Please read How to Request Help.

[drcranii]

1.
Looks like FileBot Node itself is running.

The nginx reverse proxy configuration could be a problem though, if DSM has changed how things work:
https://github.com/filebot/filebot-node ... -node.conf

Probably not something that can be fixed easily by a layman. But if you're familiar with Linux and nginx, then you might be able to investigate what has changed, and perhaps find a work around.


2.
Please include filebot -script fn:sysinfo output. Please read How to Request Help.

Thank you for a reply, somehow FileBot Node started to work again, but it was missing data on my previously set folders and custom formats.

Before that I ran clear cache via SSH:

Code: Select all

 filebot -clear-cache 

It appeared not to fix things at first. But few hours later FileBot Node was running fine.
Thank you again for a swift reply.