FileBot Node Failed to write xattr key

Support for Ubuntu and other Desktop Linux distributions
Post Reply
dyl4n20
Posts: 10
Joined: 10 Oct 2023, 23:16

FileBot Node Failed to write xattr key

Post by dyl4n20 »

Hello,

Host: Ubuntu 22.04
running on docker with portainer please see stack below.

Here are the error messages I am seeing in logs. although everything does seem to be functioning properly.
Failed to write xattr key: net.filebot.metadata:
Failed to write xattr key: net.filebot.filename:

Code: Select all

filebot-node:
    container_name: filebot-node
    image: rednoah/filebot:node
    restart: always
    depends_on:
        pdrcrd:
          condition: service_healthy  
    volumes:
      - /home/Configs/filebot-node-config:/data

      - /media/data/realdebrid:/realdebrid
      - /media/data/organized2:/organized2
    ports:
      - 5452:5452
    environment:
      - PUID=1000
      - PGID=1000  
      - FILEBOT_NODE_AUTH=BASIC
      - FILEBOT_NODE_AUTH_USER=xxxx
      - FILEBOT_NODE_AUTH_PASS=xxxx
dyl4n20
Posts: 10
Joined: 10 Oct 2023, 23:16

Re: FileBot Node Failed to write xattr key

Post by dyl4n20 »

How can This be achieved in FileBot Node docker container.

I ran the following

Code: Select all

filebot-script fn:properties --def net.filebot.xattr.store=.xattr in cmd promt
and got the following output but i believe this only applied to the desktop application and not filebot node

Code: Select all

Load user-defined System Properties
* Read /home/user/.filebot/system.properties
Update user-defined System Properties
* Set useExtendedFileAttributes = false
Store user-defined System Properties
* Write /home/user/.filebot/system.properties
#FileBot System Properties
#Sat Oct 21 17:29:17 PDT 2023
useExtendedFileAttributes=false

Done ヾ(@⌒ー⌒@)ノ

Code: Select all

Failed to write xattr key: net.filebot.metadata: /organized2/Movies/movie name: Error writing extended attribute 'net.filebot.metadata': Operation not supported
Failed to write xattr key: net.filebot.filename: /organized2/Movies/movie name: Error writing extended attribute 'net.filebot.filename': Operation not supported
I did "find / -name '*.args' 2> /dev/null" and added "net.filebot.xattr.store=.xattr" under "--def" I also tried "useExtendedFileAttributes=false"
still the error persists.

Code: Select all

-script
fn:amc
/debrid
--output
/organized
--action
symlink
-non-strict
--order
Airdate
--conflict
auto
--lang
en
--def
useExtendedFileAttributes=false
music=y
unsorted=y
subtitles=eng
clean=y
skipExtract=y
ignore=games|books
seriesFormat=/media/data/organized/{plex.id}
animeFormat=/media/data/organized/{plex.id}
movieFormat=/media/data/organized/{plex.id}
movieDB=TheMovieDB
seriesDB=TheTVDB
animeDB=AniDB
excludeList=.excludes
--apply
refresh
--log
all
--log-file
/data/filebot/node/filebot.log
after making that change and restarting filebot node i see this in the logs at "execute". I dont see it adding "useExtendedFileAttributes=false" or "net.filebot.xattr.store=.xattr"

Code: Select all

filebot -script 'fn:amc' /realdebrid --output /organized2 --action symlink -non-strict --order Airdate --conflict replace --lang en --def 'music=y' 'unsorted=y' 'skipExtract=y' 'ignore=games|books' 'seriesFormat=/organized2/{plex.id}' 'animeFormat=/organized2/{plex.id} ' 'movieFormat=/organized2/{plex.id}' 'movieDB=TheMovieDB' 'seriesDB=TheTVDB' 'animeDB=AniDB' 'unsortedFormat=Unsorted/{relativeFile}' 'excludeList=excludes.txt' --apply import metadata refresh -no-probe -no-index --log all --log-file '/data/filebot/node/filebot.log'

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

Run script [fn:amc] at [Sun Oct 22 03:14:50 GMT 2023]

[PSA] Important Discussion of Changes effective as of 28 Apr 2023:
https://www.filebot.net/forums/viewtopic.php?t=13406

Parameter: music = y
Parameter: unsorted = y
Parameter: skipExtract = y
Parameter: ignore = games|books
Parameter: seriesFormat = /organized2/{plex.id}
Parameter: animeFormat = /organized2/{plex.id} 
Parameter: movieFormat = /organized2/{plex.id}
Parameter: movieDB = TheMovieDB
Parameter: seriesDB = TheTVDB
Parameter: animeDB = AniDB
Parameter: unsortedFormat = Unsorted/{relativeFile}
Parameter: excludeList = excludes.txt
Argument[0]: /realdebrid
Use excludes: /organized2/excludes.txt
now im realizing im changing the wrong file because i deleted everything i was changing and everything is still the same and working but still producing the error. where can i find the correct location to add
"net.filebot.xattr.store=.xattr" / "useExtendedFileAttributes=false"? ive gone through every file in the config folder and cant find anything.
Last edited by dyl4n20 on 22 Oct 2023, 03:47, edited 1 time in total.
User avatar
rednoah
The Source
Posts: 23002
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: FileBot Node Failed to write xattr key

Post by rednoah »

You would have to run the command inside the container as the correct user, i.e. same filebot command, same environment variables. That said, the properties script merely helps you write a configuration file in the correct location, and you can of course do that yourself manually. The console output properties script call on your host explains how it works:

Code: Select all

* Write /home/user/.filebot/system.properties
#FileBot System Properties
#Sat Oct 21 17:29:17 PDT 2023
useExtendedFileAttributes=false

e.g. system.properties

Code: Select all

useExtendedFileAttributes=false

:!: The system.properties file goes into the application data folder. Due to docker being docker, the correct file path of the system.properties file can be a bit tricky though. Depends on the -v volume mappings and -e environment variables you have configured your container to run with.


:idea: Running filebot via docker and reading the console output might help:

Shell: Select all

docker run --rm -it -v data:/data rednoah/filebot -script fn:properties --def net.filebot.xattr.store=.xattr
:idea: Please read the FAQ and How to Request Help.
dyl4n20
Posts: 10
Joined: 10 Oct 2023, 23:16

Re: FileBot Node Failed to write xattr key

Post by dyl4n20 »

here is output from "sudo docker run --rm -it -v data:/data rednoah/filebot:node -script fn:properties --def net.filebot.xattr.store=.xattr"

Code: Select all

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

Hello! Do you need help Getting Started?

# FAQ
https://www.filebot.net/linux/docker.html

# Read License Key from Console
docker run --rm -it -v data:/data rednoah/filebot --license

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

ENVIRONMENT {
  FILEBOT_NODE_HOME: '/opt/filebot-node',
  SUDO_GID: '0',
  PUSER: 'filebot',
  PGROUP: 'filebot',
  FILEBOT_NODE_SHA256: 'xxxx',
  USER: 'filebot',
  FILEBOT_CMD_UID: '1000',
  HOSTNAME: 'b165ec68a4cd',
  HOME: '/data/filebot',
  OLDPWD: '/',
  FILEBOT_TASK_CMD: '/opt/filebot-node/task',
  FILEBOT_NODE_AUTH: 'NONE',
  PGID: '1000',
  FILEBOT_NODE_HTTP_PORT: '5452',
  SUDO_UID: '0',
  LOGNAME: 'filebot',
  TERM: 'xterm',
  FILEBOT_NODE_VERSION: '0.4.5',
  FILEBOT_VERSION: '5.1.1',
  PATH: '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTP: 'YES',
  LANG: 'C.UTF-8',
  FILEBOT_NODE_URL: 'https://github.com/filebot/filebot-node/releases/download/0.4.5/filebot-node_0.4.5.tar.xz',
  FILEBOT_NODE_DATA: '/data/filebot/node',
  PUID: '1000',
  SUDO_COMMAND: '/opt/bin/run /opt/filebot-node/start -script fn:properties --def net.filebot.xattr.store=.xattr',
  SHELL: '/bin/bash',
  FILEBOT_CMD_GID: '1000',
  SUDO_USER: 'root',
  PWD: '/data/filebot',
  FILEBOT_CMD: 'filebot',
  FILEBOT_NODE_CLIENT: '/opt/filebot-node/client',
  FILEBOT_CMD_CWD: '/'
}
STATUS {
  pid: 41,
  node: 'v18.17.1',
  uptime: '0',
  date: 'Mon, 23 Oct 2023 18:15:29 GMT'
}
USER { UID: 1000, GID: 1000 }
filebot-node listening at http://0.0.0.0:5452/


i still cannot find a config file or properties file anywhere. my docker compose volume looks like this

Code: Select all

volumes:
      - /home/dlone/Configs/filebot-node-config/data:/data
      

here is what i have inside my directory

Code: Select all

dlone@Media-Manager-vm:~$ cd /home/dlone/Configs/filebot-node-config/
dlone@Media-Manager-vm:~/Configs/filebot-node-config$ ls
data
dlone@Media-Manager-vm:~/Configs/filebot-node-config$ cd data
dlone@Media-Manager-vm:~/Configs/filebot-node-config/data$ ls
filebot
dlone@Media-Manager-vm:~/Configs/filebot-node-config/data$ cd filebot
dlone@Media-Manager-vm:~/Configs/filebot-node-config/data/filebot$ ls
cache  history.xml  license.txt  logs  node  tmp
dlone@Media-Manager-vm:~/Configs/filebot-node-config/data/filebot$ cd node
dlone@Media-Manager-vm:~/Configs/filebot-node-config/data/filebot/node$ ls
filebot.log  log  state.json  task
dlone@Media-Manager-vm:~/Configs/filebot-node-config/data/filebot/node$ 
i also tried

Code: Select all

sudo docker run --rm -it -v data:/data rednoah/filebot:node -script fn:properties --def useExtendedFileAttributes=false
here is the output from that

Code: Select all

ENVIRONMENT {
  FILEBOT_NODE_HOME: '/opt/filebot-node',
  SUDO_GID: '0',
  PUSER: 'filebot',
  PGROUP: 'filebot',
  FILEBOT_NODE_SHA256: 'xxxx',
  USER: 'filebot',
  FILEBOT_CMD_UID: '1000',
  HOSTNAME: 'cd1ba3d70b36',
  HOME: '/data/filebot',
  OLDPWD: '/',
  FILEBOT_TASK_CMD: '/opt/filebot-node/task',
  FILEBOT_NODE_AUTH: 'NONE',
  PGID: '1000',
  FILEBOT_NODE_HTTP_PORT: '5452',
  SUDO_UID: '0',
  LOGNAME: 'filebot',
  TERM: 'xterm',
  FILEBOT_NODE_VERSION: '0.4.5',
  FILEBOT_VERSION: '5.1.1',
  PATH: '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTP: 'YES',
  LANG: 'C.UTF-8',
  FILEBOT_NODE_URL: 'https://github.com/filebot/filebot-node/releases/download/0.4.5/filebot-node_0.4.5.tar.xz',
  FILEBOT_NODE_DATA: '/data/filebot/node',
  PUID: '1000',
  SUDO_COMMAND: '/opt/bin/run /opt/filebot-node/start -script fn:properties --def useExtendedFileAttributes=false',
  SHELL: '/bin/bash',
  FILEBOT_CMD_GID: '1000',
  SUDO_USER: 'root',
  PWD: '/data/filebot',
  FILEBOT_CMD: 'filebot',
  FILEBOT_NODE_CLIENT: '/opt/filebot-node/client',
  FILEBOT_CMD_CWD: '/'
}
STATUS {
  pid: 41,
  node: 'v18.17.1',
  uptime: '0',
  date: 'Mon, 23 Oct 2023 18:30:37 GMT'
}
USER { UID: 1000, GID: 1000 }
filebot-node listening at http://0.0.0.0:5452/

Code: Select all

 
 Failed to write xattr key: net.filebot.metadata: /organized2/Movies/movie name/movie name: Error writing extended attribute 'net.filebot.metadata': Operation not supported
Failed to write xattr key: net.filebot.filename: /organized2/Movies/movie name/movie name: Error writing extended attribute 'net.filebot.filename': Operation not supported
User avatar
rednoah
The Source
Posts: 23002
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: FileBot Node Failed to write xattr key

Post by rednoah »

e.g. write configuration file manually from the host:

Shell: Select all

echo "useExtendedFileAttributes=false" > "/home/dlone/Configs/filebot-node-config/data/filebot/system.properties"
:idea: Please read the FAQ and How to Request Help.
dyl4n20
Posts: 10
Joined: 10 Oct 2023, 23:16

Re: FileBot Node Failed to write xattr key

Post by dyl4n20 »

rednoah wrote: 24 Oct 2023, 00:48 e.g. write configuration file manually from the host:

Shell: Select all

echo "useExtendedFileAttributes=false" > "/home/dlone/Configs/filebot-node-config/data/filebot/system.properties"
Viola! that was the answer sir, thank you very much. problem solved.
Post Reply