Search results

Have you tuned ksmtund.conf ? The defaults are ok for small servers. For bigger ones, you should set it to be more aggressive

See https://pve.proxmox.com/wiki/Dynamic_Memory_Management

On memory settings of each guest, you can configure an upper an a lower value of ram. Those will be used to auto balloon when ram pressure reaches 80% on the host. You should also check ksm is running, and maybe tune it a bit (ksmtuned.conf)

If your thin pool has been saturated (as it seems to be), there are good chances your guests filesystems are now corrupted

Already available with the quite new "SSD emulation" feature on SCSI disks

Because reducing is far more complicated and risky, if possible at all. It needs complex operations inside the guest, and depends on all the layers you use (file system, volume manager, software raid, crypt layer etc...) in the correct order. Most of the time it can only be done offline. And...

Yes, you can enable outbound antispam filtering, and trigger an alert to the admin

Thanks for your tips. Looks my issue is on the network. After disabling jumbo frames the random latency seems to disapear. I'll ask my hoster to have a look at this.

BTW, without dm-crypt, with just LVM on top of iSCSI, I have the same behaviour, so dm-crypt is not in fault here

Hi. I'm running a 3 nodes cluster, running latest PVE 5.2. As storage, I use iSCSI, but, as I don't fully trust the storage operators, I've added a dm-crypt layer. And on top of this dm-crypt, I've created an LVM VG which is shared on all node, and used as LVM storage. So, for every node, it's...

A reboot of the faulty node cleared the issue :)

It's the correct IP in /etc/pve/corosync.conf. Only pvesh get /cluster/status reports the wrong one.

Hi there. Due to a bad entry in /etc/hosts, one member of my 3-nodes cluster has the wrong IP in the cluster info. root@pve2:~# pvesh get /cluster/status --output-format=json-pretty [ { "id" : "cluster", "name" : "fws1", "nodes" : 3, "quorate" : 1, "type" ...

It's too tightly integrated with tons of other things I setup (IMAP proxying, AD auth etc...) to be usable as is. That's why I don't share them publicly. I'll send you a PM with a link if you're interested

In this case, @killmasta93 wants to use PMG as a smarthost from another postfix (at least that's how I understand it), so, PMG's GUI cannot help here ;-)

You need to add something like in main.cf relayhost = [pmg.domain.tld]:26 Port 26 of your Proxmox Mail Gateway should be reachable

There's no point in doing the checks twice. The goal is to have Proxmox Mail Gateway handling all the verifications and filtering, and then pass the good email to a "dumb" SMTP server, which won't filter anything.

Wow, thanks. This would indeed deserve some notes in the doc ;-)

Hi there. Here's a how-to for adding authenticated SMTP (smtps and submission against AD, or LDAP), DKIM (both verifier for inbound and signer for outbound) and DMARC support to PMG https://wiki.fws.fr/tuto/linux_divers/dkim_dmarc_onpmg (This is a "translation" from what I do using ansible...

I was thinking it would list all the inbound emails, by recipient address. But clearly, it's not. There're lots of email comming in (which I can see in the tracking center), which are not visible in Stats -> Receiver. Am I missing something ?