Recent content by discontented

Not at all. We've upgraded to the latest sw, re-keyed everything, stopped / re-started services to no avail. In the end we told our users to log into the node the vm is hosted on. We really don't have the time to fault-find.

Good afternoon, Restarting the services, restarting the Node and running pvecm updatecerts (with and without -f) has not worked. We are still having problems. Ideas?

Thanks for the reply. The system is under heavy use at the moment, I'll organise some down time for this evening and restart the services. If this doesn't work I'll restart the server, if that fails I'll try updating the certs and complete another restart. I'll get back to you tomorrow with...

Here you go Dietmar: root@engvmcltr17:~# pvecm status Version: 6.2.0 Config Version: 26 Cluster Name: NAME Cluster Id: 39860 Cluster Member: Yes Cluster Generation: 708 Membership state: Cluster-Member Nodes: 20 Expected votes: 20 Total votes: 20 Node votes: 1 Quorum: 11 Active subsystems: 5...

Hello there, we are beginning to see a strange problem that only occurred for the first time yesterday. Up until yesterday morning, any user could connect to any VM console from any Node. Yesterday afternoon, a few users started to see the error above when trying to view the console of a VM on...

Hi Dietmar, Thanks for your response. I was looking at doing something similar but I need a bit of clarification please? >Create a new PV with a much larger metadata area, add it to the VG, >then stop using the too-small metadata areas on the old PVs. >For extra resiliance it might be wise...

Won't allow me to make the change: pvchange -a --metadataignore y Cannot disable all metadata areas in volume group vmsan_vg. Cannot disable all metadata areas in volume group pve. 0 physical volumes changed / 2 physical volumes not changed

OK so having done a bit of reading this morning, I think maybe, I can change the attributes of the Physical Volume using pvchange to ignore metadata. Any ideas if this would 'fix' the problem?

Hello all, We have hit a snag on our production system :( A user attempted to create a VM this AM but got presented with the error: TASK ERROR: create failed - lvcreate 'vmsan_vg/pve-vm-380' error: VG vmsan_vg metadata too large for circular buffer Any ideas on how this can be cleared? I...

On the back of this, is there an easy way to force lvcreate to skip a number? Rob

Hi All, Have an issue with PM2.1. Been using this product for a while now, no real problems until today. A user go the following error when trying to to create a vm: Found duplicate PV 40CYdqUd2ktKfq2Yx6NuKJ7hdQYLvTeG: using /dev/sdc not /dev/sdb Found duplicate PV...

Superstar, all fixed. The first line fixed the issues a treat. Thank you.

I've updated the two nodes to what they should be, /etc/pve/.members is now displaying: "01": { "id": 1, "online": 0}, "02": { "id": 2, "online": 0}, "03": { "id": 3, "online": 0}, "04": { "id": 4, "online": 1, "ip": "192.168.8.14"}, "05": { "id": 5, "online": 0}, "07": { "id": 7...

How do we change these if the settings are incorrect? This file is read-only so I'm guessing the data is populated from another location? Also, if we are in a cluster, do we change just the one node or the file on all nodes?

Hi Dietmar, Thanks for the reply, we have pools created and assigned groups to these pools but have come across a bug where new VMs in different pools try and use the same VMID. Any idea when a fix could be released for this? On another note, any way we can change the default settings for...