crashes again and again with xpra and docker

Support for unRAID and docker container users
Post Reply
Anonymousfay
Posts: 4
Joined: 05 Sep 2024, 13:40

crashes again and again with xpra and docker

Post by Anonymousfay »

Hey

I use Filebot via XPRA with Docker: https://github.com/filebot/filebot-dock ... lebot-xpra
The problem is that Filebot unfortunately runs absolutely badly and crashes again and again, especially if you want to edit more than 10 files at the same time.
Are there any ways to improve the performance?

Here are some logs from the container:

Code: Select all

filebot-xpra  | (zenity:438): GVFS-RemoteVolumeMonitor-WARNING **: 09:39:24.271: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
filebot-xpra  | Gtk-Message: 09:39:24.418: GtkDialog mapped without a transient parent. This is discouraged.
filebot-xpra  | Activate License [P62982178] on [Tue Apr 29 09:39:43 UTC 2025]
filebot-xpra  | 19 files renamed.
filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: egl: failed to create dri2 screen
filebot-xpra  | 
filebot-xpra  | (zenity:667): GVFS-RemoteVolumeMonitor-WARNING **: 09:39:50.648: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
filebot-xpra  | Gtk-Message: 09:39:51.222: GtkDialog mapped without a transient parent. This is discouraged.
filebot-xpra  | Killed
filebot-xpra  | 2025-04-29 09:40:59,394 child 'filebot' with pid 125 has terminated
filebot-xpra  | 2025-04-29 09:40:59,395 all children have exited and --exit-with-children was specified, exiting
filebot-xpra  | 2025-04-29 09:40:59,395 X11 seamless server is terminating
filebot-xpra  | 2025-04-29 09:40:59,429 Disconnecting client 10.90.10.1:40611:
filebot-xpra  | 2025-04-29 09:40:59,429  server shutdown
filebot-xpra  | 2025-04-29 09:40:59,433 HTML5 client 1 disconnected.
filebot-xpra  | 2025-04-29 09:40:59,444 closing tcp socket 0.0.0.0:5454
filebot-xpra  | 2025-04-29 09:40:59,445 killing xvfb with pid 23
filebot-xpra  | 2025-04-29 09:40:59,448 session directory '/tmp/xpra/0' was not removed
filebot-xpra  | 2025-04-29 09:40:59,448  because it still contains some files:
filebot-xpra  | 2025-04-29 09:40:59,448  'filebot.pid'
filebot-xpra  | 2025-04-29 09:41:00,458 created tcp socket '0.0.0.0:5454'
filebot-xpra  | _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
filebot-xpra  | 2025-04-29 09:41:01,827 Warning: missing 'audio' module
filebot-xpra  | 2025-04-29 09:41:01,827  for Python 3.12.7 (main, Feb  4 2025, 14:46:03) [GCC 14.2.0]
filebot-xpra  | 2025-04-29 09:41:02,092 xvfb pid 23
filebot-xpra  | 2025-04-29 09:41:02,164 using 'watchdog library'
filebot-xpra  | 2025-04-29 09:41:02,344 5.8GB of system memory
filebot-xpra  | 2025-04-29 09:41:02,905 OpenGL is supported on display ':0'
filebot-xpra  | 2025-04-29 09:41:02,905  using 'llvmpipe (LLVM 19.1.1, 256 bits)' renderer
filebot-xpra  | 2025-04-29 09:41:02,906 started command `filebot` with pid 125
filebot-xpra  | 2025-04-29 09:41:03,927 xpra is ready.
filebot-xpra  | 2025-04-29 09:41:05,430  unable to publish mDNS record for ssh connections
filebot-xpra  | 2025-04-29 09:41:07,071 xpra X11 seamless server version 6.2.5-r0
filebot-xpra  | 2025-04-29 09:41:07,072  uid=1000 (ubuntu), gid=1000 (ubuntu)
filebot-xpra  | 2025-04-29 09:41:07,072  running with pid 15 on Linux Ubuntu 24.10 oracular
filebot-xpra  | 2025-04-29 09:41:07,072  cpython 3.12
filebot-xpra  | 2025-04-29 09:41:07,072  connected to X11 display :0 with 24 bit colors
filebot-xpra  | 2025-04-29 09:48:08,694 Handshake complete; enabling connection
filebot-xpra  | 2025-04-29 09:48:08,702 HTML5 Mac OSX Chrome client version 17
filebot-xpra  | 2025-04-29 09:48:08,705 setting keyboard layout to 'de'
filebot-xpra  | 2025-04-29 09:48:08,749  client root window size is 1920x869
filebot-xpra  | 2025-04-29 09:48:08,749   HTML (508x230 mm - DPI: 96x96)
filebot-xpra  | 2025-04-29 09:48:09,252 server virtual display now set to 1920x869
filebot-xpra  | 2025-04-29 09:48:09,256  automatic picture encoding enabled, also available:
filebot-xpra  | 2025-04-29 09:48:09,257   rgb24, rgb32, png, webp, jpeg
filebot-xpra  | 2025-04-29 09:48:09,272 DPI set to 96 x 96
filebot-xpra  | 2025-04-29 09:48:28,132 server virtual display now set to 1145x782
filebot-xpra  | 2025-04-29 09:48:28,132 received updated display dimensions
filebot-xpra  | 2025-04-29 09:48:28,132 client display size is 1145x782
filebot-xpra  | 2025-04-29 09:48:28,132   HTML (303x207 mm - DPI: 96x96)
filebot-xpra  | 2025-04-29 09:48:28,142 DPI set to 96 x 96
filebot-xpra  | 2025-04-29 09:48:28,143 sent updated screen size to 1 clients: 1145x782 (max 8192x4096)
filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: egl: failed to create dri2 screen
filebot-xpra  | 
filebot-xpra  | (zenity:411): GVFS-RemoteVolumeMonitor-WARNING **: 09:48:44.217: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
filebot-xpra  | Gtk-Message: 09:48:44.367: GtkDialog mapped without a transient parent. This is discouraged.
filebot-xpra  | 2025-04-29 09:49:04,915 server virtual display now set to 1920x869
filebot-xpra  | 2025-04-29 09:49:04,915 received updated display dimensions
filebot-xpra  | 2025-04-29 09:49:04,915 client display size is 1920x869
filebot-xpra  | 2025-04-29 09:49:04,915   HTML (508x230 mm - DPI: 96x96)
filebot-xpra  | 2025-04-29 09:49:04,926 DPI set to 96 x 96
filebot-xpra  | 2025-04-29 09:49:04,927 sent updated screen size to 1 clients: 1920x869 (max 8192x4096)
filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: egl: failed to create dri2 screen
filebot-xpra  | 
filebot-xpra  | (zenity:591): GVFS-RemoteVolumeMonitor-WARNING **: 09:49:16.251: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
filebot-xpra  | Gtk-Message: 09:49:16.333: GtkDialog mapped without a transient parent. This is discouraged.
filebot-xpra  | Killed
filebot-xpra  | 2025-04-29 09:49:48,390 child 'filebot' with pid 125 has terminated
filebot-xpra  | 2025-04-29 09:49:48,391 all children have exited and --exit-with-children was specified, exiting
filebot-xpra  | 2025-04-29 09:49:48,407 X11 seamless server is terminating
filebot-xpra  | 2025-04-29 09:49:48,437 Disconnecting client 10.90.10.1:29622:
filebot-xpra  | 2025-04-29 09:49:48,437  server shutdown
filebot-xpra  | 2025-04-29 09:49:48,443 HTML5 client 1 disconnected.
filebot-xpra  | 2025-04-29 09:49:48,465 closing tcp socket 0.0.0.0:5454
filebot-xpra  | 2025-04-29 09:49:48,466 killing xvfb with pid 23
filebot-xpra  | 2025-04-29 09:49:48,469 session directory '/tmp/xpra/0' was not removed
filebot-xpra  | 2025-04-29 09:49:48,469  because it still contains some files:
filebot-xpra  | 2025-04-29 09:49:48,469  'filebot.pid'
And here the compose i used to deploy filebot:

Code: Select all

services:
  filebot:
    container_name: filebot-xpra
    image: rednoah/filebot:xpra
    restart: unless-stopped
    volumes:
      - /docker/filebot:/data:rw
      - /mnt/truenas/jdownloader/:/jdownloader:rw
    ports:
      - 5454:5454
Thank you very much for any help.
Top
User avatar
rednoah
The Source
Posts: 24009
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:
Contact rednoah

Re: crashes again and again with xpra and docker

Post by rednoah »

I notably don't get any of these error messages:

Code: Select all

filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: DRI3: Screen seems not DRI3 capable
filebot-xpra  | libEGL warning: egl: failed to create dri2 screen

Code: Select all

filebot-xpra  | (zenity:667): GVFS-RemoteVolumeMonitor-WARNING **: 09:39:50.648: remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor is not supported
filebot-xpra  | Gtk-Message: 09:39:51.222: GtkDialog mapped without a transient parent. This is discouraged.
Unfortunately, I've never seen these error message before so I also have no clue. You could post hardware and software details. There might be a clue there, or not. Might be helpful for the next guy as well.




:arrow: As an alternative to using a remote desktop container on your NAS, I would recommend using FileBot from your Desktop to then rename files remotely via network shares. The usability is much better and there's no notable downside if the local network is fast enough which would typically be the case.
:idea: Please read the FAQ and How to Request Help.
Top
Anonymousfay
Posts: 4
Joined: 05 Sep 2024, 13:40

Re: crashes again and again with xpra and docker

Post by Anonymousfay »

I have just found out that it could be due to insufficient RAM. Then the service crashes. Is there a way to use the Docker command to somehow restrict the Java heap to -Xmx512m via an environment variable?
:arrow: As an alternative to using a remote desktop container on your NAS, I would recommend using FileBot from your Desktop to then rename files remotely via network shares. The usability is much better and there's no notable downside if the local network is fast enough which would typically be the case.
This wont work because its really slow as the media are on a remote server and filebot need to calculate the media type and quality as i use it for the naming.
Top
User avatar
rednoah
The Source
Posts: 24009
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:
Contact rednoah

Re: crashes again and again with xpra and docker

Post by rednoah »

Anonymousfay wrote: ↑29 Apr 2025, 10:25 I have just found out that it could be due to insufficient RAM. Then the service crashes. Is there a way to use the Docker command to somehow restrict the Java heap to -Xmx512m via an environment variable?
You can set the container memory limit via the --memory option and the JVM memory limit via the JAVA_OPTS environment variable:

Shell: Select all

docker run --rm -it -v /mnt:/mnt -v data:/data -p 5454:5454 --memory 2g -e JAVA_OPTS="-Xmx512m" rednoah/filebot:xpra
Please report back with your findings.
:idea: Please read the FAQ and How to Request Help.
Top
Anonymousfay
Posts: 4
Joined: 05 Sep 2024, 13:40

Re: crashes again and again with xpra and docker

Post by Anonymousfay »

So i added more ram and it works now without a crash. But would also like to limit Java.

If i add the JAVA_OPTS Variable the i get an error:

Code: Select all

filebot-jlesage  | [filebot-info] Error: Could not find or load main class '-Xmx512m'
filebot-jlesage  | [filebot-info] Caused by: java.lang.ClassNotFoundException: '-Xmx512m'
filebot-jlesage  | [supervisor  ] service 'filebot-info' exited (with status 1).
filebot-jlesage  | [supervisor  ] service 'filebot-info' failed to be started: termined with error.
Top
User avatar
rednoah
The Source
Posts: 24009
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:
Contact rednoah

Re: crashes again and again with xpra and docker

Post by rednoah »

Anonymousfay wrote: ↑29 Apr 2025, 10:48

Code: Select all

filebot-jlesage  | [filebot-info] Error: Could not find or load main class '-Xmx512m'
filebot-jlesage  | [filebot-info] Caused by: java.lang.ClassNotFoundException: '-Xmx512m'
filebot-jlesage  | [supervisor  ] service 'filebot-info' exited (with status 1).
filebot-jlesage  | [supervisor  ] service 'filebot-info' failed to be started: termined with error.
:?: What is your YAML descriptor?



The docker -e option:

Shell: Select all

-e JAVA_OPTS="-Xmx512m"
expressed as docker compose YAML might look like this:

yaml: Select all

services:
  filebot-xpra:
    environment:
      JAVA_OPTS: "-Xmx512m"
:idea: Please read the FAQ and How to Request Help.
Top
Post Reply

Return to “unRAID & docker”