I was able to finally get logging working properly and use the error.log
to figure out what the heck was going on. The 500 error was getting
returned because of problems with my /etc/suphp.conf file. Once I
corrected those problems and disabled mod_php, everything worked correctly.
I think I must have enabled mod_php on the original server at some point
and not realized it would conflict with mod_suphp. Since pages were
still getting served up, I didn't realize suphp wasn't actually being used.
Thanks for the help. The problem was entirely of my own doing and
nothing mysterious at all.
Seth
On 08/02/2010 10:17 AM, Graeme Fowler wrote:
On Mon, 2010-08-02 at 08:26 -0500, Seth Galitzer wrote:
Yes I do have mod_php installed and I can easily disable it
independently of mod_suphp under debian/ubuntu. The problem is that if
I disable mod_php then mod_suphp still doesn't take over and no php
pages are served. Apache returns a 500 error.
In which case, looking at the Apache httpd error log would be a good
start.
If *nothing* is trying to process the PHP code, it will be delivered as
plain text to the browser. Something must be trying to process it, which
is why httpd is falling over.
Graeme
--
Seth Galitzer
Systems Coordinator
Computing and Information Sciences
Kansas State University
http://www.cis.ksu.edu/~sgsax
[email protected]
785-532-7790
_______________________________________________
suPHP mailing list
[email protected]
https://lists.marsching.com/mailman/listinfo/suphp
