Recent content by Mihai

So to make it more clear, all emails go through Proxmox Mail Gateway. You want to route emails depending on their source, a specific domain, and route them to a specific server? If so, I found this thread with what I believe is an answer to your question: Sender based routing

edit: I think I am confused as to what you are trying to do, so you can ignore this reply. Here are my notes: postfix relay settings at /etc/postfix/main.cf relayhost =pmg.domain.com:26 myhostname = hostname mydomain = domain.com myorigin = mailsender.domain.com To test send from command...

I would just clone the disk to the bigger one, resize it using a live cd (Gparted), then replace it as the boot disk. I wouldn't even bother reinstalling Proxmox.

3-Node Cluster with CEPH RDP backend. Note, this should not be due to Proxmox or CEPH updates, since it never changed while this issue started to occur. Header Proxmox Virtual Environment 8.0.3 Search Node 'VMHost2' Day (maximum) CPU usage 2.20% of 24 CPU(s) IO delay 0.13% Load average...

Thanks for the tip but unfortunately, it did not solve the issue, and it also made the server fans run at 100% so I reverted.

I installed the intel-microcode package and restarted then I used all of the following commands to check for a microcode update and there were none. dmesg | grep "microcode updated early to" journalctl -b -k | grep "microcode updated early to" zgrep "microcode updated early to"...

I've got BIOS Version 2.9.0. The only critical Licecycle Errors in the past 2 years are chassis opened, drives removed and power supply redundancy lost (regular stuff). Warnings have to do with NIC ports going up and down. I've never installed any intel-microcode package for a CPU update. I'm...

I've been working with a Dell R520 with dual Xeon(R) CPU E5-2430 v2 @ 2.50GHz and I've had this recurring issue (for multiple years) after various kernel updates where the virtual machines (both windows and linux) lock up. Previously, I was somehow able to rectify this issue by disabling as...

Fabian, Thank you so much for your help, I was able to successfully re-add the correct corosync addresses and clean up the config file. You were right, steps 6-8 were not necessary. To summarize for anyone else needing help: Step 1. Disarm HA systemctl stop pve-ha-crm systemctl stop...

Here I meant that this wording does not exist in the newest wiki: bindnetaddr: 10.10.2.0 ringnumber: 0 But you did answer this question and you said it was not necessary, so I will remove this from the conf file. Running corosync-cfgtool -s at this moment, here is the result: Local node ID...

Actually now that you ask, I did not provide the complete story properly. Let me start again. This was the original corosync.conf: nodelist { node { name: VMHost2 nodeid: 3 quorum_votes: 1 ring0_addr: 10.10.2.16 } node { name: VMHost4 nodeid: 1 quorum_votes: 1...

Hi Fabian, thank you for the information. but I don't fully understand the procedure: Which link(s) do I need to remove? Do I need to remove the same link on each node? I thought link 0 was the same address on both configurations: 10.10.2.16, so I am confused. How do I remove the link? I guess...

Updated original post with PVE version information.

Here's the original corosync: nodelist { node { name: VMHost2 nodeid: 3 quorum_votes: 1 ring0_addr: 10.10.2.16 ring1_addr: 10.10.1.16 ring2_addr: 10.10.0.16 } node { name: VMHost4 nodeid: 1 quorum_votes: 1 ring0_addr: 10.10.2.14 ring1_addr...

I have an existing 3 node cluster that was originally created in Proxomx 5.x. proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve) pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1) pve-kernel-helper: 7.2-2 pve-kernel-5.15: 7.2-1 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.30-2-pve: 5.15.30-3...