ich777

Please try to uninstall the GPU Statistics plugin and see if that resolves your issue. GPU Statistics calls nvidia-smi every N seconds (depending on how it's configured in the plugin) and that could cause your CPU spikes. I can't tell much about the RAM usage, however please do keep in mind that Unraid runs from RAM and the driver is also installed to RAM, compressed it has about 400MB so to speak that should be about 700 to 800MB decompressed if I'm not mistaken and that will also go into RAM.

This is your error: Feb 5 18:47:49 Dingleberry kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242 Feb 5 18:47:49 Dingleberry kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed Feb 5 18:47:49 Dingleberry kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed Feb 5 18:47:49 Dingleberry kernel: NVRM: osInitNvMapping: *** Cannot attach gpu Feb 5 18:47:49 Dingleberry kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter Feb 5 18:47:49 Dingleberry kernel: NVRM: GPU 0000:2b:00.0: RmInitAdapter failed! (0x22:0x51:763) Feb 5 18:47:49 Dingleberry kernel: NVRM: GPU 0000:2b:00.0: rm_init_adapter failed, device minor number 0 Feb 5 18:47:52 Dingleberry kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1359 Please make sure that you have: The latest BIOS version Above 4G Decding enabled in your BIOS Resizable BAR Support enabled in your BIOS I also compiled a new Open Source driver yesterday that you can try: v590.48.01

Surely it is possible, the schedule only triggers the prefill command, nothing more. Have you yet tried it when selecting yes? As said above, the container does just: SteamPrefill prefill --no-ansi Which is the usual way of triggering a prefill from the selected apps. Are you also sure that you followed the tutorial when opening a terminal, especially when entering: su $USER

Sorry, but I don't see a Nvidia GPU in your system, at least that what's lspci tells me.

Have you yet tried to select Yes and see what happens if you run the prefill now? If it then only pulls three games it is indeed a bug and you should report that on the GitHub Issue tracker from Prefill, if it pulls all 7 games then you should wait for the next schedule and see what happens since the schedule triggers just the prefill that you've configured.

Sorry, I think @ConnerVT already answered all questions, that's why I didn't looked at them. Usually I only need Diagnostics to see what's going on. Thanks for the hint with a connected display, didn't know that this was necessary for Nvidia too. :)

I have implemented a fix, please update the container itself, it should now pull the correct version.

This time it seems to be different, there are no assets available from Portfolio Performance, I assume something went wrong when building the assets. Please report that in the GitHub Issue tracker from PortfolioPerformance or where to get the new assets if this is not a mistake.

Please post your Diagnostics if you have hardware related questions (click on the "Diagnostics" texts if you don't know how to get them) and drag the zip file here into the textbox.

Do you possibly have two php errors on the page, if yes then you might suffer from a broken plugin, please follow this post: Please note that the 480.x driver isn't available anymore, you have to choose driver version 580.x now for your Pascal based card (I would recommend to choose a static 580.x version since 590.x won't work for your card).

I would recommend to set the plugin to a static 580.x version since the plugin is now updated to check if there is a 580.x driver selected and it will automatically check for a 580.x driver version if the current one couldn't be found because of a system upgrade. As said above, I would recommend to set a static 580.x driver version and then trigger the upgrade OS upgrade process.

Nothing to worry about, the backup will be running in the background when the gateway times out, this is usually the case when backing up really big containers. I would recommend that you might trigger it from the an Unraid Terminal or via a User Script by using: lxc-autobackup The backup should be finished just fine.

Please try it without a username/password, some browsers have issues with that, usually it should be enough on your home network (since this should not be available to the internet) to use it without credentials, BTW, I would strongly recommend to use SOCKS5. The container does nothing specific, it even doesn't need a configuration directory in appdata, usually you deploy it and it just runs. This seems something like a network issue but I really can't tell.

I didn't do anything.

Sorry but I don't understand, I have a Team Fortress Classic container and a Team Fortress 2 container, isn't this something different?

Probably because I don't run srcds.sh in my containers. Sorry but I don't create any new game servers.

This has nothing to do with updating the plugin, the plugin updates and the driver updates are separated from each other and the plugin will always check if a new driver is needed when upgrading to a newer Unraid version. However I would strongly recommend to upgrade the plugin in your case since I made a change that the driver version 580.x will be downloaded if driver version 580.x is selected, please do note this will not work when you set it to Production, New Feature or Latest driver version. To clarify that, plugin updates won't change the installed driver.

You have a Xid error in your syslog, to be precise 62: Jan 27 16:08:32 Mochi kernel: NVRM: Xid (PCI:0000:01:00): 62, 0001b0d6 0001ae80 0002ab00 0002aab2 0001af25 0001af2d 00000011 00000000 Jan 27 16:09:32 Mochi kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1623) Jan 27 16:09:32 Mochi kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 You can see what this means here: https://docs.nvidia.com/deploy/xid-errors/analyzing-xid-catalog.html However I would recommend that you do the following things: Upgrade your BIOS Make sure to enable Above 4G Decoding and Resizable BAR Support in your BIOS Upgrade to the latest Unraid version Probably this is caused because the BIOS version is outdated since it seems that your GPU fails to reset.

Please try another browser or at least a Private window, this looks really strange and I really can't tell you what is causing that.

Most of the times not because most game servers need special treatment when starting. However this is already a docker container from what I see, this basically means you can deploy it on Unraid. Please refer to the General Support subforums for help if you don't know how.

I'm not super familiar with NPM but do you also allow websockets to connect? I can only link you that example config for nginx: https://github.com/ich777/docker-debian-bullseye?tab=readme-ov-file#reverse-proxy-with-nginx-example

Thank you for that, in the first Diagnostics I see that the driver is not installed, that's good, in the second I see that the plugin got installed but I don't see that the driver version was changed and of course that the driver is complaining about the GPU being not supported because of Pascal. However in the third Diagnostics I also see the driver complaining of not being compatible because of Pascal. Are you sure you set the the driver version in the plugin settings to version 580.x because I don't see that it got changed in the 2nd Diagnostics before rebooting, please also do keep in mind to let the dialog open until the dialog says the driver was fully downloaded and you get a notification to reboot. I also noticed that you are on Unraid 7.2.0, is it possible for you to upgrade to the latest version since this could also solve some issues.

By default the container doesn't provide a https port but if you are proxying it through NPM you should be able to use port 8080 internally and externally you have to configure NPM to fit your needs. A word of caution, please note that if you set a password for noVNC that this is not enough and could be easily bruteforced, please make sure to put it behind some additional authentication like HTTP Basic Auth or even better some kind of authentication/authorization application like Authentik, Authelia,...

Please post your Diagnostics because I can't see what's going on without them.

So which driver do you need for which Unraid version?