mrunknownpbu

Hi Everyone, I am encountering a fatal JVM crash when running Tachidesk in Docker on an Unraid server. The container aborts with the following error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x0000147591d271fa, pid=95, tid=255 # # JRE version: OpenJDK Runtime Environment Temurin-25.0.1+8 (25.0.1+8) (build 25.0.1+8-LTS) # Java VM: OpenJDK 64-Bit Server VM Temurin-25.0.1+8 (25.0.1+8-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64) # Problematic frame: # C [libcef.so+0x76371fa] # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/suwayomi/hs_err_pid95.log # # If you would like to submit a bug report, please visit: # https://github.com/adoptium/adoptium-support/issues # Aborted The crash seems to originate from libcef.so, and the JVM terminates with SIGILL (Illegal Instruction). is there any workaround on the issue

i been having issue since update to the latest version qbittorrent [DEBUG] Curl request successful on attempt 1 2025-10-22 00:36:01,129 DEBG 'start-script' stdout output: [DEBUG] Current incoming port for VPN tunnel is '0' 2025-10-22 00:36:01,130 DEBG 'start-script' stderr output: [DEBUG] Attempting curl request to 'http://127.0.0.1:8000/v1/publicip/ip', attempt 1/10 2025-10-22 00:36:01,136 DEBG 'start-script' stderr output: [DEBUG] Curl request successful on attempt 1 2025-10-22 00:36:01,147 DEBG 'start-script' stdout output: [DEBUG] Public IP for VPN tunnel is '146.70.67.90' [DEBUG] Country for VPN tunnel is 'Singapore' [DEBUG] City for VPN tunnel is 'Singapore' 2025-10-22 00:36:01,147 DEBG 'start-script' stdout output: [DEBUG] Setting bypass authentication for localhost, required to configure qbittorrent incoming port via API: /config/qBittorrent/config/qBittorrent.conf 2025-10-22 00:36:01,155 DEBG 'start-script' stdout output: [INFO] Starting 'qbittorrent' with VPN incoming port '0'... 2025-10-22 00:36:01,155 DEBG 'start-script' stdout output: [INFO] Starting single process: /usr/bin/qbittorrent-nox --webui-port=8080 --profile=/config 2025-10-22 00:36:01,155 DEBG 'start-script' stdout output: [DEBUG] Started 'qbittorrent' with main PID '96' (all processes running in background) 2025-10-22 00:36:01,155 DEBG 'start-script' stdout output: [INFO] Waiting for port 8080 to be listening... 2025-10-22 00:36:01,159 DEBG 'start-script' stdout output: [DEBUG] Port 8080 not yet listening, waiting... 2025-10-22 00:36:01,267 DEBG 'start-script' stdout output: *** Legal Notice *** qBittorrent is a file sharing program. When you run a torrent, its data will be made available to others by means of upload. Any content you share is your sole responsibility. If you have read the legal notice, you can use command line option --confirm-legal-notice to suppress this message. WebUI will be started shortly after internal preparations. Please wait... 2025-10-22 00:36:01,307 DEBG 'start-script' stdout output: ******** Information ******** To control qBittorrent, access the WebUI at: http://localhost:8080 2025-10-22 00:36:01,784 DEBG 'start-script' stderr output: ************************************************************* Please file a bug report at https://bug.qbittorrent.org and provide the following information: qBittorrent version: v5.1.2 Caught signal: SIGSEGV ``` 0# getStacktrace[abi:cxx11]() in /usr/bin/qbittorrent-nox 1# 0x0000000000109942 in /usr/bin/qbittorrent-nox 2# 0x000000000003E540 in /usr/lib/libc.so.6 3# BitTorrent::TorrentImpl::updateTrackerEntryStatus(libtorrent::announce_entry const&, QHash<boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>, QMap<int, int> > const&) in /usr/bin/qbittorrent-nox 4# 0x0000000000193DD7 in /usr/bin/qbittorrent-nox 5# QObject::event(QEvent*) in /usr/lib/libQt6Core.so.6 6# QCoreApplication::notifyInternal2(QObject*, QEvent*) in /usr/lib/libQt6Core.so.6 7# QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) in /usr/lib/libQt6Core.so.6 8# 0x000000000044DB18 in /usr/lib/libQt6Core.so.6 9# 0x000000000005EF4D in /usr/lib/libglib-2.0.so.0 10# 0x0000000000060617 in /usr/lib/libglib-2.0.so.0 11# g_main_context_iteration in /usr/lib/libglib-2.0.so.0 12# QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/libQt6Core.so.6 13# QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) in /usr/lib/libQt6Core.so.6 14# QCoreApplication::exec() in /usr/lib/libQt6Core.so.6 15# Application::exec() in /usr/bin/qbittorrent-nox 16# main in /usr/bin/qbittorrent-nox 17# 0x0000000000027675 in /usr/lib/libc.so.6 18# __libc_start_main in /usr/lib/libc.so.6 19# _start in /usr/bin/qbittorrent-nox ``` Its an issue with libtorrent-rasterbar on arch, downgrading to 1:2.0.11-4 fixes it segmentation fault (core dumped) qbittorrent-nox · Issue #23408 · qbittorrent/qBittorrent

Hi Zepter the issue resolve when i remove unraid connect plugin

hi Squid unable to reply for past few days due to fibre issue i have run memtest multiple times and pass attached the new diag file imrannas-diagnostics-20250525-1645.zip

It still having issue where the webgui unresponsive after 18 - 19 hours

I have stop docker service as of now and uninstall the plugin

Hi Jorge webgui was unresponsive attached the new diag imrannas-diagnostics-20250520-0657.zip

Hi Jorge below are the latest output for the command "docker info" root@ImranNas:~# docker info Client: Version: 27.5.1 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.20.1 Path: /usr/libexec/docker/cli-plugins/docker-buildx Server: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? errors pretty printing info

root@ImranNas:~# docker info Client: Version: 27.5.1 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.20.1 Path: /usr/libexec/docker/cli-plugins/docker-buildx Server: Containers: 23 Running: 22 Paused: 0 Stopped: 1 Images: 23 Server Version: 27.5.1 Storage Driver: overlay2 Backing Filesystem: xfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 nvidia runc Default Runtime: runc Init Binary: docker-init containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb runc version: v1.2.4-0-g6c52b3f init version: de40ad0 Security Options: seccomp Profile: builtin cgroupns Kernel Version: 6.12.24-Unraid Operating System: Unraid OS 7.1 x86_64 OSType: linux Architecture: x86_64 CPUs: 40 Total Memory: 62.8GiB Name: ImranNas ID: bf1b6ecb-b628-48b5-a2e8-6b6817687d36 Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine WARNING: No swap limit support

HI Trurl after letting the nas running for 1 day, again encounter the error "Docker Service failed to start" where all the docker is up but inaccesible attached the diagnostics file imrannas-diagnostics-20250518-1413.zip

just update the ntp services in my router

attached latest diag file after two days in safe mode imrannas-diagnostics-20250516-0717.zip

Initially i setup 100gb for the docker image

Currently i have reboot into safe mode and performing parity check then will use factory reset using the dynamix plugin

this would no impact the data, only the docker and plugin install on the server correct ?