Hello,
I have just setup 3 x Identical Proxmox VMs running in VMWare workstation to test out the HA capabilities (The end goal is to install Ceph on them and see how it goes). My 3 nodes are called:
pm-ha01 - 10.2.10.131
pm-ha02 - 10.2.10.132
pm-ha03 - 10.2.10.133
After installing all 3, configuring networks/hostnames etc I went to create a new cluster.
The cluster has been created successfully.
Then, I ssh'ed into the 2nd proxmox host (i.e. pm-ha02) and typed
And here's what happens:
Here is the output of systemctl status pvedaemon.service :
Here's the output of systemctl status pveproxy.service
Here is the output of journalctl -xn
What is going on here?
I have just setup 3 x Identical Proxmox VMs running in VMWare workstation to test out the HA capabilities (The end goal is to install Ceph on them and see how it goes). My 3 nodes are called:
pm-ha01 - 10.2.10.131
pm-ha02 - 10.2.10.132
pm-ha03 - 10.2.10.133
After installing all 3, configuring networks/hostnames etc I went to create a new cluster.
Code:
pvecm create ha-clusterThe cluster has been created successfully.
Code:
root@pm-ha01:~# pvecm status
Quorum information
------------------
Date: Sat Feb 25 16:24:41 2017
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1/4
Quorate: Yes
Votequorum information
----------------------
Expected votes: 1
Highest expected: 1
Total votes: 1
Quorum: 1
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.2.10.131 (local)Then, I ssh'ed into the 2nd proxmox host (i.e. pm-ha02) and typed
Code:
pvecm add 10.2.10.131And here's what happens:
Code:
root@pm-ha02:~# pvecm add 10.2.10.131
The authenticity of host '10.2.10.131 (10.2.10.131)' can't be established.
ECDSA key fingerprint is 1c:45:44:e2:12:8c:f3:59:ec:5b:38:1e:02:59:5d:a4.
Are you sure you want to continue connecting (yes/no)? yes
root@10.2.10.131's password:
copy corosync auth key
stopping pve-cluster service
backup old database
waiting for quorum...OK
generating node certificates
merge known_hosts file
restart services
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and 'journalctl -xn' for details.
successfully added node 'pm-ha02' to cluster.Here is the output of systemctl status pvedaemon.service :
Code:
root@pm-ha02:~# systemctl status pvedaemon.service
â— pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-02-25 16:25:39 NZDT; 5min ago
Process: 1380 ExecStart=/usr/bin/pvedaemon start (code=exited, status=2)
Feb 25 16:25:39 pm-ha02 pvedaemon[1380]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Feb 25 16:25:39 pm-ha02 pvedaemon[1380]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Feb 25 16:25:39 pm-ha02 pvedaemon[1380]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Feb 25 16:25:39 pm-ha02 pvedaemon[1380]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Feb 25 16:25:39 pm-ha02 pvedaemon[1380]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Feb 25 16:25:39 pm-ha02 pvedaemon[1380]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Feb 25 16:25:39 pm-ha02 pvedaemon[1380]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Feb 25 16:25:39 pm-ha02 systemd[1]: pvedaemon.service: control process exited, code=exited status=2
Feb 25 16:25:39 pm-ha02 systemd[1]: Failed to start PVE API Daemon.
Feb 25 16:25:39 pm-ha02 systemd[1]: Unit pvedaemon.service entered failed state.Here's the output of systemctl status pveproxy.service
Code:
root@pm-ha02:~# systemctl status pveproxy.service
â— pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-02-25 16:25:39 NZDT; 6min ago
Process: 1383 ExecStart=/usr/bin/pveproxy start (code=exited, status=2)
Feb 25 16:25:39 pm-ha02 pveproxy[1383]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 13.
Feb 25 16:25:39 pm-ha02 pveproxy[1383]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Feb 25 16:25:39 pm-ha02 pveproxy[1383]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Feb 25 16:25:39 pm-ha02 pveproxy[1383]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Feb 25 16:25:39 pm-ha02 pveproxy[1383]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Feb 25 16:25:39 pm-ha02 pveproxy[1383]: Compilation failed in require at /usr/bin/pveproxy line 11.
Feb 25 16:25:39 pm-ha02 pveproxy[1383]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Feb 25 16:25:39 pm-ha02 systemd[1]: pveproxy.service: control process exited, code=exited status=2
Feb 25 16:25:39 pm-ha02 systemd[1]: Failed to start PVE API Proxy Server.
Feb 25 16:25:39 pm-ha02 systemd[1]: Unit pveproxy.service entered failed state.Here is the output of journalctl -xn
Code:
-- Logs begin at Sat 2017-02-25 16:22:35 NZDT, end at Sat 2017-02-25 16:27:41 NZDT. --
Feb 25 16:25:39 pm-ha02 systemd[1]: Unit pveproxy.service entered failed state.
Feb 25 16:26:01 pm-ha02 cron[1212]: (*system*vzdump) RELOAD (/etc/cron.d/vzdump)
Feb 25 16:26:51 pm-ha02 systemd-timesyncd[741]: interval/delta/delay/jitter/drift 256s/-0.002s/0.005s/0.004s/+38ppm
Feb 25 16:27:38 pm-ha02 postfix/qmgr[1207]: 8AD6010D8DF7: from=<root@pm-ha02.mydomain.com>, size=1804, nrcpt=1 (queue active)
Feb 25 16:27:38 pm-ha02 postfix/smtp[1399]: connect to mydomain.com[2406:e001:1:4000:99a1:5e5b:f8b2:27fa]:25: Connection refused
Feb 25 16:27:38 pm-ha02 postfix/smtp[1399]: connect to mydomain.com[2406:e001:1:4000:5802:c692:353a:870c]:25: Connection refused
Feb 25 16:27:38 pm-ha02 postfix/smtp[1399]: connect to mydomain.com[10.2.10.12]:25: Connection refused
Feb 25 16:27:38 pm-ha02 postfix/smtp[1399]: connect to mydomain.com[10.2.10.10]:25: Connection refused
Feb 25 16:27:41 pm-ha02 postfix/smtp[1399]: connect to mydomain.com[10.2.10.123]:25: No route to host
Feb 25 16:27:41 pm-ha02 postfix/smtp[1399]: 8AD6010D8DF7: to=<me@mydomain.com>, relay=none, delay=445, delays=442/0.01/3/0, dsn=4.4.1, status=deferred (connect to mydomain.com[10.2.10.1What is going on here?
