Different behaviors on command line & node

Support for Synology NAS, QNAP NAS and other Embedded Linux systems
Post Reply
frikeando
Posts: 8
Joined: 03 Mar 2016, 23:07

Different behaviors on command line & node

Post by frikeando »

Hi,

I finally got Node running on DSM6. When I run Node, I get this:

Code: Select all

filebot -script 'fn:amc' /volume1/Descargas/ --output /volume1/video/Peliculas/ --action hardlink -non-strict --conflict auto --lang es --def 'ut_label=movie' 'artwork=y' 'clean=y' 'skipExtract=y' 'minFileSize=500000000'  'excludeList=.excludes' --log all --log-file '/volume1/@appstore/filebot-node/data/filebot.log'

------------------------------------------

Locking /volume1/@appstore/filebot-node/data/filebot.log
Run script [fn:amc] at [Wed Mar 30 15:01:34 CEST 2016]
Parameter: ut_label = movie
Parameter: artwork = y
Parameter: clean = y
Parameter: skipExtract = y
Parameter: minFileSize = 500000000
Parameter: excludeList = .excludes
Argument: /volume1/Descargas
Using excludes: /volume1/video/Peliculas/.excludes (20092)
Ignore hidden folder: /volume1/Descargas/@eaDir
Ignore hidden folder: /volume1/Descargas/.TemporaryItems
No files selected for processing
Failure (°_°)

------------------------------------------

[Process error]
When I ssh into the Sinology and I copy/paste the command above, I get this error:

Code: Select all

SEVERE: Unexpected error during startup
java.nio.file.AccessDeniedException: /volume1/@appstore/filebot-node/data/filebot.log
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177)
	at java.nio.channels.FileChannel.open(FileChannel.java:287)
	at java.nio.channels.FileChannel.open(FileChannel.java:335)
	at net.filebot.Main.main(Main.java:123)
If I type "sudo su -" and run the command again, it works.

My questions are:
1.- Why Node is not working? I assume it is because folder permissions, but I don't know how to solve it.
2.- Why on a terminal window, with a non-root user, Filbert does not work?

Thanks in advance.
User avatar
rednoah
The Source
Posts: 23930
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Different behaviors on command line & node

Post by rednoah »

1.
If the amc script can't find any files (assuming not because of minFileSize, excludeList, etc) then it's most likely a permission issue. Folders that cannot be accessed will appear empty.

2.
Permission issues. Please find a solution via Google and report back to us what you did to fix it.
:idea: Please read the FAQ and How to Request Help.
frikeando
Posts: 8
Joined: 03 Mar 2016, 23:07

Re: Different behaviors on command line & node

Post by frikeando »

rednoah wrote:1.
If the amc script can't find any files (assuming not because of minFileSize, excludeList, etc) then it's most likely a permission issue. Folders that cannot be accessed will appear empty.

2.
Permission issues. Please find a solution via Google and report back to us what you did to fix it.
What user does FileBot uses to do its magic? Root?
User avatar
rednoah
The Source
Posts: 23930
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Different behaviors on command line & node

Post by rednoah »

FileBot Node Service is running as root (as any other Synology package). FileBot (which is what's not working here) is always called as admin.

FileBot Node -> View Log does tell you what user:group FileBot Node is calling the filebot commands as.
:idea: Please read the FAQ and How to Request Help.
frikeando
Posts: 8
Joined: 03 Mar 2016, 23:07

Re: Different behaviors on command line & node

Post by frikeando »

rednoah wrote:FileBot Node Service is running as root (as any other Synology package). FileBot (which is what's not working here) is always called as admin.

FileBot Node -> View Log does tell you what user:group FileBot Node is calling the filebot commands as.
But I have admin user disabled. Instead of that, I have created my own admin user. Can that be a problem?
frikeando
Posts: 8
Joined: 03 Mar 2016, 23:07

Re: Different behaviors on command line & node

Post by frikeando »

I tried to fix permissions, but all i have is failure...

Code: Select all

filebot -script 'fn:amc' /volume1/video/Series/Daredevil --output /volume1/video/ --action hardlink -non-strict --conflict skip --lang es --def 'artwork=y' 'clean=y' 'skipExtract=y' 'minFileSize=500000000' 'excludeList=.excludes' --log info --log-file '/volume1/@appstore/filebot-node/data/filebot.log'

------------------------------------------

[HARDLINK] Rename [/volume1/video/Series/Daredevil/Daredevil S1E01.mkv] to [/volume1/video/TV Shows/Marvel's Daredevil/Season 01/Marvel's Daredevil - S01E01 - En el ring.mkv]
[HARDLINK] Failed to rename [/volume1/video/Series/Daredevil/Daredevil S1E01.mkv]
AccessDeniedException: /volume1/video/TV Shows/Marvel's Daredevil
Finished without processing any files

------------------------------------------

[Process error]
Post Reply