Recent content by Zack Coffey

I get that message on Ubutnu, CentOS and Debian on various systems that boot just fine. It means nothing for the boot. It just happens to be the last message displayed, it has nothing to do with any problem you might be having.

That didn't seem to make a difference. Even if I don't do that, both sides get updated with the right one. But they still keep going in and out of sync.

Hmm, I'm guessing config_version is different than corosync.conf version entry? https://linux.die.net/man/5/corosync.conf This says "version" should only be "2". So I've left it at 2.

Doesn't seem to matter what I use. I've tried one, the other and just the network. According to this: https://www.suse.com/documentation/sle_ha/book_sleha/data/sec_ha_installation_terms.html > As the same Corosync configuration will be used on all nodes, make sure to use a network address as...

root@pve1:/etc/pve# cat corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: pve2 nodeid: 2 quorum_votes: 1 ring0_addr: pve2 } node { name: pve1 nodeid: 1 quorum_votes: 1 ring0_addr: pve1 } } quorum { provider...

corosync.conf... bindnetaddr.... that shouldn't be the same for both systems should it? If I change it on one, restart services, then the other host gets updated and has the same bindnetaddr which is wrong for itself?

So I added the unicast line to /etc/pve/corosync.conf, all services restarted ok. Each system can, again, see each other for a moment and then they can't. Here's a tail of syslog. Dec 1 14:18:27 pve2 corosync[1850]: [TOTEM ] Retransmit List: 182 183 184 Dec 1 14:18:27 pve2 corosync[1850]...

So it looks like multicast is the problem, again. It seems very flaky. I have both of these hosts connected through 2 different switches for redundancy and congestion mitigation. Well it appears there's some loss of multicast in IT's core switches, so sometimes each host can see each other...

This URL seems empty yet referenced from several posts and other wiki pages. https://pve.proxmox.com/wiki/Troubleshooting_multicast,_quorum_and_cluster_issues

PVE2 root@pve2:~# service pve-cluster restart root@pve2:~# service pvedaemon restart root@pve2:~# pvecm nodes Membership information ---------------------- Nodeid Votes Name 2 1 pve2 (local) root@pve2:~# pvecm status Quorum information ------------------ Date...

PVE1 root@pve1:~# service pve-cluster restart root@pve1:~# service pvedaemon restart root@pve1:~# pvecm nodes Membership information ---------------------- Nodeid Votes Name 1 1 pve1 (local) root@pve1:~# pvecm status Quorum information ------------------ Date...

I have 2 Proxmox 4.3 systems setup and working for the most part. They used to have a quorum but now they seem not to. I just updated both and rebooted both systems and the webUI shows pve1 and pve2 nodes, but they seem to go in and out of being available to each other. One minute they will show...

Well, problem seems to be gone now. For the record, it's a mix of Ubuntu 14.04 and 16.04. Very simple setup, no firewalls, no traffic limits. The one VM I was seeing the problem with, both VM's were sitting on the same Proxmox host with, what I would consider, a simple setup. Each VM has 1...

We have a couple BIND9 servers on Ubuntu server setup on different Proxmox hosts. Doing a very simple test of 'dig' from a separate host gives a 0-1ms response time. However, doing the same test from a new VM on the same Proxmox host as one of the BIND9 servers takes 22-37ms. It's on the same...

Right now we are still testing the waters, so we have anywhere from 1-4 metal servers and between whatever we come up with will be 6-24 virtuals. These virtuals will mainly be used as management hosts for running tests on other equipment. So people aren't running all their testing from their...