Search results

  1. R

    dmesg apparmor issue

    @mfreudenberg The error still persists on our system but it became better. The advice was to do a complete reinstall which we didn't want to do. We can live with the error as it doesn't seem to harm anything. We are not sure it's related but we have seen a process called ionclean misbehaved in...
  2. R

    dmesg apparmor issue

    @Moyanof you can close this ticket. The problem was never apparmor. It was simply a container that misbehaved due to ionice. (PHP cleanup session) Once I disabled that service, the problem vanished and there have not been any further apparmor issues.
  3. R

    dmesg apparmor issue

    It's a bit strange, but I still seem to be getting the issues: [61428.467478] audit: type=1400 audit(1602596045.400:75): apparmor="STATUS" operation="profile_replace" info="not policy admin" error=-13 label="lxc-102_</var/lib/lxc>//&:lxc-102_<-var-lib-lxc>:unconfined" pid=21559...
  4. R

    dmesg apparmor issue

    # systemctl status apparmor.service ● apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enab Active: active (exited) since Mon 2020-10-12 20:49:15 CEST; 59min ago Docs: man:apparmor(7)...
  5. R

    dmesg apparmor issue

    Hi Moayad, The reinstall should be done on the PVE host, not the problematic LXC, right?
  6. R

    dmesg apparmor issue

    Hi there, here are some results: From the screen log: [FAILED] Failed to start Load AppArmor profiles. See 'systemctl status apparmor.service' for details. # systemctl status apparmor.service * apparmor.service - Load AppArmor profiles Loaded: loaded...
  7. R

    dmesg apparmor issue

    Thanks for your response. pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve) pve-manager: 6.2-11 (running version: 6.2-11/22fb4983) pve-kernel-5.4: 6.2-5 pve-kernel-helper: 6.2-5 pve-kernel-5.3: 6.1-6 pve-kernel-5.0: 6.0-11 pve-kernel-5.4.55-1-pve: 5.4.55-1 pve-kernel-5.4.44-2-pve...
  8. R

    dmesg apparmor issue

    /etc/pve/lxc# more 100.conf arch: amd64 cores: 4 hostname: qbit memory: 16000 mp0: /mnt/virtualb,mp=mnt/unionb,ro=0 mp1: /mnt/virtualf,mp=mnt/unionf,ro=0 mp2: /mnt/virtuald,mp=mnt/uniond,ro=0 mp3: /mnt/virtualhv,mp=mnt/unionhv,ro=0 mp4: /mnt/virtualm,mp=mnt/unionm,ro=0 mp5...
  9. R

    dmesg apparmor issue

    Hi, I'm a bit worried as I looked in dmesg and got this: 282316.641808] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [282316.642871] fwbr102i0: port 2(veth102i0) entered blocking state [282316.643784] fwbr102i0: port 2(veth102i0) entered forwarding state [282316.645844] audit...
  10. R

    lxc start doesn't work

    Is there anything that I can try or look at to make it boot up again? It's too important to re-install from a 10 day old snapshot. Even so, if I reinstall it might happen again so it would be nice if I can somehow try to find out what went wrong...
  11. R

    lxc start doesn't work

    @wolfgang or others, any feedback what might have happened? All worked fine with restarts and all previously, and then suddenly the lxc refuse to start. All zpools indicate ONLINE (working).
  12. R

    lxc start doesn't work

    lxc-start -F -f /etc/pve/lxc/100.conf --name olle --logfile /tmp/lxc.log --logpriority DEBUG lxc-start olle 20191001063142.695 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor lxc-start olle 20191001063142.695 DEBUG terminal - terminal.c:lxc_terminal_peer_default:714 -...
  13. R

    lxc start doesn't work

    @wolfgang thanks for your prompt reply. mount shows all containers are mounted. subvol-100-disk-0 doesn't start. All other containers start as they should. storage/containers/subvol-101-disk-1 on /storage/containers/subvol-101-disk-1 type zfs (rw,xattr,noacl)...
  14. R

    lxc start doesn't work

    Hi, I can't start one of the lxc's any longer. I can mount it properly via pct mount 100. # lxc-start -F -f /etc/pve/lxc/100.conf --name olle --logfile /tmp/lxc.log --logpriority TRACE lxc-start: olle: utils.c: safe_mount: 1187 No such device - Failed to mount "file" onto "/"...
  15. R

    [SOLVED] Noob question: I can't bind mount an ext4 folder to a privileged nested container

    @Stoiko Ivanov Not sure what happened, but I just rebooted the machine after I wrote the message post. It works perfectly and have ever since. This is a non-issue.
  16. R

    OpenVPN / NordVPN tunnels TUN (solved) and not resolved for LXC privileged containers

    @Stefan_R You are awesome! It all make sense, and I'll update the configuration to reflect what you suggest. My solution was indeed dirty but at least I could figure out what went wrong. Thank you so much for your expertise!!
  17. R

    OpenVPN / NordVPN tunnels TUN (solved) and not resolved for LXC privileged containers

    [SOLVED] With the ugliest solution there is. The VPN leverage iptables quite strictly. Apparently I couldn't connect to my container from a different LAN computer. My quick and dirty solution is simply to start the VPN and then type: iptables -I INPUT -j ACCEPT By doing so, the container accepts...
  18. R

    OpenVPN / NordVPN tunnels TUN (solved) and not resolved for LXC privileged containers

    The PVE firewall was/is disabled. I can access the container from the LAN when the VPN is off. When it is on, i can't connect to the container any longer. Here's the /etc/pve/lxc/100.conf at the host: root@riliprox:~# more /etc/pve/lxc/100.conf arch: amd64 cores: 4 hostname: rtorrent memory...
  19. R

    [SOLVED] Noob question: I can't bind mount an ext4 folder to a privileged nested container

    Hi, I have a privileged nested container and I am struggling to do a bind mount. For all other containers I'm bind mounting ZFS folders without issues. I can start the container without issues, but when I save things in /mnt/download ,the files are not saved in /mnt/pve/scratch/data Instead...
  20. R

    OpenVPN / NordVPN tunnels TUN (solved) and not resolved for LXC privileged containers

    The container is not reachable from the same LAN. For example if the container runs on 192.168.1.140, then I can't access it from 192.168.1.150 (same LAN, same subnet). I do not use it as a gateway for other machines in my network. So for the case where I don't want the container to act as...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!