[FileBot Node] DSM 6.2.4 authentication workaround

[rednoah]

Looks like there might be more than one result:

Code: Select all

$ find / -name filebot-node.log 2> /dev/null
/var/log/packages/filebot-node.log
/volume1/@appstore/filebot-node/filebot-node.log

I meant the second one:

Code: Select all

sudo cat /volume1/@appstore/filebot-node/filebot-node.log

[davemccreath]

And here is the result from 'sudo cat /volume1/@appstore/filebot-node/filebot-node.log'

[davemccreath]

Ahh....I may have found the reason for not seeing the newly opened FileBot page when opening FileBot from within DSM. I use my Quickconnect ID to log into DSM. Just switched to using the local IP address and that opens FileBot in a new page and I can see all the settings. I've updated the input/output folders but when I press Execute I get an 'Unauthorised' error, see below:

[rednoah]

You cannot use QuickConnect anymore, since FileBot Node is now running independently of DSM. You will still have to log into DSM first. You must access DSM and FileBot Node via the same IP, as to create the DSM authentication cookie for that site in your browser.


If you get an Unauthorized error in the WebUI, then you may find additional information about the blocked request in the filebot-node.log file.

[davemccreath]

Thank you. I'll have a play around and see if I can get FileBot back up and running again.

[davemccreath]

rednoah.

Well all back up and running well.

Have you any idea of what the new 'User Defined Script' should be to run FileBot from within the DSM Task Scheduler?

I've tried the following without success:

/volume1/@appstore/filebot/filebot.sh
/usr/local/filebot-node/task 0 ((worked with the previous version))

Regards, as ever

Dave

[rednoah]

Click Execute ➔ Schedule and then copy the command from there:

Code: Select all

filebot-node-task 0

[davemccreath]

Perfect.

Once again, thank you.

Dave

[jonc]

I'm trying out the 0.4.0 beta spk


I followed the instructions to give the internal FileBot user access to the relevant directories/shared folder, but still getting a java.nio.file.AccessDeniedException

Any ideas?

(edit: I can hack it by giving all users access to the shared folder)

[rednoah]

I followed the instructions to give the internal FileBot user access to the relevant directories/shared folder, but still getting a java.nio.file.AccessDeniedException

Use Tools ➔ System Information to check which user filebot is called as. Then make sure that that user / group has the appropriate permissions. Note that calling filebot via FileBot Node / Synology Scheduler / SSH / etc may result in filebot being called as a different user depending on the context.

[tommygunz747]

Hey there,

is there any chance to fix this problem over an official update ? Sorry but its to complicated for me to fix it like given in option A or B.

[rednoah]

You could try this:

FileBot Node for Synology DSM 6.2.4 is available for testing: filebot-node-0.4.0-noarch.spk


You may need to uninstall older versions of FileBot Node, before manually installing the latest beta package. Upgrading the package may result in broken permissions caused by previously created user data.


FileBot Node is no longer integrated into the DSM nginx service. You therefore cannot use Quick Connect to access the FileBot Node WebUI.

[tommygunz747]

Now its working fine again! Thank you !

[drsteveplatt]

I can report that I have installed the 0.4.0 beta for the 6.2.4 filebot and was able to get it running.
Thank you, rednoah!

[aglyons]

@rednoah - my syno 'admin' account is disabled and FBN runs fine in my case, just for the record.

@Aglyons - That is the first I heard about the MODS tools, thanks for that. Is there any reason you wouldn't just schedule filebot to run a task every 5-10 mins so you don't have to hassle with running it manually? I am just curious of your usage scenario.

@colpepe - My use case really is I don't want it to run in the bg when I don't really need it to. I have a 1515+ and the CPU spikes every time FB runs. Another reason is sometimes FB just doesn't make the right match and I have to rename the file slightly for it to make a match on TMDB. I really only need it to run maybe once or twice a day, that's it so scheduling every 15 min is a waste of cycles IMO. That's when I came across MODs. One-click run makes things a bit easier to manage especially since I am supporting my dad's setup as well. If there's any way I can make things simpler for him the better my life ends up.

@rednoah - As for nixing the default admin account. I did that on day one when I bought the system years ago, well before I installed FB or Node. Still, I always get the 'run as root' message every time FB runs. It always worked so I never thought it a concern.

[jay960]

Hello,

I also have problem with DSM 6.2.4
I have installed the FileBot beta 0.4.0 but when I click on FileBot Node I have a page that load with my NAS IP address and port 5452 and I get this message
{"success":false,"error":"Error: ENOENT: no such file or directory, uv_cwd"}

Here is my log :


//EDIT//

Sorry, had to simply restart my NAS...

[norrington]

any update yet or planned? the workaround does not work for me

[Phobos]

Hi there,

I hope I'm posting in the right place. I too experienced the breakage as a result of the DSM update. I installed 4.9.3 and it mostly works but I am experiencing a problem that I never had before with FileBot. After it does its thing and moves my files from one folder into a Plex formatted media folder, Plex doesn't seem to recognize most of the media files. Doing the Plex dance of moving the files out and then back in, cleaning the bundles, and optimizing the database seems to solve the problem; but of course that takes away from some of the "set it and forget it" point of Filebot. If there's something I'm doing or not doing, please let me know. I'm a bit of a noob so if it's super technical, I may struggle with it I'm afraid. Many thanks for any assistance you can provide.

[aglyons]

is a final v0.4.0 going to be pushed to the community repository?

I've been holding off updating to DSM6.2.4 so things don't break on me.

[rednoah]

v0.4.0 going to be pushed to the community repository?

Not planned for now, since that would break things for pre-DSM 6.2.4 users.

But if you prefer to install via the package source, then you can add this package source instead for the latest package:
https://raw.githubusercontent.com/fileb ... /syno.json

[xIntenso]

v0.4.0 going to be pushed to the community repository?

Not planned for now, since that would break things for pre-DSM 6.2.4 users.

But if you prefer to install via the package source, then you can add this package source instead for the latest package:
https://raw.githubusercontent.com/fileb ... /syno.json

This worked like a charm for me!
Remember to uninstall the old version of Node before upgrading, because I forgot to, and I got permission errors until I did a full uninstall and reinstall.

[rednoah]

FileBot Node 0.4.1 for DSM 6.2.4 is now available for testing:
https://github.com/filebot/filebot-node/releases

[davemccreath]

rednoah

System is DS218+ using DSM 6.2.4, all up to date. FileBot up and working fine with FileBot Node 0.4.0.

Uninstalled FileBot Node 0.4.0 and installed 'filebot-node-0.4.1.spk'. Rebooted and it came back with 'Unauthorised', permissions all OK. Unistalled 0.4.1 and rolled back to 0.4.0 ('filebot-node-0.4.0-noarch.spk') all fine again.

Did not work my end.

Any ideas?

Dave

[rednoah]

What does the log say?

Code: Select all

cat /var/packages/filebot-node/target/filebot-node.log

[davemccreath]

Just uninstalled FileBot 0.4.0, rebooted and installed Filebot 0.4.1. Ran it and unauthorised again.

Log File below:

Code: Select all

ENVIRONMENT { SYNOPKG_DSM_LANGUAGE: 'def',
  FILEBOT_TASK_CMD: 'filebot-node-task',
  TERM: 'vt102',
  FILEBOT_CMD_UID: '0',
  SYNOPKG_TEMP_LOGFILE: '/tmp/synopkgmgr.log-filebot-node',
  SYNOPKG_DSM_ARCH: 'apollolake',
  OLDPWD: '/',
  JAVA_OPTS: '',
  FILEBOT_CMD_CWD: '/volume1',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  SELF: 'filebot-node',
  FILEBOT_CMD_GID: '0',
  PWD: '/var/packages/filebot-node/target',
  SYNOPKG_PKGDEST: '/volume1/@appstore/filebot-node',
  FILEBOT_NODE_HOST: '127.0.0.1',
  SYNOPKG_PKGVER: '0.4.1',
  SYNOPKG_DSM_VERSION_MINOR: '2',
  SHLVL: '3',
  FILEBOT_CMD: 'filebot',
  SYNOPKG_DSM_VERSION_BUILD: '25556',
  UPSTART_INSTANCE: '',
  UPSTART_EVENTS: 'syno.pkgctl.pkgstart',
  SYNOPKG_PKGNAME: 'filebot-node',
  FILEBOT_NODE_HTTP_PORT: '5452',
  SYNOPKG_DSM_VERSION_MAJOR: '6',
  SYNOPKG_PKGDEST_VOL: '/volume1',
  FILEBOT_NODE_AUTH: 'SYNO',
  UPSTART_JOB: 'pkgctl-filebot-node',
  FILEBOT_NODE_DATA: '/var/packages/filebot-node/target/data',
  FILEBOT_NODE_HTTP: 'YES',
  _: '/usr/local/bin/node' }
USER { UID: 0, GID: 0 }
filebot-node listening at http://127.0.0.1:5452
/usr/syno/synoman/webman/authenticate.cgi
{ HTTP_COOKIE: 'id=XYZ',
  REMOTE_ADDR: '192.168.1.2',
  HTTP_X_SYNO_TOKEN: undefined }

Dave