Search results

That your VM is using a lot of RAM for "no reason" could be indicative of another problem with your VM setup, but is not the root cause here. By default, through the ballooning driver the VM will continually map new RAM whenever it needs it, and internally it will again "release" the memory...

In case you haven't found a good fix for it yet, and in any case, for completeness' sake: This setting may be a bit counter intuitive, but the startup delay for a VM does not delay the startup for this specific VM, but for the next VM coming after it in the startup order. You can set how long...

Das Rechtemanagment im PVE verfolgt hier schlicht einen anderen Ansatz. Rechte lassen sich auf VMs, Storages, etc. beschränken, dabei ist es egal auf welcher Node diese laufen (wenn in einem Cluster). Der Sinn hinter einem PVE-Cluster ist es ja, das Management, geteilte Storages, und das...

Hier wären 2 Basisinformationen noch sehr relevant: Bitte poste welche PVE-Version bei euch läuft mit pveversion -v Ist das Problem reproduzierbar? Bitte poste zudem was die Ausgangskonfiguration ist und welche Veränderung dafür sorgt, dass der Backup-Job plötzlich ausgeführt wird. Danke!

I only could reproduce the error "invalid PVEVNC ticket" here if I intentionally messed with the data in the PVEVNC ticket or by waiting until it expired. (As far as I remember the ticket has a lifespan of 40 seconds, so you need to use it rather quickly - please make sure to use a ticket that...

This seems to be a grub2 bug that is sometimes triggered with some configurations. This post has some more information and a possible solution to this problem. Changing something about the LVM config and running update-grub again seems to resolve the problem in the majority of cases. For more...

Gewisse Checks im Backend werden ganz "hart" auf "root@pam" überprüft. Bei diesen scheitert der Check mit API-Tokens jedes mal, da (wie in der Ausgabe in deinem Post steht) mit "root@pam!<token-name>" verglichen wird. Das Ganze ist schlicht eine Sicherheitsvorkehrung. Quasi steht der Gedanke...

Just if anybody is wondering. The standard timeout for shutting down a VM should be 60 seconds. However, this is configurable and can be set to a shorter/longer value. (E.g. through the GUI in the VM Options > Start/Shutdown order > Shutdown delay)

Ich konnte bei mir hier einen Directory-Storage nicht in einen Zustand bringen, bei dem ich diesen oder einen ähnlichen Fehler beim Löschen bekomme. Bitte poste mal den Output von pvesm status. Ich gehe mal davon aus, dass hier der Ordner /mnt/pve/Backup gemeint ist. Wenn dieser gelöscht ist...

Ok, thanks for the log. According to your journalctl messages it looks like you are using external hard drives connected via USB. Why you experienced these crashes/errors during system start? Hard to say, unfortunately, I don't know. Here's to hoping they don't come back on the new install. It...

Another thing I saw in a few forums regarding this was that some people received these errors because of e.g. faulty SATA connectors. If you have such at hand, please try to switch them out. Yes, please do so. The best way would be to pipe them into a file and attaching them to your next post...

Your SMART data looks fine to me, I can't see any problem indicators. Is the error message you posted above the only error message you are getting? I just realized that /dev/sde seems to be the culprit. That, however, makes me a bit confused about your setup, as you said you have only 4 disks...

A quick skim of Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK on Google seems to indicate that this is very frequently a hardware problem with the disk. Are you using HDDs or SSDs with your setup? Booting with a rescue drive and invoking smartctl /dev/<disk-id> on your root disk should give...

Ja, mehrere Nutzer im englischen Forum berichten, dass sie bisher keine Abstürze mehr hatten. Auch bei @itNGO, dessen Account in diesem Thread aktiv ist, scheint der Workaround das Problem zu beheben.

Hi, Please keep in mind that templates in the sense how LXC handles them and templates from Proxmox containers are not the same kind of thing. LXC templates are just blank slates that usually represent the bare minimum of the installation of one particular Linux distribution. A template in the...

Thanks for your suggestions! There is a load balancing feature in the works, though I am not sure whether that entails power saving features for the cluster node itself. I think the way corosync clusters work might become a problem here, because one would have to "dynamically" fiddle with the...

Yes, this is a problem we have been aware of for some time now, which affects the new 5.15 kernel versions. There is a workaround that seems to fix this issue detailed in this forum post. For some more information on this issue in a more tidy format please also take a look at the upgrade guide...

A bit more information about your storage topology is needed here. Do you have any hidden folders in your root directory for some reason? du -sh /.* | sort -hr Is /backup mounted directly or do you have subfolders mounted in there? What does lsblk say? You should be able to get a hold of where...

Are both outputs from node1? The output of both commands from node2 could also be useful here. It is a bit weird though, now that I read it again. 1. In the very beginning when you issued pvecm delnode for the first time, the node should have been removed from the corosync config already. 2. As...

It seems what you have already done, removing the second node from your cluster and resetting all corosync configurations there. (And perhaps adding it again after that) It sounds like there is still a remnant configurations folder for the other node on each node. However, to make sure please...