ich777

IIRC this is the way that rsync handles snaphsots but it doesn‘t keep all files it keeps only the files that did not change. luckyBackup is just a GUI for rsync and it uses rsync as the backend for backups/snapshots. I would recommend that you create a issue on the maintainers SourceForge repository to solve this issue.

Because this is how luckyBackup does it. That's the nature of snapshots, you have to keep the old ones to actually be able to recover the files. Imagine if a file doesn't change in years and is there since day one so to speak was snapshot in the first backup run, if you would delete the first entire snapshot directory that file would be gone. However all the other files which changed over time will be deleted from the first folder but the not modified file in that folder has to stay if you want to recover the data some time later. Hope that makes sense to you.

Glad that you've solved it! Oh, I think that those cards don't have a cooler on them correct?

Are you sure that your server is able to reach the GitHub API? Do you have any AdBlocking somewhere on your network? Do you have any Unifi gear on your network? Make sure that the server can communicate with the GitHub API and from what I can see something is preventing it from communicating with the API. However, I would also strongly recommend that you upgrade to the latest Unraid version 6.12.6

First of all I would recommend that you upgrade to 6.12.6 This is named differently sometimes and may be something like "Support Large Address Space" or similar and hides in on of the PCI sub-menus. Please make also sure that you have the latest BIOS version installed. Have you yet tried to put the card in another PCIe slot (if that's possible on this board)? You can also try to boot with UEFI instead of Legacy. I have also seen that you are using S3 Sleep, are you actually active using it? Please keep in mind that a Tesla is a Datacenter card and was never meant to be put into Sleep mode <- but I actually don't recommend putting the server into sleep mode anyways because on some systems this causes issues. BTW, you don't have to create a nvidia-bug-report.log since all the necessary information are in the Diagnostics.

Nein, die GUI nutzt sogar diese Funktion im Hintergrund.

It is really hard for me since I don't have such hardware where I even can test SR-IOV. However you can post your Diagnostics again with the card bound to VFIO and without it bound to VFIO.

Hast du denn einen gleichnamigen Container auf dem Backup system? Wenn ja, sind die Pfade auch richtig zu den Backups angegeben wo du hinsynchronisierst? Das ist auch so gewollt, ein Backup ist ein Backup vom Container und kein Snapshot. Das stimmt so nicht, mach ein Unraid Terminal auf und dann gib mal: lxc-autobackup ein, das ist eine Funktion die ich geschrieben habe und nur auf Unraid verfügbar ist. Diese Funktion ermöglicht es dir automatisch Backups zu erstellen und auch wiederherzustellen. Die Anzeige in der GUI ist nur bereits für bestehende Container gedacht von denen du Backups erstellst, selbst wenn du einen Container löschen solltest, das Backup bleibt bestehen und wird nicht gelöscht (weil es eben ein Backup ist) das du dann vom Terminal wiederherstellen kannst. Wenn du die Anzeige im GUI willst legst dir einfach einen leeren, gleichnamigen Container auf dem Backup system an und syncst dann dort in das Verzeichnis das du dort angegeben hast. (bitte beachte hier die Usage und ob du die global config verwendest oder nicht)

Metamod and Sourcemod won‘t work in cstrike 1.6, you could however use RCON. Please take a look at the screenshots again, this is cstrike 1.6

But this is a completely different issue or am I wrong? However I've pushed an update to the container, the container will download and install the unstable branch now just fine and the container should also start if you have no Internet connection. Please update the container itself (go to the Docker page, enable Advanced View in the top right corner, click on "force update" at the container, wait for it to update and disable Advanced View again). Hope that helps.

Kann ich so nicht bestätigen, hier läuft alles. Entfern das Sprachpaket und installier es komplett neu, siehe Lösung von @alturismo EDIT: Hier nochmal ein Screenshot von einem Test Server:

Sorry but I only support running the current or at least newer versions from the dedicated server since the setup was a bit different if I remember correctly. However to go a bit more in detail the old executable was called: "MistServer-Linux-Shipping" the new executable is called "MistServer" and this is why it is not working, it simply can't find the game executable (you where referring to the .sh file which I don't use because this could introduce other difficulties...). Anyways, I've pushed an update to the container so that it now should start even the old server executable just fine. Please update the container itself (sorry, can't tell you how to do that on a Synology NAS) and let me know if it's working.

Please stop the container, delete the file: installed-1.19.0-rc.4 from the data directory from the container and after that it should pull the archive again and hopefully the container should start since nothing has changed. The executable should be: VintagestoryServer.exe which should be in the main directory, however if you remove the file from above and start the container again it should also work fine.

Könnte auch sein weil du eine gecrackte Version von Unraid hast und dort meistens Backdoors bzw. andere lustige Sachen eingebaut sind so wie es bei diesen Releases war die du hier verwendest. Ich vermute das du diese Version von einer Vertrauenswürdigen Quelle von Russland oder China hast richtig? Du weißt das die von dort kommen... Sorry aber generell muss ich sagen es gibt erst wieder Support wenn du dir eine Version gekauft hast und eine Diagnostics postest von der. @SpencerJ

It could be the case that sleep is causing that because sleep is somewhat unstable in Linux and I would never recommend using it on a server but that's always up to the user.

If it is working for you then I would recommend sticking to the current driver that you already have installed and not change anything otherwise you can try the driver from the CA App which Fix Common Problems tells you to install.

Can you please give me a bit more details, is this a existing installation that you try to upgrade? Have you yet installed any modules? However it seems that something is wrong with your modules, what path's have you set in the template and so on? You can extract the logs from a Unraid terminal if you do something like that: docker container logs MagicMirror-2 > /mnt/user/appdata/magicmirror2.log This will write the log to /mnt/user/appdata/magicmirror2.log you maybe have to set the container name which is in the above command MagicMirror-2 I tried it now on a fresh set up version and it seems to work fine:

Where? On CS:Source? I just set it up and it is working as expected: I can also connect to the container without any issue.

So I've tried now many things and I'm happy to report that it is indeed working and only the specified port in the template is needed. I've forwarded port 27016 UDP in my firewall, disconnected the network connection to my PC, set up a Hotspot on my mobile phone, connected my PC to it and I can connect to it via the hotspot. Strangely enough it is not working when I try to access the server from the server list when I'm on my LAN, so to speak when the game is listed with the suffix "(LAN)" right next to the server name <- seems like this is some kind of bug in the game since this was working when I initially create the container. However if you are on the LAN you can connect through direct connection. I've now deleted the server already but if you really want to I'll set up another instance that you can try to connect and you will see that it will indeed work.

I have now tested it and it is working flawlessly: I have both tested to connect from inside my local network and from outside. Have you yet tried to connect with the local IP from your server just for testing purposes? Maybe you have issues with Hairpin NAT. Nothing to worry about, this is the case for most dedicated game servers.

Are you sure that you look in the correct server.cfg, the container usually ships with a server.cfg that has the password "Docker" and "adminDocker" (also right in the first post of this thread) set by default.

Yes, a new maintainer will make it available on the CA App. However you can ignore that because the container is maintained by someone else and it should receive updates as usual. 😉

Yes.

Please update the container itself (by clicking "force update" on the Docker page with Advanced View enabled) and it should work again.

Thanks for the report, I will look into that and report back.