FileBot

The ultimate TV and Movie Renamer
https://www.filebot.net/forums/

DSM 6.0.2 Update 5

https://www.filebot.net/forums/viewtopic.php?t=4432

Page 1 of 1

DSM 6.0.2 Update 5

Posted: 30 Nov 2016, 18:08
by Mojito71
Just updated DSM, and filebot node to 4.7.5, and now I'm unable to execute command.

If I open http://192.168.1.125:5000/webman/3rdpar ... index.html, and developer tools, the console is full of:
app.js?_dc=20161125063244:1 GET http://192.168.1.125:5452/tasks 401 (Unauthorized)start
app.js?_dc=20161125063244:1 Uncaught RangeError: Maximum call stack size exceeded(…)

Using curl from the synology:
curl -v http://192.168.1.125:5452/auth
> GET /auth HTTP/1.1
> Host: 192.168.1.125:5452
> User-Agent: curl/7.50.3
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/json
< Access-Control-Allow-Origin: *
< Date: Wed, 30 Nov 2016 17:56:10 GMT
< Connection: keep-alive
< Content-Length: 51
<
{"success":true,"data":{"auth":"SYNO","user":null}}

Using curl from the computer:
url -v http://192.168.1.125:5452/auth
* Trying 192.168.1.125...
* TCP_NODELAY set
* Connected to 192.168.1.125 (192.168.1.125) port 5452 (#0)
> GET /auth HTTP/1.1
> Host: 192.168.1.125:5452
> User-Agent: curl/7.51.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/json
< Access-Control-Allow-Origin: *
< Date: Wed, 30 Nov 2016 17:57:33 GMT
< Connection: keep-alive
< Content-Length: 51
<
* Curl_http_done: called premature == 0
* Connection #0 to host 192.168.1.125 left intact
{"success":true,"data":{"auth":"SYNO","user":null}}

Where to start?

T

Re: DSM 6.0.2 Update 5

Posted: 30 Nov 2016, 22:09
by rednoah
You need to log into DSM and open the FileBot Node UI from DSM. Opening the FileBot Node IFRAME directy may or may not work depending on whether or not your browser is sending along a valid DSM session cookie.

Re: DSM 6.0.2 Update 5

Posted: 01 Dec 2016, 13:29
by Mojito71
Thank you for your replys :)

The problem seems to be the same, thats the reason for opening filebot node in a tab. If I use the IFrame, this is in the developer console:
http://<DDNS ID>.myds.me:5452/auth?_dc=1480598480904 Failed to load resource: net::ERR_CONNECTION_REFUSED
http://<DDNS ID>.myds.me:5452/tasks Failed to load resource: net::ERR_CONNECTION_REFUSED

Its using my DDNS address... I'm not sure if that call(loopback) goes through my router or not. I have not opened these ports for external access, so those calls will not get to the synology

Re: DSM 6.0.2 Update 5

Posted: 01 Dec 2016, 17:34
by rednoah
What does the FileBot Node log say? Click "View Log" in DSM Package Manager.

Re: DSM 6.0.2 Update 5

Posted: 01 Dec 2016, 17:50
by Mojito71

Code: Select all

+ FILEBOT_NODE_HOST=0.0.0.0
+ export FILEBOT_NODE_AUTH=SYNO
+ FILEBOT_NODE_AUTH=SYNO
+ export FILEBOT_NODE_HTTP=YES
+ FILEBOT_NODE_HTTP=YES
+ export FILEBOT_NODE_HTTP_PORT=5452
+ FILEBOT_NODE_HTTP_PORT=5452
+ '[' -r /usr/syno/etc/certificate/system/default/privkey.pem ']'
2016-11-30T10:47:47+0100 + export FILEBOT_NODE_HTTPS=YES
+ FILEBOT_NODE_HTTPS=YES
+ export FILEBOT_NODE_HTTPS_PORT=5453
+ FILEBOT_NODE_HTTPS_PORT=5453
+ export FILEBOT_NODE_HTTPS_KEY=/usr/syno/etc/certificate/system/default/privkey.pem
+ FILEBOT_NODE_HTTPS_KEY=/usr/syno/etc/certificate/system/default/privkey.pem
+ export FILEBOT_NODE_HTTPS_CRT=/usr/syno/etc/certificate/system/default/cert.pem
+ FILEBOT_NODE_HTTPS_CRT=/usr/syno/etc/certificate/system/default/cert.pem
+ export USER=admin
+ USER=admin
2016-11-30T10:47:47+0100 ++ free
2016-11-30T10:47:47+0100 ++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
2016-11-30T10:47:47+0100 + export JAVA_OPTS=-Xmx706m
+ JAVA_OPTS=-Xmx706m
+ export FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ export FILEBOT_CMD=filebot
+ FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ FILEBOT_CMD_CWD=/volume1
2016-11-30T10:47:47+0100 ++ id -u admin
2016-11-30T10:47:47+0100 + export FILEBOT_CMD_UID=1024
+ FILEBOT_CMD_UID=1024
2016-11-30T10:47:47+0100 ++ grep administrators
2016-11-30T10:47:47+0100 ++ cut -d: -f3
2016-11-30T10:47:47+0100 ++ cat /etc/group
2016-11-30T10:47:47+0100 + export FILEBOT_CMD_GID=101
+ FILEBOT_CMD_GID=101
+ export FILEBOT_NODE_CLIENT=
+ FILEBOT_NODE_CLIENT=
+ cd ''
+ node --max_executable_size=16 --optimize_for_size --use_idle_notification server/app.js
2016-11-30T10:47:49+0100 ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  FILEBOT_NODE_HTTPS_KEY: '/usr/syno/etc/certificate/system/default/privkey.pem',
  TERM: 'linux',
  FILEBOT_CMD_UID: '1024',
  OLDPWD: '/volume1/@appstore/filebot-node',
  JAVA_OPTS: '-Xmx706m',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  FILEBOT_NODE_HTTPS_PORT: '5453',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  FILEBOT_CMD_GID: '101',
  PWD: '/volume1/@appstore/filebot-node',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTPS_CRT: '/usr/syno/etc/certificate/system/default/cert.pem',
  SHLVL: '1',
  FILEBOT_CMD: 'filebot',
  UPSTART_INSTANCE: '',
  FILEBOT_NODE_HTTPS: 'YES',
  FILEBOT_NODE_HTTP_PORT: '5452',
  FILEBOT_NODE_AUTH: 'SYNO',
  UPSTART_JOB: 'filebot-node',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_CLIENT: '',
  _: '/usr/local/bin/node' }
2016-11-30T10:47:49+0100 USER { UID: 1024, GID: 101 }
2016-11-30T10:47:49+0100 filebot-node listening at http://0.0.0.0:5452
2016-11-30T10:47:49+0100 filebot-node listening at https://0.0.0.0:5453
2016-11-30T18:14:39+0100 + export FILEBOT_NODE_HOST=0.0.0.0
+ FILEBOT_NODE_HOST=0.0.0.0
+ export FILEBOT_NODE_AUTH=SYNO
+ FILEBOT_NODE_AUTH=SYNO
+ export FILEBOT_NODE_HTTP=YES
+ FILEBOT_NODE_HTTP=YES
+ export FILEBOT_NODE_HTTP_PORT=5452
+ FILEBOT_NODE_HTTP_PORT=5452
+ '[' -r /usr/syno/etc/certificate/system/default/privkey.pem ']'
+ export FILEBOT_NODE_HTTPS=YES
+ FILEBOT_NODE_HTTPS=YES
+ export FILEBOT_NODE_HTTPS_PORT=5453
+ FILEBOT_NODE_HTTPS_PORT=5453
+ export FILEBOT_NODE_HTTPS_KEY=/usr/syno/etc/certificate/system/default/privkey.pem
+ FILEBOT_NODE_HTTPS_KEY=/usr/syno/etc/certificate/system/default/privkey.pem
+ export FILEBOT_NODE_HTTPS_CRT=/usr/syno/etc/certificate/system/default/cert.pem
+ FILEBOT_NODE_HTTPS_CRT=/usr/syno/etc/certificate/system/default/cert.pem
+ export USER=admin
+ USER=admin
++ awk -vm=1024 -vp=0.7 '/Mem:/ {printf "-Xmx%dm", ($2*p)/m; exit}'
++ free
2016-11-30T18:14:39+0100 + export JAVA_OPTS=-Xmx706m
+ JAVA_OPTS=-Xmx706m
+ export FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ FILEBOT_TASK_CMD=/usr/local/filebot-node/task
+ export FILEBOT_CMD=filebot
+ FILEBOT_CMD=filebot
+ export FILEBOT_CMD_CWD=/volume1
+ FILEBOT_CMD_CWD=/volume1
++ id -u admin
+ export FILEBOT_CMD_UID=1024
+ FILEBOT_CMD_UID=1024
2016-11-30T18:14:39+0100 ++ cut -d: -f3
++ cat /etc/group
++ grep administrators
+ export FILEBOT_CMD_GID=101
+ FILEBOT_CMD_GID=101
+ export FILEBOT_NODE_CLIENT=
+ FILEBOT_NODE_CLIENT=
+ cd ''
+ node --max_executable_size=16 --optimize_for_size --use_idle_notification server/app.js
2016-11-30T18:14:51+0100 ENVIRONMENT { FILEBOT_TASK_CMD: '/usr/local/filebot-node/task',
  FILEBOT_NODE_HTTPS_KEY: '/usr/syno/etc/certificate/system/default/privkey.pem',
  TERM: 'linux',
  FILEBOT_CMD_UID: '1024',
  OLDPWD: '/volume1/@appstore/filebot-node',
  JAVA_OPTS: '-Xmx706m',
  USER: 'admin',
  FILEBOT_CMD_CWD: '/volume1',
  FILEBOT_NODE_HTTPS_PORT: '5453',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  FILEBOT_CMD_GID: '101',
  PWD: '/volume1/@appstore/filebot-node',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTPS_CRT: '/usr/syno/etc/certificate/system/default/cert.pem',
  SHLVL: '1',
  FILEBOT_CMD: 'filebot',
  UPSTART_INSTANCE: '',
  FILEBOT_NODE_HTTPS: 'YES',
  FILEBOT_NODE_HTTP_PORT: '5452',
  FILEBOT_NODE_AUTH: 'SYNO',
  UPSTART_JOB: 'filebot-node',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_CLIENT: '',
  _: '/usr/local/bin/node' }
2016-11-30T18:14:52+0100 USER { UID: 1024, GID: 101 }
2016-11-30T18:14:52+0100 filebot-node listening at http://0.0.0.0:5452
2016-11-30T18:14:52+0100 filebot-node listening at https://0.0.0.0:5453
<

Re: DSM 6.0.2 Update 5

Posted: 01 Dec 2016, 18:17
by rednoah
According the FileBot Node logs, nobody ever opened the FileBot Node WebUI with valid DSM login credentials. Try fully logging out of your DSM and clearing all cache and cookies and the logging in DSM again and then running FileBot Node from within DSM.

Maybe the DSM update broke things? I don't know, and I won't have access to my DSM for the next few weeks, so there's little I can do for now.
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited