[SOLVED] Lost web access and one node cluster

Gastondc

Well-Known Member
Aug 3, 2017
35
0
46
41
Dear,

I just updated Proxmox, and on rebooting I have the red node. That node also has no web service running.

I feel lost to do a troubleshooting


I have this problem in syslog:

/varlog/syslog

Sep 15 10:58:02 pmx02 systemd[1]: Stopping The Proxmox VE cluster filesystem...
Sep 15 10:58:02 pmx02 pmxcfs[16062]: [main] notice: teardown filesystem
Sep 15 10:58:02 pmx02 pve-ha-lrm[2382]: ipcc_send_rec failed: Transport endpoint is not connected
Sep 15 10:58:02 pmx02 pve-ha-lrm[2382]: ipcc_send_rec failed: Connection refused
Sep 15 10:58:02 pmx02 pve-ha-lrm[2382]: ipcc_send_rec failed: Connection refused
Sep 15 10:58:03 pmx02 pmxcfs[16062]: [main] notice: exit proxmox configuration filesystem (0)
Sep 15 10:58:03 pmx02 systemd[1]: Starting The Proxmox VE cluster filesystem...
Sep 15 10:58:03 pmx02 pmxcfs[17326]: [status] notice: update cluster info (cluster name pmx-guemes,
version = 7)
Sep 15 10:58:03 pmx02 corosync[16937]: [TOTEM ] A new membership (192.168.48.11:239076) was formed. Members
Sep 15 10:58:03 pmx02 corosync[16937]: [QUORUM] Members[1]: 2
Sep 15 10:58:03 pmx02 corosync[16937]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 15 10:58:03 pmx02 pmxcfs[17326]: [dcdb] notice: members: 2/17326
Sep 15 10:58:03 pmx02 pmxcfs[17326]: [dcdb] notice: all data is up to date
Sep 15 10:58:03 pmx02 pmxcfs[17326]: [status] notice: members: 2/17326
Sep 15 10:58:03 pmx02 pmxcfs[17326]: [status] notice: all data is up to date
Sep 15 10:58:04 pmx02 systemd[1]: Started The Proxmox VE cluster filesystem.


And then continues repeat this lines, all the time:

Sep 15 10:58:05 pmx02 corosync[16937]: [TOTEM ] A new membership (192.168.48.11:239080) was formed. Members
Sep 15 10:58:05 pmx02 corosync[16937]: [QUORUM] Members[1]: 2
Sep 15 10:58:05 pmx02 corosync[16937]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 15 10:58:06 pmx02 pve-ha-crm[2367]: ipcc_send_rec failed: Transport endpoint is not connected
Sep 15 10:58:06 pmx02 corosync[16937]: [TOTEM ] A new membership (192.168.48.11:239084) was formed. Members
Sep 15 10:58:06 pmx02 corosync[16937]: [QUORUM] Members[1]: 2
Sep 15 10:58:06 pmx02 corosync[16937]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 15 10:58:08 pmx02 corosync[16937]: [TOTEM ] A new membership (192.168.48.11:239088) was formed. Members
Sep 15 10:58:08 pmx02 corosync[16937]: [QUORUM] Members[1]: 2
Sep 15 10:58:08 pmx02 corosync[16937]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 15 10:58:08 pmx02 pvestatd[2348]: ipcc_send_rec failed: Transport endpoint is not connected
Sep 15 10:58:09 pmx02 corosync[16937]: [TOTEM ] A new membership (192.168.48.11:239092) was formed. Members
Sep 15 10:58:09 pmx02 corosync[16937]: [QUORUM] Members[1]: 2
Sep 15 10:58:09 pmx02 corosync[16937]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 15 10:58:11 pmx02 corosync[16937]: [TOTEM ] A new membership (192.168.48.11:239096) was formed. Members
Sep 15 10:58:11 pmx02 corosync[16937]: [QUORUM] Members[1]: 2
Sep 15 10:58:11 pmx02 corosync[16937]: [MAIN ] Completed service synchronization, ready to provide




root@pmx02:~# pvecm status
Quorum information
------------------
Date: Fri Sep 15 11:20:30 2017
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000002
Ring ID: 2/242844
Quorate: No

Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:

Membership information
----------------------
Nodeid Votes Name
0x00000002 1 192.168.48.11 (local)
root@pmx02:~#


root@pmx02:~# pveversion
pve-manager/4.4-18/ef2610e8 (running kernel: 4.4.76-1-pve)
root@pmx02:~#




Need help.... thanks you!!!
 
What was the networking error?Because I am having the exact same problem in my cluster. I

Hello.

In my case the problem it was de switch port, allow multiples vlan. And one of this has a lot multicast. We restrict the vlan and solved the problem.

but in your case, maybe is other reason.