Search results

  1. Corosync error messages since reboot

    No manual changes, we added and removed nodes from the cluster. I will do an upgrade asap. The node was added via CLI. While adding the node to the cluster we haven't performed any reboot manually but because of a unidentified problem the cluster was rebooting by itself. root@xx-prox32:~#...
  2. Corosync error messages since reboot

    Hi Tom, I see the following outputs in the log: Here are the outputs ov pveversion -v: Proxmox 6.1 Nodes (all excepting the new one) root@xx-xx1-prox31:~# pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve) pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e) pve-kernel-5.3: 6.1-5...
  3. Corosync error messages since reboot

    Our latency is under 1ms every time and sometimes peaks to ~3ms. But this doesn't explain the problems mentioned here: https://forum.proxmox.com/threads/corosync-error-messages-since-reboot.71307/#post-321001
  4. Corosync error messages since reboot

    Hello, does nobody have an idea?
  5. Corosync error messages since reboot

    In this screenshot you can see a behavior for which we could not find a reason so far. It looks like the IP addresses of the nodes change when a new member is added to the cluster.
  6. Corosync error messages since reboot

    What do you think is the maximum latency for corosync?
  7. Corosync error messages since reboot

    Hello, the nodes aren't on the same switch and are also splitted over two DCs with multiple fiber links in between. We will do the upgrade as soon as possible. As there were no heavy changes between 6.1 and 6.2 regarding corosync (checked in changelogs) we installed the new node on the newest...
  8. Corosync error messages since reboot

    I will check the version! Thank you for this hint. (Checked it, the new node is on 6.2 and the old nodes are on 6.1) We had 7 nodes in the cluster and now have 8 nodes, can you imagine why we loose quorum when we add a new node? Regards, Alex
  9. Corosync error messages since reboot

    Hello, today we had a problem after adding a new node to a 7 node proxmox cluster. After adding the node the cluster rebooted completely. Since this reboot we are getting constantly (every second) the following message on two of our 8 nodes. corosync[2710]: [TOTEM ] Retransmit List: 1c23c We...
  10. [SOLVED] memory leak

    Sieht aus als ob das Problem behoben wäre. Vielen Dank nochmal!
  11. [SOLVED] memory leak

    Tatsächlich verwende ich check_mk und deren Agent. Danke für den Hinweis! Ich habe soeben das Update ausgerollt und werde das Verhalten nun beobachten. LG
  12. [SOLVED] memory leak

    Servus. Ich betreibe auf zwei dedizierten Maschinen Proxmox mit KVM und habe in letzter Zeit seit Debian 10 regelmäßig Probleme mit 90% der VMs. — Nachfolgendes bezieht sich auf die VMs und nicht auf den Proxmox Host. Auswirkung Nach einiger Zeit läuft der RAM + SWAP voll und das System fährt...
  13. [SOLVED] Cluster Synchronization failed

    Ich habe nun in Richtung SSH weitergesucht mx1 sshd[1105]: Received request to connect to path /var/run/postgresql/.s.PGSQL.5432, but the request was denied. Anschließend habe ich die SSH Config nochmals vom Original Kopiert und die beiden Systeme komplett neu gestartet. Siehe da, es...
  14. [SOLVED] Cluster Synchronization failed

    Servus, Da erhalte ich den genannten Fehler zurück root@mx0 /var/log # psql -h /var/run/pmgtunnel/ -p 3 Proxmox_ruledb psql: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. Ich habe soeben...
  15. [SOLVED] Cluster Synchronization failed

    Servus, der Service läuft, ja. Der Log kommt direkt aus /var/log/postgresql/postgresql-9.6-main.log am master (mx0). Das scheint mir die ganze Fehlermeldung zu sein. Ich ziehe diese aus dem "Syslog" Fenster im Webinterface. May 16 14:00:51 mx0 pmgdaemon[1067]: successful auth for user...
  16. [SOLVED] Cluster Synchronization failed

    mx0 proxmox-mailgateway: 5.1-1 (API: 5.1-2/0b56b766, running kernel: 4.15.18-7-pve) pmg-api: 5.1-2 pmg-gui: 1.0-42 proxmox-spamassassin: 3.4.2-1 proxmox-widget-toolkit: 1.0-20 pve-kernel-4.15.18-7-pve: 4.15.18-26 pve-kernel-4.15: 5.2-10 libpve-http-server-perl: 2.0-11 lvm2: 2.02.168-2...
  17. [SOLVED] Cluster Synchronization failed

    I can see the following lines in the postgres log file: postgres@postgres LOG: provided user name (postgres) and authenticated user name (root) do not match postgres@postgres FATAL: Peer authentication failed for user "postgres" That's part of the output of journalctl May 15 20:20:50 mx0...
  18. [SOLVED] Cluster Synchronization failed

    Servus, ich habe derzeit ein Problem, dass nach einer Neuinstallation von zwei Proxmox Mail Gateways die Synchronisation der Datenbank nicht sauber funktioniert. Ich erhalte im Syslog andauernd nachfolgenden Fehler May 14 23:02:57 mx0 pmgmirror[1035]: starting cluster syncronization May 14...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!