Search results

same thing here any help would be appreciated

This thread seems to have the same issue : https://www.mail-archive.com/ceph-users@lists.ceph.com/msg47357.html

Same thing here, any feedback would be appreciated? Any ceph issue related ?

Hi, I'm running with this environment : pve-kernel-5.4: 6.4-9 pve-kernel-helper: 6.4-9 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.148-1-pve: 5.4.148-1 pve-kernel-5.4.143-1-pve: 5.4.143-1 pve-kernel-4.15: 5.4-6 pve-kernel-5.3.18-3-pve: 5.3.18-3 pve-kernel-4.15.18-18-pve: 4.15.18-44 ceph...

use persistent logging in LXC, https://forum.proxmox.com/threads/oom-kill-process-inside-lxc-memory-cgroup-out-of-memory.65106/#post-336131

Hi @fbrachere, Didi you solved your issue ? It looks like we have the same issue here

Obviously, default network conf in recent SoYouStart install for PXMX>5.2 is configured thanks to : https://www.freedesktop.org/software/systemd/man/systemd.network.html The default conf is found under /etc/systemd/network/[50-default.network] Commenting the routing part allow my interfaces conf...

Here is the interface file : # network interface settings; autogenerated auto lo iface lo inet loopback auto vmbr1 iface vmbr1 inet manual bridge_ports dummy0 bridge_stp off bridge_fd 0 auto vmbr0 iface vmbr0 inet static address A.B.C.D netmask...

Well, We didin't really know why this happened, but we recreate the interface file with correct parameters and almost everything is working. We still have an issue in routing, we have 2 default routes and we didin't succeed in identifying where the first route associated to the physical NIC is...

Hi, I've just installed a fresh proxmox 5.2.1 on SoYouStart Datacenter. I'm really surprised to have no interface file available. It's really stranged because i've already installed 4.x and 5.1.x successfully. Any advice ? regards

Hi, Could you give us some additionnal precisions on which file you modified? regards

Sadly no, I have this issue : `unable to parse config: lxc.limits.kernel.nofile = 20000` Additionnaly, the syntax is definitivelylike this : https://linuxcontainers.org/fr/lxc/manpages//man5/lxc.container.conf.5.html#lbAZ `lxc.prlimit.nofile = 20000` This one worked for me

Hi, I tried to add : `limits.kernel.nofile = 20000` in my ct_id.conf but the option seems to not be parsable. Any advice?

Thanks to zapotah on IRC : https://github.com/lxc/lxc/pull/1276

Hi, Did you kept the confs in the proxmox or only working with the lxc.conf files ? regards

Hi everyone, I'm trying to make many LXc runn together and each of thoses CT has at least 2Go of SWAP Yet during the install, the host has been set up with only 4Go of RAM and of course, many OOM killed the process that are put in SWAP CT. I would like to increase the size of the SWAP...

Hi, You could try this : https://forum.proxmox.com/threads/pve-uses-swap-while-ram-is-enough-why.20069/#post-102317 And of course swapoff command

Hi folks, I personnally have the same issue and I configured the named service inside the LXC. I changed the PID location and user /var/run.... instead of /run. From now the LXC service don't try to write in the "host" part anymore so no more need to set up apparmor.

Hy, personnly I used this procedurehttps://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Physical_server_.28or_KVM.2C_VMware.2C_XEN_or_other.29_to_Proxmox_VE_OpenVZ_Container and http://wiki.openvz.org/Physical_to_container

+1 I totally agree. Aditionnaly, when you delete some backups and recreate a new vm with the old same ID, your backup won't be significant at all. Chnaging its name and providing a little comment could be very useful