[unRAID] Filebot Crashing During naming of seasons of TV

Support for unRAID and docker container users
Post Reply
cominatcha1
Posts: 2
Joined: 05 Apr 2023, 19:33

[unRAID] Filebot Crashing During naming of seasons of TV

Post by cominatcha1 »

I run Filebot on unraid, and I'm getting pretty consistent crashes while trying to rename and move seasons of silicon valley

Here are the logs:

Code: Select all

text  error  warn  system  array  login  

[filebot-info] Script Bundle: 2023-03-28 (r895)
[filebot-info] Groovy: 4.0.9
[filebot-info] JRE: OpenJDK Runtime Environment 17.0.6
[filebot-info] JVM: OpenJDK 64-Bit Server VM
[filebot-info] CPU/MEM: 4 Core / 8 GB Max Memory / 25 MB Used Memory
[filebot-info] OS: Linux (amd64)
[filebot-info] HW: Linux 1ae01af362f1 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux
[filebot-info] CPU/MEM: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz [MemTotal: 33 GB | MemFree: 668 MB | MemAvailable: 26 GB]
[filebot-info] STORAGE: btrfs [/] @ 31 GB | btrfs [/:/watch:rw] @ 31 GB | fuse.shfs [/config] @ 860 GB | fuse.shfs [/storage] @ 8 TB | btrfs [/output] @ 31 GB | btrfs [/watch] @ 31 GB | btrfs [/:/output:rw] @ 31 GB
[filebot-info] UID/GID: uid=99(app) gid=100(app) groups=100(app)
[filebot-info] DATA: /config
[filebot-info] Package: DOCKER
[filebot-info] Apr 05, 2023 12:25:15 PM net.sf.ehcache.store.disk.DiskStorageFactory <init>
[filebot-info] WARNING: The index for data file /config/cache/0/data_1.data is out of date, probably due to an unclean shutdown. Deleting index file /config/cache/0/data_1.index
[filebot-info] Activate License [P42923835] on [Wed Apr 05 12:25:15 PDT 2023]
[filebot-info] License: FileBot License P42923835 (Valid-Until: 2023-10-31)
[filebot-info] Done ヾ(@⌒ー⌒@)ノ
[supervisor  ] starting service 'app'...
[supervisor  ] starting service 'amc'...
[supervisor  ] all services started.
[xvnc        ] Wed Apr  5 12:25:33 2023
[xvnc        ]  Connections: accepted: /tmp/vnc.sock
[xvnc        ]  SConnection: Client needs protocol version 3.8
[xvnc        ]  SConnection: Client requests security type None(1)
[xvnc        ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc        ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)
[app         ] 8 files linked.
[app         ] Failed to parse media property: CreationTime: /storage/LocalMedia/TV Shows/Silicon Valley/Season 01/Silicon Valley - S01E01 - Minimum Viable Product - 1080p.mkv: java.time.format.DateTimeParseException: 2015-03-30 20:29:44 UTC
[app         ] Failed to parse media property: CreationTime: /storage/LocalMedia/TV Shows/Silicon Valley/Season 01/Silicon Valley - S01E03 - Articles of Incorporation - 1080p.mkv: java.time.format.DateTimeParseException: 2015-03-30 20:30:05 UTC
[app         ] Failed to parse media property: CreationTime: /storage/LocalMedia/TV Shows/Silicon Valley/Season 01/Silicon Valley - S01E04 - Fiduciary Duties - 1080p.mkv: java.time.format.DateTimeParseException: 2015-03-30 20:30:37 UTC
[app         ] Failed to parse media property: CreationTime: /storage/LocalMedia/TV Shows/Silicon Valley/Season 01/Silicon Valley - S01E06 - Third Party Insourcing - 1080p.mkv: java.time.format.DateTimeParseException: 2015-03-30 20:34:37 UTC
[app         ] Failed to parse media property: CreationTime: /storage/LocalMedia/TV Shows/Silicon Valley/Season 01/Silicon Valley - S01E07 - Proof of Concept - 1080p.mkv: java.time.format.DateTimeParseException: 2015-03-30 20:37:16 UTC
[app         ] Failed to parse media property: CreationTime: /storage/LocalMedia/TV Shows/Silicon Valley/Season 01/Silicon Valley - S01E08 - Optimal Tip-to-Tip Efficiency - 1080p.mkv: java.time.format.DateTimeParseException: 2015-03-30 20:35:59 UTC
[app         ] 8 files added.
[app         ] #
[app         ] # A fatal error has been detected by the Java Runtime Environment:
[app         ] #
[app         ] #  SIGSEGV (0xb) at pc=0x0000145d8e331030, pid=775, tid=966
[app         ] #
[app         ] # JRE version: OpenJDK Runtime Environment (17.0.6+10) (build 17.0.6+10-alpine-r0)
[app         ] # Java VM: OpenJDK 64-Bit Server VM (17.0.6+10-alpine-r0, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
[app         ] # Problematic frame:
[app         ] # C  [libmediainfo.so+0x131030]  ZenLib::BitStream_LE::Get(unsigned long)+0x50
[app         ] #
[app         ] # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
[app         ] #
[app         ] # An error report file with more information is saved as:
[app         ] # /storage/hs_err_pid775.log
[app         ] #
[app         ] # If you would like to submit a bug report, please visit:
[app         ] #   https://gitlab.alpinelinux.org/alpine/aports/issues
[app         ] # The crash happened outside the Java Virtual Machine in native code.
[app         ] # See problematic frame for where to report the bug.
[app         ] #
[supervisor  ] service 'app' exited (got signal SIGABRT).
[supervisor  ] service 'app' exited, shutting down...
[supervisor  ] stopping service 'amc'...
[supervisor  ] stopping service 'openbox'...
[supervisor  ] service 'openbox' exited (with status 0).
[supervisor  ] stopping service 'nginx'...
[xvnc        ] Wed Apr  5 12:27:53 2023
[xvnc        ]  VNCSConnST:  closing /tmp/vnc.sock: Clean disconnection
[xvnc        ]  EncodeManager: Framebuffer updates: 628
[xvnc        ]  EncodeManager:   Tight:
[xvnc        ]  EncodeManager:     Solid: 565 rects, 12.3567 Mpixels
[xvnc        ]  EncodeManager:            8.82812 KiB (1:5468.3 ratio)
[xvnc        ]  EncodeManager:     Bitmap RLE: 160 rects, 68.605 kpixels
[xvnc        ]  EncodeManager:                 5.0459 KiB (1:53.4817 ratio)
[xvnc        ]  EncodeManager:     Indexed RLE: 855 rects, 1.05686 Mpixels
[xvnc        ]  EncodeManager:                  115.556 KiB (1:35.8129 ratio)
[xvnc        ]  EncodeManager:   Tight (JPEG):
[xvnc        ]  EncodeManager:     Full Colour: 888 rects, 4.77757 Mpixels
[xvnc        ]  EncodeManager:                  3.42268 MiB (1:5.32774 ratio)
[xvnc        ]  EncodeManager:   Total: 2.468 krects, 18.2597 Mpixels
[xvnc        ]  EncodeManager:          3.54908 MiB (1:19.6343 ratio)
[xvnc        ]  Connections: closed: /tmp/vnc.sock
[xvnc        ]  ComparingUpdateTracker: 47.1976 Mpixels in / 13.2652 Mpixels out
[xvnc        ]  ComparingUpdateTracker: (1:3.55799 ratio)
[supervisor  ] service 'nginx' exited (with status 0).
[supervisor  ] stopping service 'xvnc'...
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)
[supervisor  ] service 'xvnc' exited (with status 0).
[supervisor  ] sending SIGTERM to all processes...
[amc         ] Terminated
[supervisor  ] service 'amc' exited (with status 143).
[finish      ] executing container finish scripts...
[finish      ] all container finish scripts executed.

** Press ANY KEY to close this window ** 

You can see I successfully renamed one of the seasons here, but then after clicking my TV preset it crashed during the naming of season 2. I've replicated this issue over 5 times. Not sure what is happening. Any ideas?
User avatar
rednoah
The Source
Posts: 22851
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Filebot Crashing During naming of seasons of TV

Post by rednoah »

:?: Which docker container are you using?
viewtopic.php?t=12965


:arrow: Looks like you're using the jlesage/filebot 3rd party docker container (and not the official docker container) which according to the unRAID community forums recently had issues which have since been fixed:
https://forums.unraid.net/topic/68916-s ... nt=1248479
:idea: Please read the FAQ and How to Request Help.
cominatcha1
Posts: 2
Joined: 05 Apr 2023, 19:33

Re: [unRAID] Filebot Crashing During naming of seasons of TV

Post by cominatcha1 »

This appears to have been the issue! Pulling a new docker image seems to have fixed it. Looks like I posted about it about a day before they announced the fix, glad it's all solved now! Issue closed
Post Reply