Memory (gc) error with filebot:watcher docker container
Posted: 06 Mar 2023, 13:35
I've been running filebot watcher as a container for a long time successfully, here is the docker command:
It stopped working recently, from the log it seems there is a memory error:
The machine has GBs of free RAM and SWAP, so there shouldn't be an issue with resource consumption.
I didn't change anything on the system/setup, but the container runs with the :latest tag. Did anything change recently that could cause this?
Code: Select all
docker run \
-it \
--restart always \
--detach \
--name filebot \
-v /mnt/media:/volume1 \
-v /opt/downloads:/volume2 \
-v /opt/filebot/data:/data \
--env INOTIFYWAIT_OPTS="--recursive"
rednoah/filebot:watcher /volume2/extracted/input \
--output /volume1 \
--conflict auto \
--def artwork=n \
--def extras=y \
--def seriesFormat="{kodi}" \
--def plex=server:token \
--action move
Code: Select all
Setting up watches.
Watches established.
[INOTIFY] /volume2/extracted/input/XYZ.mkv
Waiting 300 seconds for changes to settle down...
[0.031s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create worker GC thread. Out of system resources.
I didn't change anything on the system/setup, but the container runs with the :latest tag. Did anything change recently that could cause this?