Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, Dec 22, 2016 at 10:53:24AM +0100, Roberto Resoli wrote: > Il 21/12/2016 12:40, Roland Kammerer ha scritto: > > On Wed, Dec 21, 2016 at 12:15:58PM +0100, Roberto Resoli wrote: > >> Il 12/12/2016 11:51, Roland Kammerer ha scritto: > >>> $ apt-get update > >> .... > >> W: Conflicting distribution: http://packages.linbit.com proxmox-43 > >> Release (expected proxmox-43 but got proxmox-4) > > Hi, > > > > yes we changed that, one repo per proxmox major release. We created > > symlinks but obviously this did not fix the expected Release. > > > > Please change your repo entry to point to "proxmox-4" instead of > > "proxmox-43". > > Yes, I tried and apt-get update went well. > > Unfortunately when upgraded to drbd components from the new linbit > repository on a node without running vm something started going wrong, > main issue being new drbdmanage from python-drbdmanage not working; even > a simple > > drbdmanage list-nodes > > resulted in a wait forever, without any info in syslog. There should be. Maybe set "loglevel=debug" in /etc/drbdmanaged.cfg For the second thing: There I would need more information. The version we ship and the one from proxmox are very different. In between these versions the architecture of DM was changed. Just as an example: If you have two nodes in your cluster and you started DM only on one node, it will never start up successfully. Or if only a minority of your overall nodes is operational, drbdmanage will refuse to start, as it waits for a majority. -) Try to get logging working. -) Maybe start with a simple one-node cluster. Just to check if it works in general. In that case startup is trivial and fast. -) Make sure that the majority (or in a two node cluster both) nodes have a running drbdmange ("drbdmanage startup"). In that particular version actually make sure all nodes are up. - Startup will take longer, look at the syslog where it writes who won the leader election, to which nodes it has contact, ... - Please start a new thread, I think this is not proxmox related, it is related to the new version and the new architecture. Thanks, rck