Search results

In fresh upgraded cluster to 4.4-1/eb2d6f1e, if i try to open a SPICE console on a vm residing on cluster nodes different from the one i'm logged in, I receive an "HTTP proxy connection failed: 401 invalid ticket" error. rob

I think is the combined effect of firefox (50.1 currently) upgrade with ad/tracking block extension. The 4.4 version of pve does not plays a primary role; we have some 4.3 in production, and the problem is exactly the same (exception in noVNC, no live graphs in the GUI)

Same error here. We found it related to the presence of anti-tracking/anti-ad extension, "privacy badger" and "adblock plus" in particular. Note that whitelisting the specific pve GUI site is not sufficient, the problem disappears only disabling the extension globally. In Privacy Badger case...

Try with: drbdsetup primary --force vm-221-disk-1 rob

No switch at all; see former messages: bye, rob

I succedded in setup a working full-mesh; the right suggestion came from drbd-user mailing list: use bridging instaead of routing. In this post I give the details: https://lists.gt.net/drbd/users/28251#28251 bye, rob

Better a single: drbdmanage export-res "*" # the quotes are important

Yes, I mistakenly added 0.97 to my statement. 0.97 is still not in enterprise repo (right decision imho). May be 0.97.1 or 0.97.2 would be the right candidates; I will test them as soon as they will be in no-subscription repo. bye, rob

From "man drbdmanage-add-node": rob

Not a dumb question at all. You do not need hostname -> ip resolution for configuring drbd9, you provide IP of the nodes ( drbdmanage add-node -q <node-name> <ip>) . Personally i put storage network IPs in /etc/hosts only to enable reverse lookup for ssh.

Good question. 0.97.1, and also 0.97 (and of course 0.97.2) are indeed not even in no-subscription repo.

You have to put two lines in the hosts files for every hostname; one beginning with the ip for the storage network, one with the ip of the ordinary network. That's it. bye, rob

I asked about *.res files on drbd-user ml; it seems that's a fix in 0.97.1 or 0.97.2 (now in git). http://lists.linbit.com/pipermail/drbd-user/2016-August/023169.html

Same here; it is causing (for instance) unusability of drbdadm command (cannot find resource), and many resync issues. At the moment i trigger recreation of /var/lib/drbd.d/*.res files issuing a series of: drbdmanage net-options --resource <target resource> --max-buffers 8000 or similar. rob

Wrong free space calculation should be fixed in drbdmanage 0.96: http://lists.linbit.com/pipermail/drbd-user/2016-May/022937.html

Thanks on my part as well. I had the same problem with the new APU2: http://pcengines.ch/apu2b2.htm rob

I forgot: "makes sense" at drbdmanage level, not at pve, where redundancy is currently fixed and configured at cluster level.

No, drbd redundancy is not costrained as pve one. It is perfectly ok to create a resource attaching to one node only (redundancy 1), while another one may be attached to 2 nodes or more. So aggregate space as sum of storage size on various nodes makes sense. rob

Hello @mmenaz. Please note that drbdmanage reports available space correctly: #drbdmanage list-free-space 3 The maximum size for a 3x redundant volume is 46624624 kiB (Aggregate cluster storage size: 5032497152 kiB) Aggregate cluster storage is in fact correct, in your case as well, i think...

Hello, I don't want to bother you with another rant on "DRBD9 reports wrong pool free space", there is already another thread on this, and I posted my fidings on drbd-user mailing list (where I detailed also the current drbd version in my setup). I want to share here my experience with pve...