God_TM

For now I'm using the container Dell-iDRAC-Fan-Controller and it's working (but it would be nice to get this plugin working because I like how it shows the fan speed at the bottom of the window).

It seems that after updating from 2025.12.13 to 2026.04.28, it doesn't seem to change fan speeds on my Dell r730xd like it used to (it just stays maxed out). I even tried uninstalling the plugin and reinstalling but that didn't seem to make any difference. Any ideas on what I can do to troubleshoot and get this going again? I'm on unraid 7.2.0.

So in theory setting the Docker Stop Timeout should also work perhaps (but also not ideal as that can cause issues during shutdowns). I had mine set to 360 seconds, but it still wasn't enough for home assistant to update. I guess I'll put the terminal commands into a user script and kick that off before the next update for now. It's too bad the system isn't smart enough to be a bit more generous with the time allowances during an update...

I've had the same issues with ActualServer as well but I've been on 6.12.10 for quite some time so I don't think it's the upgrade of your server that caused your issue. I would notice, it would run fine for a while and I'd notice one day that it just stopped, and this happened multiple times. I'd have to restore from a backup after the crash. After I fixed it to a specific version (in my case: actualbudget/actual-server:24.12.0) it doesn't crash on it's own any longer, so I suspect something breaks from the container itself updating (but I'm mainly still on YNAB so I'm just running Actual to learn/test things out). I went to their github page and in their issues I found this that might help: https://github.com/actualbudget/actual-server/issues/521

If you can, you can change the template's repository to read: flaminel/cleanuperr:latest so that it doesn't break moving forward. NM.... I just saw your update on your original post, so it seems you (or someone) fixed the template. Thank you!

Couldn’t you put the command into a User Script and then kick out off to run in the background?

I'm still having issues with Webtrees. If anyone could please help. I can get it to install, and it gets to the login page, but I can't seem to log in. I set up variables for WT_ADMIN, WT_ADMINPW and WT_ADMINMAIL but it doesn't accept that username/password. Is there a default username/pass I can use? I'm also still consistently having issues shutting down the container (it'll give me an execution error message when trying to stop it and it just stays running). Does anyone have any ideas on what I can do next to get in (and fixing the restarting/stopping container issue would be good too)? Thank you.

I'm having an issue with webtrees... it'll start up fine (well, still working on getting it to work), but my main concern is that it doesn't want to shut down from the GUI... I have to go to terminal and kill it's process to stop it. Any ideas what would cause that issue? It's fine for other containers... just that one doesn't ever want to stop.

I've noticed this same issue on a newer system I just set up. Unraid is on 6.11.5 and pop-up blockers have been completely turned off (and I don't have this issue on a different server also on 6.11.5) which leads me to believe this is a server issue and not a browser/client issue.

I received an "Out Of Memory errors detected on your server" in fix common problems. Server has been up for 2.5 months so far. It's doing a parity check currently if that matters. Here are the diagnostics attached. zhq-diagnostics-20230205-0727.zip

I've searched, and it seems for my adapter (RTL8761BU based) the issue in the past was the driver wasn't installed on the system. Now, after upgrading to 6.11.1, it seems that the drivers are there (I see it listed in /lib/firmware/rtl_bt/) but it still doesn't show up in /dev/serial/by-id (lsusb shows it is connected however?). How do I get the system to recognize the usb stick, so I can then pass it through to the home assistant container, or is this still not possible because of some limitation in the specific linux kernel version? Thank you.

I tried this and can't get it to work. In home assistant, it has an error on the integrations page for the bluetooth integration: Retrying setup: Failed to start Bluetooth: adapter 'hci0' not found What exactly do you have passed in to the container? I have the path /var/run/dbus pointed to /var/run/dbus AND I have the device /dev/bus/usb/003/013 (as that's what's showing up for the bluetooth adapter in Tools > System Devices).

I don't think it affects ALL Dell R730xd's.... mine has an has an Intel board (Intel X710 Quad Port 10GbE SFP +, rNDC)

I recently updated to Unraid 6.10 and subsequently to 6.10.1. Not many issues for the most part, but today, I noticed mariadb had an update available. I ran the update on the container, but now it won't start. The logs have this: 2022-05-23 12:29:19-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started. 2022-05-23 12:29:20-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required 2022-05-23 12:29:20-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting 2022-05-23 12:29:20 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ... 2022-05-23 12:29:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-05-23 12:29:20 0 [Note] InnoDB: Number of transaction pools: 1 2022-05-23 12:29:20 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-05-23 12:29:20 0 [Note] InnoDB: Using liburing 2022-05-23 12:29:20 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2022-05-23 12:29:20 0 [Note] InnoDB: Completed initialization of buffer pool 2022-05-23 12:29:20 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.4. 2022-05-23 12:29:20 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2022-05-23 12:29:20 0 [Note] InnoDB: Starting shutdown... 2022-05-23 12:29:20 0 [ERROR] Plugin 'InnoDB' init function returned error. 2022-05-23 12:29:20 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2022-05-23 12:29:20 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-05-23 12:29:20 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2022-05-23 12:29:20 0 [ERROR] Aborting 2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started. 2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required 2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting 2022-05-23 12:40:25 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ... 2022-05-23 12:40:25 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-05-23 12:40:25 0 [Note] InnoDB: Number of transaction pools: 1 2022-05-23 12:40:25 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-05-23 12:40:25 0 [Note] InnoDB: Using liburing 2022-05-23 12:40:25 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2022-05-23 12:40:25 0 [Note] InnoDB: Completed initialization of buffer pool 2022-05-23 12:40:25 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.4. 2022-05-23 12:40:25 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2022-05-23 12:40:25 0 [Note] InnoDB: Starting shutdown... 2022-05-23 12:40:25 0 [ERROR] Plugin 'InnoDB' init function returned error. 2022-05-23 12:40:25 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2022-05-23 12:40:25 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-05-23 12:40:25 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2022-05-23 12:40:25 0 [ERROR] Aborting Any idea on how to fix this?

The container has a server and it's available at 8080. What this is saying above is take port 8085 on the host (the server running docker (which is Unraid in this case)) and map it to port 8080 for this container. So if you go to http:your-ip:8085, you'll actually be presented with whatever is what that container is serving on port 8080. You can change the host port, but it's unnecessary to change the container's port (unless you're wanting to run it on a a host network, which you won't want to do).