Search results

I take it no-one knows how to do this, or isn't prepared to share the secret? In my searching of the web I did find this article https://stackoverflow.com/questions/23065673/how-to-re-run-cloud-init-without-reboot Which seems to explain the ease with which it can actually be accomplished...

I have been playing with cloud-init support in PVE and am loving it ... however, one of the things I want to disable on certain VMS (for good or for bad, please don't lecture on security) is to enable the root user to be able to ssh into the VMs (at least while we're building them and scp'ing...

Likewise, we've started to see this error on our nodes, and we're seeing fairly poor network performance too with 4.5.18-5 and pve-manager/5.2-9/4b30e8f9 root@pve-7:~# cat /etc/network/interfaces auto lo iface lo inet loopback iface eno1 inet manual iface eno2 inet manual iface eno3 inet...

Thanks ... done

Perfect, thanks - this is just what I needed

Is there a recommended way to change the subnet which CoroSync/Proxmox uses for it's "primary" interface, without breaking the cluster or experiencing excessive downtime? For technical/design reasons, I need (want) to move the corosync traffic to a a different vlan and renumber the admin...

how / where would you like the log archives? They're currently just over 3M gzip'd

ok, using pmxcfs -l I have managed to bring up the core services again ... The problem remains however that the cluster seems to be fubar .. despite having been working fine for more than a year :(

omping -m 239.192.51.129 pve-1.fido.net pve-2.fido.net pve-3.fido.net gives pve-1.fido.net : unicast, xmt/rcv/%loss = 1087/1087/0%, min/avg/max/std-dev = 0.147/0.294/1.305/0.055 pve-1.fido.net : multicast, xmt/rcv/%loss = 1087/1087/0%, min/avg/max/std-dev = 0.172/0.323/1.303/0.059 whilst...

ceph health is ok ... corosync is on vlan603 which is basically where the Proxmox nodes live and talk to each other Starting VMs now results in a timeout (after the upgrade) TASK ERROR: start failed: command '/usr/bin/kvm -id 6026 -chardev...

Each Proxmox node is setup similarly to this auto lo iface lo inet loopback iface eno1 inet manual iface eno2 inet manual iface eno3 inet manual iface eno4 inet manual iface enp5s0f0 inet manual iface enp5s0f1 inet manual allow-vmbr0 bond0 iface bond0 inet manual ovs_bonds enp5s0f0...

Also worth noting that the VMs are alive but I can't ping the containers ... I'm wondering if this is an issue with Open vSwitch and vlans?

multicast all seems to be working and nothing has changed on the switch or router side of things in months

My German is pretty non existent so I didn't see (or understand) that thread sadly :) root@pve-1:~# gdb -batch -p $(pidof pmxcfs) -ex "thread apply all bt full" [New LWP 2436] [New LWP 2475] [New LWP 2476] [New LWP 2477] [New LWP 2576] [New LWP 3033] [Thread debugging using libthread_db...

Having upgraded to 5.1-46 (from 5.1-41) all of my VMs are no longer on the network We are using OpenvSwitch for the networking stack, which may be related? Is there a way to downgrade or any recommendations on how to fix this?

Seems to think it is running, however there are still major freezes when trying to access any of the shared directories root@pve-6:~# systemctl status corosync.service ● corosync.service - Corosync Cluster Engine Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset...

This is happening to me on the latest 5.1 release currently ... which is somewhat problematic :(

It also seems as though the corosync stuff has stopped working. Whilst a pvecm status shows all nodes and the cluster being quorate, as soon as I try and view any files (in any directory) under /etc/pve/nodes everything just grinds to a halt We have Juniper EX4200 configured as set protocols...

did you ever find a solution to this?

more debug info just in case