Toby-ch

On the „Old“ Server: Version: 6.10.3 docker: 20.10.14 The New empty container is Running. after a reboot 🫣 I'm trying to migrate again.

Yes Is attached to. I created a nine container on my other Unraid server. CPU last over 22% Start Log: In the appendix: New-OBV-Docker.txt The same as with the migrated container: eb75344e1cd2.err Is in the appendix Is it possible to outsource the MariaDB to a separate Maria DB container? All in one is great but it doesn't seem to work. Currently I use 5.0.0 (MariaDB 10.7.4) 7.0.1 requires MariaDB 10.11.2 I think the internal migration does not work. I hope I was able to help you with this information. Greetings Toby-ch edbf6a8d423d.err New-OBV-Docker.txt eb75344e1cd2.err

OK, I'm trying to help, I found something else before I went back to the old version. 1. My CPU load of the Unraid server was very high 60%, it's not a high-end server now but I don't really have more than 20%. 2. I receive this message:DB not connected, please check database connection configuration. DB Error 2002: No such file or directory. Start Log: Attached If this is not enough for you, I can try the whole thing again because I am planning a server migration. message.txt

Hello can you from the Intel NUC chassis "Intel NUC PRO FORT BEACH CMCM2FB" Create a graphic. Thank you very much 🙂

Hello, everyone I'm still using the version 5.0 because the container died during the last update, a downgrade to 5.0 helped, but does this have to be solved?

Hello I have a problem with nut, my UPS disconnects intermittently. The UPS is only recognized again by reconnecting the USB cable. But wenn i use lsusb the UPC is connected: Screenshot. but not in NUT. NUT UPS-Config: [UPPSII] driver = usbhid-ups port = auto NUT.conf MODE=netserver upsmon.conf MONITOR [email protected] 1 Monitor4ups ups4monitor master SHUTDOWNCMD "/sbin/poweroff" POWERDOWNFLAG /etc/nut/no_killpower NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYCMD "/usr/sbin/nut-notify" Do you have an idea greetings Toby

Hallo zusammen Ich habe mein Zweiten Unraid server aufgesetzt, leider bekomme ich auch bei diesem ein Problem mit dem Thema Vlan: Lan port et01 Statische Adresse VLAN tag 3 wird mit gegeben: Auf dem Switch: Auf dem Switch muss ich das Lan als Untaggd setzten ansonsten ist der server nicht erreichbar. Wie Ihr sehen könnt auf dem Trunk (18) sind alle Clans aufgeschaltet. Was mache ich falsch?