Posts by c64wolf

  • LXC - I-MSCP 1.4.x - Debian Wheezy to Jessie

    host node /etc/pve/CTID.conf configuration for the VPS

    Code
    1. arch: i386cpulimit: 3cpuunits: 1024hostname: web.example.commemory: 2560net0: net0: name=eth0,bridge=vmbr0,gw=xx.xx.xx.xx,hwaddr=02:xx:xx:xx:xx:xx,ip=xx.xx.xx.xx/32,type=vethostype: debianrootfs: local:101/vm-101-disk-1.raw,size=500Gswap: 2560lxc.cap.drop:lxc.aa_profile: lxc-container-imscp


    lxc-container-imscp apparmor config


    Code
    1. profile lxc-container-imscp flags=(attach_disconnected,mediate_deleted) {
    2. #include <abstractions/lxc/container-base>
    3. mount,
    4. remount,
    5. umount,
    6. }

  • LXC - I-MSCP 1.4.x - Debian Wheezy to Jessie

    More information, in addition I am getting apparmor errors in /var/log/messages inside the container

    Code
    1. May 19 16:09:01 web kernel: [335147.880658] audit: type=1400 audit(1495199341.753:872): apparmor="DENIED" operation="file_lock" profile="lxc-container-imscp" pid=26284 comm="(ionclean)" family="unix" sock_type="dgram" protocol=0 addr=none
    2. May 19 16:18:32 web kernel: [335718.572511] maildrop[28079]: segfault at 0 ip (null) sp 00000000ffee6ccc error 14 in maildrop[8048000+35000]
    3. May 19 16:18:44 web kernel: [335730.707563] maildrop[28103]: segfault at 0 ip (null) sp 00000000ffabd07c error 14 in maildrop[8048000+35000]
    4. May 19 16:23:44 web kernel: [336030.869634] maildrop[29013]: segfault at 0 ip (null) sp 00000000fffa851c error 14 in maildrop[8048000+35000]
    5. May 19 16:28:44 web kernel: [336330.427211] maildrop[29946]: segfault at 0 ip (null) sp 00000000ffefca1c error 14 in maildrop[8048000+35000]
    6. May 19 16:33:44 web kernel: [336630.799952] maildrop[30916]: segfault at 0 ip (null) sp 00000000ff862b4c error 14 in maildrop[8048000+35000]
    7. May 19 16:33:44 web kernel: [336630.960986] maildrop[30920]: segfault at 0 ip (null) sp 00000000ffd3d48c error 14 in maildrop[8048000+35000]

  • LXC - I-MSCP 1.4.x - Debian Wheezy to Jessie

    I managed to upgrade the VPS to Jessie and to 1.4.3 version of i-mscp.


    I am having issues with email service. Currently it seems that I am not receiving any emails from outside and mail.log is full of this:
    May 19 17:43:44 web postfix/pipe[17219]: F072CC802EF: to=<[email protected]>, relay=maildrop, delay=101193, delays=101193/0.01/0/0.25, dsn=4.3.0, status=deferred (Command died with signal 11: "maildrop")


    and this
    May 19 17:42:39 web imapd-ssl: couriertls: /etc/imscp/imscp_services.pem: error:0906D06C:PEM routines:PEM_read_bio:no start line


    Any help? I am using postgrey plugin. As a temporary solution I will disable it now and reboot server.

  • LXC - I-MSCP 1.4.x - Debian Wheezy to Jessie

    I remember reading from Debian errata that dist-upgrading Wheezy LXC container won't work because it pulls in systemd and breaks things, but I guess it is no longer an issue (looked up the issue and found only this https://www.debian.org/release…n.html#lxc-upgrade-issues). The debian release notes state that I would need to add following to LXC container config for systemd to work in container after upgrade:



    Code
    1. lxc.autodev = 1
    2. lxc.kmsg = 0

    I guess this is true for Proxmox host too as it is running systemd and is based on Jessie.

  • Proxmox 4.2 i-MSCP inside LXC container

    Quote from Nuxwin

    @c64wolf


    There is already a thread opened for those issues. I must investigate.


    See Usage de i-MSCP dans un conteneur LXC

    Thanks for the quick reply. I saw that thread earlier and tried the VE capability trick, but it did not work. I will keep following the situation. I am in no hurry with the VPS transfer to new platform and in worst case I will continue using OpenVZ. However I would like to use i-MSCP with the LXC as I desire newer kernels than the ones provided by OpenVZ.

  • Proxmox 4.2 i-MSCP inside LXC container

    After reboot it seems that AppArmor did change the profile, but still I am getting same errors about mounting /var/log directories. I did add ro and remount to the mount options of the default-with-nesting apparmor policy and did a reboot again. Still getting this in dmesg:


    [ 651.389206] audit: type=1400 audit(1470042501.831:144): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-with-nesting" name="/var/www/virtual/website.org/logs/website.org/" pid=9264 comm="mount" flags="ro, remount, bind"


  • Proxmox 4.2 i-MSCP inside LXC container

    Tried to add a different AppArmor profile (the one with nesting enabled, it seemed to have proper mount options) to VE configuration file under /etc/pve/local/lxc/<VMID>.conf and even after reload and restart of both the AppArmor and the LXC container it seems that in dmesg there is still A DENIED error and it refers to the old profile. It is as if AppArmor somehow does not honour the configuration files or truly reload them. I will try to reboot the server next.