DSM 6.2.4 permissions problems

Support for Synology NAS, QNAP NAS and other Embedded Linux systems
Post Reply
Predator2912
Posts: 64
Joined: 20 May 2017, 17:51

DSM 6.2.4 permissions problems

Post by Predator2912 »

Hello all,

I have a question about using Filebot(Node).

After I did a DSM update to DSM 6.2.4-25556 update 2, I had to update Filebot(Node) and Java among other things.
I got it to work, but I still have some messages or rather problems with some access rights that I can't get changed.

Filebot-Node Sysinfo says:

Code: Select all

filebot -script 'fn:sysinfo' --log-file '/var/packages/filebot-node/target/data/filebot.log'

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

WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by net.filebot.Main (file:/volume1/@appstore/filebot/jar/filebot.jar)
WARNING: Please consider reporting this to the maintainers of net.filebot.Main
WARNING: System::setSecurityManager will be removed in a future release
FileBot 4.9.4 (r8736)
JNA Native: 6.1.0
MediaInfo: 21.09
Tools: fpcalc/1.5.0 p7zip/9.20 unrar/5.21 ffprobe/3.3.7
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2021-08-02 (r761)
Groovy: 3.0.8
JRE: OpenJDK Runtime Environment 17.0.1
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 4 Core / 2.1 GB Max Memory / 24 MB Used Memory
OS: Linux (amd64)
HW: Linux MadM4x-NAS 3.10.105 #25556 SMP Sat Aug 28 02:13:34 CST 2021 x86_64 GNU/Linux synology_braswell_916+
CPU/MEM: Intel(R) Pentium(R) CPU  N3710  @ 1.60GHz [MemTotal: 8 GB | MemFree: 189 MB | SwapTotal: 7 GB | SwapFree: 7 GB]
STORAGE: ext4 [/] @ 1.0 GB | btrfs [/volume9] @ 11 TB | btrfs [/volume4] @ 6 TB | btrfs [/volume3] @ 7 TB | btrfs [/volume6] @ 10 TB | btrfs [/volume5] @ 8 TB | btrfs [/volume7] @ 5 TB | btrfs [/volume1] @ 2.4 TB | btrfs [/volume8] @ 1.4 TB | btrfs [/volume2] @ 544 GB | ext4 [/volumeUSB3/usbshare] @ 509 GB | ext4 [/volumeUSB2/usbshare] @ 2.4 TB
USER: FileBot
DATA: /volume1/@appstore/filebot/data/106247
Package: SPK
License: FileBot License PX19270080 (Valid-Until: 2070-10-27)
Done ヾ(@⌒ー⌒@)ノ

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

[Process completed]
And in the Info Mail from planned task says:

Code: Select all

Startzeit: Mon, 03 Jan 2022 05:08:17 GMT
Stoppzeit: Mon, 03 Jan 2022 05:08:43 GMT
Aktueller Status: 0 (Normal)
Standardausgabe/Fehler:
tee: /var/packages/filebot-node/target/data/log/1502109085627.log: Permission denied
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by net.filebot.Main (file:/volume1/@appstore/filebot/jar/filebot.jar)
WARNING: Please consider reporting this to the maintainers of net.filebot.Main
WARNING: System::setSecurityManager will be removed in a future release
Run script [fn:amc] at [Mon Jan 03 05:08:39 CET 2022]
My question is now which permissions I have to change so that the following info
tee: /var/packages/filebot-node/target/data/log/1502109085627.log: Permission denied
finally disappears and the filebot script gets the rights to create the logfiles.

The Filebot-Node System internal user rights are entered and so far everything seems to work fine, only the creation of the logfiles does not.
The planned task runs under my own user MadM4x and the deactivation of the admin user and the creation of an own admin user I have not managed because by the deactivation but still already exists in user with the name admin.


Thx a lot
Predator2912
Posts: 64
Joined: 20 May 2017, 17:51

Re: DSM 6.2.4 permissions problems

Post by Predator2912 »

fixed it by myself
User avatar
rednoah
The Source
Posts: 22923
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: DSM 6.2.4 permissions problems

Post by rednoah »

e.g. Remove the file, so the the current user can create the file anew with a new set of default permissions:

Code: Select all

rm -v /var/packages/filebot-node/target/data/log/1502109085627.log
e.g. Add read/write permissions for the current user:

Code: Select all

chmod +rw /var/packages/filebot-node/target/data/log/1502109085627.log

:idea: If it's a prepared task created via FileBot Node, then creating a new one might be the easiest solution.
:idea: Please read the FAQ and How to Request Help.
Post Reply