When php is upgraded to php5 on CentOs, the Plesk show 403 error

[shockata]

Hi

After upgrading php to version 5,I cant access plesk any more.
Php is upgraded to 5.2.6.Websites are still online,ftp and mysql is working.

When i go to https://######.com:8443 I see only 403 error,You don't have permission to access / on this server.

If I try this : com:8443/login.php3?previous_page=index
then i see error 404: The requested URL /login.php3 was not found on this server.

OS: CentOS_v4.4-i386

Please help

Thank you

 

[dpicella]

I have the same problem... did you ever get this resolved?

 

[shockata]

NO,sorry

I have paid someone to reinstall my server and plesk.

 

[dpicella]

Yikes, that is too bad. It seems there is an easy fix for this. That seems pretty drastic, but hope all goes well. Cheers!

 

[atomicturtle]

How did you update PHP? I have a wiki page covering the process here:
http://www.atomicorp.com/wiki/index.php/PHP

 

[shockata]

Yikes, that is too bad. It seems there is an easy fix for this. That seems pretty drastic, but hope all goes well. Cheers!

I did not lose anything,i just made backup of my files and databases

 

[sergius]

Hi

After upgrading php to version 5,I cant access plesk any more.
Php is upgraded to 5.2.6.Websites are still online,ftp and mysql is working.

When i go to https://######.com:8443 I see only 403 error,You don't have permission to access / on this server.

If I try this : com:8443/login.php3?previous_page=index
then i see error 404: The requested URL /login.php3 was not found on this server.

OS: CentOS_v4.4-i386

Please help

Thank you

Hello shockata,

How did you upgrade PHP?

 

[shockata]

from atomicorp using yum update

 

[dpicella]

My websites are all up and running, it is just that I cant get plesk to respond on 8443. For some reason psa is missing from /etc/rc.d/init.d

The catastrophe happened for me after I selected php with atomic-yum updater that I put in plesk.

 

[dpicella]

I think it is just a matter of completing the reconfigure of plesk where it halted. I think it halted on one of my websites with a complaint about admin_php_values customization.

Anyway, I am sure there is a solution.

 

[snowyremy]

I have managed to reproduce this problem on two plesk control panels.

I have the following setup on both VPS

3.6 xeon cpu
512+ mb ram

plesk 8
centos 4.2
php 5.1
mysql 5
apache 2

install it, it works happily at first, come back the next day and bam plesk boots you out, can log into virtuozzo and restart the container, but this is often short lived and plesk returns to the red lollipop warning.

I check the processes Im getting kemsize, omourpages and today for the first time i also got tcprcvbuf warnings.

I go into ssh (when it lets me) and I ps aux - which produces the usual list of processes, apache usually twice as with psadm but nothing indicating any high memory or cpu usuage

but often I dont get into the terminal or get in and get 'out of memory allocation' message when I try and commit a command.

I thought this was a 5.2.6 php problem but on the newest vps i installed straight to 5.1 and the same thing happened.

I have read in one forum here http://forums.hostmysite.com/about6498.html that the httpsd should not be updated as this will cause problems with plesk. As apache runs 2 instances one for httpd and one for http
sd (plesk cp's apache instance). Now i always thought the httpsd was the secure httpd,, but then i realised ' hey i dont run ssl '. So is this the error in my ways? Was i supposed to only update the php for httpd and not for httpsd?

Now that I already have is there a way of rolling back? or is there a way I can update plesk to be compatible with php 5. I did not use the yum roll back when I updated, btw.

The tech support at my web house, easyspace, say they have other clients who are running php 5,, so this must be possible,, maybe im being dumb. My linux, ssh and other such cld skills are novice.

This has been plaguing my work's vps for 2 weeks now, websites continue to run (which further suggest this is a plesk issue), although on occassion the server does crash under the weight of the invisible memory leaks.

any clever person who can help me out I would be very pleased to hear from them.