OpenVZ to LXC Conversion

zefie

• April 17, 2017 23:14

Proxmox recently discontinued 3.x, forcing me to migrate over to 4.x. Long story short, after converting the OpenVZ cPanel VM to LXC and re-configuring it, I booted it and all of my sites returned error 500. I looked at the apache logs and found errors like: [Tue Apr 18 04:12:11.207619 2017] [cgid:error] [pid 5454:tid ] [client :59504] End of script output before headers: redirect.cgi This error is one of the remaining errors I have, when you try to go to domain/cpanel or domain/whm. I fixed the sites by checking: /usr/local/cpanel/bin/rebuild_phpconf --current which reported all (except the default) PHP were using suphp instead of cgi. When I switched the default php to suphp, sites worked, but the redirection still does not. I believe something happened that is blocking cgi. Any ideas?

• 

  cPanelMichael

  • April 18, 2017 14:00

  Hello @zefie, Could you review our

  0
• 

  zefie

  • April 18, 2017 18:34

  Hello @zefie, Could you review our

  0
• 

  cPanelMichael

  • April 18, 2017 19:22

  Hello, We do have an internal case open (EA-5010) related to "suexec" (/usr/sbin/suexec) using file capabilities to specify setuid/setgid permissions instead of the traditional file mode bits. Could you open a support ticket using the link in my signature and reference this case number so we can verify if your system is affected by this issue? Thank you.

  0
• 

  zefie

  • April 19, 2017 02:47

  Hello, We do have an internal case open (EA-5010) related to "suexec" (/usr/sbin/suexec) using file capabilities to specify setuid/setgid permissions instead of the traditional file mode bits. Could you open a support ticket using the link in my signature and reference this case number so we can verify if your system is affected by this issue? Thank you.

  
  I am just re-rolling a new CentOS 7 VM in KVM instead of fighting with LXC. I believe AppArmor was an issue too as it was messing up named. However, I tried putting that lxc.aa_profile var in various config locations without success. Therefore I decided for the sake of fast repair, and to hopefully prevent issues in future Proxmox forced conversions/breakage, that a KVM would be better. Thanks though.

  0
• 

  cPanelMichael

  • April 19, 2017 16:05

  Hello @zefie, Let us know if you encounter any additional issues after switching to KVM. Thank you.

  0

Please sign in to leave a comment.