Search results

sorry I did not try, I reverted to the native vlan to be the proxmox vlan 10.0.5.0/24 as the suggested workaround does not work at the end, sometime the enp2s interface does not go up even with the pre-up ifconfig $IFACE up. However, as documented on debian Wiki network page, using a bridge...

Hi, do you recall the changes required to the OSD ? Thanks

I could not handle it myself, so I reverted to the previous backup of /var/lib/ceph/mon/ceph-proxmox and reinjected the monmap. Regreated the mgr and mds and here are we back online.

"failed to fetch mon config (--no-mon-config to skip)" is due to the mon keyring in /var/lib/ceph/osd/ceph-5/keyring not added in the ceph auth list. I added it with "ceph auth add osd.5 osd 'allow *' mon 'allow rwx' -i /var/lib/ceph/osd/ceph-5/keyring" However, it is not giving the crush map

my crushmap is also empty from osd and rules .... this begins to smell bad The osd service that still run on non-rebooted services report healthcheck failed on the old IPs.

I also wanted to mention that creating the monitor the manual way is set as root:root user for permissions of content in /var/lib/ceph/mon/ceph-proxmox5/store.db/, whereas it is ceph:ceph when created with the GUI.

ok, I created the monitor with the manual procedure on two nodes in order to get the quorum. the proxmox interface could communicate with the ceph cluster again. I destroyed all the manager with the GUI and created them again. As well with the Metadata servers. However .... all the OSD are...

Hello, In order to change the ceph public network, I followed this : https://ceph.readthedocs.io/en/latest/rados/operations/add-or-rm-mons/ Of course, the messy way, as I had also to change the network in ceph.conf. it failed when I wanted to restart the monitors. I wanted to recreate the...

it seems to be documented here : https://wiki.debian.org/NetworkConfiguration#Bringing_up_an_interface_without_an_IP_address if there is no ip address, then the interfaces does not come up and generates the error at 'gateway' instruction ifupdown2 was installed

Hi, Thanks for the advice, I use these only for the host access and communication, not for the VMs, and migrated proxmox cluster IPs from VLAN ID1 to 5, so I maybe will revert the native vlan to ID 5. How is it better ? just so that I can remove the added workaround in the interface itself...

Hi, I wanted to report an issue I got when using only vlan interfaces. The gateway would not get up due to : "failed: returned 2 (Error: Nexthop device is not up.)" This error was due to the underlying interface not up because it does not have an IP. The workaround is to modify the physical...

Tested : on each node one by one : 1. Change IP assigned to vmbr0, add network settings for the new interface so cluster can communicate. 2. Edit /etc/pve/corosync.conf with the new ip, and increment the config_version setting 3. edit the /etc/hosts with the new ip value 4. Reboot the node 5...

Hi RobFantini, I could successfully manage to make it work, this was due to a mismatch in the zabbix template if I remember correctly. Here is my latency graph (sorry for the bad results, this is a home lab with also spinning disks)

Thanks, worked for me

I could workarounf by removing ipv6 on the bridge in sysctl.conf : net.ipv6.conf.vmbr0.disable_ipv6 = 1 When I restart networking service, it puts correctly the configured ip to the bridge interface. After some time, the vmbr0 interface takes back the main interface ip. Does anyone know if...

how much later ? :D

Hello, I've followed the network configuration like here : https://pve.proxmox.com/wiki/Network_Configuration at Masquerading with iptables for my lxc subnet It worked at first, but now it does not. Here is my config : /etc/network/interface file auto lo iface lo inet loopback auto eth0...

But this does not work unfortunately ... I did workaround by modifying the template. Any ideas ?

Sorry I did not read the banner of /etc/hosts : # Your system has configured 'manage_etc_hosts' as True. # As a result, if you wish for changes to this file to persist # then you will need to either # a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl # b.) change or...

Hi, I created a debian vm with cloud-init, everything is working fine. with the command 'qm cloudinit dump <vmid> user' I could see : manage_etc_hosts: true This settings overwrites the changes made in the /etc/hosts file, and thus breaks my applications setup. the reference of this is here...