Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We use suPHP and whenever our php packages are updated, a new php.conf file is dropped into the apache config folder (/etc/httpd/conf.d) and this causes 500 error's as it configures the handler for php scripts to be the standard php interpreter (AddHandler php5-script .php) instead of suphp. When this happens we have to manually delete php.conf and restart Apache.

In addition the PHP package also changes the ownership of /var/lib/php/sessions to root:apache and we need it to be root:suphpgroup.

Any ideas on how we can avoid these two issues caused by every PHP update?

share|improve this question
up vote 1 down vote accepted

Create a blank /etc/httpd/conf.d/php.conf and leave it there. The RPM packages will not overwrite it, since it's changed from the original distributed file; instead they'll create it as php.conf.rpmnew which Apache will ignore, and you can go clean up later at your leisure.

share|improve this answer
Thanks, great solution, I should have remembered that! Any idea about the permission issue on the sessions folder? – Michelle Dec 6 '12 at 17:36
There's no great solution for that. The best idea I can come up with is to put your sessions somewhere else. – Michael Hampton Dec 6 '12 at 17:38
Thanks works for me, thanks Michael. – Michelle Dec 6 '12 at 18:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.