Creating a Cluster issues

[LorenTedford]

Hello greetings I am bringing some of my servers home out of the data center and figured I would want to create a cluster here on the home network..

Here is what I have done.

The main server which I will label home is 192.168.9.201 and the second server will be labeled home2 its located on 192.168.9.202.

So here is the commands I have done.

On the first server which is home at 192.168.9.201 I typed this line.

pvecm create LorensServers

Then checked it via this command

root@home:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-04-01 07:25:49 CDT; 15h ago
  Process: 5280 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 5265 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 5276 (pmxcfs)
    Tasks: 6 (limit: 4915)
   Memory: 38.6M
      CPU: 31.250s
   CGroup: /system.slice/pve-cluster.service
           └─5276 /usr/bin/pmxcfs

Apr 01 17:25:48 home pmxcfs[5276]: [dcdb] notice: data verification successful
Apr 01 18:25:48 home pmxcfs[5276]: [dcdb] notice: data verification successful
Apr 01 19:25:48 home pmxcfs[5276]: [dcdb] notice: data verification successful
Apr 01 20:25:48 home pmxcfs[5276]: [dcdb] notice: data verification successful
Apr 01 21:25:48 home pmxcfs[5276]: [dcdb] notice: data verification successful
Apr 01 22:25:01 home pmxcfs[5276]: [dcdb] notice: wrote new corosync config '/etc/corosync/corosync.conf' (version = 2)
Apr 01 22:25:01 home pmxcfs[5276]: [status] notice: update cluster info (cluster name  LorensServers, version = 2)
Apr 01 22:25:01 home pmxcfs[5276]: [status] notice: node lost quorum
Apr 01 22:25:03 home pmxcfs[5276]: [status] notice: node has quorum
Apr 01 22:25:48 home pmxcfs[5276]: [dcdb] notice: data verification successful

Next I went to the home2 server which ip is 192.168.9.202 and entered in this.

root@home2:~# pvecm add 192.168.9.201

The authenticity of host '192.168.9.201 (192.168.9.201)' can't be established.
ECDSA key fingerprint is SHA256:ZkSUmqgZqmP0VPa4ep/6AffE9F+xgyH9Q+pm/ESPeN0.
Are you sure you want to continue connecting (yes/no)? yes
root@192.168.9.201's password:
copy corosync auth key
stopping pve-cluster service
backup old database
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
starting pve-cluster failed
root@home2:~# pvecm status
pve configuration filesystem not mounted
root@home2:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-04-01 22:25:03 CDT; 54s ago
  Process: 16445 ExecStart=/usr/bin/pmxcfs (code=exited, status=255)
 Main PID: 1453 (code=exited, status=0/SUCCESS)
      CPU: 7ms

Apr 01 22:25:03 home2 systemd[1]: Starting The Proxmox VE cluster filesystem...
Apr 01 22:25:03 home2 pmxcfs[16445]: fuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
Apr 01 22:25:03 home2 pmxcfs[16445]: [main] crit: fuse_mount error: Transport endpoint is not connected
Apr 01 22:25:03 home2 pmxcfs[16445]: [main] crit: fuse_mount error: Transport endpoint is not connected
Apr 01 22:25:03 home2 pmxcfs[16445]: [main] notice: exit proxmox configuration filesystem (-1)
Apr 01 22:25:03 home2 systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Apr 01 22:25:03 home2 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Apr 01 22:25:03 home2 systemd[1]: pve-cluster.service: Unit entered failed state.
Apr 01 22:25:03 home2 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
root@home2:~#

I am following the directions listed in pages 59 and 60 of the Proxmox VE Administration Guide I am curious as to what i might have missed that caused this to error out.

 

[LorenTedford]

I was able to fully remove the cluster although I was unable to get it to work correctly.. I have a concern though How much internal bandwidth is needed for using the feature?

 

[dietmar]

I have a concern though How much internal bandwidth is needed for using the feature?

All you need is reliable multicats. Bandwidth depends on the amount of changes in /etc/pve/

 

[LorenTedford]

What gets changed in /etc/pve? Is this just system changes? If I am understanding clustering correctly I am assuming that my system resources are being used on the physical hardware of the individual node that is host the vm rather then across the network and on another system.. Is this a correct assumption?

 

[LorenTedford]

I suppose for simplicity I may not want to use a cluster for my individual installations of prox.. Meaning although I don't understand what caused the failure I may not want to continue with the clustering process.. Not sure at the moment..