Search results

Yes, that was the issue. I fixed it. Thank you. What should I do differently when I replace SSL certificates in the future? Should I always manually update `cluster.conf`?

The issue seems to have been solved without intervention. Strange.

Via GUI. See attachment. And in `pmgcm status` as well: proot@mgw0-0:~# pmgcm status NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK mgw0-0(1) $ipremoved master S 57 days 12:40 0.17 62% 38% mgw0-1(2) $ipremoved node ERROR...

Yes. Certificates (/etc/pmg/pmg-api.pem and /etc/pmg/pmg-tls.pem) have been renewed and updated. Upon logging in. I do not see this fingerprint in /etc/pmg/cluster.conf . Where should I change the fingerprint? Also, does this mean manual intervention is required every single time the SSL...

I can confirm this issue does not occur on 6.0-7. Our production runs on 5.4-13, so I will try on that version as well.

No, this test host has 12. I have also updated my post to show that not setting vCPUs (`maxcpus`) but only setting `cores` leads to the same issue. I feel like Proxmox passes default values to 'smp' by mistake. root@pxdev:~# lscpu | grep CPU CPU op-mode(s): 32-bit, 64-bit CPU(s)...

Both my PMG clusters are in a 'strange' state. I have two completely separate PMG clusters and they are both complaining about the same fingerprint: fingerprint 'C2:DB:59:C8:1F:C4:C4:8E:50:1D:6F:9C:4B:B1:4F:CF:8A:B5:9B:BA:46:78:E4:EB:B5:5E:38:AC:62:90:7D:9A' not verified, abort! I do not know...

Issue: When creating a VM with Proxmox API, I get the error "kvm: maxcpus must be equal to or greater than smp" on startup. The startup command contains `-smp '4,sockets=1,cores=1,maxcpus=1'`, but these values differ from processor configuration: Values I am passing to API: cores = 6, vcpus...

Please see posts above. What I did is described there.

I am trying to decide between using XFS or EXT4 inside KVM VMs. My goal is not to over-optimise in an early stage, but I want to make an informed file system decision and stick with that. Situation: Ceph as backend storage SSD storage Writeback cache on VM disk No LVM inside VM CloudLinux 7...

I solved this by promoting previous slave to master, deleting new slave from cluster, then re-adding old master to cluster as slave (had to remove `/etc/pmg/cluster.conf`). I then promoted the old slave again. root@mxfilter0-0:~# pmgcm status...

Well, seems like both my master and slave are stuck in 'syncing' now: root@mxfilter0-0:~# pmgcm status NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK mxfilter0-0(1) 185.233.175.215 master S 2 days 13:53 0.28 57% 75% mxfilter0-1(2)...

I am currently running this script in a screen with `watch -n 1`: root@mxfilter0-0:~# cat fetch.sh cat /tmp/quarantinefilelist.1990 >> tmp.txt I will post the results in a bit.

Increasing the timeout did not help. Neither did the solution in the other thread, or so it seems. I rsync'ed `/var/spool/pmg` so the situation is the same on both nodes. root@mxfilter0-0:/var/spool/pmg# find | wc -l 622 root@mxfilter0-1:/var/spool/pmg# find | wc -l 622 I can imagine I now...

This seems quite likely, as both nodes were only able to reach each other on-and-off during the IP swap. I executed `pmgmirror stop` and `pmgmirror start` after patching `Cluster.pm`: root@mxfilter0-0:~# diff Cluster.pm /usr/share/perl5/PMG/Cluster.pm 303c303 < $host_name, '--timeout'...

70M on master, 480M on slave.

Both work..

I just migrated a cluster to another vLAN by swapping NICs and changing cluster IPs in `/etc/hosts` and `/etc/pmg/cluster.conf`. Everything seems to be ok, except the master is stuck in 'syncing' state. This seems to be due to 'pmgmirror' database sync failing, but I don't understand why. Sync...

I saw your patches on Bugzilla. Cool stuff! Exactly what I need.

Um, why would I not want this? I want my entire IPv6-only DMZ to be able to send mail.