ich777

Do you have any custom scripts installed? I would recommend that you remove PowerTOP for now and see if this helps, seems that your GPU fails to initialize: Jul 31 22:15:37 darkstar kernel: NVRM: GPU at PCI:0000:01:00: GPU-ea06c034-1c38-9a48-60ea-e0779d32f6a1 Jul 31 22:15:37 darkstar kernel: NVRM: GPU Board Serial Number: 1322722038690 Jul 31 22:15:37 darkstar kernel: NVRM: Xid (PCI:0000:01:00): 62, pid='<unknown>', name=<unknown>, 20c2(2bc4) 00000000 00000000 Jul 31 22:15:47 darkstar kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x23:0x65:1426) Jul 31 22:15:47 darkstar kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Jul 31 22:15:51 darkstar kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x23:0x65:1426) Jul 31 22:15:51 darkstar kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 Does the card work or does it not work at all?

@dlandon something seems wrong with the package that was updated yesterday, can you take a look at that?

Yes.

No, this means you need to replace this whole line with: nvidia-persistenced This is nothing new to me, software readings are most certainly wrong.

Thank you for the heads up! Will look into that later today. EDIT: Please update the container itself, the container supports now both the .net7 version and mono version.

Only if you post your Diagnostocs.

I would strongly report that on the ATS Forums since it seems that all servers except for a few are outdated, simply look at the server list. My assumption is that the few ones which are working are actually Windows and not Linux servers.

Please read the description from the container. This is most likely caused because the developers haven't update the dedciated server yet if there was a recent released update. Are you sure that your game on your local PC is up to date? If you just installed the container it will always pull the latest version from Steam Pipe. Do you have any AdBlocking or special DNS servers in place which are maybe preventing it from pulling the latest version?

Seems to be a known issue: https://feedback.bistudio.com/T170140 There is nothing I can do about that until the developers solved that.

Das ist das offizielle von Zabbix, ich hab nur das Template gemacht: Das heißt es pullt immer den "latest" tag. Das müsstest du wohl im Zabbix Forum/Support erfragen. Du kannst dir aber eine zweite MariaDB einrichten mit der versionsnummer 10.11 Hier: Aber bedenke das du dir damit evtl. deine bestehende Datenbank zerschießt wenn du downgradest, kann ich aber nicht mit sicherheit sagen.

NerdTools is still available. Sorry but I don't build any drivers for hardware that I don't have on hand anymore because I simply can't support/tell when something is broken or doesn't work.

Not if you have bound the card to VIFO. It may be the case that radeontop works differently and tries to access it directly which in your case resulted in a crash. Your motherboard BIOS or your GPU BIOS <- the GPU BIOS is usually read only. My suspicion is that the card was not properly reset. Shut down your server, cut the power to the wall for about a minute and then try to boot again.

RadeonTOP or GPU Statistics? RadeonTOP does by default nothing other than modprobing your amdgpu, GPU Statistics also does nothing by default if you haven't configured it. Pretty sure, if you are binding a card to VFIO the host basically can't "see/use" it, it reserved for use in VMs so there is no point anyways if you install any of the two plugins because it is bound to VFIO. I really can't imagine that now you have a higher power draw because of this, because as said the two plugins even can't access your GPU. Please try a restart after the parity check finished, maybe shut down the system completely, wait a bit and then turn it back on.

Too less information that I can say anything. Where is the logfile, with which line did it crash?

Are you really sure that this was the cause of the issue? Have you yet tried to issue: radeontop from a Unraid terminal and see what the output is? No definitely not. Do you have bound the card to VFIO? I would strongly recommend that you wait for the parity check to finish and then see what the real power consumption is. Always post your Diagnostics with such issues like that, I really can't tell much without them and the above things are all assumptions...

That's what I thought two post before... You can also set the path to /mnt/user/... instead of /mnt/cache/... in the template but my recommendation would be to set it always to the real file path instead of /mnt/user/... at least for game servers (some won't even run if you use /mnt/user/...)

Nice, glad to hear that it is working. Yes, but that's not an issue. No, not if you are using it just for that, setting up your own Matrix server can be quite difficult and for such a use case it's most of the time not really worth the time and the matrix.org server does the job also just fine. It is safe to use the matrix.org server for that (of course as long as you've chosen a strong password for that account).

Yes, but you don't need to do that when you only want to push messages from your local network, you could always use my.unraid.ip:8050 internally to push messages. This is the admin account you have to set up and that is meant for creating applications through the pushbits api so to speak with pbcli No, I assume this is your account. Pushbits needs it's own account. No, you just need a server where you can create a user with a password so that Pushbits can use it to invite you to rooms and push messages. I assume you haven't created a account on your home server or the server that you want to use for the account for Pushbits. I hope this explains it a bit better admin: name: & password: <- this is the username and password (which you can specify) that is allowed to create/delete/list applications through pbcli matrixid: <- this is usually your account in this format: @yourusername:matrix.example.com (if you create a application Pushbits will invite this user to the room) matrix: homeserver: <- This is where the Matrix server for Pushbits itself is hosted and you first have to create the user on this server username: <- This is the Pushbits username on homeserver: password: <- This is the Pusbhits password on homeserver: So to speak it could look like this: admin: name: 'thewave' password: 'mysupersecretpassword' matrixid: '@thewave:matrix.org' matrix: homeserver: 'https://matrix.org' username: 'pb_thewave' password: 'superstrongpasswordhere'

I would recommend that you use your real domain like: https://matrix.yourdomain.com You only need one account for pushbits, if you create a application it will show up as a new room in matrix and the account pushbits will invite you to the room. Hope that makes sense. I heavily use pushbits and have around 15 to 20 applicaitons.

This shortcut is to hide and show the desktop.

Please wait until the copy finishes and then try again. I haven‘t seen this issue yet. You can try to press CTRL + ALT + D (but please remember that you have to use the noVNC side menu to simulate the CTRL and ALT key) If that all doesn‘t work you have to restart the container.

Please report that on the Plex forums since this is a Plex issue also read the first few posts on that page. i also can’t reproduce that on my test machine. If you report anything here I need your Diagnostics where you had that issue.

Click on the entries in the task bar.

Then the password is wrong, I've tried it now on a fresh installed container and it works perfectly fine: I even can reproduce this when I put in a wrong password: This is the log: You have to make sure that you use the admin credentials: Please also make sure that you've use the port 8080 like in this example. Check also if your password have quotes or double quotes in it and remove them if so, maybe you have some characters in it which Pushbits isn't too happy about. I would also recommend that you remove the database file again when changing passwords and create a new one with this commands when you are in the directory from Pusbhits: touch pushbits.db chmod 777 pushbits.db chown 99:100 pushbits.db (please change the file name if you are using a different on in your config.yaml) What you can try is to set the permission to 777 for pushbits which lives in your appdate folder with chmod 777 and to user and group to 99:100 with chown 99:100

Give me a bit please, I will try this on my machine a bit later with a fresh installed container.