Just updated from Plesk 10.1 to 10.3.1 and Plesk is now reporting 500 internal server error.

I've posted a note on the Plesk forum but, based on their response to another poster, I've a feeling they might say it's a result of having Atomic's PHP installed.

Here's a link to the thread on Parallels forum:
http://forum.parallels.com/showthread.p ... post454811

Has any one else had trouble with this upgrade?

Thank you.

PS My IP address 74.56.78.10 has been blocked from atomicorp.com - I have to use proxy to access
PPS Even then trying to load http://www.atomicorp.com/support/support-portal.html loads the header and footer but the main content area stays white and the loading times out. Tried Safari and Chrome.

A couple of notes
1. Parallels doesn't take responsibility for ANYTHING if there's even a hint of a non-standard package
2. Plesk (the control panel) uses its own Apache and PHP. If you upgrade PHP in general, you're upgrading for the main Apache server, not Plesk

Thank you for the tip.

How might I go about removing all traces of Atomic from my system? - as indeed now I'm concerned even if it's a Plesk problem they won't support me.

Ok I'm sorry to say it turned out Atomic's Kernel was the problem.

I rebooted with my regular Kernel and the problem went away.

All in all I think you need to check into an incompatibility with Plesk 10.3.0 / 10.3.1 and the Atomic Kernel.

Full details of my war story here:
http://forum.parallels.com/showthread.p ... post454998

Based on your post on the Parallels forums, you said Plesk was generating this error:



That is caused by a bug in Plesk. Plesk incorrectly "detects" you are running a debugger when you use a kernel (any kernel) that protects you from ptrace exploits. So, you just have to disable that protection in the ASL kernel:

https://www.atomicorp.com/wiki/index.ph ... ..._Bye.21

Its not a bug in the kernel, its a bug in Plesk so its not something we can fix. This was reported to Parallels as a bug in their product a long time ago (over a year ago), but obviously they still havent fixed it. We recommend you add your voice to that growing list of users that have asked Parallels to fix this.

As a future tip, any time we are aware of some error like this we always document it in the FAQ:

https://www.atomicorp.com/wiki/index.php/ASL_FAQ

So the first place to look is on our FAQ page, the odds are high that we have a solution already, even when its a bug in someone elses product.