[SOLVED] 2 Cluster nach Cluster-"Aufräumarbeiten"

Mischmosch

New Member
Jul 5, 2024
11
1
3
Guten Tag zusammen,

ja, ich musste bei dem Titel auch lachen.
Ich habe mein Cluster aufgeräumt, also VM/CT entfernt und andere auf die richtigen Server verschoben.

Dies alles kam daher, dass ich den "Main-Server" ausgetauscht habe. Nachdem ich diesen aus dem Cluster von drei Rechnern entfernen wollte, hatte ich auf einmal zwei Cluster mit jeweils einem Rechner.

Eine Verbindung auf den jeweils anderen habe ich nicht.

1720386427201.png & 1720386440876.png

Kann mir jemand sagen, wie ich die beiden wieder zusammengeführt bekomme?

Vielen lieben Dank für eure Rückmeldung und liebe Grüsse,
Mischmosch
 
Wie ist der Status von corosync? Ich suche gerade nach der Anleitung für das starten vom proxmox cluster fielsystem im lokalen modus; pmxcfs -l
da gibt es recovery-szenarien, mit denen man splitbrain reparieren kann.

* `pvecm status`
* `pvecm members`
* `journalctl -r` (general logs)
* `journalctl -r -u corosync.service` - corosync logs
* `journalctl -r -u pve-cluster.service` - pmxcfs logs
 
Last edited:
Wie ist der Status von corosync?
Vault1
Code:
root@vault1:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
     Loaded: loaded (/lib/systemd/system/corosync.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-07-07 23:00:13 CEST; 13h ago
       Docs: man:corosync
             man:corosync.conf
             man:corosync_overview
   Main PID: 1134 (corosync)
      Tasks: 9 (limit: 18930)
     Memory: 130.2M
        CPU: 3min 39.905s
     CGroup: /system.slice/corosync.service
             └─1134 /usr/sbin/corosync -f

Jul 07 23:00:13 vault1 corosync[1134]:   [QB    ] server name: quorum
Jul 07 23:00:13 vault1 corosync[1134]:   [TOTEM ] Configuring link 0
Jul 07 23:00:13 vault1 corosync[1134]:   [TOTEM ] Configured link number 0: local addr: 192.168.1.200, port=5405
Jul 07 23:00:13 vault1 corosync[1134]:   [KNET  ] link: Resetting MTU for link 0 because host 1 joined
Jul 07 23:00:13 vault1 corosync[1134]:   [QUORUM] Sync members[1]: 1
Jul 07 23:00:13 vault1 corosync[1134]:   [QUORUM] Sync joined[1]: 1
Jul 07 23:00:13 vault1 corosync[1134]:   [TOTEM ] A new membership (1.a) was formed. Members joined: 1
Jul 07 23:00:13 vault1 corosync[1134]:   [QUORUM] Members[1]: 1
Jul 07 23:00:13 vault1 corosync[1134]:   [MAIN  ] Completed service synchronization, ready to provide service.
Jul 07 23:00:13 vault1 systemd[1]: Started corosync.service - Corosync Cluster Engine.

Vault2
Code:
root@vault2:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
     Loaded: loaded (/lib/systemd/system/corosync.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-07-07 23:01:16 CEST; 13h ago
       Docs: man:corosync
             man:corosync.conf
             man:corosync_overview
   Main PID: 964 (corosync)
      Tasks: 9 (limit: 18730)
     Memory: 132.6M
        CPU: 4min 39.472s
     CGroup: /system.slice/corosync.service
             └─964 /usr/sbin/corosync -f

Jul 07 23:01:16 vault2 corosync[964]:   [KNET  ] host: host: 3 has no active links
Jul 07 23:01:16 vault2 corosync[964]:   [KNET  ] link: Resetting MTU for link 0 because host 2 joined
Jul 07 23:01:16 vault2 corosync[964]:   [QUORUM] Sync members[1]: 2
Jul 07 23:01:16 vault2 corosync[964]:   [QUORUM] Sync joined[1]: 2
Jul 07 23:01:16 vault2 corosync[964]:   [TOTEM ] A new membership (2.9e) was formed. Members joined: 2
Jul 07 23:01:16 vault2 corosync[964]:   [QUORUM] Members[1]: 2
Jul 07 23:01:16 vault2 corosync[964]:   [MAIN  ] Completed service synchronization, ready to provide service.
Jul 07 23:01:16 vault2 systemd[1]: Started corosync.service - Corosync Cluster Engine.
Jul 07 23:03:44 vault2 corosync[964]:   [QUORUM] This node is within the primary component and will provide service.
Jul 07 23:03:44 vault2 corosync[964]:   [QUORUM] Members[1]: 2

* `pvecm status`
* `pvecm members`
* `journalctl -r` (general logs)
* `journalctl -r -u corosync.service` - corosync logs
* `journalctl -r -u pve-cluster.service` - pmxcfs logs
Soll ich die Logs von jedem Vault mal liefern?

Vielen Dank für die Rückmeldung.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!