Recent content by keeka

An uneducated guess, and one that assumes the 'vma_writer_close: close failed - Host is down' is not what's implied! But, could your live guest backup be failing because you do not have qemu agent installed (VMs) or enabled (PVE guest config)? Since they successfully backup when off/shutdown...

I haven't come across this kvm warning with PVE as yet (upgrade path PVE7->8->9). But I have encountered it after upgrading a regular Debian 12 desktop to Debian 13. The machine was unsupported and qemu would not even start. The kvm guests affected by the deprecated machine types were ancient...

I have many CTs, Some running with less than 128MB RAM. Host has only 32GB RAM total. So quite like to specify guest memory in MB!

I switched to chrony at some point but I cannot remember if I was using systemd-timesyncd or full ntpd. Either way AIUI `apt install chrony` will warn about removal of a conflicting package. My preference would be for switching time daemon rather than editing apparmor's package files. You could...

IIRC older PVE installs may have had the full debian ntp package. Newer installations and guides recommend chrony.

If you want the ability to reject mail based on spam score, I believe you must enable 'before queue filtering'. As far as custom rules, there are quite a few examples on here. You define those in /etc/mail/spamassassin/custom.cf. You can also define matches on headers directly in the web GUI and...

Mount tmpfs on /var/log/pve/tasks? You may also need to specify an alternate, writetable `--tmpdir`.

I have been burnt by this in the past when purging configuration from uninstalled packages (with ifupdown and grub-pc). I assumed common files were factored out in to some shared dependency but IIRC some configuration came from postinst scripts.

I am in a similar situation. I have a spare router but I've not needed it. Having no PVE storage on the system disk makes for a simple image of the entire system disk (<5GB) for peace of mind. Then apt update && apt dist-upgrade Modify apt sources apt update && apt dist-upgrade --download-only...

In these instances, where some MTA declines to relay a sender's message because the recipient domain fails some PBL/RBL query, I wonder if that MTA: sends an SMTP reject/fail response during the initial transaction. sends a failed delivery notification to the sender some point after accepting...

How many do that I wonder? To refuse to deliver an email because the receiving domain's MX is on a PBL (or other BL for that matter) doesn't seem inline with intended use of blocklists.

It's not clear to me from reading this thread or the linked bugzilla page if this is a bug or an anticipated consequence of recent kernel/security code. Assuming it is the latter, and is here to stay, will unprivileged containers no longer support RO mountpoints?

AFAIK smtp_helo_name=$myhostname and the latter comes from the template: myhostname = [% dns.hostname %].[% dns.domain %]. Try to regenerate the config files by way of pmgconfig sync --restart 1

The version numbering (~deb13u1), whilst originating from the proxmox repo, was unusual in my experience. Thanks for the information.

Why is, for example, the Debian package systemd available via the Proxmox repo? Also in this case it's newer than that on Debian repo. I have not encountered that before. Do I have misconfigured sources? ~# apt policy systemd systemd: Installed: 257.8-1~deb13u2 Candidate: 257.9-1~deb13u1...