constantly being asked to login proxmox 4.1-22

[dirtbag]

Hey, Ive been running proxmox for a while and thought I would try to make my two servers clustered..
well, I got them joined together, but now my main host keeps asking me to login over and over again..
I have since removed the second node from my cluster, but the first main node continues to
prompt me for login every so often although I am not logging out.
any ideas?

root@rock:/# pveversion -v
proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-39
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie

i see this in the logs..
Mar 23 14:28:43 rock pveproxy[19154]: ipcc_send_rec failed: Connection refused
Mar 23 14:28:43 rock pveproxy[19154]: ipcc_send_rec failed: Connection refused
Mar 23 14:28:43 rock pveproxy[19154]: ipcc_send_rec failed: Connection refused
Mar 23 14:28:43 rock pveproxy[19154]: ipcc_send_rec failed: Connection refused
Mar 23 14:28:44 rock pvecm[19967]: ipcc_send_rec failed: Connection refused
Mar 23 14:28:44 rock pvecm[19967]: ipcc_send_rec failed: Connection refused
Mar 23 14:28:44 rock pvecm[19967]: ipcc_send_rec failed: Connection refused
Mar 23 14:29:04 rock pveproxy[18475]: ipcc_send_rec failed: Transport endpoint is not connected
Mar 23 14:29:04 rock pvedaemon[3876]: ipcc_send_rec failed: Transport endpoint is not connected
Mar 23 14:32:05 rock pveproxy[19197]: ipcc_send_rec failed: Transport endpoint is not connected


-db

 

[dirtbag]

i found https://pve.proxmox.com/wiki/Proxmox_Cluster_file_system_(pmxcfs)#Remove_Cluster_configuration
which seems to have fixed it.

 

[sdinet]

When you add and remove nodes from the cluster, you damage the configuration. I would start over again to be safe, and make sure the nodes have the same system time.