February 8, 20233 yr Hello, I have been using UnRaid for 6 months, and I love it. Recently I did a small update on my mainboard, and since then, I have many problems with one the linuxserver transmission docker. It stops working, the UI does not load and other applications cannot communicate with it. The logs (either system logs or the docker logs) do not tell me anything of use. When I restart the docker, it starts working again. All other docker are running without any problems and do not do anything alike. What I have done so far: 1) Run memtest86+, run 10 test all good 2) Migrate to a different pendrive 3) Change Drives to enable/disable cache use in AppSetting 4) Force update of the application 5) remove the docker and install it again. Any ideas / suggestions what can I do to debug and fix the issue? Thanks in advance!
February 8, 20233 yr Author Checking further, right now I cannot even restart that container, but I saw a log entry from the container that I did not have before [2023-02-07 16:45:59.299] Couldn't connect socket 37 to 2a0d:6fc2:5e40:9a00:a485:df8c:bb2a:65a9, port 46742 (errno 99 - Address not available) (/home/buildozer/aports/community/transmission/src/transmission-3.00/libtransmission/net.c:339) s6-supervise svc-transmission: warning: finish script lifetime reached maximum value - sending it a SIGKILL The error I get if I try to restart or stop that container is Execution error Server error There are no entry on the unraid logs
February 12, 20233 yr Author Solution Closing this threat. I came with further problems, but something I realized is that some files had a wrong permission settings. There is a tool within Unraid to fix permissions for Dockers in the other drives, that fixed part of the problem
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.