eman31

Sorry, didn't see your reply. I've had both happen but it doesn't restart after a crash and it sometimes will cause the whole server to hang up needing to reboot. This is from the most recent crash after running about a half hour. text error warn system array login [supervisor ] loading service 'default'... [supervisor ] loading service 'app'... [supervisor ] loading service 'gui'... [supervisor ] loading service 'audiorecorder'... [supervisor ] service 'audiorecorder' is disabled. [supervisor ] loading service 'certsmonitor'... [supervisor ] service 'certsmonitor' is disabled. [supervisor ] loading service 'dbus'... [supervisor ] loading service 'nginx'... [supervisor ] loading service 'webauth'... [supervisor ] service 'webauth' is disabled. [supervisor ] loading service 'xvnc'... [supervisor ] loading service 'openbox'... [supervisor ] loading service 'pulseaudio'... [supervisor ] service 'pulseaudio' is disabled. [supervisor ] loading service 'webservices'... [supervisor ] service 'webservices' is disabled. [supervisor ] loading service 'xcompmgr'... [supervisor ] loading service 'xrdb'... [supervisor ] loading service 'logmonitor'... [supervisor ] service 'logmonitor' is disabled. [supervisor ] loading service 'logrotate'... [supervisor ] all services loaded. [supervisor ] starting services... [supervisor ] starting service 'dbus'... [supervisor ] starting service 'xvnc'... [xvnc ] Xvnc TigerVNC 1.16.0 - built Feb 22 2026 16:30:20 [xvnc ] Copyright (C) 1999-2026 TigerVNC team and many others (see README.rst) [xvnc ] See https://www.tigervnc.org for information on TigerVNC. [xvnc ] Underlying X server release 12101021 [xvnc ] Could not find any render nodes [xvnc ] Failed to initialize DRI3 extension [xvnc ] Sat Mar 28 11:24:09 2026 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900 [xvnc ] vncext: Created VNC server for screen 0 [xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x146b0fe540bd for event 2 [xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x146b0fe540bd for event 3 [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [supervisor ] starting service 'openbox'... [supervisor ] starting service 'xcompmgr'... [supervisor ] starting service 'xrdb'... [supervisor ] starting service 'app'... [supervisor ] all services started. [supervisor ] service 'xrdb' exited (with status 0). [app ] 16:24:12.996 [INFO] czkawka_core::common::logger: Logging to file "/config/xdg/cache/czkawka/czkawka_gui.log" and terminal [app ] 16:24:13.012 [INFO] czkawka_core::common::logger: Czkawka gtk version: 11.0.1(<unknown> U <unknown>), release mode, rust 1.94.0 (2026-03-02), os Alpine Linux 3.20.9 (x86_64 64-bit), 16 cpu/threads, features(2): [heif, libraw], app cpu version: x86-64-v1 (SSE2), os cpu version: x86-64-v3 (AVX2), libc musl [build + runtime (glibc <not detected> | musl 1.2)] [app ] 16:24:13.012 [INFO] czkawka_core::common::config_cache_path: Config folder set to "/config/xdg/config/czkawka" and cache folder set to "/config/xdg/cache/czkawka" [app ] 16:24:13.321 [INFO] czkawka_gui: Czkawka Gui - used thread number: 16, gtk version 4.14.4 [xvnc ] Sat Mar 28 11:24:15 2026 [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 [app ] 03:44:12.478 [INFO] czkawka_core::tools::duplicate::traits: find_duplicates [app ] 04:03:42.716 [INFO] czkawka_core::tools::duplicate::traits: find_duplicates: Done in 1170.24s [app ] 04:06:04.841 [INFO] czkawka_core::tools::duplicate::traits: find_duplicates [supervisor ] service 'app' exited (got signal SIGSEGV). [supervisor ] service 'app' exited, shutting down... [supervisor ] stopping service 'xcompmgr'... [supervisor ] service 'xcompmgr' exited (got signal SIGTERM). [supervisor ] stopping service 'openbox'... [supervisor ] service 'openbox' exited (with status 0). [supervisor ] stopping service 'nginx'... [xvnc ] Sat Mar 28 23:37:44 2026 [xvnc ] VNCSConnST: Closing /tmp/vnc.sock: Clean disconnection [xvnc ] EncodeManager: Framebuffer updates: 16069 [xvnc ] EncodeManager: Tight: [xvnc ] EncodeManager: Solid: 3.189 krects, 34.5304 Mpixels [xvnc ] EncodeManager: 49.8281 KiB (1:2707.74 ratio) [xvnc ] EncodeManager: Bitmap RLE: 1.274 krects, 181.585 kpixels [xvnc ] EncodeManager: 36.2939 KiB (1:19.955 ratio) [xvnc ] EncodeManager: Indexed RLE: 18.169 krects, 15.0514 Mpixels [xvnc ] EncodeManager: 3.7577 MiB (1:15.335 ratio) [xvnc ] EncodeManager: JPEG: [xvnc ] EncodeManager: Full Colour: 10.487 krects, 65.2215 Mpixels [xvnc ] EncodeManager: 45.962 MiB (1:5.41578 ratio) [xvnc ] EncodeManager: Total: 33.119 krects, 114.985 Mpixels [xvnc ] EncodeManager: 49.8038 MiB (1:8.81482 ratio) [xvnc ] Connections: Closed: /tmp/vnc.sock [supervisor ] service 'nginx' exited (with status 0). [supervisor ] stopping service 'xvnc'... [supervisor ] service 'xvnc' exited (with status 0). [supervisor ] stopping service 'dbus'... [supervisor ] service 'dbus' exited (with status 0). [finish ] executing container finish scripts... [finish ] all container finish scripts executed.

I just recently started using this container to start migrating from rtorrent and get better integration with the other *arr stacks. I'm currently running without any VPN's. I decided to try and run a few instances to break up my torrents by categories and have run into an issue running two instances together. They spin up fine and as long as I don't try and add a torrent manually or access the settings, everything seems to be ok. As soon as I do one of these two things, it kills the web instances on the second one requiring a refresh of both. I did some searching and it seems to be a problem similar to this linuxserver issue. https://github.com/linuxserver/docker-qbittorrent/issues/423 Has anyone else run into something similar? I was under the impression that running multiple instances shouldn't be a problem.

I've been getting timed out or reconnects to VNC after a couple of hours the last few times I've tried to do scans. Not sure where I should be looking for logs to try and troubleshoot. Also tried running Krokiet alone with the same results. Everything seemed fine the last time I used it. Have tried a couple more times and now it seems to be crashing the system. Here is the information from the docker log before running a scan. ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮ │ │ │ Application: Czkawka │ │ Application Version: 11.0.1 │ │ Docker Image Version: 26.02.3 │ │ Docker Image Platform: linux/amd64 │ │ │ ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯ [cont-init ] 89-info.sh: terminated successfully. [cont-init ] all container initialization scripts executed. [init ] giving control to process supervisor. [supervisor ] loading services... [supervisor ] loading service 'default'... [supervisor ] loading service 'app'... [supervisor ] loading service 'gui'... [supervisor ] loading service 'audiorecorder'... [supervisor ] service 'audiorecorder' is disabled. [supervisor ] loading service 'certsmonitor'... [supervisor ] service 'certsmonitor' is disabled. [supervisor ] loading service 'dbus'... [supervisor ] loading service 'nginx'... [supervisor ] loading service 'webauth'... [supervisor ] service 'webauth' is disabled. [supervisor ] loading service 'xvnc'... [supervisor ] loading service 'openbox'... [supervisor ] loading service 'pulseaudio'... [supervisor ] service 'pulseaudio' is disabled. [supervisor ] loading service 'webservices'... [supervisor ] service 'webservices' is disabled. [supervisor ] loading service 'xcompmgr'... [supervisor ] loading service 'xrdb'... [supervisor ] loading service 'logmonitor'... [supervisor ] service 'logmonitor' is disabled. [supervisor ] loading service 'logrotate'... [supervisor ] all services loaded. [supervisor ] starting services... [supervisor ] starting service 'dbus'... [supervisor ] starting service 'xvnc'... [xvnc ] Xvnc TigerVNC 1.16.0 - built Feb 13 2026 23:37:28 [xvnc ] Copyright (C) 1999-2026 TigerVNC team and many others (see README.rst) [xvnc ] See https://www.tigervnc.org for information on TigerVNC. [xvnc ] Underlying X server release 12101021 [xvnc ] Could not find any render nodes [xvnc ] Failed to initialize DRI3 extension [xvnc ] Sun Mar 8 12:40:18 2026 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900 [xvnc ] vncext: Created VNC server for screen 0 [xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x1513f24540bd for event 2 [xvnc ] [mi] mieq: warning: overriding existing handler 0 with 0x1513f24540bd for event 3 [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [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 ] Socket: Failed to flush remaining socket data on close: write: Broken [xvnc ] pipe (32) [xvnc ] VNCSConnST: Closing /tmp/vnc.sock: write: Broken pipe (32) [xvnc ] EncodeManager: Framebuffer updates: 1 [xvnc ] EncodeManager: Tight: [xvnc ] EncodeManager: Solid: 21 rects, 1.37088 Mpixels [xvnc ] EncodeManager: 320 B (1:17136.8 ratio) [xvnc ] EncodeManager: Total: 21 rects, 1.37088 Mpixels [xvnc ] EncodeManager: 320 B (1:17136.8 ratio) [xvnc ] Connections: Closed: /tmp/vnc.sock [supervisor ] starting service 'openbox'... [supervisor ] starting service 'xcompmgr'... [xvnc ] Sun Mar 8 12:40:20 2026 [xvnc ] Connections: Accepted: /tmp/vnc.sock [supervisor ] starting service 'xrdb'... [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 [supervisor ] starting service 'app'... [supervisor ] all services started. [supervisor ] service 'xrdb' exited (with status 0). [app ] 17:40:23.901 [INFO] czkawka_core::common::logger: Logging to file "/config/xdg/cache/czkawka/czkawka_gui.log" and terminal [app ] 17:40:23.904 [INFO] czkawka_core::common::logger: Czkawka gtk version: 11.0.1(<unknown> U <unknown>), release mode, rust 1.93.1 (2026-02-11), os Alpine Linux 3.20.9 (x86_64 64-bit), 16 cpu/threads, features(2): [heif, libraw], app cpu version: x86-64-v1 (SSE2), os cpu version: x86-64-v3 (AVX2), libc musl [build + runtime (glibc <not detected> | musl 1.2)] [app ] 17:40:23.905 [INFO] czkawka_core::common::config_cache_path: Config folder set to "/config/xdg/config/czkawka" and cache folder set to "/config/xdg/cache/czkawka" [app ] 17:40:24.162 [INFO] czkawka_gui: Czkawka Gui - used thread number: 16, gtk version 4.14.4 [xvnc ] Sun Mar 8 12:40:52 2026 [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

Have been using this container for a long time with no problems but now when I pull up a new series and try to add, the green "add" box just flashes but won't actually add the show and stays green. I'm running unraid 6.12.10 and have tried forcing an update to the docker and also reinstalling but nothing changes. Everything else seems to be working fine. It's grabbing and adding existing series, just nothing new. The only error I see in the logs is this: [Fatal] SonarrErrorPipeline: Request Failed. POST /api/v3/series. Not sure if it is related but I know one of my trackers api is down so it may be from that.

I was thinking along the same lines yesterday but didn't see an obvious way to stop them and have never had a reason to before. Is there a way to turn off individual plugins like with the containers or do they need to be uninstalled?

I had started all of the same containers that were running ok in safe mode. Basically everything other than Jellyfin.

Rebooted out of safe mode without Jellyfin running and system locked up on me again after a couple of hours. Ran fine in safe mode for two weeks. No idea what the issue is here. I don't see anything in the syslog at the time it locked up. syslog-192.168.50.68 - 03-17-24.log

After letting things run for a while, starting all my dockers one by one and letting them run for at least 24 hours before starting another one, it looks like the issue may be with my binhex-jellyfin application. As soon as I turn it on it eats up all my ram and pegs the cpu to 100%. I didn't let it run long enough for the system to crash but none of the others have acted like that.

I've been running in safe mode for about 72 hours with no lock ups. What's a reasonable length to go to rule out a hardware issue? Once that time has passed, do I just start turning on dockers one by one and letting it run for a while to see if one is causing the problem?

I tried running in safe mode yesterday and while it lasted longer it still locked up overnight. Not sure where to take my troubleshooting to next. Edit: I just read that I should have dockers disabled in safe mode which I did not do. Will give it another try with that.

No luck after all the changes I made. Went down after about 3 hours. Attaching current syslog to see if anything is relevant. syslog-192.168.50.68-03-03-24.log

Thanks for the suggestions. After the last lock up yesterday, I updated my bios and changed the Power Supply Control and disabled C-States. Also ran a memory test for 24 hours to rule a RAM problem out. It came back clean so that appears to be good. I will update after running for a while to see if this fixes things.

I setup remote syslog and this is what I have. Hopefully I did it correctly to capture everything. There were two times that it became unresponsive again after the mover ran where I had to hard reboot. One at 01:00 and again at 13:00 today. I did run the mover manually after the 01:00 and it ran with no issues and a few times after that as well. syslog-192.168.50.68.log

Hi, Currently running 6.12.8 and the past couple of weeks started having problems with the server becoming unresponsive. Prior to this I was up running for months without issues. When it happens I can't access anything and have to hard reset the server. I've been trying to look at the previous logs and the only thing I've been seeing is that it happens right after the mover is finished. Not every time the mover runs but when it hangs, that is the last entry in the log. Current hardware is: Micro-Star International Co., Ltd. MEG X570 ACE (MS-7C35) Version 1.0 AMD Ryzen 7 3700X 8-Core @ 3600 MHz 32 GiB DDR4 Any help would be appreciated. tower-diagnostics-20240229-2012.zip