sonofdbn Posted July 14, 2023 Share Posted July 14, 2023 I'm on 6.11.5. Over the last week I've twice had a problem with the web UI becoming unresponsive in parts - some tabs won't open, the main tab shows the unRAID wave in the Unassigned Devices section and after a while the main tab also fails to open. Although the unRAID GUI is unresponsive, other things are running: I can access files and open them. I think the first time the Win10 VM was still running, although this time I can't RDP into it. Both times I've tried "powerdown" via SSH but the server doesn't seem to shut down. The first time I couldn't get into the GUI to get diagnostics (and didn't know that this could have be done via the command line). Unfortunately I can't recall exactly how I shut down the server the first time. Might have been via IPMI. This time (today) I grabbed diagnostics and then tried to shut down via the GUI. Heard the beeps (as before) but after about 45 minutes the server was still on (as before). In the end I shutdown via IPMI. When I rebooted after the first incident, one of my disks was marked as missing. Seemed to be a loose SATA connector; after some replugging I started the server and everything seemed OK. But today I got the unresponsive GUI again. tower-diagnostics-20230714-2143.zip Quote Link to comment
Solution JorgeB Posted July 14, 2023 Solution Share Posted July 14, 2023 Possibly this issue: https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/ Should also change docker network type to ipvlan, since there's a related call trace. Quote Link to comment
sonofdbn Posted July 15, 2023 Author Share Posted July 15, 2023 On qbittorrent I had been using an older version of the container precisely because of the problem described. But recently that older version stopped working and I changed to the latest version, which seems to be running fine, unless it's causing these crashes. I'm not sure, but I think the first crash came before switching to the latest version. For the moment I'll stick to the latest version, but I have changed docker network type to ipvlan. Let's see how things go.... Quote Link to comment
sonofdbn Posted July 24, 2023 Author Share Posted July 24, 2023 After changing the docker network type to ipvlan, the same problem re-occurred. So (additionally) I switched to the binhex/arch-qbittorrentvpn:libtorrentv1 version of qbittorrent, and now everything is running fine. Quote Link to comment
Recommended Posts
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.