Search results

I guess it comes down to convenience and minimizing impact. It would allow us to keep using the keys generated in Zimbra and just migrate them to PMG, without having to change DNS entries. In addition, it would be more in line with how bigger E-Mail service providers handle those things. All in...

We are currently evaluating PMG as a gateway for a Zimbra instance, designed to serve >32 domains in its final form. Currently, Zimbra signs every domain with a seperate key and we would like to let PMG do the DKIM signing in the future. However, currently PMG supports only one key for all...

Update: I reinstalled the whole cluster to check my documentation of the installation process and did not configure the no-subscription repo, so the PMG hosts are still on version 8.0.3. With 8.0.3 I can see mails in the quarantine for both the main address and the alias, so the problem might be...

Since I am unable to conclude the evaluation process without information on this topic, any reply here would be much appreciated!

Hi there! We are happy users of PVE and PBS and are currently evaluating PMG v8.0.7 for one of our projects. I am currently testing the options users have to access their spam quarantine and have configured LDAP auth for this purpose. While synchronizing and authentication works fine, I'm...

Hallo! Wir möchten drei PVE Systeme neu aufsetzen. Dazu müssen zunächst unsere Subscription Keys (Community) freigeschaltet werden. In der Vergangenheit hat das immer unser Reseller übernommen, bei dem wir die Keys ursprünglich gekauft hatten. Von dem erhalte ich allerdings schon seit einer...

After installing pve-ha-manager (3.6.1) and doing some rudimentary testing, I can confirm that every node remained in maintenance mode after reboot. The issue seems to be solved. Is there anything specific to look for in the logs to be certain?

Hi mira, we have no cluster without subscriptions at hand. Is there an easy way to install this package on a cluster with subsciptions out of the pve-no-subscription repository without risking to install any other packages?

Got it, thank you for clarifying. I guess we will leave ha-rebalance-on-start disabled until its behaviour is changed accordingly.

I had the same suspicion, but cannot confirm it. 'Slave' nodes have this issue as well.

I guess it comes down to what's actually meant by started. Does it mean: 1. the HA manager is started for the VM 2. the VM itself is in state started (although the terminology in PVE is running in general) My interpretation and expectation would be 1. with the VM then being online migrated as...

Like this: console: html5 crs: ha=static ha: shutdown_policy=migrate keyboard: de max_workers: 10 next-id: lower=3000,upper=3500 notify: package-updates=never u2f:

I recently updated our clusters to 7.4 and played around with CRS and ha-rebalance-on-start. I noticed that when I added a new VM to the HA manger with ha-rebalance-on-start enabled and the VM would then be migrated to another node, it shuts down the VM before migration and then starts it again...

Well, there's nothing special about it. I set one of the cluster nodes to maintenance mode by executing ha-manager crm-command node-maintenance enable <node>, wait for the VM migration and transition to finish and then reboot. I wasn't able to find a way to force this behaviour yet, it just...

Sure thing. Here are the logs.

I just updated one of our clusters to 7.4 and was playing aroung with node maintenance mode. It is stated in the documentation that the maintenance mode persists on reboot and is only deactivated through the ha-manager command. However during my testing it occured several times that after...

Thanks a lot for the quick reply. Good to know its already been addressed. One last question: Since this is a productive cluster, will stopping the CRM service cause any interference with the running VMs?

Hi there! I was trying to set a node in our cluster to maintenance mode, but had a typo in the node name, so instead of typing ha-manager crm-command node-maintenance enable pve11 the node name was pve01. To my surprise there was no error message displayed and after taking a look at the HA...

Thanks for the info. Is there any way to check if it was added to the enterprise repos?

The other day, I had to do some updates on several VMs across our network and wanted to take some snapshots including RAM beforehand. The machines are running on different PVE clusters, all clusters consisting of three nodes each with PVE 7.2-4 and hyperconverged ceph 16.2.9 underneath. All VMs...