I've been running Filebot & Filebot-node on Qnap for a few years without problem. Today I saw there was an update in the Qnap store and so I updated. After the update, I learned that my configuration is gone. I reactivated my (lifetime) license without issue and re-entered my configuration (I had all of the settings written down).
However, when I press "execute", nothing happens. Below is the filebot-node.log file:
Apologies, but my linux knowledge is nearly zero. Thanks for your help.
Code: Select all
ENVIRONMENT {
FILEBOT_TASK_CMD: '/opt/filebot-node/task',
QPKG_NAME: 'filebot-node',
FILEBOT_CMD_UID: '0',
LC_ALL: 'en_US.UTF-8',
JAVA_OPTS: '',
USER: 'admin',
FILEBOT_CMD_CWD: '/share/CACHEDEV1_DATA',
QPKG_DEFAULT_VOLUME: '/share/CACHEDEV1_DATA',
PATH: '/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin/X11:/usr/local/sbin:/usr/local/bin',
FILEBOT_CMD_GID: '0',
PWD: '/share/CACHEDEV1_DATA/.qpkg/filebot-node',
LANG: 'en_US.UTF-8',
QNAP_QPKG: 'filebot-node',
FILEBOT_NODE_HOST: '127.0.0.1',
SHLVL: '2',
FILEBOT_CMD: 'filebot',
LC_CTYPE: 'en_US.UTF-8',
QPKG_CONF: '/etc/config/qpkg.conf',
FILEBOT_NODE_HTTP_PORT: '5452',
FILEBOT_NODE_AUTH: 'QNAP',
FILEBOT_NODE_DATA: '/opt/filebot-node/data',
FILEBOT_NODE_HTTP: 'YES',
QPKG_ROOT: '/share/CACHEDEV1_DATA/.qpkg/filebot-node',
FILEBOT_NODE_CLIENT: 'client',
OLDPWD: '/',
_: '/usr/bin/node'
}
USER { UID: 0, GID: 0 }
filebot-node listening at http://127.0.0.1:5452/
-------------------- Run /share/CACHEDEV1_DATA/.qpkg/filebot-node/start (PID: 18249) -------------------- Thu Sep 2 14:55:02 ICT 2021
ENVIRONMENT {
FILEBOT_TASK_CMD: '/opt/filebot-node/task',
QPKG_NAME: 'filebot-node',
TERM: 'vt102',
SHELL: '/bin/sh',
FILEBOT_CMD_UID: '0',
OLDPWD: '/share/CACHEDEV1_DATA/.qpkg/.tmp',
QM: '1',
JAVA_OPTS: '',
USER: 'admin',
FILEBOT_CMD_CWD: '/share/CACHEDEV1_DATA',
QBOOT_HDCONF: '1',
QM_DIR: '/share/CACHEDEV1_DATA/.@app_center/filebot-node',
QPKG_DEFAULT_VOLUME: '/share/CACHEDEV1_DATA',
PATH: '/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin',
FILEBOT_CMD_GID: '0',
PWD: '/share/CACHEDEV1_DATA/.qpkg/filebot-node',
QM_OPT: '',
QNAP_QPKG: 'filebot-node',
intel_iommu: 'on,igfx_off',
FILEBOT_NODE_HOST: '127.0.0.1',
SHLVL: '9',
HOME: '/',
BOOT_IMAGE: '/boot/bzImage',
FILEBOT_CMD: 'filebot',
QPKG_CONF: '/etc/config/qpkg.conf',
FILEBOT_NODE_HTTP_PORT: '5452',
FILEBOT_NODE_AUTH: 'QNAP',
FILEBOT_NODE_DATA: '/opt/filebot-node/data',
FILEBOT_NODE_HTTP: 'YES',
QPKG_ROOT: '/share/CACHEDEV1_DATA/.qpkg/filebot-node',
FILEBOT_NODE_CLIENT: 'client'
}
STATUS {
pid: 18249,
node: 'v14.1.0',
uptime: '0',
date: 'Thu, 02 Sep 2021 07:55:03 GMT'
}
USER { UID: 0, GID: 0 }
filebot-node listening at http://127.0.0.1:5452/
events.js:292
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE: address already in use 127.0.0.1:5452
at Server.setupListenHandle [as _listen2] (net.js:1314:16)
at listenInCluster (net.js:1362:12)
at doListen (net.js:1499:7)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
Emitted 'error' event on Server instance at:
at emitErrorNT (net.js:1341:8)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '127.0.0.1',
port: 5452
}