Lxc Cpanel services down.
- Thread starter fusion
- Start date
We wanted to migrate this past weekend to LXC due to requests from customers to Proxmox 4.1 But because of this we recommended to the client to rather wait until a solution is found regarding this exact issue. Luckily we have understanding clients 
So sticking to 3.4 until this is sorted or someone has some solution please?
So sticking to 3.4 until this is sorted or someone has some solution please?Hi, this is the answer to Cpanel, someone could help me with this issue thanks.
email 1:
Hello,
The first thing I notice is that your server currently in runlevel 5, or the graphical runlevel, which is not expected for a server environment.
[14:13:56 server2 root@7418255 ~]cPs# runlevel
N 5
[14:15:42 server2 root@7418255 ~]cPs#
The general recommendation is runlevel 3, and I believe this may be related to the problem. Can you please change the default runlevel to 3, or multi-user, and reboot? You can accomplish that by running these two commands:
systemctl set-default multi-user.target
shutdown -r now
You can also read more about runlevels here:
http://www.unixmen.com/change-runlevels-centos7/
http://www.itzgeek.com/how-tos/linux/centos-how-tos/change-default-runlevel-in-centos-7-rhel-7.html
email: 2
Hello,
It seems like your lxc container has something preventing cPanel from accessing certain parts of the file system, even as root. There are errors in dmesg that seem to indicate that something named AppArmor is installed and is limiting the filesystem in a way that is very similar to SELinux. Unfortunately, both of these cause the symptoms that we're seeing, which is that the services appear to be online and running without a problem, but cPanel is unable to confirm that.
Please disable any Operating-system level security that you have, so we can confirm that the services are running as intended.
Thanks,
email 1:
Hello,
The first thing I notice is that your server currently in runlevel 5, or the graphical runlevel, which is not expected for a server environment.
[14:13:56 server2 root@7418255 ~]cPs# runlevel
N 5
[14:15:42 server2 root@7418255 ~]cPs#
The general recommendation is runlevel 3, and I believe this may be related to the problem. Can you please change the default runlevel to 3, or multi-user, and reboot? You can accomplish that by running these two commands:
systemctl set-default multi-user.target
shutdown -r now
You can also read more about runlevels here:
http://www.unixmen.com/change-runlevels-centos7/
http://www.itzgeek.com/how-tos/linux/centos-how-tos/change-default-runlevel-in-centos-7-rhel-7.html
email: 2
Hello,
It seems like your lxc container has something preventing cPanel from accessing certain parts of the file system, even as root. There are errors in dmesg that seem to indicate that something named AppArmor is installed and is limiting the filesystem in a way that is very similar to SELinux. Unfortunately, both of these cause the symptoms that we're seeing, which is that the services appear to be online and running without a problem, but cPanel is unable to confirm that.
Please disable any Operating-system level security that you have, so we can confirm that the services are running as intended.
Thanks,
Hi I am having same problem my runlevel has been changed to 3 but service still fails on cpanel
how do you disable any Operating-system level security ?
i have been also advised to run centos 7 in unprivileged mode for cpanel to work properly but how do i do that in proxmox 4.1
sorry for about my lack of knowledge in this matter and thanks in advance
how do you disable any Operating-system level security ?
i have been also advised to run centos 7 in unprivileged mode for cpanel to work properly but how do i do that in proxmox 4.1
sorry for about my lack of knowledge in this matter and thanks in advance