#17614 [Com]: After a few hours, PHP scripts are returned as-is and not run

ID: 17614 Comment by: mark@nospam.gov Reported By: bmerry@cs.uct.ac.za Status: No Feedback Bug Type: Scripting Engine problem Operating System: Debian/unstable PHP Version: 4.2.1 New Comment: I show the same problem under 4.2.3, under debian (using their "unstable" packages) and the same problem under slackware 8.0.0 running a hand rolled version, nothing fancy just curl and mcrypt, gd, however I've found that if the client hits Reload in their browser the script executes instead of sending the source as-is, and the problem is solved for a while. Both machines running 1.3.27/4.2.3 Previous Comments: ------------------------------------------------------------------------ [2002-09-11 11:15:22] sniper@php.net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2002-06-13 10:00:25] sniper@php.net It does sound like an Apache problem but I wouldn't bet any money on that horse. :) You propably should submit a bug report about it to them too? (or search their database if someone else has had similar problem?) Just in case, try the latest CVS snapshot of PHP too: http://snaps.php.net/php4-latest.tar.gz ------------------------------------------------------------------------ [2002-06-06 10:56:57] bmerry@cs.uct.ac.za I've moved the php config stuff out of the <Directory> block and into the VirtualHost block, and now it seems to be working perfectly. Would that make it an Apache problem? ------------------------------------------------------------------------ [2002-06-06 05:06:26] bmerry@cs.uct.ac.za Thanks, I wasn't aware of the SIGHUP problem (and apparently neither are the Debian guys). Unfortunately stopping and starting the server again didn't work either - it worked for about 15 minutes. Worse, it seems as though after it stops working it will occasionally work again: I set up a cron job to request the page every 5 minutes and at some odd times it would suddenly work. It also worked for a while after logrotate SIGHUP'ed apache. There is also a vhost on that server that has as its DocumentRoot /home/bob/public_html, and the PHP scripts for that site seem to break as well i.e. it seems to be related to the <Directory> block rather than the vhost itself. I'm going to try shuffling some directives around e.g. moving the safe_mode from that <Directory> block into the vhost block and will let you know. ------------------------------------------------------------------------ [2002-06-05 14:15:11] sniper@php.net Instead of 'SIGHUP', why aren't you doing a full stop and start of Apache?? There is some problem with DSOs and SIGHUP (which I can't now remember what it was). apachectl stop apachectl start those only should be used when dealing with DSOs. --Jani ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/17614 -- Edit this bug report at http://bugs.php.net/?id=17614&edit=1