This is set to: max_execution_time = 30 max_input_time = 60 This is the default and I would expect to run a simple phpinfo it would be adequate. I was playing further and now I have got rid of the "No Input File Specified" in favour of "Prohibited". I had this problem before while I was trying to resolve the situation. Makes me think that there is a configuration error somewhere that is affecting the security settings in Apache, but the directory has "Require All Granted" set on it and I'm not aware of any others. John ================================== On Monday 01 May 2017 15:08:17 Arthur E. Johnston wrote: > John > > I am not near my computer right now. > > There is a setting in PHP.ini to extend the time for each process. > > > Arthur Johnston > > Sent from my iPhone. Please excuse > The typos. > > > On May 1, 2017, at 8:24 AM, John Iliffe <john.iliffe@xxxxxxxxx> wrote: > > > > Thanks for the response Nick. > > > > I originally suspected PHP too but using mod_php most of this works. > > (It all does on the old server on Apache-2.4.10 using mod_php) I'm > > using mod_fcgid on Apache so that is why I posted here. I already > > tried the Apache download of PHP-FPM about a month back with mostly > > similar errors, even with a considerable amount of help by Daniel; so > > I gave up and went to what looked like it should be the easier path > > (mod_fcgid). As it turned out, it wasn't. > > > > The odd install locations are because I don't want to use the Fedora > > repositories to get the Apache and PHP and other software. I've been > > hit before by a non-trivial change when the software gets updated and > > something breaks. So now I maintain my own and I always have a > > back-out position. > > > > The locations for the PHP scripts are because there are several named > > virtual hosts on Apache and each one has its own subdirectory under > > /httpd. For example, the test server, and the hacker trap on the > > first named host is iliffe.ca with /httpd/iliffe as the document > > root. Both scripts and static pages related to the virtual server > > are stored in the same place. > > > > The really odd thing is that if the PHP ini file is incorrect (syntax > > error in one line) then everything works as it should. The problem > > that arises is that every page served has a line right in the middle > > of the page that says something like "syntax error in ini file on > > line #432" or similar. Certainly not acceptable for a production > > server! Note that this occurs on EVERY page served, indicating that > > a new PHP child process must have been started on every script which > > is not what I would expect from the docs on mod_fcgid. (which should > > have started a pool I would have thought). > > > > So, yes, you are correct, I may be barking up the wrong tree. The > > problem is, I'm lost in the forest! > > > > Regards, > > > > John > > ========================================= > > > >> On Monday 01 May 2017 01:54:26 Nick Kew wrote: > >> On Sun, 2017-04-30 at 14:56 -0400, John Iliffe wrote: > >> > >> I find your post confusing, so I may be barking up the > >> > >> wrong tree. But I see: > >>> Now Apache has started php-cgi, the parent process is one of the > >>> workers The response to the browser is "No input file specified" > >>> > >>> There are no errors shown in the Apache error log, nor in the > >>> php.log, nor in the php-fpm.log. > >> > >> It looks as if you're looking in the wrong place. > >> It's all working fine as far as Apache is concerned: > >> PHP has accepted a request and produced a response. > >> Your problem lies in something PHP is doing. > >> > >> Questions to consider: > >> Why the idiosyncratic install locations of httpd and php > >> in your filesystem? > >> What's the HTTP response? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|