Search results

If the web GUI is available, your PC must be booting Proxmox. Have you tried to ssh into the server? What does the monitor display when you boot your PC?

Do you happen to have any hook-scripts on the system that would be causing weird behavior? (particularly a backup-end hook script?) Could you post the config file for VM 161 (cat /etc/pve/qemu-server/100.conf)?

It's possible by: 1. Add the system user as a PVE user: pveum user add user@pam (assuming user@pam exists on the system) - It will now show up with: pveum user list 2. Add a permission for the user, giving it PVEAdmin: pveum acl modify <PATH> --roles PVEAdmin --users user@pam

Happy to help :)

I can confirm that this issue exists. I'll have a closer look at it, but for now, entering 0 for the user and group is the easiest workaround to achieve what you want.

I imagine that your problems started because of misconfigured repositories [1]. This is usually the case when apt is suggesting the removal of proxmox-ve. To clear up this confusion, there are two options in regard to network configuration in the GUI. If ifupdown is installed (default), the...

Hi, This sounds like an issue with your Windows machine rather than an issue with Proxmox. I'm not very familiar with Windows, but the link below provides a troubleshooting guide, which seems to cover the most common issues. https://windowsreport.com/windows-10-unable-to-ping-other-computers/

Hi, I was able to reproduce the issue, so opened up a bug report for it [1]. Thanks for reporting! [1] https://bugzilla.proxmox.com/show_bug.cgi?id=3369

I'd say that has more to do with the workloads of the server than ZFS itself. In general, it's advised to use enterprise SSDs (especially in production) for a multitude of reasons (kingsinton themselves have a good explanation [1]). [1]...

By using 4 SSDs in raidz1, you will lose roughly a quarter of the usable space, because of parity storage. In this case, rather than 2Tb, the 4SSDs will give you around 1.3Tb. There are calculators online that help you break down raidz setups [1]. [1] https://wintelguy.com/zfs-calc.pl

Hi, I tried to replicate this with no success. Could you post the exact error message from the backup? Does the machine go into a locked state or does it simply power down? Could you also post the output of pveversion -v?

The graph just shows the amount of data read/written (y-axis) at a particular moment in time (x-axis). This is useful as an overview, to understand if a specific VM is demanding on a disk. Are you referring to a value given in 'M' at the side, this would just mean that the VM read/wrote...

Yes, unfortunately, backup jobs in PVE weren't really created with more flexibility in mind, so in terms of PVE, the choice is currently between updating the cron job and losing it on the GUI, or being limited to daily snapshots. I would probably select the cron job, as it's not so difficult to...

I would only use kill -9 PID as a final step, in case there is no other way to stop a process, because SIGKILL gives the process no opportunity to clean up and exit correctly, which can leave around unwanted locks and files. But good that it finished without problem the second time. If it...

This is largely dependent on the tasks of each guest. You should consult the system requirements pages for any operating systems/software you are using. I would go one step further than this, and say always undersell, i.e., leave a physical core (2vCPUs in your cpu's case) for Proxmox itself...

Using Google translate, I translated your question to: Hello everyone, I would like your guide to know what I should do since the backup process has taken longer than normal and I have tried to kill the processes but I have not managed to stop it, it keeps appearing in this way in the tasks...

Following a snapshot, only differences are stored in the current state, so previous snapshots should only really be an issue if the data is changing rapidly and significantly. In your case where you had two old snapshots, I don't know what would suddenly cause the operating system to deviate so...

Could you check if the web gui is accessible through another browser? If that works, you could also try clearing cache/history/active logins in the original browser.

It seems like there are problems accessing the Debian repositories too. Could you provide more information on your network setup? Are you using any kind of proxy?

There macros are detailed in the appendix of the PVE admin guide [1]. They basically just specify the ports used by each service. [1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_integrated_firewall