Search results

For what its worth - I'm getting this too. Aug 06 16:06:07 pbs unix_chkpwd[23232]: password check failed for user (root) Aug 06 16:06:07 pbs proxmox-backup-api[612]: pam_unix(proxmox-backup-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=<ip> user=root Aug 06...

Has anyone had this issue with the installed kernels after the update to the PBS Beta? root@pbs:~# apt update Hit:1 http://ftp.au.debian.org/debian trixie InRelease Hit:2 http://ftp.au.debian.org/debian trixie-updates InRelease Hit:3 http://security.debian.org...

I've noticed with the change to PVE9 and PBS4 betas that I've had a lot of problems with my passkeys giving the following error message: Aug 06 13:57:34 pbs proxmox-backup-api[26218]: Credential backup elligibility has changed! Aug 06 13:57:34 pbs proxmox-backup-api[26218]: error in 2nd factor...

Reality is though, nobody is going to do that :D I'm guessing we can just disable the pve-test repo and enable the no-subscription one?

Nah - nothing to do with the update. Was more me switching from grub -> systemd-boot. My error :) Fair enough - I think I wrote that request :) I might convert a couple of ones I've manually hacked in to non-encrypted to test out the auto-sync jobs etc and go from there until that feature...

I upgraded to PBS 4.0.8 today, mostly seems to be fine. Is there any update on using LUKS encrypted disks as removable storage?

Hmmm - I'm on 9.0.0~12 and I don't see any of these new graphs...

So.... Bayes with more inefficiency?

You mean like Bayes filtering?

Thanks guys. Installed these updates just now: Get:1 http://download.proxmox.com/debian/pve trixie/pve-test amd64 apparmor amd64 4.1.1-pmx1 [711 kB] Get:2 http://download.proxmox.com/debian/pve trixie/pve-test amd64 libapparmor1 amd64 4.1.1-pmx1 [43.8 kB] Get:3...

I ran into this today doing an upgrade on a 2 node cluster: proxmox-ve: 9.0.0 (running kernel: 6.14.8-1-pve) pve-manager: 9.0.0~10 (running version: 9.0.0~10/0fef50945ccd3b7e) proxmox-kernel-helper: 9.0.0 proxmox-kernel-6.14.8-1-pve-signed: 6.14.8-1 proxmox-kernel-6.14: 6.14.8-1...

Looks like the torrent is dead. Happy to add seeding to it, but would need *someone* to have the complete torrent first. Adding a web source doesn't help as the metadata isn't complete atm.

I figured I'd try and fix this on my setup, as I keep getting: Jul 16 18:12:02 mailfilter pmg-smtp-filter[112488]: WARNING: check: dns_block_rule RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating /root/.spamassassin/dnsblock_bl.score.senderscore.com (This means DNSBL blocked you due to too many...

For what its worth, I run Fedora 42 in all my VMs with most having ballooning enabled and I don't see this :|

Copy the main.cf.in template from /var/lib/pmg/templates/ to /etc/pmg/templates/ and add your edits. Then run: pmgconfig sync --restart 1 you'll need to randomly check changes between the distributed template and your template in case things change. When you do hashmaps, make a new directory...

Given the number of guides here on configuring PMG, I thought I'd try to put together a guide that covers the latest versions of PMG - now that a number of things mentioned are not supported / functional anymore - or have been built into PMG. Link: http://link.crc.id.au/pmg Would be happy to...

Yeah - I didn't see that most of the list of changes are functional.... I'm trying to document my own steps here: https://link.crc.id.au/pmg Adding to it as I go.... but I need to sleep now.

I've been re-visiting these guides recently, and lots has changed... fail2ban now needs to use nftables instead of iptables, the given DCC stuff doesn't seem to work at all - I don't seem to get any mail scanned by DCC... I'm wondering if anyone has updated these guides in a while?

Thanks @fabian - I didn't think of trying a live migration - as the systems are in two very different locations and network configs are completely different for the VM. I ended up doing a backup to local storage, then scp'ing it between systems and doing a restore on the target. It's kind of...

Trying to migrate a VM from a standalone PVE system to a 2 node clustered PVE system. When I start the migration, it fails quickly with: 2025-07-03 14:51:09 remote: started tunnel worker 'UPID:mel-pm1:00270FB2:07501C9E:68660C3D:qmtunnel:205:root@pam!pdm-admin:'tunnel: -> sending command...