Recent content by nandex

Hi, We have a cluster with 6 nodes. One of the nodes re-joined the cluster after being reinstalled updated a few days ago and when we realize that all other nodes of the cluster were updated too! Proxmox launched automatically "apt upgrade" & "apt dist-upgrade" commands, by this order at the...

Hi Iampretch, Is an upgrade. Thank you for the info about network. Finally, I detected the problem with multicast connection because when I force the unicast connection, the cluster works perfectly. Thanks for your help.

I was watching the network interface and has a INTERRUPT. How could I solve this? # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 90:b1:1c:af:43:c2 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8889403 errors:0 dropped:2745 overruns:0 frame:0...

I could make a cluster with 5 nodes but node 1 disconnected and in systemctl status pve.cluster -l said this: [dcdb] notice: members: 1/21448 Feb 17 18:44:08 cetamox-01 pmxcfs[21448]: [status] notice: members: 1/21448 Feb 17 18:44:08 cetamox-01 pmxcfs[21448]: [status] notice: node lost quorum...

- Journalctl -u corosync -u pve-cluster -b [MAIN ] Completed service synchronization, ready to provide service. Feb 17 16:34:50 cetamox-01 corosync[28546]: [TOTEM ] A new membership (192.168.3.34:33940) was formed. Members left: 2 4 5 6 Feb 17 16:34:50 cetamox-01 corosync[28546]: [TOTEM ]...

I only see this problem: ipcc_send_rec failed: Connection refused

# cat /etc/pve/.members { "nodename": "node-01", "version": 4, "cluster": { "name": "cluster", "version": 9, "nodes": 6, "quorate": 1 }, "nodelist": { "node-01": { "id": 1, "online": 1, "ip": "X.X.X.X"}, "node-02": { "id": 2, "online": 0}, "node-03": { "id": 3, "online": 0}, "node-04"...

You could: 1. Create a new VM with a Disk with the same capability or higher. This VM with Nothing 1. Start the VM 2. Press F12 and STOP the Process 3. Get your old VM Disk and copy to the New VM: # dd if=OLDVMDISK of=NewVMDISK bs=50M example: # dd if=vm-101-disk-1...

The VM Confs are in: /etc/pve/qemu-server and this is a Simbolic Link from /etc/pve/nodes/YOURNODE/qemu-server You could do: #updatedb and after that, #locate VM_ID.conf

Could you send me another photo? In your photo I can't see nothing.

I think that you could be have in your Bios: UEFI "Secure Boot" enabled and now are trying to boot with "Secure Boot" disabled, try re-enabling it in your BIOS if you have it disabled. In my case, was a problem with HP Blasde ws460c bios.

Re: Cluster crashed Again Hi debi@n, before reboot try always "pvecm updatecerts" it could be restore the cluster.

Hi All, is possible to disable a network device? Or I need to put a comment in VM.conf Thanks,

Hi, are you using your root and pass?? its the same that your system. Could you explain to us what did you try? ;)

xDDD, Thanks Tom!!! But I want to use this clusters to pass a TestVM to Production. I think that the best idea is one HACluster with all nodes(7) and differents failover domains (test & production). What do you think about this?