Search results

Debian Bullseye has machine-id on two places, it's probably good idea to keep them in sync. When clonning servers, I do something like rm /etc/machine-id /var/lib/dbus/machine-id /usr/bin/dbus-uuidgen --ensure /bin/systemd-machine-id-setup

Sure, all hypervisors are in given group cluster with priority 1. When I want to do maintanance on some host, I just set its priority to 0. Interesting part of groups.cfg looked like this group: cluster comment Whole cluster group nodes...

Hello guys, I am reinstalling two Proxmox hypervisors to new hardware, so I need to migrate all VMs from old hypervisors. I have lowered HA priority (from 0 to 1) of given hosts and VMs started to get migrated out (as expected). Unfortunately single VM (ID 204) migration failed (unable to...

Thanks @aaron for all your answers. Yea, I understand that there is some cases where this behavior is not intended. I am currently in situation when I try to build cluster as realiable as possible. I don't mind reserving RAM and never using it, rather than unexpected VM failure because of OOM...

Hello there, yesterday one of our hypervisor crashed (actualy it was probably rebooted by watchdog) when VM had it's memory resized. I would really appreciate if you can give me some insight into VM placement algorithm, because I am still unable to completely understand how node selection...

Hi, current status probably won't show you that much. Try to search logs instead. You can start with corosync logs, where you can find information if any cluster communication link is lost. If so, there will be probably some networking issue to investigate.

Thank you very much @dylanw , it looks like deleting folders was enought to clean it up. I cannot find it anywhere else.

Sure, no problem. But I can see no traces of virt98 in corosync configurations or runtime. P virt3[root](15:20:22)-(~) -> pvecm status Cluster information ------------------- Name: virt Config Version: 21 Transport: knet Secure auth: on Quorum information...

Hello, I am struggling to remove single Proxmox node from cluster properly. I am following guide in docs https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node and it looks like node is only partially removed. Basicaly I did something like # ensured no VMs are on node...

Done - https://bugzilla.proxmox.com/show_bug.cgi?id=3037. Thanks for info.

Hello, I am trying to execute command via qemu-ga with pvesh but it's failing when I am trying to do it from remote node. Executing command with qm works fine: A ovirt9[root](14:01:56)-(~) -> qm guest exec 158 -- date { "exitcode" : 0, "exited" : 1, "out-data" : "Wed 23 Sep 2020...

Sequential restart of corosync daemons in cluster fixed the quorum issue.

Update: It happened again and it's still broken right now. History: added nodes ovirt6 -> ovirt5 disabling HA as workaround, everything was okay removed nodes ovirt97, ovirt98, ovirt99 nodes powered off, discs cleaned removed nodes from cluster ovecm delnode ovirt97 restarted corosync on 2...

Thank you for pointing out network QOS, I didn't think about that before and will definately consult that with network colleagues. Current network setup is not final, we plan upgrading to MLAG, but we are not there yet. I am currently not afraid of filling up network, but I know it can happen...

Hello there, I would like to ask for some help and guidance to debug issues, when our cluster lose corosync quorum (and reboots completely) when adding new node to cluster happened already twice on 7 node cluster (adding 4th and now with 7th node). Deployment context: every server is fresh...

So are going to extend pvecm add command to accept also API token in future? I know there is currently API method for joining, but it says "for internal use only" so I suppose there is more tasks pvecm add is doing.

Thank you very much @aaron :)

I have no idea how to achieve that.

@Usul I have run in same issue. Documentation has extra whitespace before first line, so copy&paste don't work. Thanks for pointing out your solution, it really helped. Detailed error message was in logs when restarted pvestatd. Please mark thread as Solved.

Hello and sorry for writing to solved thread, but I also run into this issue and have a question. I am using SSH-based fallback method because I can run it from my puppet module to automaticaly join new server to cluster. API-based joining requires entering root password directly into console...