[SOLVED] can't control the cluster - proxy loop detected

[aPollO]

Hi Guys,

i habe a crazy issue. I can't control my cluster nodes and vms.
I can login into the proxmox ve webinterface on any node. The nodes shown as green. Cluster shown as OK (green).
But i can't start a VM. In my "Tasks" list i can see that the "Node" entry switches from the node names to a number "213". I don't no this number. My nodes don't have this number in it's names or ip addresses.



The command "qm list" does not give any output

root@proxmox01 ~ # qm list
root@proxmox01 ~ #

root@proxmox01 ~ # pvecm status
Quorum information
------------------
Date:             Tue Aug  7 11:12:08 2018
Quorum provider:  corosync_votequorum
Nodes:            2
Node ID:          0x00000001
Ring ID:          2/36
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      2
Quorum:           2
Flags:            Quorate

Membership information
----------------------
    Nodeid      Votes Name
0x00000002          1 192.168.30.8
0x00000001          1 192.168.30.30 (local)

root@proxmox01 /etc/pve # cat .members
{
"nodename": "proxmox01",
"version": 8,
"cluster": { "name": "cluster01", "version": 2, "nodes": 2, "quorate": 1 },
"nodelist": {
  "proxmox01": { "id": 1, "online": 1, "ip": "192.168.10.30"},
  "proxmox02": { "id": 2, "online": 1, "ip": "192.168.10.8"}
  }
}

IP addresses node proxmox01

• 192.168.10.30 - promox01
  
• 192.168.30.30 - proxmox01.giga

IP addresses node proxmox02

• 192.168.10.8 proxmox02
  
• 192.168.30.8 poxmox02.giga

All ip addresses are reachable and all hostnames are resolvable.

How can i futher investigate this issue?

 

[aPollO]

Now i see a third node in my three bar. The one with the "213". I dont know how this happened.

 

[dcsapak]

can you post the output of

pvesh get /cluster/resources

and

ls -l /etc/pve/nodes

 

[aPollO]

Hi Dominik,

thank you for your assistance. With this i found out wahts the problem. I don't know exactly how i could happened but on the first cluster a command "hostname 213.XXX.XXX.XXX" was entered. The hostname from the first node changed to the IP-Adress 213..... and the confiusion has started.

I hope i can solve this muddle cluster