Search results

Thanks for the quick responses! For now, I changed the ARC cache size to 4 GB root@XXX:~# cat /sys/module/zfs/parameters/zfs_arc_max 4294967296 and increased the Windows VMs' RAM to 8 GB. I am now at 70 % RAM consumption on the host, so I am happy for the moment ;-) Will definitely look into...

Hi, I have a single PVE 7.3-4 machine that runs on the (default) ZFS setup. It is equipped with 32 GB of RAM and 512 GB + 1 TB disk space. On this machine, I have three VMs: - Windows #1 with 4 GB - Windows #2 with 4 GB - Linux with 256 MB Ballooning is enabled, but I did set fixed RAM limits...

Thanks for the hint, actually I *did* use the built-in support for ACME. Seems like something is going wrong then with updating the fingerprints. I will investigate further when it happens the next time. Philipp

@Dave.r: In my case, the error happened in an already existing cluster. I faced the - presumably - same issue recently (with PMG 7.0-7) and found https://forum.proxmox.com/threads/cluster-join-error-with-le-certificates.41525/ - it seems that due to Let's Encrypt being used, the fingerprint...

Completely removing the cluster (i. e. removing /etc/pmg/cluster.conf from both master and node) and recreating the cluster from the UI solved the issue for me.

Same problem here with 6.4-4. Logged in the GUI and both nodes (master/slave) said "master ERROR: fingerprint '54:03:74:39:BD:CF:A4:C7:XXXXXX' not verified, abort!" Deleted the slave from the master config, removed /etc/pmg/cluster.conf to re-join the cluster, but to no avail...

No more issues seen with 0.9.7. Thank you again!

Looks like the issue is still reproducible - backup is stuck for ~10 mins now :-( Do I misinterpret https://git.proxmox.com/?p=proxmox-backup.git;a=shortlog and the fix is in 0.9.7? root@jackie:~/backups$ proxmox-backup-client version client version: 0.9.6 root@jackie:~/backups$ top (...)...

Thank you for the quick response and the immediate fix!

Same here. Server and client have 0.9-4. 2020-11-04T10:24:42+01:00: starting new backup on datastore 'pvth_jackie': "host/jackie/2020-11-04T09:24:42Z" 2020-11-04T10:24:42+01:00: protocol upgrade done 2020-11-04T10:24:42+01:00: GET /previous 2020-11-04T10:24:42+01:00: download 'index.json.blob'...

Right after hitting the "Post" button, I realized my mistake: The CLI expects the realm, i. e.: proxmox-backup-manager user create test_2@pbs --password test2 ...which then works!

Hi, I have created several users via the WebUI which always contain an underscore in their username. This works: I now tried to automate the user creation by a script, but had to realize that the CLI does not accept usernames with an underscore. root@jane:~# proxmox-backup-manager user...