ich777

Please remove the Intel GVT-g plugin because it causes Kernel traces in your syslog from what I can see and you even don't have a VM installed so it makes not much sense to have it installed. You have a Xid error in your syslog: Sep 5 10:22:03 Ironman kernel: NVRM: Xid (PCI:0000:01:00): 62, pid='<unknown>', name=<unknown>, 0000(0000) 00000000 00000000 The error code 62 means: Internal micro-controller halt which is a Hardware Error which the driver reports and indicates a Thermal Issue of some sort (you can get more information on Xid error codes here) Anyways, I would recommend that you uninstall the Intel GVT-g plugin, then do a reboot and pull the Diagnostics again and post them here if you got that issue again (please don't reinstall the Nvidia Driver plugin again because it won't help in any case if you GPU is not detected and you make it a bit more dificult for me to troubleshoot). After you've reinstalled the driver you got these errors in your syslog which can be basically everything but it is most certainly caused because the micro controller is halt: Sep 5 10:22:07 Ironman kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x23:0xffff:1426) Sep 5 10:22:07 Ironman kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Sep 5 10:22:07 Ironman kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x23:0xffff:1426) Sep 5 10:22:07 Ironman kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 You could also try to boot with Legacy Boot (CSM) since it will most of the times solve such issues too, but as said above, please uninstall the Intel GVT-g plugin, reboot and post your Diagnostics again if you experience further issues.

Without the Diagnostics I have no idea what's going on and can't tell anything.

Thanks. @Rysz will you take over the NUT plugin entirely? If yes, can you create a option so that users can choose if they want to stick with stable or a build from the latest master branch?

@Rysz thanks for creating a new plugin. May I ask what is the difference between your plugin and the one from @SimonF? Just asking because users maybe get confused when they find two plugins.

These are bundled with the application, you can however replace the files in the FiveM directory if you want to manually update them. I've never heard that it's not up to date.

I don't understand, what version? FiveM? It does auto update on a container reboot.

What do you mean exactly? txadmin is bundled with FiveM and you only have to activate it.

Wenn sie zu weit einbricht stürzt es mit sicherheit ab, du redest von fluktuationen die du mit den Software Tools hier sowieso nicht feststellen könntest da sie schlichtweg zu langsam mit der Anzeige wären. Wenn du so ein verhalten siehst dann solltest du generell an ein neues Netzteil denken, das Netzteil MUSS auf jeden fall die Spannung halten und nicht einbrchen. Damit du die Spannung auslesen kannst und noch weitere Informationen musst du dir aber ein Corsair Netzteil holen das eben genau das kann und dann das plugin von @giganode installieren. Ich wüsste auch nicht wie du das jetzt auf die schnelle tracken kannst, da müsstest dir wieder irgendwas selbst schreiben und dann in Grafana usw... Vergiss auch nicht, wir sind im Consumer Bereich und ob die Sensoren das alles so schön und akkurat auslesen bzw. ob die nicht auch was beschönigen bei den Werten bleibt offen. Es gibt single Rail Netzteil und multi Rail Netzteile, lies mal hier weiter bitte: Klick

You could install LXC and then install AMP in there then it would be possible to install Docker. It is not possible what you are trying to run Docker in Docker, at least not that easy.

It is: Click I don't use that because I don't want this... Simply create a new variable in the container and add a Variable with the Key: ROUTE and as the Value: 192.168.1.0/24 This should do the trick.

Gib im Terminal mal: sensors ein und schau was da raus kommt. Es gibt aber nichts um diese im WebUI abzubilden noch sehe ich wirklich nicht wie du dort schlüssig was auslesen willst wenn was falsch konfiguriert ist im Bezug auf Energieverbrauch, da ist PowerTOP die richtige Wahl.

This is not much information that you‘ve given here but I assume that you have left the path in the template at the default which is /mnt/cache/… and in the share settings where your SotF direcotry is located is most certainly set that the files are moved from the cache to the Array. I‘m assuming this because it is not able to find the game files or at least not all. You either have to set the share where SotF is located to stay on the cache or set the path to /mnt/user/… where I would always recommend that you set the share to stay on the cache.

You have to quit Thunderbird from within Thunderbird and not restart the container since if you are simply restarting the container the settings for filters and so on will be wiped. So to speak click this icon: right next to the search bar and click Quit, this will restart the container and make the settings stick. Press ESC on your keyboard this will do also the same, I hide the close button because this can lead to serious trouble for some users, closing the main application instead of another window, hope that makes a bit of sense to you (something like that gave me trouble). Yes, DockerHub is sometimes weird. Anyways, glad that you figured it out yourself and that it's working now, at least that the filters stick.

No, this is not true, this allows you to copy to and from the container, I know that because I heavily use my container with the noVNC web client and it works flawlessly. I use the Thunderbird container as my main mail application. I've also edited my post about the rate limit.

You can use a VNC client on your local PC and connect to the VNC server which is running inside the container, this will allow you to directly copy past from it. Just add another port entry like that in the template: (please don't use the port 5900 since this port and the following ports are also used by the VM manager on Unraid so I would recommend that you use something like 5990) This will then allow you to connect to the container with YOURUNRAIDIP:5990 to the containers VNC server directly. This is done on purpose since this can be a serious risk, malware and so on and I don't want that the database or something inside the container is harmed. You can use the VNC menu on the left side of the screen as an alternative to copy paste (there is a little clipboard icon that allows you to copy to and from the app that is running inside the container. I have not applied a rate limit, the rate limit applies to your machine and means that you can only pull 100 containers (from your IP) in six hours.

No, this was just a coincidence. The plugin driver packages are nowadays usually ready when the new Unraid version is released. You will receive a notification after using the built in Unraid update assistant after the download is finished and if you get an error you can come back here before rebooting your system to solve issues. As a note, you maybe have to open up the notifications to actually see the notifications if you are on Unraid 6.12.x because there the notifications disappear by default after 5 seconds. So to speak, use the built in Unraid update assistant and you will receive additional notifications (like if a Parity check started/finished) after you close the updater. Please look only at the 2nd and 3rd picture from this post: Click and you will know what I mean.

Oh, I understood that incorrect, yes, always update the plugins because I improve them and make bugfixes to them, this will not affect how the plugin is working since the driver packages are only pulled in by the plugin on installation on boot. Yes, it is totally possible to run the plugin with an older Unraid version because the plugin always pulls the correct drivers for the Unraid version which is installed. Even if you update through the Unraid update assistent, it will pull the drivers for the new version ahead of time so that they are available on boot and leave the drivers for the current running Unraid version untouched until you reboot. So to speak, you don't update the drivers with a plugin update. The update from the plugin itself only improves the plugin page and how things are working but not the drivers. Hope that makes sense to you.

Then do exactly that, just place this in your, daemon.json If the file doesn't exist create it and restart the Docker service, this will do the trick. You can make this persistent if you put these lines in the go file before emhttp starts: mkdir -p /etc/docker echo '{ "metrics-addr" : "127.0.0.1:9323" }' > /etc/docker/daemon.json (this will basically create the /etc/docker directory and then create or better speaking inject the contents that you've posted above) By putting it before the emhttp you ensure that the file is there before the Docker service starts and therefore you don't have to restart the Docker service on a reboot. Please keep in mind that this will cause issues when you use this with the Nvidia Driver plugin. Hope that makes sense.

Just use the built in upgrade assistant from Unraid itself and watch the Unraid notifications after the upgrade assistant finished, the plugin_update_helper should kick in and update the plugin ahead of time and it will tell you when it is safe to reboot or a error happened. So to speak the plugin package should be pulled automatically for the new Unraid version after the Unraid upgrade assistant finished and will notify you. You don't have to do anything with the plugin if everything went well.

I don't think so because it is designed to deliver information form the host and it's attached devices not VMs or Docker. However, maybe there is a Prometheus Docker Exporter out there, which should definitely be the case. But the Node Exporter won't deliver these information.

Did you wait with the reboot until you received the Unraid notification that it is safe to reboot when doing the first update to 6.12.4?

Then it's not installed, make sure that you have no Plugins Error tab on the Plugin page. Then simply upgrade to 6.12.4 and then pull a fresh copy from the CA App, but only after the reboot, I would recommend that you reboot after installing the Nvidia Driver plugin again.

No, because Rambox-CE was deprecated and this was the time where I also deprecated the container. Look into Ferdi, it's almost the same, at least I think.

Please uninstall the plugin, upgrade to 6.12.4, reboot, install the plugin again.

This container was deprecated a while back.