Search results

You should be able to tell whether there is actually an open session since Feb 14th by issuing who while logged in as root on the node. If there is actually a corresponding session you should investigate what is running (and why), with ps -A | grep <tty-id> and with ps auxwf | grep <tty-id> to...

With the default configuration, no. Though you can tell them to automatically start at boot under VM > Options > Start at boot However, with 5 VM's you will probably also get away with starting them manually ;)

Proxmox issues a shutdown job for running VMs when the host is shutdown.

Hallo, ich kann dir leider nicht die Lösung des Problems sagen, wollte dich aber darauf hinweisen dass der Link zu "Mögliche Lösung" kaputt ist. Den müsstest du also bitte noch einmal einfügen / reparieren.

It seems you could solve your problem. If you have the time, please explain what the problem was/how to fix it and mark the thread as solved so other community members with the same problem have an easier time finding it :)

Not being able to log in only in the GUI is usually a problem with clusters when they are in a non-quorate state. Are you running a cluster? The other errors you posted seem to all come from Postfix. MIsconfiguration or errors in postfix should not impair the PVE at all.

No, as of now there is no functionality to skip backups for stopped VMs and containers. For now you would still have to exclude VMs to skip manually. Still, backups for stopped VMs (that didn't change since the last backup) will not increase your disk usage due to deduplication, if you can...

Well I am afraid so too ;) Renaming the node is not really optional in this regard... I have not tried it but I believe if you change the node name now your configuration should be recoverable. To be sure, you can also revisit the corosync.conf afterwards and increment the config_version...

I suspect you won't really be able to get rid of this error, because it might result from a device not being loaded yet, similar to this bug report. You should be able to tell exactly which device is at fault here by issuing grep . /sys/class/thermal/thermal_zone2/type The message will most...

To rename a node you have to change its hostname and if its in a cluster then change its configuration in corosync: Please take a look at Renaming a PVE node for the proper way to rename a node. For safely editing the corosync config please also see the steps at PVECM - editing the...

This seems to indicate that Windows isn't actually "using" all of that RAM, it might just be using most of your still available memory for caching, which is normal behavior on most operating systems. At least that's how I would interpret what's at fault here. Did you install the QEMU guest...

What do you mean by user session, the command line window? I am not 100% sure how Windows handles that, but your script is launched by the Qemu-Guest agent and therefore the script is running as a child of the agent process. For the command line GUI windows to appear you probably would have to...

Not quite sure what the problem is, though I found a thread about this here on the forum (albeit rather old, but on PVE 6). Aaron suggested that it might have to do with RAM usage and the host not being able to clear it quickly enough, could you verify whether you have enough RAM available? A...

I don't understand, does your local script write the file or does the "remote" host? Also its not clear to me whether the "Invoke-RestMethod" causes the problem or if its somewhere else. Please elaborate what you mean by "file-write" exactly. If its the former, (and if you are running...

You might be able to send files to print over to your Raspberry Pi and print it from there depending on the printer manufacturer and driver compatibility. It is probably also possible to set up your Raspberry as yet another VPN server and then connect from the Windows VM to there for the time...

Just to expand upon ness1602s answer a bit: No, a cluster needs to be always quorate to work properly, not just for HA. High availability just means that the cluster will try to keep your HA-enabled VMs and containers always available, i.e. if a cluster node fails the HA-manager will launch...

Yes, you need a valid subscription to access the enterprise subscription repository by Proxmox. Like Fabian said, the security repository by Debian is in no way connected to the Proxmox repositories. You do not need a subscription key for this repository and really should not disable it.

I don't see any error with your statement to be honest but you can test whether the configuration is correct by running mount -a, which tries to mount all entries not yet mounted and usually tells you a bit more what the problem is.

From what I understand it seems some files in the cluster were not created correctly. Did you have existing guest VMs or containers on the nodes you added to the cluster? Also, please check whether your nodes have enough storage (even if unlikely with a new installation)...

Is it only happening on one specific VM or in all VMs? What kind of VM are you running, Windows 10, Debian, ...? In my experience this is usually a problem with guest drivers. DId you enable the QEMU guest agent? For a (temporary) workaround, using SPICE to access your VM should make it work...