Search results

I am not sure if i should care that it's using 60% of a core on a 54 core/ht box, but it still seems egregious. I can try to tune it but Im nervous Ill cause it to explode with even worse usage or otherwise hobble the box (which has a few vms and lots of ct's) I have 256GB ram, and while the...

#lxc-ls -fF NAME,STATE,RAM NAME STATE RAM 100 RUNNING 0.00MB 261 RUNNING 0.00MB 270 RUNNING 0.00MB proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-12 pve-kernel-5.13: 7.1-7...

An ancient container I inherited in a /25 at location 1 with ip Q on host Z needs to be moved to location 2 on host Y and retain ip Q. We cannot move the /25, there are other hosts+vms+cts on it at 1. We can only route Q/32 to Y. The CT's software cannot be touched or reconfigured or otherwise...

This is the second server with this issue now. I mentioned it here before: https://forum.proxmox.com/threads/pct-list-not-working.59820/#post-281223 when I 'pct enter' the lxc, there's no /proc, this causes a lot of problems. It seems a customer sshing as a user then su'ing to root also saw...

A few days ago I added some sound loopback (aloop) stuff to run jitsi in a container. I put this into the lxc/673.conf lxc.apparmor.profile: unconfined lxc.cgroup.devices.allow = c 116:2 rwm lxc.cgroup.devices.allow = c 116:4 rwm lxc.cgroup.devices.allow = c 116:3 rwm lxc.cgroup.devices.allow =...

Very curious situation, which occured as well on another node of mine which I've been slowly unloading to reinstall completely, but has now happened on a more recently installed node. Mariadb crashed for some reason (it is doing this much more frequently under pve 5.3 and .4 with maria 10.2 an...

Screen users cant start screen because '/run/screen - no such directory' But /run comes up 755 - so anything that doesnt suid cant put it's pid file or create its /run directory hierarchy. How to mitigate this? /etc/init.d/screen-cleanup is supposed to create the directory properly, and used...

I've got a remote machine with remote console and want the quickest way to reinstall overtop of the old disks (losing all data, I've moved all containers elsewhere). Problem is if I dont wipe the disks, the installer barfs on rpool already existing. I am pretty sure I cant zpool export rpool...

Something is out of sync cant pct list: can't open '/sys/fs/cgroup/cpuacct/lxc/741/ns/cpuacct.stat' - No such file or directory how to fix? proxmox-ve: 5.4-2 (running kernel: 4.15.18-20-pve) pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec) pve-kernel-4.15: 5.4-8...

Had a situation where constraints from apparmor were causing problems with cpanel's dovecot. The container is NOT unpriviledged and not protected. The cpanel support guy said I need lxc.aa_profile = unconfined But from what I...

Something funky with pct enter -- this just stared happening, wasnt occuring before. Something's changed (no no packages have been updated on the container that i know of... but obviously something changed while I wasnt looking...) root@arch:/etc/pve/nodes/arch/lxc# pct enter 909 website:/# ps...

whenever i issue a pct comand I get setlogsock(): type='unix': path not available at /usr/share/perl5/PVE/SafeSyslog.pm line 38. Is there a path missing somewhere? This was after a recent upgrade to latest.

Seems LXC is susceptible to a container-escape problem. Just wondering about updates for this issue. https://seclists.org/oss-sec/2019/q1/119 At this point in time debian has no patches yet. https://security-tracker.debian.org/tracker/CVE-2019-5736

Following along hints from https://unix.stackexchange.com/questions/450308/how-to-allow-specific-proxmox-lxc-containers-to-mount-nfs-shares-on-the-network and elsewhere, I've updated /etc/apparmor.d/lxc/lxc-default-with-mounting to include simfs in the list, and then in the lxc container's...

Im using an ascii template I created (by installing a VM off the iso, then tarring up what was in the filesystem...), I've had success using it on older Pve (5.0?) or either I missed this warning or it's new on 5.2 - maybe it's ignorable. extracting archive...

Read lots of threads about grub rescue, but short of mounting a live iso to boot from (can't right now, the remote kvm is half busted), we're stuck at grub rescue> however, looking at (hd0) throught (hd7) (the max # of drives presented to bios by the JBOD controller), I can see...

I accidentally didn't pay enough attention trying to get qemu-utils on the server. TL;DR: DONT INSTALL QEMU-UTILS in 4.4 I installed pve from proxmox-ve_4.4-eb2d6f1e-2.iso # pveversion pve-manager/4.4-5/c43015a5 (running kernel: 4.4.19-1-pve) # apt-get install qemu-utils Reading package...

I see for some of my containers that var/lib/vz/private/$CTID is deleted, but the containers are operational as their mounts exist in /var/lib/vz/root. The dirs under private/ are empty (but exist). $ grep 114 /proc/mounts /var/lib/vz/private/114 /var/lib/vz/root/114 simfs rw,relatime 0 0...

Though this is already old, can't find a thread on it here. https://tech.vijayp.ca/linux-kernel-bug-delivers-corrupt-tcp-ip-data-to-mesos-kubernetes-docker-containers-4986f88f7a19

Finally figured out how to create a container on pve 4.1. (I had installed PVE4.1 on a ZFS mirror, not sure if that has anything to do with it, but I had to go and create myself another datastore, which I did as ZFS). The datastore is CTDATA: enabled, active, content = disk image,container...